SpyAttachDevice in FileSpy

NTFSD
1

SpyAttachDevice()… is not work for FAT16, FAT32 at BOOT time ???
I tried the SPY_BOOT_DRIVER definition, but FAT16, FAT32 is not attached at boot time…

Each time I reboot the computer, I have to type the command at FileSpy.exe.
So I tried the SPY_BOOT_DRIVER definition. NTFS drive is attached very well at BOOT time, but NOT FAT16, FAT32.

help me…

Thanks
Ryan
b???.???????&?v?'??j?.n?Qyȩf??]?:.?˛???m??֛???zf???%y?ޞ??v˛??^r*Lzfެ?…???l??ܢ

2

Unfortunately, the SP_BOOT_DRIVER feature only works on the file system
you booted from. This is because the
IoRegisterBootDriverReinitialization callback occurs after all of the
boot time drivers are loaded. Since you didn’t boot from fat, the fat
recognizer was loaded at boot time, not the fat file system itself.

-----Original Message-----
From: Ryan Kim [mailto:xxxxx@finaldata.com]
Sent: Wednesday, January 31, 2001 4:56 AM
To: File Systems Developers
Subject: [ntfsd] SpyAttachDevice in FileSpy

SpyAttachDevice()… is not work for FAT16, FAT32 at BOOT time ???
I tried the SPY_BOOT_DRIVER definition, but FAT16, FAT32 is not
attached at boot time…

Each time I reboot the computer, I have to type the command at
FileSpy.exe.
So I tried the SPY_BOOT_DRIVER definition. NTFS drive is attached very
well at BOOT time, but NOT FAT16, FAT32.

help me…

Thanks
Ryan
b??箷????&vڵ??Wjx2’?ʵ?N???zǧu?jy???j???׮?>X???,?&

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com