Filter DriverEntry not called in NT4

NTFSD
1

Hi,

We have a filter driver that we used to load on Auto (Start=2) with no problems on NT, 2K and XP. Now, from several reasons we decided to load it on SYSTEM_START (Start=1). The filter loads ok on 2k and XP but on NT the driver’s DriverEntry is not even called. In the event viewer I see a message from the Service Control Manager saying that the filter driver failed to load. If I load it manually afterwards it loads without a glitch. What is the problem? Are there special requirements/parameters for a filter driver to load on SYSTEM_START on NT4?

Thanks

Gilad

2

I’ve noticed that different flavors of the NT platform are more or less
strict on the format of the ‘ImagePath’ registry key, and at what time
in the boot process they are more or less strict. You may want to focus
on this.

Gilad Ben-Zeev wrote:

Hi,

We have a filter driver that we used to load on Auto (Start=2) with no
problems on NT, 2K and XP. Now, from several reasons we decided to load
it on SYSTEM_START (Start=1). The filter loads ok on 2k and XP but on NT
the driver’s DriverEntry is not even called. In the event viewer I see a
message from the Service Control Manager saying that the filter driver
failed to load. If I load it manually afterwards it loads without a
glitch. What is the problem? Are there special requirements/parameters
for a filter driver to load on SYSTEM_START on NT4?

Thanks

Gilad

–
Nick Ryan (MVP for DDK)

3

“ImagePath” can be omitted in all NT versions. In this case, the binary must be
in system32\drivers and must be named .sys

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

----- Original Message -----
From: “Nick Ryan”
Newsgroups: ntfsd
To: “File Systems Developers”
Sent: Sunday, September 07, 2003 9:06 PM
Subject: [ntfsd] Re: Filter DriverEntry not called in NT4

> I’ve noticed that different flavors of the NT platform are more or less
> strict on the format of the ‘ImagePath’ registry key, and at what time
> in the boot process they are more or less strict. You may want to focus
> on this.
>
> Gilad Ben-Zeev wrote:
>
> > Hi,
> >
> >
> >
> > We have a filter driver that we used to load on Auto (Start=2) with no
> > problems on NT, 2K and XP. Now, from several reasons we decided to load
> > it on SYSTEM_START (Start=1). The filter loads ok on 2k and XP but on NT
> > the driver?s DriverEntry is not even called. In the event viewer I see a
> > message from the Service Control Manager saying that the filter driver
> > failed to load. If I load it manually afterwards it loads without a
> > glitch. What is the problem? Are there special requirements/parameters
> > for a filter driver to load on SYSTEM_START on NT4?
> >
> >
> >
> > Thanks
> >
> >
> >
> > Gilad
> >
>
> –
> Nick Ryan (MVP for DDK)
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Thanks Max and Nick, I removed the ImagePath from the registry entry for my filter, and now the Driver entry is called. I still have problems to load on SYSTEM_START but at least I can debug now!

Thanks!

Gilad

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Sun, September 07, 2003 1:24 PM
To: File Systems Developers
Subject: [ntfsd] Re: Filter DriverEntry not called in NT4

“ImagePath” can be omitted in all NT versions. In this case, the binary must be
in system32\drivers and must be named .sys

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

----- Original Message -----
From: “Nick Ryan”
Newsgroups: ntfsd
To: “File Systems Developers”
Sent: Sunday, September 07, 2003 9:06 PM
Subject: [ntfsd] Re: Filter DriverEntry not called in NT4

> I’ve noticed that different flavors of the NT platform are more or less
> strict on the format of the ‘ImagePath’ registry key, and at what time
> in the boot process they are more or less strict. You may want to focus
> on this.
>
> Gilad Ben-Zeev wrote:
>
> > Hi,
> >
> >
> >
> > We have a filter driver that we used to load on Auto (Start=2) with no
> > problems on NT, 2K and XP. Now, from several reasons we decided to load
> > it on SYSTEM_START (Start=1). The filter loads ok on 2k and XP but on NT
> > the driver’s DriverEntry is not even called. In the event viewer I see a
> > message from the Service Control Manager saying that the filter driver
> > failed to load. If I load it manually afterwards it loads without a
> > glitch. What is the problem? Are there special requirements/parameters
> > for a filter driver to load on SYSTEM_START on NT4?
> >
> >
> >
> > Thanks
> >
> >
> >
> > Gilad
> >
>
> –
> Nick Ryan (MVP for DDK)
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

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