New computer - moving hard drive

[ride525]

My old computer is a Duron 600 on a Abit Kt7 motherboard.

I just built a AMD XP 2800+ on a ECS N2U400 motherboard.

I moved my hard drive over to the new computer, but Windows 2000 won't boot all the way....goes to the Windows 2000 startup screen, then get a blue screen, that suggests a virus, or a new install, or something like that....move hard drive back to old computer, no problems....

Any suggestions?

Thanks

Jeff

 

[Blain]

You should reformat and reload everything after a MB change. Sorry
I've read about people doing what you tried, but Windows OS needs to be "repaired".

This is a topic for the OS Forum for sure. If you can be helped, it will probably come from there.

 

[ride525]

Yeah, I've done it before successfuly using Windows 98

 

[imported_Phil]

Originally posted by: ride525
Yeah, I've done it before successfuly using Windows 98

Sorry to point out the obvious, but you're not using Windows 98.
Windows 2000 will not usually survive a motherboard/chipset swapout unless the chipsets are identical, or from the same product family.

 

[ride525]

Sorry to point out the obvious, but you're not using Windows 98. Windows 2000 will not usually survive a motherboard/chipset swapout unless the chipsets are identical, or from the same product family.

Yeah, I know I'm not using Windows 98, but have Win 2000.

So what's a guy to do....

 

[bdmst16]

Windows 2000's kernel when first installed checks basic hardware, called HAL (Hardware Abstract Layer) this includes things like MB, CPU, HD controller, etc. This are different from most PnP devices. While I've never done this I would presume that you would need a reinstall. You could move the HD back to the old computer, make a temporary partition backup all data then reinstall Win2K on the system partition and then restore the data.

 

[uOpt]

I would think you could just reinstall over the old installation and keep your applications. But don't quote me on that.

And yes the move works for Win95/98, Linux, FreeBSD but not for NT and up and Solaris.

If you know enough you could possibly assemble a generic kernel.

 

[imported_rhfactor]

You can sometimes do a reinstall and do repair instead of install. Otherwise, you could have done a sysprep before moving the hard disk.

 

[ride525]

sysprep?

What's that ,and how do you do it?

Thanks for your help.

Did a google search, and got some a couple of different approaches....

Any more thoghts here?

Thanks again,

Jeff

 

[bdmst16]

Sysprep is a deployment tool used when you have numerous IDENTICAL pc that all need a fresh install. Its found on the Win2K CD in the Deploy.cab file in the Support\Tools. Sysprep makes a master image which then can be deployed to other computers using a third-party utility (ie Ghost).

I don't believe sysprep would work here since the HAL has to be the same for sysprep to work. The only thing that can be different are PnP devices.

 

[imported_rhfactor]

sysprep is in the deploy.cab in your windows xp \support\tools folder. What is does is to setup your hard disk for moving XP to different PC environments. When you boot up again, Windows will do the hardware lookups and will either reload drivers or prompt for new ones.

This is basically used by OEMs but can be done by the home user.

 

[bdmst16]

Sysprep will detect all PnP devices once the Setup Wizard starts up, but the HAL must be the same. Here he is moving from a different HD controller and mobo. Sysprep should not work in this instance. Sysprep would only work if he cloned the image off a machine that had the same basic hardware configuration.

 

[imported_rhfactor]

I forgot to mention that there is an entry you have to put into the sysprep.inf file to make this work. A standard sysprep will not work. It is on the web somewhere on the exact name.

[Sysprep]
BuildMassStorageSection=yes
[SysprepMassStorage]

 

[bdmst16]

It really depends on what version of Sysprep that you have. If you have 1.0, which comes with Win 2K then you can NOT duplicate different HD Controllers. If you have XP with Sysprep 1.1, then you can get around this. The newest version of Sysprep is available for DL from microsoft's site.