Hi:
I am trying to learn the process of writing a file system driver by
experimenting with the fast fat sample included in the IFS kit (build
3790.1830). I’ve successfully installed the RamDisk sample and can see its
debugging messages using WinDbg.
To get started with FastFat, I’ve added a couple of calls to KdPrint in the
DriverInit routine located in fatinit.c. I’m running virtual PC 2004, and I
believe I’ve gotten the fastfat.sys file successfully replaced in
\windows\system32\drivers, following the techniques discussed in
http://www.osronline.com/lists_archive/ntfsd/thread1732.html (once I’d
booted into safe mode, I was able to ftp the compiled .sys file).
I then restarted the Virtual PC with WinDbg connected to it. I still see my
debugging output from the RamDisk sample, but don’t see anything from
FastFat. My question is: should this driver be loaded automatically by the
system? If so, any ideas on why I don’t see any messages? If not, what
would I have to do to get the driver loaded - format a disk with the FAT
file system? I also note that KdPrint/DbgPrint can only be called from a
kernel mode driver - I’m assuming that’s what FastFat is, but I’m not 100%
certain.
Any pointers on what I should do next are greatly appreciated.
Thanks!
Ryan
Sorry - ignore this message. The output was there, it just slipped past my
eyes 
Ryan
“Ryan McFall” wrote in message news:xxxxx@ntfsd…
> Hi:
>
> I am trying to learn the process of writing a file system driver by
> experimenting with the fast fat sample included in the IFS kit (build
> 3790.1830). I’ve successfully installed the RamDisk sample and can see
> its debugging messages using WinDbg.
>
> To get started with FastFat, I’ve added a couple of calls to KdPrint in
> the DriverInit routine located in fatinit.c. I’m running virtual PC 2004,
> and I believe I’ve gotten the fastfat.sys file successfully replaced in
> \windows\system32\drivers, following the techniques discussed in
> http://www.osronline.com/lists_archive/ntfsd/thread1732.html (once I’d
> booted into safe mode, I was able to ftp the compiled .sys file).
>
> I then restarted the Virtual PC with WinDbg connected to it. I still see
> my debugging output from the RamDisk sample, but don’t see anything from
> FastFat. My question is: should this driver be loaded automatically by
> the system? If so, any ideas on why I don’t see any messages? If not,
> what would I have to do to get the driver loaded - format a disk with the
> FAT file system? I also note that KdPrint/DbgPrint can only be called
> from a kernel mode driver - I’m assuming that’s what FastFat is, but I’m
> not 100% certain.
>
> Any pointers on what I should do next are greatly appreciated.
>
> Thanks!
> Ryan
>
>