Hi

I am debugging some driver, I build and replace its sys file in
system32\drivers.

I find that I should reboot Windows to see new debug messages. If I remove and
add this device, or disable then enable it, I cannot see new debug messages.

Is there any way or tool to clean driver process, I have seen other driver
which
do not need to reboot Windows, what's the root cause ?

Thank you .

Re: How to kill driver process ? by Tim

Tim
Thu Mar 20 23:22:08 CDT 2008

Kid <Kid@discussions.microsoft.com> wrote:
>
>I am debugging some driver, I build and replace its sys file in
>system32\drivers.
>
>I find that I should reboot Windows to see new debug messages. If I remove and
> add this device, or disable then enable it, I cannot see new debug messages.
>
>Is there any way or tool to clean driver process, I have seen other driver
>which do not need to reboot Windows, what's the root cause ?

What kind of driver? As long as you have a DriverUnload routine, your
driver shoul be unloaded when disabled, so the next load gets the new copy.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

Re: How to kill driver process ? by Ben

Ben
Fri Mar 21 09:11:59 CDT 2008

Kid wrote:
> Hi
>
> I am debugging some driver, I build and replace its sys file in
> system32\drivers.
>
> I find that I should reboot Windows to see new debug messages. If I
> remove and add this device, or disable then enable it, I cannot see
> new debug messages.
>
> Is there any way or tool to clean driver process, I have seen other
> driver which
> do not need to reboot Windows, what's the root cause ?

A driver isn't a process, there isn't any memory isolation which would allow
you to force unload it. You have to design the driver to detach itself so
it can be unloaded.

>
> Thank you .