IFSTEST woes

I am trying to run IFSTEST on a floppy disk. Both my FSD and FastFAT fail.
The only calls made are:
IRP_MJ_CREATE
IRP_MJ_CLEANUP
IRP_MJ_CLOSE
IRP_MJ_DEVICE_CONTROL

IRP_MJ_DEVICE_CONTROL calls come with two different IOCTLS:
0x2D1080 = IOCTL_STORAGE_GET_DEVICE_NUMBER
DeviceType = FILE_DEVICE_MASS_STORAGE

and

0x560000 = IOCTL_??? - I couldn’t find this one in any of the header files
provided with the IFS kit
DeviceType = FILE_DEVICE_MODEM

Both of the IOCTLs are passed on to the underlieing floppy driver, where
they fail. Does anyone recognise this? Am I doing something wrong when
configuring the test, is my floppy drive or driver messed up, or can the
test simply not be run on a floppy drive?

Thanks in advance,
Jeremy

I resolved this issue by switching to a hard disk. Now the tests are
running. It would save me alot of time to have the source for the IFS test
suite. Is this code available to developers? How would I go about getting
it?

Thanks,
Jeremy

“Jeremy Sherrill” wrote in message
news:xxxxx@ntfsd…
> I am trying to run IFSTEST on a floppy disk. Both my FSD and FastFAT
fail.
> The only calls made are:
> IRP_MJ_CREATE
> IRP_MJ_CLEANUP
> IRP_MJ_CLOSE
> IRP_MJ_DEVICE_CONTROL
>
> IRP_MJ_DEVICE_CONTROL calls come with two different IOCTLS:
> 0x2D1080 = IOCTL_STORAGE_GET_DEVICE_NUMBER
> DeviceType = FILE_DEVICE_MASS_STORAGE
>
> and
>
> 0x560000 = IOCTL_??? - I couldn’t find this one in any of the header files
> provided with the IFS kit
> DeviceType = FILE_DEVICE_MODEM
>
> Both of the IOCTLs are passed on to the underlieing floppy driver, where
> they fail. Does anyone recognise this? Am I doing something wrong when
> configuring the test, is my floppy drive or driver messed up, or can the
> test simply not be run on a floppy drive?
>
> Thanks in advance,
> Jeremy
>
>
>