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 ?
Take a class from OSR or one of the others. Install to FAT32 and then you
only have to boot a DOS 7.1 bootable CD to go in and delete your driver. Do
NOT make your driver a boot driver and flag it to fail the boot if it fails.
At least not until it is working. This is driver pre-101. You can also use
a bootable OS CD if it is NTFS or you can buy the bootable NTFS package from
www.wininternals.com.
wrote in message news:xxxxx@windbg…
> 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 ?
>
xxxxx@uow.edu.au wrote:
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 ?
I’ve never actually had to reinstall… knock on wood keep my
fingers crossed (of course, I’m not writing a filter either
but a mini-redirector, and I’m especially not filtering my boot
volume:-))
One thing that does make life easier for me is 1394 debugging
and kdfiles That way if I’ve got a bug in the driver, I just
rebuild and reboot and the debugger pulls the new (fixed) build
during image load. Very slick.
Thanks,
Joseph
Try this: Uninstall your driver, reboot then save the current hardware
profile via Control Panel - System - Hardware - Hardware Profiles.
Choose an easily recognizable name. Next install your driver again. Each
time you boot now you should be offered a choice of hardware profiles to
boot from, one of which won’t load your driver.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joseph Galbraith
Sent: 17 August 2005 05:52
To: Kernel Debugging Interest List
Subject: Re: [windbg] system restart
xxxxx@uow.edu.au wrote:
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 ?
I’ve never actually had to reinstall… knock on wood keep my
fingers crossed (of course, I’m not writing a filter either
but a mini-redirector, and I’m especially not filtering my boot
volume:-))
One thing that does make life easier for me is 1394 debugging
and kdfiles That way if I’ve got a bug in the driver, I just
rebuild and reboot and the debugger pulls the new (fixed) build
during image load. Very slick.
Thanks,
Joseph
You are currently subscribed to windbg as: chris.thomas@hp.com
To unsubscribe send a blank email to xxxxx@lists.osr.com