New motherboard, HD won't boot!!!

One of my older computer's power supply failed a few weeks back. While buying a new case, I decided to upgrade the motherboard as well. I was thinking that if I just transfer everything from the old motherboard to the new one (i.

Windows Hardware 9627 This topic was started by ,


data/avatar/default/avatar21.webp

12 Posts
Location -
Joined 2001-05-28
One of my older computer's power supply failed a few weeks back. While buying a new case, I decided to upgrade the motherboard as well. I was thinking that if I just transfer everything from the old motherboard to the new one (i.e. processor, memory, cards, and drives) everything will be fine. However, after I installed the new board, my hard disk won't boot up. Everything else seems to be working fine. My computer can boot from the floppy and CD ROM, but it can't seem to access the hard disk. I get a boot disk error message. I tried changing the jumper setting between cable select and master, but neither seems to make a difference. The BIOS does detect the HD as the primary master. And I'm sure both the IDE cable and power cable are fine. Does anyone have any idea on how to fix this problem? I backed up everything before I switched motherboards, so I guess I can reinstall Win2k. However, I would really like to restore my old system.
 
My new motherboard is an Abit VH6T running on a PIII 733 CPU.

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar24.webp

437 Posts
Location -
Joined 2000-05-28
What are you saying here- that you can't boot from the hard disk or that the hard disk is invicible after you've booted ?
 
As a rule, you shouldn't, and often simply cannot pick a HD with OS installed from an old Mobo and plug it in on a new system and just boot. Different chipsets etc are not recognized on the fly with W2K or XP. With older OS's this was not that much of a problem. A reinstall is the only way to go. There are some tricks that might circumvent this, but not worth tring IMO.
 
If you again are saying that you can't see / access the old HD at all when you've booted from somewhere else - could it be that you boot with a DOS /w98 boot disk etc and the HD is NTFS formatted. Then you can't access it, its not a bug its a MS "feature".
 
H.

data/avatar/default/avatar40.webp

3087 Posts
Location -
Joined 2001-01-21
Dirty Harry pretty much said it all. Unless you got a mobo with the same chipset, you need to reinstall Windows. And while you can get around it, you just end up having to reinstall Windows later anyway. That's one good thing about keeping your OS on a different partition: just format that one when necessary and reinstall Windows. While you still need to reinstall all your apps, the data (saved games, mp3s, nudie pix, secret deathstar plans, etc. ) are still there.

data/avatar/default/avatar21.webp

12 Posts
Location -
Joined 2001-05-28
OP
Thanks for the replies. I guess a reinstall is in order. I'll miss my nudie pix.

data/avatar/default/avatar25.webp

1297 Posts
Location -
Joined 1999-07-16
a10thunder reinstall in to new folder then back up what you want then start clean install

data/avatar/default/avatar20.webp

18 Posts
Location -
Joined 2002-05-22
I was thinking about doing the same thing, replacing my KT133 motherboard with a new KT333 one. I've got the latest VIA 4n1 drivers installed and I figured it shouldn't be too much of a problem since the chipset is the same line. Anyone gone from KT133 to KT333 without reinstalling?

data/avatar/default/avatar40.webp

3087 Posts
Location -
Joined 2001-01-21
Just because it has KT in it doesn't mean you can just jump over to another KT chipset w/o a hassle. Some review I saw had the guy going from a KT133 to a KT133A chipset (same manufacturer, board with new chipset), and he had to do a clean install to get things running.