Are you using a kernel-mode debugger? The kernel debugger has a feature
which will transfer your device driver from the development/debugger machine
to the test machine over the debug cable, every time that driver starts.
This way, you can simply delete the driver on the host machine (no file in
system32/drivers at all), or leave a reliable “known-good” copy in that
directory. Read up on the .kdfiles command; it’s a life-saver and a
time-saver.
Under normal conditions, you should never have to reinstall your system,
even while debugging nasty driver bugs. Also, you do not say that happens
when deleting the driver “does not work”, so we cannot help you diagnose
that situation. Please provide more information.
– arlie
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@uow.edu.au
Sent: Tuesday, August 16, 2005 11:52 PM
To: Kernel Debugging Interest List
Subject: SPAM-LOW: [windbg] system restart
after i make a mistake in my file system filter driver (eg access memory
that not mine etc) i get the usual blue screen, so i go to the recovery
console and delete the driver from system32/drivers and that will fix the
problem 70% of the time but the other 30% of the time that will not work so
i am forced to reinstall windows on my existing windows installation( just
the system files are reinstalled, repair reinstall ) which is rather time
consuming ~1h. is there a better way ?
You are currently subscribed to windbg as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com