Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Unable To Boot Xp From New Build


  • Please log in to reply
3 replies to this topic

#1 bycoverofnight

bycoverofnight

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:02:10 AM

Posted 06 September 2008 - 12:57 PM

So I've put together a new system, with a blank 500 GB SATA Seagate drive. I put a bootable XP disc in my CD drive, set the bios to boot from CD, and have not been able to get it to work.

Sometimes, I get a message on the top of the screen right before it freezes saying setup is inspecting your computer hardware configuration, indicating that it is able to read the XP disc. This XP disc works in other computers that I try it with.

I tried putting in my old IDE drive from my other computer, that has windows loaded on it already, and that got me to the windows splash screen, before an almost instant blue screen of death (it resets before I can read the error message, like in 1/10 of a second).

Any ideas as to what the problem could be?

The computer recognizes the RAM, and the Harddrive and the CD ROM drive in the BIOs. Usually it just hangs on "Boot from CD", occasionally, I get the "press any key to boot from cd" option, but then nothing from there. The CD drive makes a lot of noise (working hard) during all of this.

I put in a Rosewill 500 W Power Supply which should be enough to power my EVGA 640-P2-N829-AR GeForce 8800GTS SSC at least to load windows, right? All fans are spinning fine.

Does this sound like a hardware issue or some sort of configuration snafu, or neither?

I've tried pulling out the RAM, no different result. CPU is secure, heatsink on tight.

Board: GIGABYTE GA-EP35-DS3L
CPU: Intel Core 2 Duo E8400 Wolfdale 3.0GHz
VGA: EVGA 640-P2-N829-AR GeForce 8800GTS SSC 640MB
RAM: CORSAIR 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
Intel Core 2 Duo E8400 Wolfdale 3.0GHz LGA
PSU: Rosewill RP500-2 500W ATX12V v2.01 Power


I'm just about at my wits end here. I would tear out my hair if I weren't bald already.

Oh, and this is my 2nd build, but first in 5 years, some components have changed obviously. So it's possible that I'm missing something obvious.

Unfortunately, my old computer doesn't have SATA, so I can't preload the operating system there. But like I said before, I have a disk with a functioning
XP operating system that will blue screen me on this new build. What does that mean?

Thanks so much.

BC AdBot (Login to Remove)

 


#2 dbough

dbough

  • Members
  • 96 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:02:10 AM

Posted 06 September 2008 - 09:50 PM

Is the HDD new or did you format a different one and put it here? Is the CD / DVD Drive new? Any beep codes on boot?

With weird issues like this (which ALWAYS happen to me) I put in the bare minimum components needed to operate. This way you can rule out certain things. So - put in // 1 Optical Drive, 1 HDD, 1 stick of RAM, 1 Video Card (if there is a built in Video card use that instead of an addon.) //

If there are still issues do one or all of the following:

1. Make sure the IDE cable from the optical drive to the motherboard is tight.
2. Try a different IDE cable on the optical drive.
3. Try a different optical drive.
4. Check BIOS RAM settings (This is often a 'gotcha' as some bios need to be set differently for different RAM)
Everything has a beginning and an end. Life is just a cycle of starts and stops. There are ends we don't desire, but they're inevitable, we have to face them. It's what being human is all about. -Jet Black; Cowboy Bebop

-CCVP

Well, Technically ...

#3 Platypus

Platypus

  • Global Moderator
  • 15,210 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:06:10 PM

Posted 06 September 2008 - 09:53 PM

a blank 500 GB SATA Seagate drive. I put a bootable XP disc in my CD drive, set the bios to boot from CD, and have not been able to get it to work.

I think it's pretty certain XP is not able to recognise your SATA drive. This is normal for XP. If the system has a floppy drive, find the drivers for the motherboard SATA controller on the CD supplied with the board, copy them to a floppy disk. During the XP setup preliminaries, when an instruction to Press F6 if you need to use third-party drivers comes up, press F6 and put the floppy disk into the drive (or have it there anyway if the FDD isn't ahead of the CD in boot order).

If the system is legacy-free, so lacks a FDD, you'll need to create a slipstreamed CD of XP with the SATA drivers included. You can use a slipstreaming utility such as nLite. This is also a good opportunity to include SP3 in the installation, so avoiding a huge online update.

An alternative is to set up the SATA controller in the BIOS to use IDE emulation (most but not all BIOS offer this option). The SATA controller will appear to be a standard UDMA133 IDE controller, and Windows generic EIDE drivers will work. A few advanced SATA features will be lost, such as SATA II transfer rate, hotswap and Native Command Queing, but this may not be important for many applications.

I tried putting in my old IDE drive from my other computer, that has windows loaded on it already, and that got me to the windows splash screen, before an almost instant blue screen of death (it resets before I can read the error message, like in 1/10 of a second).
Unfortunately, my old computer doesn't have SATA, so I can't preload the operating system there. But like I said before, I have a disk with a functioning
XP operating system that will blue screen me on this new build. What does that mean?

Windows on the old drive is installed according to the hardware in your old system, so crashes if you try to run it on the new hardware. The same thing would happen if the old system did have SATA and you were able to load the new drive on the old system - when the drive was transferred, Windows could not run on the different hardware in the new system. It is possible that the old Windows installation on the IDE drive could be repaired on the new system by booting from the XP CD and choosing to do a repair installation. But the Windows on the IDE drive would still not have SATA drivers installed, so you would have to install them, then image the old repaired installation across to the new SATA drive. I think it is best to achieve a fresh Windows installation to the new drive.

Edited by Platypus, 06 September 2008 - 10:00 PM.

Top 5 things that never get done:

1.

#4 dbough

dbough

  • Members
  • 96 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:02:10 AM

Posted 06 September 2008 - 09:57 PM

Platypus' post reminded me -

Try setting your SATA drive to function as an IDE drive in your BIOS. I sometimes forget how quirky Windows is with SATA drives.
Everything has a beginning and an end. Life is just a cycle of starts and stops. There are ends we don't desire, but they're inevitable, we have to face them. It's what being human is all about. -Jet Black; Cowboy Bebop

-CCVP

Well, Technically ...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users