OT - Upgrade MB without reinstalling OS?

I am going to upgrade MB/CPU/RAM and don't want to reinstall on dual boot Win2K/98se System Commander system. I've read about exporting/removing the ENUM section of the registry in Win98 before installing a new MB/RAM/Processor, and letting OS find new hardware, but what will work in Win2K, anything? Will Win2K just find new hardware, or is the drill the same/similar? -- Tom Hesselman Greenville, WI

I don't know about Win 2k, but I did the ENUM trick in Win98SE with no probs. Just delete the HKLM/ENUM from the registry the last time you boot before installing the hardware. Rafe Mc On Mon, 19 Nov 2001 19:01:41 -0600, Tom Hesselman <[email hidden]> wrote:

Quoted text (8 lines)

>I am going to upgrade MB/CPU/RAM and don't want to reinstall on dual >boot Win2K/98se System Commander system. > >I've read about exporting/removing the ENUM section of the registry in >Win98 before installing a new MB/RAM/Processor, and letting OS find new >hardware, but what will work in Win2K, anything? > >Will Win2K just find new hardware, or is the drill the same/similar?

Win98 will do this no problems. Win2k will probably not boot - the changes to your IDE controller alone would account for this. I went from an Intel BX platform to an AMD760 base and I had to do a Win2k repair from the cd-rom and then re-apply service packs and then the vendor drivers. It was stable after that, but I'm not sure how "clean". I have since re-installed win2k for other reasons so I can't vouch for long term stability. And be very very careful with system command and 98se. iksteh "Tom Hesselman" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (8 lines)

> I am going to upgrade MB/CPU/RAM and don't want to reinstall on dual > boot Win2K/98se System Commander system. > > I've read about exporting/removing the ENUM section of the registry in > Win98 before installing a new MB/RAM/Processor, and letting OS find new > hardware, but what will work in Win2K, anything? > > Will Win2K just find new hardware, or is the drill the same/similar?

<snip>

iksteh wrote:

Quoted text (16 lines)

> > Win98 will do this no problems. > > Win2k will probably not boot - the changes to your IDE > controller alone would account for this. I went from an > Intel BX platform to an AMD760 base and I had to > do a Win2k repair from the cd-rom and then re-apply > service packs and then the vendor drivers. It was > stable after that, but I'm not sure how "clean". > > I have since re-installed win2k for other reasons so I > can't vouch for long term stability. > > And be very very careful with system command and 98se. > > iksteh

Went from an intel P3 BX to an abit kg7 athlon1.4 setup without any problems whatsoever on W2k. It only complained a bit because it was left in hibernation mode before the upgrade! Phil

On Tue, 20 Nov 2001 15:23:37 +1100, "iksteh" <[email hidden]> wrote: *SNIP > >And be very very careful with system command and 98se. >*SNIP* Care to elaborate on being careful with System Commander and 98se? Worked great here for last year or so with 98se on C: and Win2k on E: Thanks -- Tom Hesselman Greenville, WI

Just curious, I have WinME and have just installed a new motherboard and CPU. ME detected the new board and everything seems fine. When is this ENUM trick necessary? "Rafe McAuliffe" <[email hidden]> wrote in message news:[email hidden]... > I don't know about Win 2k, but I did the ENUM trick in Win98SE with no > probs. Just delete the HKLM/ENUM from the registry the last time you > boot before installing the hardware. > > Rafe Mc >

Yeah, Simon, I'm abt. to try this trick (new AMD CPU & mobo replacing an elderly P3-650), so I'm curious, too. "Simon Brown" <[email hidden]> wrote in message news:xQsK7.6311$%[email hidden]...

Quoted text (15 lines)

> Just curious, I have WinME and have just installed a new motherboard and > CPU. ME detected the new board and everything seems fine. When is this > ENUM trick necessary? > > "Rafe McAuliffe" <[email hidden]> wrote in message > news:[email hidden]... > > I don't know about Win 2k, but I did the ENUM trick in Win98SE with no > > probs. Just delete the HKLM/ENUM from the registry the last time you > > boot before installing the hardware. > > > > Rafe Mc > > > > >

If you let Windoze detect the new hardware, etc. by itself then it *should* work fine still. But the old hardware will still be left in the system, drivers etc. will still be loaded. You can boot to safe mode and clear them out but it's still not 100%. This way Windoze starts from a clear slate and re-detects all new hardware. The drivers will still be present on the system but not loaded, so it will only utilise the ones it needs. It won't fix a broken windoze but it should work well 99% of the time. And heaps easier than a full reinstall :) Rafe Mc On Tue, 20 Nov 2001 17:02:11 GMT, "Stephen Smith" <[email hidden]> wrote:

Quoted text (21 lines)

>Yeah, Simon, I'm abt. to try this trick (new AMD CPU & mobo replacing an >elderly P3-650), so I'm curious, too. > >"Simon Brown" <[email hidden]> wrote in message >news:xQsK7.6311$%[email hidden]... >> Just curious, I have WinME and have just installed a new motherboard and >> CPU. ME detected the new board and everything seems fine. When is this >> ENUM trick necessary? >> >> "Rafe McAuliffe" <[email hidden]> wrote in message >> news:[email hidden]... >> > I don't know about Win 2k, but I did the ENUM trick in Win98SE with no >> > probs. Just delete the HKLM/ENUM from the registry the last time you >> > boot before installing the hardware. >> > >> > Rafe Mc >> > >> >> >> >

"Tom Hesselman" <[email hidden]> wrote in message news:[email hidden]... > On Tue, 20 Nov 2001 15:23:37 +1100, "iksteh" <[email hidden]> wrote:<snip> > Care to elaborate on being careful with System Commander and 98se? > Worked great here for last year or so with 98se on C: and Win2k on E: hehe - probably not, i might might a complete fool out of myself. it's in the SysCommander doco that you can nuke Win98 installs very easily. sounds like you did it the right way. myself and a friend were drunk one night and thought we'd repartition our drives. needless to say, after one of us broke his system, the other (me) said "that should have worked" and broke his. It was good for a laugh, but it's made me paranoid of SC. We have since called it the SC Drunk Virus because it spreads from drive to drive in the presence of alcohol. That and 6 months later a friend went to boot his machine and the system commander partition which he though he'd deleted months ago pops up. He was sober so i reckon it's big brother... The caution is valid though - the SC documentation does list some specific steps to take care of when using with 98 or you can lose your system partition. iksteh

Rafe, So what yer saying is I should amputate the ENUM branch of the Registry tree, shut down, swap mobos, then fire it up & let Win discover the new h/w? Or are you saying never mind messing w. the Reg, just shut down, swap, & reboot? (I'm not changing anything BUT the mobo & CPU: same RAM, HD, video, sound, NIC, mouse, kybd., monitor, all apps, etc.) --Steve "Rafe McAuliffe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (24 lines)

> If you let Windoze detect the new hardware, etc. by itself then it > *should* work fine still. But the old hardware will still be left in > the system, drivers etc. will still be loaded. You can boot to safe > mode and clear them out but it's still not 100%. > > This way Windoze starts from a clear slate and re-detects all new > hardware. The drivers will still be present on the system but not > loaded, so it will only utilise the ones it needs. > > It won't fix a broken windoze but it should work well 99% of the time. > And heaps easier than a full reinstall :) > > Rafe Mc > > > On Tue, 20 Nov 2001 17:02:11 GMT, "Stephen Smith" > <[email hidden]> wrote: > > >Yeah, Simon, I'm abt. to try this trick (new AMD CPU & mobo replacing an > >elderly P3-650), so I'm curious, too. > > > >"Simon Brown" <[email hidden]> wrote in message > >news:xQsK7.6311$%[email hidden]... > >> Just curious, I have WinME and have just installed a new motherboard

and > >> CPU. ME detected the new board and everything seems fine. When isthis > >> ENUM trick necessary? > >> > >> "Rafe McAuliffe" <[email hidden]> wrote in message > >> news:[email hidden]... > >> > I don't know about Win 2k, but I did the ENUM trick in Win98SE withno

Quoted text (10 lines)

> >> > probs. Just delete the HKLM/ENUM from the registry the last time you > >> > boot before installing the hardware. > >> > > >> > Rafe Mc > >> > > >> > >> > >> > > >

"Rafe McAuliffe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (13 lines)

> If you let Windoze detect the new hardware, etc. by itself then it > *should* work fine still. But the old hardware will still be left in > the system, drivers etc. will still be loaded. You can boot to safe > mode and clear them out but it's still not 100%. > > This way Windoze starts from a clear slate and re-detects all new > hardware. The drivers will still be present on the system but not > loaded, so it will only utilise the ones it needs. > > It won't fix a broken windoze but it should work well 99% of the time. > And heaps easier than a full reinstall :) > > Rafe Mc

Just to mention I changed my aliV based mobo with k6II chip for an abit kg7 lite with 1400 tbird, everything else stayed the same- gfx, sound, drives, etc. WinME picked up all the necessary changes on first boot, then I installed the updates (via 4 in 1 etc) and no problems since. System does a clean shutdown in three seconds, no problems with confused OS. cheers John

Thx for the info, John. "JM" <[email hidden]> wrote in message news:%3SK7.3351$[email hidden]...

Quoted text (18 lines)

> > "Rafe McAuliffe" <[email hidden]> wrote in message > news:[email hidden]... > > If you let Windoze detect the new hardware, etc. by itself then it > > *should* work fine still. But the old hardware will still be left in > > the system, drivers etc. will still be loaded. You can boot to safe > > mode and clear them out but it's still not 100%. > > > > This way Windoze starts from a clear slate and re-detects all new > > hardware. The drivers will still be present on the system but not > > loaded, so it will only utilise the ones it needs. > > > > It won't fix a broken windoze but it should work well 99% of the time. > > And heaps easier than a full reinstall :) > > > > Rafe Mc > > Just to mention I changed my aliV based mobo with k6II chip for an abit

kg7

Quoted text (12 lines)

> lite with 1400 tbird, everything else stayed the same- gfx, sound, drives, > etc. > > WinME picked up all the necessary changes on first boot, then I installed > the updates (via 4 in 1 etc) and no problems since. System does a clean > shutdown in three seconds, no problems with confused OS. > > cheers > John > > >

Ok, thanks for the reply Rafe :) "Rafe McAuliffe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (14 lines)

> If you let Windoze detect the new hardware, etc. by itself then it > *should* work fine still. But the old hardware will still be left in > the system, drivers etc. will still be loaded. You can boot to safe > mode and clear them out but it's still not 100%. > > This way Windoze starts from a clear slate and re-detects all new > hardware. The drivers will still be present on the system but not > loaded, so it will only utilise the ones it needs. > > It won't fix a broken windoze but it should work well 99% of the time. > And heaps easier than a full reinstall :) > > Rafe Mc >

Sorry, kind of wixed my mords :) If you amputate the ENUM branch of the registry (just as you stated) then change the hardware you will only have the drivers, etc. loaded that pertain to your NEW system. Once Windoze loads them. Some ppl seem to have resonable success with just letting windoze change to the new hardware automatically (like John below), but this has never worked for me. Horses for courses, but I do believe that the ENUM trick works better. Rafe Mc On Wed, 21 Nov 2001 13:46:21 GMT, "Stephen Smith" <[email hidden]> wrote:

Quoted text (56 lines)

>Rafe, > >So what yer saying is I should amputate the ENUM branch of the Registry >tree, shut down, swap mobos, then fire it up & let Win discover the new h/w? >Or are you saying never mind messing w. the Reg, just shut down, swap, & >reboot? (I'm not changing anything BUT the mobo & CPU: same RAM, HD, video, >sound, NIC, mouse, kybd., monitor, all apps, etc.) > >--Steve > >"Rafe McAuliffe" <[email hidden]> wrote in message >news:[email hidden]... >> If you let Windoze detect the new hardware, etc. by itself then it >> *should* work fine still. But the old hardware will still be left in >> the system, drivers etc. will still be loaded. You can boot to safe >> mode and clear them out but it's still not 100%. >> >> This way Windoze starts from a clear slate and re-detects all new >> hardware. The drivers will still be present on the system but not >> loaded, so it will only utilise the ones it needs. >> >> It won't fix a broken windoze but it should work well 99% of the time. >> And heaps easier than a full reinstall :) >> >> Rafe Mc >> >> >> On Tue, 20 Nov 2001 17:02:11 GMT, "Stephen Smith" >> <[email hidden]> wrote: >> >> >Yeah, Simon, I'm abt. to try this trick (new AMD CPU & mobo replacing an >> >elderly P3-650), so I'm curious, too. >> > >> >"Simon Brown" <[email hidden]> wrote in message >> >news:xQsK7.6311$%[email hidden]... >> >> Just curious, I have WinME and have just installed a new motherboard >and >> >> CPU. ME detected the new board and everything seems fine. When is >this >> >> ENUM trick necessary? >> >> >> >> "Rafe McAuliffe" <[email hidden]> wrote in message >> >> news:[email hidden]... >> >> > I don't know about Win 2k, but I did the ENUM trick in Win98SE with >no >> >> > probs. Just delete the HKLM/ENUM from the registry the last time you >> >> > boot before installing the hardware. >> >> > >> >> > Rafe Mc >> >> > >> >> >> >> >> >> >> > >> >

Thx, Rafe. "Rafe McAuliffe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (21 lines)

> Sorry, kind of wixed my mords :) > > If you amputate the ENUM branch of the registry (just as you stated) > then change the hardware you will only have the drivers, etc. loaded > that pertain to your NEW system. Once Windoze loads them. > > Some ppl seem to have resonable success with just letting windoze > change to the new hardware automatically (like John below), but this > has never worked for me. Horses for courses, but I do believe that the > ENUM trick works better. > > Rafe Mc > > > On Wed, 21 Nov 2001 13:46:21 GMT, "Stephen Smith" > <[email hidden]> wrote: > > >Rafe, > > > >So what yer saying is I should amputate the ENUM branch of the Registry > >tree, shut down, swap mobos, then fire it up & let Win discover the new

h/w? > >Or are you saying never mind messing w. the Reg, just shut down, swap, & > >reboot? (I'm not changing anything BUT the mobo & CPU: same RAM, HD,video,

Quoted text (25 lines)

> >sound, NIC, mouse, kybd., monitor, all apps, etc.) > > > >--Steve > > > >"Rafe McAuliffe" <[email hidden]> wrote in message > >news:[email hidden]... > >> If you let Windoze detect the new hardware, etc. by itself then it > >> *should* work fine still. But the old hardware will still be left in > >> the system, drivers etc. will still be loaded. You can boot to safe > >> mode and clear them out but it's still not 100%. > >> > >> This way Windoze starts from a clear slate and re-detects all new > >> hardware. The drivers will still be present on the system but not > >> loaded, so it will only utilise the ones it needs. > >> > >> It won't fix a broken windoze but it should work well 99% of the time. > >> And heaps easier than a full reinstall :) > >> > >> Rafe Mc > >> > >> > >> On Tue, 20 Nov 2001 17:02:11 GMT, "Stephen Smith" > >> <[email hidden]> wrote: > >> > >> >Yeah, Simon, I'm abt. to try this trick (new AMD CPU & mobo replacing

an

Quoted text (13 lines)

> >> >elderly P3-650), so I'm curious, too. > >> > > >> >"Simon Brown" <[email hidden]> wrote in message > >> >news:xQsK7.6311$%[email hidden]... > >> >> Just curious, I have WinME and have just installed a new motherboard > >and > >> >> CPU. ME detected the new board and everything seems fine. When is > >this > >> >> ENUM trick necessary? > >> >> > >> >> "Rafe McAuliffe" <[email hidden]> wrote in message > >> >> news:[email hidden]... > >> >> > I don't know about Win 2k, but I did the ENUM trick in Win98SE

with > >no > >> >> > probs. Just delete the HKLM/ENUM from the registry the last timeyou

Quoted text (11 lines)

> >> >> > boot before installing the hardware. > >> >> > > >> >> > Rafe Mc > >> >> > > >> >> > >> >> > >> >> > >> > > >> > > >

Well, if I remember correctly, I had 98se installed on C:\ and installed System Commander. I let SC set itself up for Win2K install. Everything has been working great for over a year. I just last night installed SC 7, now with a Windows install. I installed it from the E:\ partition where Win2K lives, and it went perfectly. It now has a true graphical interface, mouse support, and works very well. Now, if I can summon the balls to do the MB swap that started this thread, get both OS's working, then I might attempt to summon the balls to add WinXP in it's own partition, with NTFS. I use FAT32 even with Win2k now because I want access to all hard drive area. But....I just swapped in a 60GB, so now space isn't much of a problem! And I promised myself "No upgrades this computer season" Now....new EPoX 8KHA+/Athlon XP 1900+\512mb of Corsair PC2400\Alpha 8045 are on a FedEX plane somewhere over mid America on their way to my doorstep! Sigh....I love it! On Wed, 21 Nov 2001 19:52:18 +1100, "iksteh" <[email hidden]> wrote:

Quoted text (29 lines)

>"Tom Hesselman" <[email hidden]> wrote in message >news:[email hidden]... >> On Tue, 20 Nov 2001 15:23:37 +1100, "iksteh" <[email hidden]> wrote: ><snip> >> Care to elaborate on being careful with System Commander and 98se? >> Worked great here for last year or so with 98se on C: and Win2k on E: > >hehe - probably not, i might might a complete fool out of myself. > >it's in the SysCommander doco that you can nuke Win98 installs > very easily. sounds like you did it the right way. myself >and a friend were drunk one night and thought we'd repartition >our drives. needless to say, after one of us broke his system, the >other (me) said "that should have worked" and broke his. > >It was good for a laugh, but it's made me paranoid of SC. We >have since called it the SC Drunk Virus because it spreads from >drive to drive in the presence of alcohol. > >That and 6 months later a friend went to boot his machine and >the system commander partition which he though he'd deleted >months ago pops up. He was sober so i reckon it's big brother... > >The caution is valid though - the SC documentation does list >some specific steps to take care of when using with 98 or you >can lose your system partition. > >iksteh >

-- Tom Hesselman Greenville, WI