loading a debug version of my driver

NTFSD
1

I’ve been working primarily on a file system filter that runs on XP and now Vista workstations. Once I installed my driver with the inf file,etc I had no problem during debug sessions simply copying my driver to \windows\system32\drivers and rebooting to get to my next version loaded for testing,etc.

Now, I working on a 2003 server SP1 (released version, not the checked one) and this method is not working. My driver in release mode installs and run just fine, but when I just overwrite the driver with my debug version the new debug version does not load.

What bit of space dust in the inf file or other corner is at issue? Or is there something else going on?

TIA

Larry.

2

What is wrong with kdfiles? The target will load a new copy from your host
system and it doesn’t matter if it is a free or checked build. You may have
added a DDI that only exists in Vista or Server 2008 - look at all new code
since the last time it loaded. If you use 1394 kdfiles is very quick, but
with serial it does take a while.

wrote in message news:xxxxx@ntfsd…
> I’ve been working primarily on a file system filter that runs on XP and
> now Vista workstations. Once I installed my driver with the inf file,etc
> I had no problem during debug sessions simply copying my driver to
> \windows\system32\drivers and rebooting to get to my next version loaded
> for testing,etc.
>
> Now, I working on a 2003 server SP1 (released version, not the checked
> one) and this method is not working. My driver in release mode installs
> and run just fine, but when I just overwrite the driver with my debug
> version the new debug version does not load.
>
> What bit of space dust in the inf file or other corner is at issue? Or is
> there something else going on?
>
> TIA
>
> Larry.
>

3

> Now, I working on a 2003 server SP1 (released version, not the

checked one) and this method is not working. My driver in release
mode installs and run just fine, but when I just overwrite the
driver with my debug version the new debug version does not load.

First of all, run DEPENDS.EXE YourDrv.sys to see if there
are all imports resolved.

L.

4

> file system filter that runs on XP and

now Vista workstations.

I had no problem during debug sessions simply copying my
driver to \windows\system32\drivers and rebooting to get to my next
version loaded
Hmmm… WFP should not allow you to do that since XP.

Did you disable WFP (I had to)?

Are you positive that WFP does not restore the sys before you
reboot?

Look (from http://support.microsoft.com/kb/222193):

“This protection is triggered after WFP receives a directory change notification for a file in a protected directory. After WFP receives this notification, WFP determines which file was changed. If the file is protected, WFP looks up the file signature in a catalog file to determine if the new file is the correct version. If the file is not the correct version, WFP replaces the new file with the file from the cache folder (if it is in the cache folder) or from the installation source.”

etc.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-323865-
xxxxx@lists.osr.com] On Behalf Of xxxxx@sbcglobal.net
Sent: Saturday, May 10, 2008 1:51 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] loading a debug version of my driver

I’ve been working primarily on a file system filter that runs on XP and
now Vista workstations. Once I installed my driver with the inf
file,etc I had no problem during debug sessions simply copying my
driver to \windows\system32\drivers and rebooting to get to my next
version loaded for testing,etc.

Now, I working on a 2003 server SP1 (released version, not the checked
one) and this method is not working. My driver in release mode
installs and run just fine, but when I just overwrite the driver with
my debug version the new debug version does not load.

What bit of space dust in the inf file or other corner is at issue? Or
is there something else going on?

TIA

Larry.

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

I use four mechanisms:

  1. replace the driver using the debugger remapping interface (.kdfiles)
    which works on all systems for everything except boot load drivers,
  2. or for everything except x64 vista/w2k8, brute force copy over all
    images of the target driver (which defeats WFP.)
  3. For x64 vista/w2k8 you have to install a test signed/self signed
    driver (and possibly boot in testsigning mode)
  4. or use F8 when the system boots to turn off signed driver protection.

On Sat, May 10, 2008 at 8:20 AM, Alex Shvedov wrote:

> > file system filter that runs on XP and
> > now Vista workstations.
>
> > I had no problem during debug sessions simply copying my
> > driver to \windows\system32\drivers and rebooting to get to my next
> > version loaded
> Hmmm… WFP should not allow you to do that since XP.
>
> Did you disable WFP (I had to)?
>
> Are you positive that WFP does not restore the sys before you
> reboot?
>
> Look (from http://support.microsoft.com/kb/222193):
>
> “This protection is triggered after WFP receives a directory change
> notification for a file in a protected directory. After WFP receives this
> notification, WFP determines which file was changed. If the file is
> protected, WFP looks up the file signature in a catalog file to determine if
> the new file is the correct version. If the file is not the correct version,
> WFP replaces the new file with the file from the cache folder (if it is in
> the cache folder) or from the installation source.”
>
> etc.
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-323865-
> > xxxxx@lists.osr.com] On Behalf Of xxxxx@sbcglobal.net
> > Sent: Saturday, May 10, 2008 1:51 AM
> > To: Windows File Systems Devs Interest List
> > Subject: [ntfsd] loading a debug version of my driver
> >
> > I’ve been working primarily on a file system filter that runs on XP and
> > now Vista workstations. Once I installed my driver with the inf
> > file,etc I had no problem during debug sessions simply copying my
> > driver to \windows\system32\drivers and rebooting to get to my next
> > version loaded for testing,etc.
> >
> > Now, I working on a 2003 server SP1 (released version, not the checked
> > one) and this method is not working. My driver in release mode
> > installs and run just fine, but when I just overwrite the driver with
> > my debug version the new debug version does not load.
> >
> > What bit of space dust in the inf file or other corner is at issue? Or
> > is there something else going on?
> >
> > TIA
> >
> > Larry.
> >
> > —
> > NTFSD is sponsored by OSR
> >
> > For our schedule debugging and file system seminars
> > (including our new fs mini-filter seminar) visit:
> > http://www.osr.com/seminars
> >
> > You are currently subscribed to ntfsd as: xxxxx@comcast.net
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

–
Mark Roddy

6

> for everything except x64 vista/w2k8, brute force copy

over all images of the target driver (which defeats WFP.)

I may be wrong but I would bet that brute force did not work

for me even on 32-bit XP.

I had to use F8 or .kdfiles after actually seeing how WFP copies an old

binary (the one from the cache folder, exactly as advertised) over the new

one after I overwrite it.

Anyway.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Saturday, May 10, 2008 4:45 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] loading a debug version of my driver

I use four mechanisms:

  1. replace the driver using the debugger remapping interface (.kdfiles)
    which works on all systems for everything except boot load drivers,
  2. or for everything except x64 vista/w2k8, brute force copy over all
    images of the target driver (which defeats WFP.)
  3. For x64 vista/w2k8 you have to install a test signed/self signed
    driver (and possibly boot in testsigning mode)
  4. or use F8 when the system boots to turn off signed driver
    protection.

On Sat, May 10, 2008 at 8:20 AM, Alex Shvedov wrote:

> file system filter that runs on XP and
> now Vista workstations.

> I had no problem during debug sessions simply copying my
> driver to \windows\system32\drivers and rebooting to get to my next
> version loaded

Hmmm… WFP should not allow you to do that since XP.

Did you disable WFP (I had to)?

Are you positive that WFP does not restore the sys before you
reboot?

Look (from http://support.microsoft.com/kb/222193):

“This protection is triggered after WFP receives a directory change
notification for a file in a protected directory. After WFP receives this
notification, WFP determines which file was changed. If the file is
protected, WFP looks up the file signature in a catalog file to determine if
the new file is the correct version. If the file is not the correct version,
WFP replaces the new file with the file from the cache folder (if it is in
the cache folder) or from the installation source.”

etc.

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-323865-
> xxxxx@lists.osr.com] On Behalf Of xxxxx@sbcglobal.net
> Sent: Saturday, May 10, 2008 1:51 AM
> To: Windows File Systems Devs Interest List
> Subject: [ntfsd] loading a debug version of my driver
>
> I’ve been working primarily on a file system filter that runs on XP and
> now Vista workstations. Once I installed my driver with the inf
> file,etc I had no problem during debug sessions simply copying my
> driver to \windows\system32\drivers and rebooting to get to my next
> version loaded for testing,etc.
>
> Now, I working on a 2003 server SP1 (released version, not the checked
> one) and this method is not working. My driver in release mode
> installs and run just fine, but when I just overwrite the driver with
> my debug version the new debug version does not load.
>
> What bit of space dust in the inf file or other corner is at issue? Or
> is there something else going on?
>
> TIA
>
> Larry.
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>

> You are currently subscribed to ntfsd as: xxxxx@comcast.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

–
Mark Roddy — NTFSD is sponsored by OSR For our schedule debugging and file
system seminars (including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars You are currently subscribed to ntfsd as:
xxxxx@comcast.net To unsubscribe send a blank email to
xxxxx@lists.osr.com

7

Oh, here is the clue: I was playing with (my own instrumented

builds of) disk.sys, fat32.sys etc.; that’s why simple overwrite

did not work and F8 or .kdfiles were necessary.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alex Shvedov
Sent: Saturday, May 10, 2008 9:34 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] loading a debug version of my driver

for everything except x64 vista/w2k8, brute force copy

over all images of the target driver (which defeats WFP.)

I may be wrong but I would bet that brute force did not work

for me even on 32-bit XP.

I had to use F8 or .kdfiles after actually seeing how WFP copies an old

binary (the one from the cache folder, exactly as advertised) over the new

one after I overwrite it.

Anyway.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Saturday, May 10, 2008 4:45 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] loading a debug version of my driver

I use four mechanisms:

  1. replace the driver using the debugger remapping interface (.kdfiles)
    which works on all systems for everything except boot load drivers,
  2. or for everything except x64 vista/w2k8, brute force copy over all
    images of the target driver (which defeats WFP.)
  3. For x64 vista/w2k8 you have to install a test signed/self signed
    driver (and possibly boot in testsigning mode)
  4. or use F8 when the system boots to turn off signed driver
    protection.

On Sat, May 10, 2008 at 8:20 AM, Alex Shvedov wrote:

> file system filter that runs on XP and
> now Vista workstations.

> I had no problem during debug sessions simply copying my
> driver to \windows\system32\drivers and rebooting to get to my next
> version loaded

Hmmm… WFP should not allow you to do that since XP.

Did you disable WFP (I had to)?

Are you positive that WFP does not restore the sys before you
reboot?

Look (from http://support.microsoft.com/kb/222193):

“This protection is triggered after WFP receives a directory change
notification for a file in a protected directory. After WFP receives this
notification, WFP determines which file was changed. If the file is
protected, WFP looks up the file signature in a catalog file to determine if
the new file is the correct version. If the file is not the correct version,
WFP replaces the new file with the file from the cache folder (if it is in
the cache folder) or from the installation source.”

etc.

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-323865-
> xxxxx@lists.osr.com] On Behalf Of xxxxx@sbcglobal.net
> Sent: Saturday, May 10, 2008 1:51 AM
> To: Windows File Systems Devs Interest List
> Subject: [ntfsd] loading a debug version of my driver
>
> I’ve been working primarily on a file system filter that runs on XP and
> now Vista workstations. Once I installed my driver with the inf
> file,etc I had no problem during debug sessions simply copying my
> driver to \windows\system32\drivers and rebooting to get to my next
> version loaded for testing,etc.
>
> Now, I working on a 2003 server SP1 (released version, not the checked
> one) and this method is not working. My driver in release mode
> installs and run just fine, but when I just overwrite the driver with
> my debug version the new debug version does not load.
>
> What bit of space dust in the inf file or other corner is at issue? Or
> is there something else going on?
>
> TIA
>
> Larry.
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>

> You are currently subscribed to ntfsd as: xxxxx@comcast.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

–
Mark Roddy — NTFSD is sponsored by OSR For our schedule debugging and file
system seminars (including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars You are currently subscribed to ntfsd as:
xxxxx@comcast.net To unsubscribe send a blank email to
xxxxx@lists.osr.com

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

8

Oh no - brute force works, but you have to find all of the copies including
the ones in the cab files. It is the only way to permanently force the inbox
boot drivers out of the mix, unless you have somehow managed to get the
bootloader version of kdfiles working - I never have.

On Sat, May 10, 2008 at 9:34 PM, Alex Shvedov wrote:

> > for everything except x64 vista/w2k8, brute force copy
>
> > over all images of the target driver (which defeats WFP.)
>
> I may be wrong but I would bet that brute force did not work
>
> for me even on 32-bit XP.
>
>
>
> I had to use F8 or .kdfiles after actually seeing how WFP copies an old
>
> binary (the one from the cache folder, exactly as advertised) over the new
>
> one after I overwrite it.
>
>
>
> Anyway?
>
>
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Mark Roddy
> Sent: Saturday, May 10, 2008 4:45 PM
> To: Windows File Systems Devs Interest List
> Subject: Re: [ntfsd] loading a debug version of my driver
>
>
>
> I use four mechanisms:
>
> 1. replace the driver using the debugger remapping interface (.kdfiles)
> which works on all systems for everything except boot load drivers,
> 2. or for everything except x64 vista/w2k8, brute force copy over all
> images of the target driver (which defeats WFP.)
> 3. For x64 vista/w2k8 you have to install a test signed/self signed
> driver (and possibly boot in testsigning mode)
> 4. or use F8 when the system boots to turn off signed driver
> protection.
>
> On Sat, May 10, 2008 at 8:20 AM, Alex Shvedov
> wrote:
>
> > file system filter that runs on XP and
> > now Vista workstations.
>
> > I had no problem during debug sessions simply copying my
> > driver to \windows\system32\drivers and rebooting to get to my next
> > version loaded
>
> Hmmm… WFP should not allow you to do that since XP.
>
> Did you disable WFP (I had to)?
>
> Are you positive that WFP does not restore the sys before you
> reboot?
>
> Look (from http://support.microsoft.com/kb/222193):
>
> “This protection is triggered after WFP receives a directory change
> notification for a file in a protected directory. After WFP receives this
> notification, WFP determines which file was changed. If the file is
> protected, WFP looks up the file signature in a catalog file to determine if
> the new file is the correct version. If the file is not the correct version,
> WFP replaces the new file with the file from the cache folder (if it is in
> the cache folder) or from the installation source.”
>
> etc.
>
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-323865-
> > xxxxx@lists.osr.com] On Behalf Of xxxxx@sbcglobal.net
> > Sent: Saturday, May 10, 2008 1:51 AM
> > To: Windows File Systems Devs Interest List
> > Subject: [ntfsd] loading a debug version of my driver
> >
> > I’ve been working primarily on a file system filter that runs on XP and
> > now Vista workstations. Once I installed my driver with the inf
> > file,etc I had no problem during debug sessions simply copying my
> > driver to \windows\system32\drivers and rebooting to get to my next
> > version loaded for testing,etc.
> >
> > Now, I working on a 2003 server SP1 (released version, not the checked
> > one) and this method is not working. My driver in release mode
> > installs and run just fine, but when I just overwrite the driver with
> > my debug version the new debug version does not load.
> >
> > What bit of space dust in the inf file or other corner is at issue? Or
> > is there something else going on?
> >
> > TIA
> >
> > Larry.
> >
> > —
> > NTFSD is sponsored by OSR
> >
> > For our schedule debugging and file system seminars
> > (including our new fs mini-filter seminar) visit:
> > http://www.osr.com/seminars
> >
>
> > You are currently subscribed to ntfsd as: xxxxx@comcast.net
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> –
> Mark Roddy — NTFSD is sponsored by OSR For our schedule debugging and
> file system seminars (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars You are currently subscribed to ntfsd as:
> xxxxx@comcast.net To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

–
Mark Roddy

9

It took me a really long time, but I eventually got the bootloader/.kdfiles method to work on XP. My initial mistake was to follow
the WinDbg documentation. It talks about using $LDR and the NTLDR that comes with WinDbg, and I couldn’t get either of these to
work, but using the checked build of NTLDR did work, although even that pretty much involved begging due to things like
‘\SystemRoot\system32\drivers’ and ‘??\c:\windows\system32’ not being treated the same.

If you’re using XP, are looking for something a little more permanent, and are feeling subversive, I believe that you can change the
resources of the dll that sfp uses to determine what to protect (I think that’s sfcfiles.dll, and for that matter, I think got this
to work once, but it’s easily been five years, so that not may not be correct either.).

Oddly enough, SFP has been helping me out for the past two days, demanding that I insert the Windows Service Pack 2 CD in to a drive
letter that I no longer have and of course it doesn’t seem to be willing to allow to tell it to look elsewhere. This is the first
time in years that I’ve seen that irritating little dialog box. This time it’s because I installed a SP for a MS user mode product
that caused a bluescreen and screwed up my Office installation somehow. So I tried to install the new version of Office, which
didn’t work because the installation program is apparently ‘language neutral,’ whatever that means, and the system is telling me
that it’s an unsupported language. So then I tried to reinstall the old version of Office, which is what is giving me the SFP
dialog box, but looking at the setupapi.log indicates that the file in question is one used by…Windows Genuine Product or whatever
it is called. So, it looks like I either get debug this or reinstall everything. Either way, it looks like about three days of
work because of a ‘service pack’ that I knew not to install, because shit like always happens, but I did anyway. Not a good decision.

Cheers,

mm

Mark Roddy wrote:

Oh no - brute force works, but you have to find all of the copies
including the ones in the cab files. It is the only way to permanently
force the inbox boot drivers out of the mix, unless you have somehow
managed to get the bootloader version of kdfiles working - I never have.

On Sat, May 10, 2008 at 9:34 PM, Alex Shvedov > mailto:xxxxx> wrote:
>
> > for everything except x64 vista/w2k8, brute force copy
>
> > over all images of the target driver (which defeats WFP.)
>
> I may be wrong but I would bet that brute force did not work
>
> for me even on 32-bit XP.
>
>
>
> I had to use F8 or .kdfiles after actually seeing how WFP copies an old
>
> binary (the one from the cache folder, exactly as advertised) over
> the new
>
> one after I overwrite it.
>
>
>
> Anyway…
>
>
>
>
>
>
>
> From: xxxxx@lists.osr.com
> mailto:xxxxx
> [mailto:xxxxx@lists.osr.com
> mailto:xxxxx] *On Behalf Of *Mark Roddy
> Sent: Saturday, May 10, 2008 4:45 PM
>
> To: Windows File Systems Devs Interest List
> Subject: Re: [ntfsd] loading a debug version of my driver
>
>
>
> I use four mechanisms:
>
> 1. replace the driver using the debugger remapping interface
> (.kdfiles) which works on all systems for everything except
> boot load drivers,
> 2. or for everything except x64 vista/w2k8, brute force copy over
> all images of the target driver (which defeats WFP.)
> 3. For x64 vista/w2k8 you have to install a test signed/self
> signed driver (and possibly boot in testsigning mode)
> 4. or use F8 when the system boots to turn off signed driver
> protection.
>
> On Sat, May 10, 2008 at 8:20 AM, Alex Shvedov > mailto:xxxxx> wrote:
>
> > file system filter that runs on XP and
> > now Vista workstations.
>
> > I had no problem during debug sessions simply copying my
> > driver to \windows\system32\drivers and rebooting to get to my next
> > version loaded
>
> Hmmm… WFP should not allow you to do that since XP.
>
> Did you disable WFP (I had to)?
>
> Are you positive that WFP does not restore the sys before you
> reboot?
>
> Look (from http://support.microsoft.com/kb/222193):
>
> “This protection is triggered after WFP receives a directory change
> notification for a file in a protected directory. After WFP receives
> this notification, WFP determines which file was changed. If the
> file is protected, WFP looks up the file signature in a catalog file
> to determine if the new file is the correct version. If the file is
> not the correct version, WFP replaces the new file with the file
> from the cache folder (if it is in the cache folder) or from the
> installation source.”
>
> etc.
>
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> mailto:xxxxx [mailto:bounce-323865-
> mailto:bounce-323865-
> > xxxxx@lists.osr.com mailto:xxxxx] On Behalf Of
> xxxxx@sbcglobal.net mailto:xxxxx
> > Sent: Saturday, May 10, 2008 1:51 AM
> > To: Windows File Systems Devs Interest List
> > Subject: [ntfsd] loading a debug version of my driver
> >
> > I’ve been working primarily on a file system filter that runs on
> XP and
> > now Vista workstations. Once I installed my driver with the inf
> > file,etc I had no problem during debug sessions simply copying my
> > driver to \windows\system32\drivers and rebooting to get to my next
> > version loaded for testing,etc.
> >
> > Now, I working on a 2003 server SP1 (released version, not the
> checked
> > one) and this method is not working. My driver in release mode
> > installs and run just fine, but when I just overwrite the driver with
> > my debug version the new debug version does not load.
> >
> > What bit of space dust in the inf file or other corner is at
> issue? Or
> > is there something else going on?
> >
> > TIA
> >
> > Larry.
> >
> > —
> > NTFSD is sponsored by OSR
> >
> > For our schedule debugging and file system seminars
> > (including our new fs mini-filter seminar) visit:
> > http://www.osr.com/seminars
> >
>
> > You are currently subscribed to ntfsd as: xxxxx@comcast.net
> mailto:xxxxx
> > To unsubscribe send a blank email to
> xxxxx@lists.osr.com
> mailto:xxxxx
>
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: unknown lmsubst tag
> argument: ‘’
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
> mailto:xxxxx
>
>
>
>
> –
> Mark Roddy — NTFSD is sponsored by OSR For our schedule debugging
> and file system seminars (including our new fs mini-filter seminar)
> visit: http://www.osr.com/seminars You are currently subscribed to
> ntfsd as: xxxxx@comcast.net mailto:xxxxx To
> unsubscribe send a blank email to xxxxx@lists.osr.com
> mailto:xxxxx
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: unknown lmsubst tag
> argument: ‘’
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
> mailto:xxxxx
>
>
>
>
> –
> Mark Roddy</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:bounce-323865-></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>