Replacing signed drivers during development
in [Device Drivers]
|
Prev: Reading/Writing to PCI Config Space of PLX bridge
Next: updated driver in OOBE(audit mode) no longer selected in normal mo
From: RamenWarrior on 19 Jan 2010 18:43 I have just added a certificate to my driver. Will it be possible to replace this driver manually during the development process? It will be much easier if I can just replace the file and skip the entire driver installation process. I realize I could also use F8 during the boot process, but I am hoping that my familiar method will still work.
From: 440gtx on 19 Jan 2010 19:41 > I have just added a certificate to my driver. Will it be possible to replace > this driver manually during the development process? kdfiles in windbg is a very efficient way to do this.
From: Thomas F. Divine on 19 Jan 2010 20:09 After the initial successful install, just copy the new driver binary over the old (in System32\drivers folder...) and reboot. Or, as another poster mentioned, use the WinDbg .kdfiles facility. Once you are familiar with .kdfiles you'll probably use it a lot. Goof luck! Thomas F. Divine http://www.rawether.net "RamenWarrior" <RamenWarrior(a)nospam.nospam> wrote in message news:D90C7024-BE91-464E-805C-C0A83468C81C(a)microsoft.com... > I have just added a certificate to my driver. Will it be possible to > replace > this driver manually during the development process? > > It will be much easier if I can just replace the file and skip the entire > driver installation process. > > I realize I could also use F8 during the boot process, but I am hoping > that > my familiar method will still work.
From: Alexander Grigoriev on 19 Jan 2010 23:00 I wish .kdfiles could just replace the binary in memory, without also overwriting it on a disk. This way, I would always have a safe copy on the disk. Or would allow to substitute a different file from the target system. "Thomas F. Divine" <tdivineATpcausaDOTcom> wrote in message news:3098BA57-EAF8-4581-AF7E-F89E4ECF209D(a)microsoft.com... > After the initial successful install, just copy the new driver binary over > the old (in System32\drivers folder...) and reboot. > > Or, as another poster mentioned, use the WinDbg .kdfiles facility. Once > you are familiar with .kdfiles you'll probably use it a lot. > > Goof luck! > > Thomas F. Divine > http://www.rawether.net > > > "RamenWarrior" <RamenWarrior(a)nospam.nospam> wrote in message > news:D90C7024-BE91-464E-805C-C0A83468C81C(a)microsoft.com... >> I have just added a certificate to my driver. Will it be possible to >> replace >> this driver manually during the development process? >> >> It will be much easier if I can just replace the file and skip the entire >> driver installation process. >> >> I realize I could also use F8 during the boot process, but I am hoping >> that >> my familiar method will still work. >
From: David Craig on 20 Jan 2010 00:02
After a driver crash, just F8 and use last known good. It works some of the time, otherwise use kdfiles to get another version. "Alexander Grigoriev" <alegr(a)earthlink.net> wrote in message news:OqIttUYmKHA.6096(a)TK2MSFTNGP02.phx.gbl... >I wish .kdfiles could just replace the binary in memory, without also >overwriting it on a disk. This way, I would always have a safe copy on the >disk. Or would allow to substitute a different file from the target system. > > "Thomas F. Divine" <tdivineATpcausaDOTcom> wrote in message > news:3098BA57-EAF8-4581-AF7E-F89E4ECF209D(a)microsoft.com... >> After the initial successful install, just copy the new driver binary >> over the old (in System32\drivers folder...) and reboot. >> >> Or, as another poster mentioned, use the WinDbg .kdfiles facility. Once >> you are familiar with .kdfiles you'll probably use it a lot. >> >> Goof luck! >> >> Thomas F. Divine >> http://www.rawether.net >> >> >> "RamenWarrior" <RamenWarrior(a)nospam.nospam> wrote in message >> news:D90C7024-BE91-464E-805C-C0A83468C81C(a)microsoft.com... >>> I have just added a certificate to my driver. Will it be possible to >>> replace >>> this driver manually during the development process? >>> >>> It will be much easier if I can just replace the file and skip the >>> entire >>> driver installation process. >>> >>> I realize I could also use F8 during the boot process, but I am hoping >>> that >>> my familiar method will still work. >> > > |