Regarding IOCTL_DISK_VERIFY

NTDEV
1

Hello All,

I am facing a problem related to IOCTL_DISK_VERIFY. If we make an IRP using IoBuildDeviceIoControlRequest for IOCTL_DISK_VERIFY and set the length for VERIFY_INFORMATION equal to 1024 * 128, the status we get after IoCallDriver for IoBuildDeviceIoControlRequest is STATUS_SUCCESS but if we set the length for VERIFY_INFORMATION equal to 1024 * 256, the status we get after IoCallDriver for IoBuildDeviceIoControlRequest is STATUS_INVALID_DEVICE_REQUEST.

By status I mean the IO_STATUS_BLOCK’s status field set for IoBuildDeviceIoControlRequest

Why is the status changes if we increase the length.

Thanks

2

Hello All,

In addition to the above question I want to ask one more question. I want to find out the name of IOCTL having hex value 4D0008. Using OSR Online IOCTL Decoder, I got this:

That IOCTL decodes to:

Device: 0x4d

Function: 0x2

Access: FILE_ANY_ACCESS

Method: METHOD_BUFFERED

Can any one help me in finding the name of this IOCTL.

Thanks.

3

Try a little deduction and knowledge of the ddk header files.

0x4d is the ascii code for the letter ‘M’. Try scanning the headers
for a place where the letter ‘M’ is used to create a base Ioctl value.

To help you on your way, you might want to look in MountMgr.h.

Mark.

At 09:52 AM 5/22/2007, xxxxx@yahoo.com wrote:

Hello All,

In addition to the above question I want to ask one more question. I
want to find out the name of IOCTL having hex value 4D0008. Using
OSR Online IOCTL Decoder, I got this:

That IOCTL decodes to:

Device: 0x4d

Function: 0x2

Access: FILE_ANY_ACCESS

Method: METHOD_BUFFERED

Can any one help me in finding the name of this IOCTL.

Thanks.

4

Hello All,

Thanks for the speedy reply. The IOCTL is IOCTL_MOUNTDEV_QUERY_DEVICE_NAME.

Thanks