Mobo Swap - Registry Hack Failed - Now What?

[MoboMojo]

Well, replaced my Abit VA6 with a Abit BE6-II v2 yesterday. I used the registry hack (delete ENUM key) before shutting down on the VA6. Then did the swap, re-booted. All looked well as several re-boots found the new mobo devices (I only included my ATI video card - no other cards). But now I'm getting BSOD in Windows (0E error) no matter what I do. I've restored the old registry and re-dropped ENUM key (and subkeys), but the same result.
I'm at the point where I'll re-install Win98SE, but what's the best way to do this (if it can be done) so that I don't have to re-install all my apps??

Can I export the software keys and re-import after the clean install??

Will a re-install over the existing Win98SE image retain the apps (I don't think so)?

I did ghost the disk image the night before onto a second disk, so I could extract any files that may be necessary.

BTW, I think the problem is related to the video card. The card is an ATI All in Wonder 32MB AGP card and the ATI instructions say to de-install the driver by going to Control Panel/Add-Remove Programs and click on the ATI display driver to remove it. I didn't do that, but just tried switching back to the standard VGA driver. I also uninstalled ATI's multimedia software and now when I click on the ATI display driver in Add-remove programs, I get an error from rundll32 and it won't uninstall.

Any suggestions on how to reinstall Win98SE and still retain apps (don't want to re-install all my apps).

Sorry for the long post and TIA!!
Mobo////

 

[Supradude]

reinstall over the existing win98se will keep all apps installed and all associations intact, i do it all the time

 

[MoboMojo]

Will a re-install also clean out the crap in the registry left over from the VIA-based VA6??

Also, what's the recommended way to reinstall over the existing Win98SE image? Boot from a startup Win98 disk, then execute setup on the Win98SE CD?? BTW, I have Win98SE full version OEM CD (not an upgrade CD).

TIA,
Mobo////

 

[Supradude]

i think it keeps your registry intact (i believe the program associations and such have registry keys so wiping the reg would probably screw your installed apps), but if you have missing or corrupt files it will re-install them... as for method, either star-up disk and setup off cd, running setup from cd in windows, or copying the cd to your HD and setting up from there will work... startup disk and cd-rom is probably the safest way...

 

[MoboMojo]

bump

 

[Rhonda85]

I tested this hack several times on three different systems & it caused a great deal of trouble for me. I would not ever suggest doing this. I just replaced my Abit BH6 with a KT 133 based board & did nothing but let windows detect the changes. It worked very well. Re-installing windows probably will do you no good, Goog luck.

Rhonda

 

[MoboMojo]

Rhonda,
Thanks for the advice. I tried as you suggested; it appeared to work for multiple re-boots as devices were detected. But, alas, the BSOD appeared and crashed windows. Interestingly, the crashes occurred (several times) exactly when the PCI-to_isa bridge drivers were installed. Also, it looked like some of the new mobo's devices (bx chipset)were actually using the same drivers as the old mobo (Via chipset).

So I deleted all system devices in control panel and re-booted. This time it re-detected many more mobo devices, but the end result was still the same.

Right now, I think I'll just rename the Windows directory and do a clean re-install of Win98SE. Assuming that goes well, I can re-import the registry entries for my installed software and hopefully all will be well.
mobo////

 

[hclarkjr]

one simple command for you mobomojo- format c: is your best route to take for getting rid of the BSOD problems. i do that at least once a year to clean out the registry of all the old apps and stuff that collect dll's and such in there. it is a pain in the A$$ but well worth the performance gain you see. just my 2 cents worth though

 

[MoboMojo]

Yep, will keep format c: in mind for tonight.
Mobo////

 

[nino]

Try this as a last step.
Look under Hkey_local_machine_>System->Currentcontrolset->services->Class

Get rid of your class folder and everything within that folder AND get rid of the ENUM key. This "should" work as it removes the references in the Enum so should remove any potential conflicts.

let me know how you make out at nino@purdue.edu

The Enum keys point to drivers in the Class folders. Typically removing the Enum is all that is necessary and removing the Class keys remove the references to the actual drivers needed by the Enum keys.

 

[nino]

Hey mobomojo,
Did it work?

 

[RoboTECH]

yeah, I was wondering about this....how'd it go?

 

[MoboMojo]

Sorry about not posting a response sooner.

I actually got the machine up and running before I saw Nino's post. To do that, I dropped the ENUM key and searched through the rest of the registry and deleted any references to "VIA", since they made the chipset on my old VA6 and the new BE6-II is an Intel BX Board.

But I think I'll re-do the whole thing this morning using Nino's suggestion. The reason is that I'm getting a few strange problems. For example, my 2 NICs (an SMC EZ10 Card for my cable modem, and a Linksys LNETX100 for my home LAN) are auto-deteted every time I restart Win98SE. This morning the damn thing re-detected and re-booted 4 times and even then the NIC's showed up in Device Mgr with a yellow exclam. This *is* an improvement. Last night they didn't show up in Device Mgr at all even though they were auto-detected.

So with no LAN or cable modem, I've had to go to another machine and use a dial-up.

Most other functions on the machin, BTW look OK.

Will post back later today on the results. If you don't hear from me, its because I'm leaving on vacation for next week and couldn't get it done. Will then have to pick-up the pieces next weekend.

Mobo////

 

[MoboMojo]

Nope -- no go. Didn't have much time to work on this today.
But the latest is: all appeared OK using Nino's suggestion and running selective startup. The NICs were there, video card was installed, etc. Then, I checked normal startup and the NIC's kept re-detecting. So there must be something with one of the proggies in the startup.

No time to check it now. Off on vacation. Will look at it next weekend.
Mobo////

 

[nino]

I'm sorry but I forgot to mention that you'll have to remove and reinstall your networking options also.
Go to add/remove programs and remove ALL microsofts networking options (under the windows setup tab) under communications and then once they are removed....re-install them.

Let me know if this doesn't work and I'm sorry for not mentioning it last time.