Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Vista Drivers > PsRemoveLoadImageNotifyRoutine??

Reply
Thread Tools Display Modes

PsRemoveLoadImageNotifyRoutine??

 
 
Gian-Luca
Guest
Posts: n/a

 
      06-09-2005
With Win2k I can use PsSetLoadImageNotifyRoutine but there is no link to the
PsRemoveLoadImageNotifyRoutine.
But if I use the first I also HAVE to use the second in order to avoid a
BSOD when i dischard the driver.

What I can do in order to use the PsSetLoadImageNotifyRoutine and avoid a
blue screen?


 
Reply With Quote
 
 
 
 
Don Burn
Guest
Posts: n/a

 
      06-09-2005
With Win2k you should not have an Unload routine in a driver with
PsSetLoadImageNotifyRoutine.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply


"Gian-Luca" <> wrote in message
news:740ADE47-87AA-4FF9-BC1A-...
> With Win2k I can use PsSetLoadImageNotifyRoutine but there is no link to
> the
> PsRemoveLoadImageNotifyRoutine.
> But if I use the first I also HAVE to use the second in order to avoid a
> BSOD when i dischard the driver.
>
> What I can do in order to use the PsSetLoadImageNotifyRoutine and avoid a
> blue screen?
>
>



 
Reply With Quote
 
Gian-Luca
Guest
Posts: n/a

 
      06-10-2005
You're telling me that if I use PsSetLoadImageNotifyRoutine on Loading my
driver, I've not to use the PsRemoveLoadImageNotifyRoutine to remove the
call back when I discard my driver? (the driver can be loaded and then
unloaded from system more time, it should not be resident)
I've attempt to do this, but after the driver is unloaded from Windows and I
launch an application, the sytem give me a beautiful Blue screen.
It seems that the kernel try to load the callback even if The code was
discarded from memory!! so wath I can do?

Thank's Don

"Don Burn" wrote:

> With Win2k you should not have an Unload routine in a driver with
> PsSetLoadImageNotifyRoutine.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
> "Gian-Luca" <> wrote in message
> news:740ADE47-87AA-4FF9-BC1A-...
> > With Win2k I can use PsSetLoadImageNotifyRoutine but there is no link to
> > the
> > PsRemoveLoadImageNotifyRoutine.
> > But if I use the first I also HAVE to use the second in order to avoid a
> > BSOD when i dischard the driver.
> >
> > What I can do in order to use the PsSetLoadImageNotifyRoutine and avoid a
> > blue screen?
> >
> >

>
>
>

 
Reply With Quote
 
Don Burn
Guest
Posts: n/a

 
      06-10-2005
Not on Win2K, it doesn't work correctly, which is wasn't provided. For
Win2K you have to accept the fact that your driver will stay resident for
once loaded.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply




"Gian-Luca" <> wrote in message
news:47222558-5028-4A62-839D-...
> You're telling me that if I use PsSetLoadImageNotifyRoutine on Loading my
> driver, I've not to use the PsRemoveLoadImageNotifyRoutine to remove the
> call back when I discard my driver? (the driver can be loaded and then
> unloaded from system more time, it should not be resident)
> I've attempt to do this, but after the driver is unloaded from Windows and
> I
> launch an application, the sytem give me a beautiful Blue screen.
> It seems that the kernel try to load the callback even if The code was
> discarded from memory!! so wath I can do?
>
> Thank's Don
>
> "Don Burn" wrote:
>
>> With Win2k you should not have an Unload routine in a driver with
>> PsSetLoadImageNotifyRoutine.
>>
>>
>> --
>> Don Burn (MVP, Windows DDK)
>> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> Remove StopSpam from the email to reply
>>
>>
>> "Gian-Luca" <> wrote in message
>> news:740ADE47-87AA-4FF9-BC1A-...
>> > With Win2k I can use PsSetLoadImageNotifyRoutine but there is no link
>> > to
>> > the
>> > PsRemoveLoadImageNotifyRoutine.
>> > But if I use the first I also HAVE to use the second in order to avoid
>> > a
>> > BSOD when i dischard the driver.
>> >
>> > What I can do in order to use the PsSetLoadImageNotifyRoutine and avoid
>> > a
>> > blue screen?
>> >
>> >

>>
>>
>>



 
Reply With Quote
 
Maxim S. Shatskih
Guest
Posts: n/a

 
      06-10-2005
The driver which uses PsSetLoadImageNotifyRoutine cannot be resident.
Sorry. It cannot be unloaded without BSODs.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

"Gian-Luca" <> wrote in message
news:47222558-5028-4A62-839D-...
> You're telling me that if I use PsSetLoadImageNotifyRoutine on Loading my
> driver, I've not to use the PsRemoveLoadImageNotifyRoutine to remove the
> call back when I discard my driver? (the driver can be loaded and then
> unloaded from system more time, it should not be resident)
> I've attempt to do this, but after the driver is unloaded from Windows and I
> launch an application, the sytem give me a beautiful Blue screen.
> It seems that the kernel try to load the callback even if The code was
> discarded from memory!! so wath I can do?
>
> Thank's Don
>
> "Don Burn" wrote:
>
> > With Win2k you should not have an Unload routine in a driver with
> > PsSetLoadImageNotifyRoutine.
> >
> >
> > --
> > Don Burn (MVP, Windows DDK)
> > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > Remove StopSpam from the email to reply
> >
> >
> > "Gian-Luca" <> wrote in message
> > news:740ADE47-87AA-4FF9-BC1A-...
> > > With Win2k I can use PsSetLoadImageNotifyRoutine but there is no link to
> > > the
> > > PsRemoveLoadImageNotifyRoutine.
> > > But if I use the first I also HAVE to use the second in order to avoid a
> > > BSOD when i dischard the driver.
> > >
> > > What I can do in order to use the PsSetLoadImageNotifyRoutine and avoid a
> > > blue screen?
> > >
> > >

> >
> >
> >



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off




1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59