why my filter driver failed after reboot?

NTFSD
1

I implemented a filter driver, start type set to 3, use
“net start servicename” can start my driver,but when I set start type to
0(load on boot),then reboot my machine, I found my driver doesn’t work. I
can use “net start servicename” to start it even the start type is 0.

my os is win2000 pro, what is the possible reason?

please help and thanks in advance!
holk

2

I implemented a filter driver, start type set to 3, use
“net start servicename” can start my driver,but when I set start type to
0(load on boot),then reboot my machine, I found my driver doesn’t work. I
can use “net start servicename” to start it even the start type is 0.

my os is win2000 pro, what is the possible reason?

please help and thanks in advance!
holk

3

You gave very vague description.
At boot time, many things (like some files,
some registry files are not available yet.
So maybe your filter tries to open
something which does not exist yet.

You have to find a way how to debug your filter
at boot time (it is possible with Soft-ICE,
I don’t know if WinDBG offers this posibility)
and then find why your driver fails.

L.

4

> At boot time, many things (like some files,

some registry files are not available yet.

More so.

The init paths of the Boot driver have NO files available, since SystemRoot is
not mounted yet.

Among the registry hives, only SYSTEM is available.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com