I’ve had installation problems with my KMDF1.1 based drivers two or three times recently: the drivers install fine on my target machine, but fail on a machine that has never had a KMDF driver installed.
The problem in each case is because I’ve modified the .inf file incorrectly and the coinstaller fails to install (The last time was when I tried to alter it from installing a KMDF filter over a KMDF function driver to installing the filter over one of two different function drivers). I use ChkInf but, even on the .inf files that work, it complains that the coinstaller sections are not referenced so there isn’t an easy way to validate the changes - except by trying it on a clean machine.
So how can I simulate a clean installation? What services do I need to uninstall, what files to delete etc.?
All suggestions gratefully accepted.
Don
The simplest answer is to set up your test lab so you can do clean OS
installs with a minimum of hassle and wasted time. For example do a
clean install once for each OS release and ghost an image and archive
it. Re-ghost anytime you need a clean test environment.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@careful.co.uk
Sent: Tuesday, October 10, 2006 9:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to simulate a clean machine for KMDF1.1
installation?
I’ve had installation problems with my KMDF1.1 based drivers two or
three times recently: the drivers install fine on my target machine, but
fail on a machine that has never had a KMDF driver installed.
The problem in each case is because I’ve modified the .inf file
incorrectly and the coinstaller fails to install (The last time was when
I tried to alter it from installing a KMDF filter over a KMDF function
driver to installing the filter over one of two different function
drivers). I use ChkInf but, even on the .inf files that work, it
complains that the coinstaller sections are not referenced so there
isn’t an easy way to validate the changes - except by trying it on a
clean machine.
So how can I simulate a clean installation? What services do I need to
uninstall, what files to delete etc.?
All suggestions gratefully accepted.
Don
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Hello Mark
The simplest answer is to set up your test lab so you can do clean OS
installs with a minimum of hassle and wasted time. For example do a
clean install once for each OS release and ghost an image and archive
it. Re-ghost anytime you need a clean test environment.
You’re right. It is probably the simplest, although perhaps not the quickest.
I don’t really want to restore the O/S every time I want to try out my latest
tweak to an inf file that isn’t working. But if that’s the only way …
BTW. Did you mean Norton Ghost? or were you using “Ghost” as a generic term for
disk imaging and restore software? If the former, it looks as though it only
works for Win2000 and XP targets.
However, your suggestion made me think that perhaps I could do what I wanted
with system restore points. Presumably, going back to an SRP prior to the first
ever installation of a KMDF driver would remove all traces of it.
I still wish I could just uninstall it though (and be guaranteed to get rid of
all of the background stuff that the coinstaller puts on my system).
Thanks.
Don
Ghost as in the generic term. SRP would appear to be an excellent way to
get right back to where you started from. I hadn’t considered that but
it seems bloody obvious that this does exactly what we have been moaning
about for the last few years.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Ward
Sent: Tuesday, October 10, 2006 3:59 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to simulate a clean machine for KMDF1.1
installation?
Hello Mark
The simplest answer is to set up your test lab so you can do clean OS
installs with a minimum of hassle and wasted time. For example do a
clean install once for each OS release and ghost an image and archive
it. Re-ghost anytime you need a clean test environment.
You’re right. It is probably the simplest, although perhaps not the
quickest.
I don’t really want to restore the O/S every time I want to try out my
latest
tweak to an inf file that isn’t working. But if that’s the only way …
BTW. Did you mean Norton Ghost? or were you using “Ghost” as a generic
term for
disk imaging and restore software? If the former, it looks as though it
only
works for Win2000 and XP targets.
However, your suggestion made me think that perhaps I could do what I
wanted
with system restore points. Presumably, going back to an SRP prior to
the first
ever installation of a KMDF driver would remove all traces of it.
I still wish I could just uninstall it though (and be guaranteed to get
rid of
all of the background stuff that the coinstaller puts on my system).
Thanks.
Don
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer