Hi all - I am working on an FSD. We implement a Network Provider, a File
System Redirector, an auxilliary logging driver, and a service to interact
with our package.
We are moving to an MSI (Microsoft Installer) install for the next version
of the program. This mandates that we have different filenames for our
drivers on NT4 and Win2k (the install cannot have foo_nt.sys and foo_2k.sys
and rename to foo.sys at install time).
Now the problem – when using the new platform-specific name for our
logging driver the system is unable to successfully load our package. If I
rename the logging driver to the original name all is happy.
This seems like a no-brainer process of scouring the codebase and registry
and making sure nothing refers to the old driver name. I have done that,
many times 
Any suggestions about what the problem might be or how to ferret out the
entity that is trying to load the driver via the old name would be much
appreciated.
Kjell
**************
Kjell Swedin
Software Engineer
WRQ Inc.
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