You know you have been coding to long when you make mistakes like the one I
did today
After taking a break, I realized I just finished my PnP Stop/Remove code for
the driver yesterday, and that if I properly shut the driver down from the
USB control Panel, the old driver properly unloads and I can load mine.
Before then I had no real PnP code in place, and could get away with simply
unplugging the device.
I guess when I unplug the device w/out shutting it down first, the PnP
managed holds onto my driver. Not sure if this is a bug in my Surprise
Removal code in my PnP Handler or by just the way Win2k Deals with
unexpected device removals.
But original crisis solved !!!
Thanks for the reply however, at the time I was getty pretty frustrated,
mostly because I used to use Windbg when it was much less reliable, and have
been really enjoying using it over the past few months.
Later
-Chris
Christopher Pane
Software Engineer
Vanteon
2851 Clover Street
Pittsford, NY 14534
Tel: (716) 248-0510 (Ext 232)
Fax: (716) 248-0537
email: xxxxx@vanteon.com
web: www.vanteon.com
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Friday, August 04, 2000 7:06 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !!!HELP !!! Windbg Issue !!!
This has nothing to do with Windbg.
Before updating your driver make sure you unload the driver. Then restart
it.
-----Original Message-----
From: Pane, Chris [mailto:xxxxx@vanteon.com mailto:xxxxx]
Sent: Friday, August 04, 2000 12:45 PM
To: NT Developers Interest List
Subject: [ntdev] !!!HELP !!! Windbg Issue !!!
Does WinDbg, and the Windows 2000 Resident debugger that boots with the
system cache driver images in any way.
I am using the latest version, came out 1-2 weeks ago (5.1.2250.3)
Here is what I am seeing
1. I build the driver
2. Copy it to the Winnt drivers dir on target
3. Turn on my device, see the correct DbgPrint statements in the WinDbg
window for my device
4. Power down my device, See the appropriate shutdown messages I expect in
the Windbg command window
5. Update my driver, add a DbgPrint statement to it for example just to see
how recent it is.
6. Copy my driver to the Winnt drivers dir
7. Turn on my device, I see the old driver but not the new one !!! Its as
if I never installed the new driver
8. Reboot the device, and new driver comes up on reboot
I never had to do this before !!, I could always have the PnP manager unload
my device (usually by simply powering it down), copy an updated version into
the driver dir, re-power and watch it load.
I even noticed that when the device is powered off, and if I delete the
device driver then power the device back on it still loads the driver.
Anyone know whats going on under the hood with 2000 and WinDbg
Thanks
Thanks
-Chris
Christopher Pane
Software Engineer
Vanteon
2851 Clover Street
Pittsford, NY 14534
Tel: (716) 248-0510 (Ext 232)
Fax: (716) 248-0537
email: xxxxx@vanteon.com
web: www.vanteon.com
—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)</mailto:xxxxx>