Hardware

Ask something
Discussion Locked

mainboard won't run WindowsXP

0 helpful
12 replies

by kmerrillt 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am building a new system with mostly new parts. New parts consist of: case with power supply, fan, keyboard, speakers. A KOB 630E motherboard with gigapro 1ghz cpu onboard, onboard video, onboard sound. A 128 sdram memory board, new IDE cables for hard drive and floppy and cd rom. Old parts consist of: western digital wd-300 protoge ata 100 hard drive which has WindowsXP home on it and runs in my previous E Machine. At present, the motherboard recognizes and sets all parameters for the hard drive, cd rom and floppy. Computer will not boot into Windows even with safe mode selected. I can however install a 10 year old IBM hard (2 gig) with Windows98 on it and the computer will boot and run fine. Same cable and no changes made in CMOS. I know the hard drive is ok because I can put it back in my original computer and it will boot and run. In waiting for tech support from the manufacturer (KOBIAN) I figured I see if anyone has run across this or might have some suggestions.

12 replies

by wcp

Back up your data and follow the steps below.

1. Reinstall Windows on top of the current one. Boot the computer with the Windows XP Home CD and choose Repair after the Microsoft license agreement.

2. If this fails, clean install Windows.

Either way, you have to reactivate.

by boli

The answer is this:
When you install any version of windows, it configures the installation of windows to be exactly compatible with the hardware that is connected. Only plug and play things are able to work on any installation but they still come with DRIVERS. You need to install the INF files for your M/B and all the drivers for everything after windows installation finnishes, thats why when you boot up windows for the first time after you installed Windows (not including brand name computers)it looks all wierd and nothing works quite right.

by dmiles

The problem exist with Windows XP not recognizing the configuration of the new computer and will not boot up.The cause of this is of new security measures by Microsft to thwart the installation on more than one system,you can get aroungd it by doing a fresh install and callint Microsoft for installation code

by csmith

There is nothing wrong with your hardware.
This is a Windows XP problem.
Large hardware changes under XP are not allowed, because that is how XP determines that you are a "Pirate".
I know you are not a pirate, and you know you are not a pirate, but WinXP builds a hardware profile, and any major changes cause the OS to not boot.
Since you are doing serious rebuilding/upgrading, new installs of XP will be necessary each time.
Keep your copy of Win98SE, so you can find out if your new hardware configuration works, before you try to install WinXP.
Regards, Chris

by csmith

Hi Lee,
By what you have said, all of the boot failures are hardware conflicts.
I am going to have to look into that.
Reason:
If you do a typical upgrade, of changing the tape backup unit, adding another disk array, and changing the video card, there is only about a 15% chance that the PC will boot under XP.
If you skip the video card change, the chances of a successful boot rise to about 25%.
This is using hardware that works under XP.
An upgrade of adding a DVD-RAM recorder, CD burner, and a scanner will produce the same 15% chance of successful boot.
But.
Adding another processor, in a low cost system, means changing the motherboard, and fixing the no boot problem. (IDE controller problem)
(Makes you appreciate Servers like the old COMPAQ Proliant, where you just have to change the CPU card, to add a processor.)
I am beginning to think that I am wrong in blaming the anti-piracy settings in XP, and rather it may be a software bug in XP, that causes these no boots, after a multiple upgrade.
But. The theory, that these are mostly hardware conflicts, does have merit, judging by the number of PCs we get, that were trashed when the owner tried to upgrade from Win98SE or Win2K to WinXP.
The problem is, finding the time to do documented tests.
I definitely do agree with you on the IDE controller problem.
The problem of the no default IDE driver, that you mentioned, is an unacceptable failure, in error handling, by Microsoft.
I wonder if they are going to fix it in SP2.

Regards, Chris

by wlbowers

You did not say if you are getting error messages during the boot.

If it will boot to floppy. Your problem could be associated with resource drivers.

First while it is true that XP monitors severe changes in system components,it will not keep a system from booting. It might require you to reregister either through the internet or through a call to moma microsoft.

The call is usually (I repeat usually) not required until three or four online reregisterations have been performed.

Here is what I have found in a motherboard change with Windows XP or Windows 2000.

The chipsets that are used by different motherboard manuafacturers are a critical issue in xp and 2000. The os does not leave generic drivers in place after the OS install is complete.

This will usually result in an error message during startup. Boot_Device_Inacessable.

The motherboard is not at fault. Windows has drivers installed for a specific chipset and these need to be changed. You need to do an inplace upgrade.

http://support.microsoft.com/default.aspx?scid=kb;en-us;315341&Product=winxp

This is the url for Q315341 in the Microsoft knowledgebase. Remove any spaces that happen during copy/paste.

You can also access this information by going to microsoft.com. On the left of the page under Resources select support and Knowledge Base. Enter the Q number is the search for window and click on Go.

This should get you back up and running.

FYI: Q292175 is the inplace upgrade knowledge base doc for Win2000.

Good Luck Lee

This discussion is closed to new replies.