Never thought about this...

[JoHo22]

What would happen if i built my new rig,
but grabbed the hard drive (that has everything i need/want on it)
and didnt do a fresh install of windows, and just ran it as is?

 

[MercenaryForHire]

Depends what your old rig was, but I'm gonna say BSOD with IRQL_NOT_LESS_OR_EQUAL or UNMOUNTABLE_BOOT_VOLUME

- M4H

 

[JoHo22]

well im working in my schools computer repair center.
we had a discussion about it (im really gonna do it on saturday, cause my windows XP corporate disk is at home)
well here are the specs for the original pcs

P4 1.6 Ghz
Gigabyte GA-8IRX Motherboard
1 gig of 3200 ram *bought for the new rig, but left it in there cause it ran)
Radeon 9500 128 Pro
160GB Seagate Baracuda SATA2
40GB Seagate IDE
Windows XP corporate.

new rig
AMD Athalon 64 +3200 Venice
BIOSTAR TForce6100-939 Socket 939 NVIDIA GeForce 6100 Micro ATX AMD Motherboard
SAPPHIRE 100130VIVOL Radeon X800GTO2 256MB GDDR3 PCI Express x16 Video Card
Same hd's
Same Ram
Same os


I can imagine that installing the Motherboard drivers could pose an issue,
but the IDE HD is blank. Perhaps i could leave the empty hd in and do the drivers for the biostar.
Sound possible?

 

[JoHo22]

Well, worst that could happen is i have to transfer all the stuff off my pc onto another, and go from there. or to the 40 gig, and get the cd, reinstall windows... do all the updates ... god the firewall req's here at buff state are rediculous!

 

[Blain]

You can simply do a "repair" on the OS. It's shouldn't be that big of a deal.

 

[JoHo22]

we all totally overlooked that,
but i might have 1 up on you.
Windows corporate edition,
doesnt that have a recovery console installed with it?

 

[JoHo22]

perhaps i can just do that... cause mu install disk is no where near the school.

 

[Lord Evermore]

The "repair" install requires the CD anyway, and still requires you to download all the updates again. It wipes out all driver references, all updates to the OS and integrated software, while leaving all user-installed applications and files alone. It's very handy for migrating a system without having to re-install everything.

All Win2k/XP discs have the recovery console available (and it can be installed to the hard drive) but this is used for troubleshooting. It basically gives you a command prompt with some tools like chkdsk and Registry repair.

There's actually a very good chance you'll be able to just move the drive to the new system and not have any problems. XP is pretty good about just detecting the new hardware and prompting for drivers. To be safe, you might just want to uninstall the chipset drivers before the last shutdown, if you've installed the drivers from Intel. That way it's essentially like XP is booting for the first time as far as those drivers are concerned.

 

[JoHo22]

well im newb,
so do tell how to uninstall the chipset drivers...
just throught the Device Manager?

 

[Markbnj]

I've done it. Usually Windows will figure out what is going on. You might have to manually uninstall some drivers. I think your chances are better if you disable/uninstall all the stuff that won't be in the new computer before you shut down the old on and take the drive out.

 

[Lord Evermore]

Originally posted by: JoHo22
well im newb,
so do tell how to uninstall the chipset drivers...
just throught the Device Manager?

If you installed Intel's drivers by downloading them from the Intel website, or from the motherboard's CD, then they should be in the Add/Remove Programs screen. Otherwise, you probably don't even need to bother, but yes in the Device Manager you could uninstall the IDE controller, Processor, any brand-specific Sound controllers, the network adapter, and items in the System Devices that specify a brand.

 

[JoHo22]

fantastic idea,
any other possible snags I may run into??

 

[Nocturnal]

You'd probably geta BSOD. Your best bet is to plug it into your current box, remove any IDE drivers there are and let Windows install the regular Windows IDE drivers. This in turn should help you avoid the BSOD but it isn't a guarantee.

 

[JoHo22]

Originally posted by: Lord Evermore

Originally posted by: JoHo22
well im newb,
so do tell how to uninstall the chipset drivers...
just throught the Device Manager?

If you installed Intel's drivers by downloading them from the Intel website, or from the motherboard's CD, then they should be in the Add/Remove Programs screen. Otherwise, you probably don't even need to bother, but yes in the Device Manager you could uninstall the IDE controller, Processor, any brand-specific Sound controllers, the network adapter, and items in the System Devices that specify a brand.

eek!
i never did that, just went plug and play...
possible reason for the crashes and random restarts and reaching 55 degress?? (heat wise on therm 3)

 

[JoHo22]

Originally posted by: Nocturnal
You'd probably geta BSOD. Your best bet is to plug it into your current box, remove any IDE drivers there are and let Windows install the regular Windows IDE drivers. This in turn should help you avoid the BSOD but it isn't a guarantee.

waht if i jsut install the SATA2 first, then later the IDE?
the ide isnt really performing that great anyway...

 

[Nick5324]

I recently went from a nforce 2 based MB to the ASRockDual939, which uses a ULi chipset (new CPU also, obviously). I also got a new HDD and used it to do a fresh install. However, since I've seen lots of AT'ers say that just moving the HDD over won't work, I put my previous HDD in to see what would happen. I didn't have a single problem. It started right up, installed a few drivers by itself, and ran just fine. Go figure. Despite this, I would say doing this kind of thing won't always work. Even if it doesn't go this well, as Blain said, do a repair and it should be fine.

 

[Kaido]

Easy solution: build your computer with a new hard drive, install Windows, and install your old hard drive as a slave to pull files from. Cake.

 

[GamerExpress]

Originally posted by: MercenaryForHire
Depends what your old rig was, but I'm gonna say BSOD with IRQL_NOT_LESS_OR_EQUAL or UNMOUNTABLE_BOOT_VOLUME

- M4H

Yep, you gotta love MS.

 

[NYTRIDR]

HAL might have something to say about moving an XP hdd to another system.

 

[Lord Evermore]

Originally posted by: NYTRIDR
HAL might have something to say about moving an XP hdd to another system.

"I can't do that, Dave."

Perhaps?

 

[NYTRIDR]

lol