Fast way to remove all from device manager/ENUM key (Win9x/ME ONLY)

[PardeGT]

Will the delete enum trick work if you are going to use a different motherboard upon reinstall? Probably a whole different setup - mobo, cpu and ram.

I know it would be better to do a clean install but a friend in another state asked me and doesn't really want to try and move/rebuild all his files etc but wants to update his pentium 200mmx.

Is it worth a try?

Thanks

[glc]

Yes, this is exactly where you want to use this procedure as long as it's Win9x/ME.

[PardeGT]

Thanks glc. I told someone in a different forum to use this trick when doing so. Another member responded and said they had had several problems doing such and it only really works correctly when replacing with the exact same motherboard. I'm glad to hear otherwise.

[bdunn]

If you are hesitatnt about removing the enum key export it first so you have a backup. Worst case and the new system fails you can boot back in safemode and import it back in using regedit.

[Carl Price]

Originally posted by bdunn If you are hesitatnt about removing the enum key export it first so you have a backup. Worst case and the new system fails you can boot back in safemode and import it back in using regedit.

No need for that! Just boot to dos and restore a previous registry.

[Rancher]

Originally posted by puggs With 2000/XP, just use hardware control panel and choose Uninstall Hardware. When it gives a list of devices, click show hidden and then you can remove the ones for those parts that you no longer have in your system.

I ain't got no "hardware control panel" in my xp dude! can ya try & clear this up a bit? Add/remove software or Add Hardware is all i got & there ain't no hidden option

[bdunn]

Originally posted by Carl Price No need for that! Just boot to dos and restore a previous registry.

That works well in WinME and Win98 but in 95 there isnt always a backup registry to import.

[Jaak]

Hi folks

the enum trick does work.

but...
when motherboard is way different

one can avoid trouble by also manually deleting VMM32.vxd

this is a compilation of drivers setup creates at first setup, and subsequent setups / hardware changes will only add drivers into subdirs.
this means that the machine specific drivers can be awful wrong, even when enum (hardware key) is deleted from registry.
(or when an option switch to acomplish same is used)

another consideration
the INF folder.
this contains lots of hardware info.
if the drive migrates to another machine, there can be driver install problems.

One can copy (its rare, but sometimes one does better to move it) content of this folder

Kind regards, Jaak

[Hpro]

No it will make your computer unusable - and you need to setup windows again..
VMM32 is a critical Windows File you should not delete it and if you do read my line above...

The frist Setup for Win9X is named SYSTEM.1st and it found the root folder on your computer .!

[Jaak]

Hi

I know that deleting VMM32.vxd makes your computer unusable, but having wrong hardware drivers in this compiled driver (which is what it is) can make it unusable too.

so, in the case of a migrated hard drive, (other type Mobo, CPU) this is when you can remove it, because a dirty setup does not replace it, see.. (something to do with machine.inf and such as well, if I have that right...)

Hmmm, I had not thought about system.1st
what's it exactly hold/DO?
(i just looked in mine, looks like it has data on registry keys)

if there is one thing one should absolutely do before migrating drive, or replacing/upgrading mobo in an existing system, is make backups of all crucial data and such things as email / adressbooks, favourites, ISP settings...

[Hpro]

Deleting the enum key all of it - will let windows think that it has a new computer - so it will redetect all the hardware and there will be no dirty hardwae and windows will install all the DEFAULT drivers for it - all in all it is like a new installation without the program section - everything else will be left in place and all your third party programs will still work as the motherboard never had been changed at all.

As for System.1st - it's the first hardware and also machine detection of your Windows setup - this is only the SYSTEM.DAT - no USER.DAT (Rgeistry) so if renaming that to the accurate name then if would be like after the first restart of the computer while setup windows..
Just to make it clear - Windows Registry consist 4 files not two as many think - and each day those 4 files will also be backed up automatically and they are..
1.System.Dat
2.User.Dat
3.System.Ini
4Win.Ini

Either one of them or Vmm32 is missing and you are in for reinstall..
Hth

[topnode]

Is this sure to work like a charm in ME too?

[HAL9000]

Yup

[Charger]

Another Enum success story! Man does it feel good to see all of your existing programs still there after a complete overhaul.

[mike breck]

The "Inf" folder

Regarding Jaak's comments about the Inf folder.

I have read suggestions from quite a few sources now that prior to deleting the Enum key, it is a good idea to remove as many drivers as possible and then boot into Safe Mode and delete the Inf\Other folder (C:\Windows\Inf\Other).

This is purported to minimise any possible driver conflicts on the new system.

It makes sense to me as removing the .inf file for old graphics cards is recommended procedure.

However, I do accept that no one on PC Mech has yet reported problems after using ENUM that might or seems to be related to driver conflicts.

Having said that, it does no harm to report other people's views and method's of using the Enum key trick - and it may be something to keep in mind if unexplicable conflicts occur - particularly if you are using different Hardware on the new system.

[Carl Price]

This trick has again saved my a$$. This morning I had a machine in the shop that had a flagged scsi controller. This machine had a Jaz drive, a cdrom reader, a cdrom writer and a 4.2 gig harddrive attached to this card and it had conflicts. I deleted enum and reinstalled the drivers. It still had conflicts. I deleted enum again and removed all the extra cards (modem, SCSI, sound, etc.) leaving nothing but the video card. I let it find everything again and quit asking for reboots. After installing the video driver, I replaced the cards one at a time and added the drivers. This worked out all the conflicts. The point is deleting the enum key leaves you with a clean sheet. You just have to replace the drivers as if it was a clean install.

[HAL9000]

I agree Carl. I've been using that little trick in my shop for some time now and it saves a lot of time and hassle.

[glc]

I have discovered a way to do something similar to this for Windows 2000, I'll start a new thread.

[bell_kicks]

How do you actually get a comand prompt when booting from cold into windows but not actually going into windows itself and doing ENUM before going into windows???????

[reboot]

You can't. You have to be in windows to run regedit to delete the key...well there is a way to edit the reg in DOS, but I've purposely forgotten it because of WAY too much user error.
If you've already done the hardware install/change, and didn't delete the enum key first, then boot to SAFE MODE on your FIRST boot, delete the enum key, and THEN restart normally. It has the same effect as the original procedure.
I have actually used this on MANY win9x machines with hardware being fussy, especially in Win95. Deleting the ENUM key forces a new detection of all hardware, and completely rewrites the VMM32 file anyhow. A great way to resolve IRQ conflicts.

[Jp1095]

For this trick do you kill all the folders under enum or just the files in enum, I only see one file, but there are about a thousand folders.

[glc]

You kill the entire ENUM key - highlight it in the left pane and hit Delete.

[ghost_of_war]

OK, let me just get this all straight before I go do something rash and hate all of you and myself for doing it later if it fails.

I am going to replace my cheapass PCChips motherboard and 800MHz Athlon with a new completely different motherboard and AMD XP 1800+ CPU. I want to swap everything else over into the new mobo/cpu combo. Before actually removing the old parts, I use the ENUM trick, right?

Then, once I reboot, I may need to manually install drivers, which is fine, but I want to make sure this is all OK to do. I am using and will be using Windows ME...

[reboot]

The LAST thing you do, before shutting down the old system, is remove the ENUM key.
Exit the registry, shutdown, and start pulling parts.

[ghost_of_war]

Excellent, thank you...

[BRANDAN]

yes, this was just what i was looking for i remeber seeing this like last year but it was link to a website that told how to do it but this will do fine
thanx

[cdnref]

What is the ENUM key thing......don't laugh I'm trying to learn.

[glc]

I'm not laughing, but if you would review all the posts in this thread it should answer that question for you.

It's the hardware enumeration key in the registry, it contains data about all the hardware in your machine. When you move a hard drive from a Win9x/ME machine into a totally different machine, this procedure is a very clean way to force Windows to re-enumerate all the hardware without all the old data hanging around to bloat the registry and cause conflicts. It's kinda like reinstalling Windows without losing your programs and data.

[Alex123]

I have a question regarding an alternate method for the enum trick.

Would not do the trick saving the current configuration, then replacing the hardware that is going to be changed and at start up, If I am not mistaking, should appear a message asking you if you want to use current configuration or the one you named when saving it, prior to change your hardware?

I am just thinking of that possibility, then if you take current configuration, it should start looking for all of this new hardware (mobo, or whatever you put in there), then, install corresponding drivers.
Do you think that would work?

Or I am just dreaming here

[cdnref]

Is that how they out the old HDD into a *new* PC? if so bitchn'

Will it work for XP? or just 9x/ME?