I've been experimenting with USB driver development for a few months now,
including "from-scratch" and using existing off-the-shelf drivers and tools.
I'd like to completely purge my system of all accumulated junk related to
these experiments.

I figure I could do it as follows:
1) Browse the registry and remove all folders and symbolic links that
contain my vendor and product ID?.
2) Search for and delete all .sys and .inf files that are specific to my
driver.

Is this the proper approach?
Other suggestions?

Thanks in advance for the help,
Dennis

Re: Purging System of Driver Junk by Don

Don
Fri Sep 17 13:27:05 CDT 2004

Here is my standard answer to this question.

Removing all traces of a driver from a system

When testing a device install developers want to cleanup the system so
they can try reinstalling the device, unfortunately this is something
Microsoft hasn't provided an easy way to do. The steps needed are:

1. Delete the files copied by the INF from the system.

2. Delete the INF and corresponding PNF files for the device, from the
inf directory off of the system root. Note, this file is named OEM*.INF and
OEM*.PNF if your driver is not signed. Searching the OEM*.INF files for
your device identifier will determine the OEM* name of your inf file.

3. If your device has a unique class, delete the registry entry in
HLKM\System\CurrentControlSet\Control\Class corresponding to the device
class you created for device. Note the key is named for the GUID of the
class.

4. If your device has a CoInstaller, delete the registry entry in
HLKM\System\CurrentControlSet\Control\CoDeviceInstallers corresponding to
the device class you created for device. Note the key is named for the GUID
of the class.

5. Delete the registry entries in HLKM\System\CurrentControlSet\Enum
corresponding to the device you specified in the inf file. For PCI devices
this is under the PCI key, for legacy devices this is under the Root key.
Note: if you specify more than one device in the inf, you will have an entry
for each device type the system has seen. DELETING THIS KEY REQUIRES
CHANGING ITS SECURITY FIRST.

6. Delete the registry entry in
HLKM\System\CurrentControlSet\Services corresponding to the driver you
specified in the inf file. Note this is the standard cleanup one would have
done in the pre-PNP days.

7. Reboot the system, now that was easy and intuitive wasn't it.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply


"Dennis Burns" <dburns@rtessentials.com> wrote in message
news:e3a9iuNnEHA.4004@TK2MSFTNGP10.phx.gbl...
> I've been experimenting with USB driver development for a few months now,
> including "from-scratch" and using existing off-the-shelf drivers and
tools.
> I'd like to completely purge my system of all accumulated junk related to
> these experiments.
>
> I figure I could do it as follows:
> 1) Browse the registry and remove all folders and symbolic links that
> contain my vendor and product ID?.
> 2) Search for and delete all .sys and .inf files that are specific to my
> driver.
>
> Is this the proper approach?
> Other suggestions?
>
> Thanks in advance for the help,
> Dennis
>
>



Re: Purging System of Driver Junk by Dennis

Dennis
Fri Sep 17 13:45:51 CDT 2004

Hi Don,
Thanks for the excellent and thorough reply!
Dennis


"Don Burn" <burn@stopspam.acm.org> wrote in message
news:10kmb4ssggo4047@corp.supernews.com...
> Here is my standard answer to this question.
>
> Removing all traces of a driver from a system
>
> When testing a device install developers want to cleanup the system
so
> they can try reinstalling the device, unfortunately this is something
> Microsoft hasn't provided an easy way to do. The steps needed are:
>
> 1. Delete the files copied by the INF from the system.
>
> 2. Delete the INF and corresponding PNF files for the device, from
the
> inf directory off of the system root. Note, this file is named OEM*.INF
and
> OEM*.PNF if your driver is not signed. Searching the OEM*.INF files for
> your device identifier will determine the OEM* name of your inf file.
>
> 3. If your device has a unique class, delete the registry entry in
> HLKM\System\CurrentControlSet\Control\Class corresponding to the device
> class you created for device. Note the key is named for the GUID of the
> class.
>
> 4. If your device has a CoInstaller, delete the registry entry in
> HLKM\System\CurrentControlSet\Control\CoDeviceInstallers corresponding to
> the device class you created for device. Note the key is named for the
GUID
> of the class.
>
> 5. Delete the registry entries in
HLKM\System\CurrentControlSet\Enum
> corresponding to the device you specified in the inf file. For PCI
devices
> this is under the PCI key, for legacy devices this is under the Root key.
> Note: if you specify more than one device in the inf, you will have an
entry
> for each device type the system has seen. DELETING THIS KEY REQUIRES
> CHANGING ITS SECURITY FIRST.
>
> 6. Delete the registry entry in
> HLKM\System\CurrentControlSet\Services corresponding to the driver you
> specified in the inf file. Note this is the standard cleanup one would
have
> done in the pre-PNP days.
>
> 7. Reboot the system, now that was easy and intuitive wasn't it.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
> "Dennis Burns" <dburns@rtessentials.com> wrote in message
> news:e3a9iuNnEHA.4004@TK2MSFTNGP10.phx.gbl...
> > I've been experimenting with USB driver development for a few months
now,
> > including "from-scratch" and using existing off-the-shelf drivers and
> tools.
> > I'd like to completely purge my system of all accumulated junk related
to
> > these experiments.
> >
> > I figure I could do it as follows:
> > 1) Browse the registry and remove all folders and symbolic links that
> > contain my vendor and product ID?.
> > 2) Search for and delete all .sys and .inf files that are specific to my
> > driver.
> >
> > Is this the proper approach?
> > Other suggestions?
> >
> > Thanks in advance for the help,
> > Dennis
> >
> >
>
>



Re: Purging System of Driver Junk by Guillaume

Guillaume
Fri Sep 17 14:24:58 CDT 2004

> 7. Reboot the system, now that was easy and intuitive wasn't it.

LOL.

Re: Purging System of Driver Junk by Don

Don
Fri Sep 17 14:47:08 CDT 2004

Well the last line was sarcastic, but I know of many folks who have followed
the directions successfully. The alternative is to reload the system
everytime (rather long between debugs), ghost or similar image copies
(quicker, but costs for the program, and is still not fast).


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"Guillaume" <youbet@rideabike.biz> wrote in message
news:u5wrGwOnEHA.592@TK2MSFTNGP11.phx.gbl...
> > 7. Reboot the system, now that was easy and intuitive wasn't it.
>
> LOL.



Re: Purging System of Driver Junk by David

David
Fri Sep 17 15:32:26 CDT 2004

It is rather fast for a small test system, but not for a production system.
Today with all the patches required before you can put a system on the
internet, it becomes problematic to use Ghost. However, I do it that way
just because Microsoft won't provide a real uninstall. Some vendors do
provide one that can clean up to varying degrees. I have written logic such
as you described to back out an install. However, you also need to test
with a clean install to make sure you haven't messed something up that just
lets it work, but fails on a clean system.

"Don Burn" <burn@stopspam.acm.org> wrote in message
news:10kmfqveascd6a1@corp.supernews.com...
> Well the last line was sarcastic, but I know of many folks who have
> followed
> the directions successfully. The alternative is to reload the system
> everytime (rather long between debugs), ghost or similar image copies
> (quicker, but costs for the program, and is still not fast).
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> "Guillaume" <youbet@rideabike.biz> wrote in message
> news:u5wrGwOnEHA.592@TK2MSFTNGP11.phx.gbl...
>> > 7. Reboot the system, now that was easy and intuitive wasn't
>> > it.
>>
>> LOL.
>
>



Re: Purging System of Driver Junk by Alexander

Alexander
Fri Sep 17 22:51:52 CDT 2004

You can roll back to a system checkpoint. Don't know if it will delete the
driver files, but deleting them manually is not a big deal.

"Don Burn" <burn@stopspam.acm.org> wrote in message
news:10kmfqveascd6a1@corp.supernews.com...
> Well the last line was sarcastic, but I know of many folks who have
> followed
> the directions successfully. The alternative is to reload the system
> everytime (rather long between debugs), ghost or similar image copies
> (quicker, but costs for the program, and is still not fast).
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> "Guillaume" <youbet@rideabike.biz> wrote in message
> news:u5wrGwOnEHA.592@TK2MSFTNGP11.phx.gbl...
>> > 7. Reboot the system, now that was easy and intuitive wasn't
>> > it.
>>
>> LOL.
>
>



Re: Purging System of Driver Junk by Robby

Robby
Mon Sep 20 18:37:14 CDT 2004

> "Don Burn" <burn@stopspam.acm.org> wrote in message
> news:10kmfqveascd6a1@corp.supernews.com...
> > everytime (rather long between debugs), ghost or similar image copies
> > (quicker, but costs for the program, and is still not fast).


Unless using g4u or "ghost for unix" which I think will image nearly any
drive format. It runs on a floppy and needs an FTP server for storing
images.





Re: Purging System of Driver Junk by Robby

Robby
Mon Sep 20 18:42:43 CDT 2004


"Robby Tanner" <rtanner@lightsource.ca> wrote in message
news:%23e91Ar2nEHA.4056@TK2MSFTNGP09.phx.gbl...
> > "Don Burn" <burn@stopspam.acm.org> wrote in message
> > news:10kmfqveascd6a1@corp.supernews.com...
> > > everytime (rather long between debugs), ghost or similar image copies
> > > (quicker, but costs for the program, and is still not fast).
>
>
> Unless using g4u or "ghost for unix" which I think will image nearly any
> drive format. It runs on a floppy and needs an FTP server for storing
> images.

I meant with respect to the "but costs" part of Don's post. I really have
no idea how quickly it performs.

Rob



Re: Purging System of Driver Junk by Mark

Mark
Mon Sep 20 19:08:14 CDT 2004

In article <#X7FFu2nEHA.2388@TK2MSFTNGP10.phx.gbl>,
rtanner@lightsource.ca says...
>
> "Robby Tanner" <rtanner@lightsource.ca> wrote in message
> news:%23e91Ar2nEHA.4056@TK2MSFTNGP09.phx.gbl...
> > > "Don Burn" <burn@stopspam.acm.org> wrote in message
> > > news:10kmfqveascd6a1@corp.supernews.com...
> > > > everytime (rather long between debugs), ghost or similar image copies
> > > > (quicker, but costs for the program, and is still not fast).
> >
> >
> > Unless using g4u or "ghost for unix" which I think will image nearly any
> > drive format. It runs on a floppy and needs an FTP server for storing
> > images.
>
> I meant with respect to the "but costs" part of Don's post. I really have
> no idea how quickly it performs.
>
> Rob
>
>
>
ghost is a reasonable one-time cost and as long as you keep your boot
partitions under 10G or so, is quick enough to be considered painless.


--

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
markr@hollistech.com

Re: Purging System of Driver Junk by Robby

Robby
Tue Sep 21 13:19:12 CDT 2004

FYI, a comany I worked for used a FAT12 partition on the local hard drive
to store the image. That way, each machine had it's image locally that
could not be tampered with easily. The FAT12 driver was on a floppy used to
restore the image. It was all a matter of sliding the disk in and
rebooting. Pretty painless.

Rob

> ghost is a reasonable one-time cost and as long as you keep your boot
> partitions under 10G or so, is quick enough to be considered painless.
>