Compatible Support Forums: New motherboard, HD won't boot!!!

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

New motherboard, HD won't boot!!!

#1 User is offline   a10thunder 

  • stranger
  • Group: Members
  • Posts: 12
  • Joined: 28-May 01

Posted 25 April 2002 - 02:52 AM

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.
0

#2 User is offline   Dirty Harry 

  • addict
  • Group: Members
  • Posts: 437
  • Joined: 28-May 00

Posted 25 April 2002 - 09:48 AM

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.
0

#3 User is offline   Brian Frank 

  • Carpal Tunnel
  • Group: Members
  • Posts: 3088
  • Joined: 21-January 01

Posted 25 April 2002 - 10:29 AM

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. :p) are still there.
0

#4 User is offline   a10thunder 

  • stranger
  • Group: Members
  • Posts: 12
  • Joined: 28-May 01

Posted 25 April 2002 - 11:43 PM

Thanks for the replies. I guess a reinstall is in order. I'll miss my nudie pix. smile
0

#5 User is offline   SHS 

  • veteran
  • Group: Moderators
  • Posts: 1245
  • Joined: 16-July 99

Posted 26 April 2002 - 01:19 AM

a10thunder reinstall in to new folder then back up what you want then start clean install
0

#6 User is offline   der King Mongo 

  • stranger
  • Group: Members
  • Posts: 13
  • Joined: 03-November 01

Posted 19 May 2002 - 11:22 PM

without blowing away your data...
0

#7 User is offline   thekourier 

  • stranger
  • Group: Members
  • Posts: 18
  • Joined: 22-May 02

Posted 22 May 2002 - 01:50 PM

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?
0

#8 User is offline   Brian Frank 

  • Carpal Tunnel
  • Group: Members
  • Posts: 3088
  • Joined: 21-January 01

Posted 24 May 2002 - 03:53 AM

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.
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users