Hi all, During bootup, case lights come on, including blue cathodes, fans, etc, I get no beep codes, the screen initially flashes the indentity of the vid card installed, then goes to intell splash page, then to the unable to load windows screen with many options such as boot in normal mode, safe mode, etc. The setup: mobo - intel 865perl (new) cpu - intel p4 2.4c boxed (new) memory- corsair 3200 ddr 1024mb twinx dual channel (new) (1 stick each installed in channel A raid 0, channel B raid 0). video - gainward geforce fx5600 128mb ddr, ultra 760 tv/dvi. (new). hard drive - wd 40gb (from previous computer...not new). Verified working, and has win xp installed. power supply - icute 430watt (new). Only things on mobo right now are cpu,mem,video card. Board has current BIOS (verified on intel site). In BIOS, verified cpu, memory, etc. I've had problems with "no signal" on other builds, but those were memory problems. The twin corsair sticks are installed properly, 1 in channel A raid0 and the other in channel B raid0. The bios recognizes them (1024mb) as well. Any ideas on why I can't get the OS to load? Thanks.
You're going to need to reinstall Windows when you switch to a new motherboard. That's basically all there is to it.
thanks for the reply Big B. the more i searched, the more this "solution" comes up. doing a fresh o/s install. so off to get another drive. b.t.w. what's the reason for needing to do a fresh o/s install when a new mobo is installed? Does the o/s installation and boot instructions record the motherboard type?
Different chipset, specifically, the IDE channels. If you're changing boards with the same chipset, that's a different story. You can go into device manager and delete/uninstall everything, but you can't go wrong with a fresh install.
Well, that did it. A fresh o/s install. Thanks Big B for the info...helps to know why this is needed as well!
In the future, you can remove all drivers for all the hardware prior to the installation of the new MoBo. After the hardware installation, commence software [driver] installation. With Linux, this is little or no problem at all; you don't even have to remove the previous drivers first. With Windows NT5.x, this can be a messy but somewhat forgiving process. With Windows 9x however, it's downright NASTY (Ever heard of a ".VXD Error"?). In any case, if you're running some build of Win32 it's probably the best idea in the long run to just do a clean install and get it over with. Just remember: backup, backup, backup