Installing Windows XP on SATA HDD

C

Clayton

I don't know what's going on here but I am trying to install Windows XP on a
SATA HDD.

I have copied the manufactures raid drivers to a floppy and have on
installation of Windows pressed F6, it has asked for the files which
installed them ok and continued, but when I select F8 ( Licence Agreement)
it Blue Screens saying:
Stop 0xC2 or BAD_POOL_CALLER

The Motherboard is a ASUS P5S800-VM and is using the latest BIOS
 
C

Clayton

I don't know if this is related or not but on startup I get a message saying
"Intel CPU uCode loading error" Press F1 to Resume. it seems to resume ok
after pressing F1
 
K

Kawosa

This error is usually caused by bad memory sticks. In your case it could
just be a funky driver. Make sure you are using the latest available driver
and if it continues, run a good memory tester program.


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0607-1, 02/14/2006
Tested on: 2/16/2006 8:27:01 PM
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com
 
J

John R Weiss

Clayton said:
I don't know if this is related or not but on startup I get a message saying
"Intel CPU uCode loading error" Press F1 to Resume. it seems to resume ok after
pressing F1


I've seen the BAD_POOL_CALLER BSOD on several occasions, but not in this
context.

Check your BIOS settings, and see if you can enable/disable the CPU ID code. It
might be worth a try...
 
B

Bob Harris

I found a description at

http://aumha.org/win5/kbestop.htm

It suggests a bad driver.

A couple of possibly related items about SATA and RAID: I have an ASUS
P4S8X motherboard with an SATA/RAID controller. Before I could install XP I
had to do several things.

(1) Tell the BIOS that an allowed boot device was "SCSI/onboard ATA". This
refers to the SATA drive, not the more common IDE drives (which I do not
have). I also had to be sure that "onboard ATA device" was enabled on a
separate BIOS screen.

(2) Define a raid array. This seemed odd, since I assumed that the default
BIOS setup would make individual disks, but I was wrong. So I made two
arrays with one disk each. (Note that I installed 2 SATA disks, not one.)
In some setups this is called JBOD (just a bunch of disks). The point is
that I had to manaully do this. Until I did, even the hard drive maker's CD
could not access the disks. Thereafter, I formatted them no problem. All
this raid setup was, technically speaking, not really in the BIOS. Rather
it came after the BIOS stuff in the boot sequence, but still in the black
screen with white characters that is below the XP level. In my case I had
to enter the "FastTrack" setup, which was the name of the raid controller.

(3) Install drivers from floppy via F6. BUT, that was harder than it
sounds. First, I copied only the drivers to a floppy. That ultimately
failed to get XP installed. The trick was to copy the entire SATA driver
directory to the floppy. This included a very important file called
txtsetup.oem in the root directory of the floppy. Under that were
directories for nt4, win2000, and winxp.

Otherwise I took defualts or auto-setting for things like clock speed and
memory timings. I figured that tweaking could be done later, one the basic
PC had been tested at "safe" settings.

A few other hints about initial XP installs. Be sure that NO USB or
firewire devices are connected, except possibly for USB keyboard and mouse.
However, PS/2 mouse and old-fashioned key board may prove more reliable.
Have no ZIP drives attached, even internal ZIP drives. Have no printer
attached, USB or parallel port. Once XP is installed, attach each device,
one at a time, and they should be installed almost automatically.

Finally, read the entire motherboard manual. Sometimes the required
information is scattered in strange places. Also, since most manually are
translated into English, sometimes it is necessary to guess what they meant
to say, not what the words actually say.
 
C

Clayton

Thanks guys, I excamined the HDD closely and found it was damaged where
there SATA cable goes into, the plastic surround around the pins are broken
and jammed in the SATA cable.
 
B

Brett I. Holcomb

Hmm, I have an Asus A7M266-D with one XP processor and am using a SATA PCI
card with a Seagate SATA disk. I was able to install XP Pro as was the
original poster. However, I cannot get the system to boot off the SATA.
I've removed all other drives, removed all except the video card and I get
the No disk operating system message when the system boots. I've put SCSI
first in the list, tried various PCI slots but still not boot! Where did
you tell your BIOS you could boot SCSI? On my Boot section of the BIOS
I've put SCSI first and did not have USB connected when installing.

Any more suggestions? I'm wondering if the motherboard (latest BIOS, too)
doesn't support this.
 
C

Clive in Kent

Hi Brett,

Brett I. Holcomb said:
Hmm, I have an Asus A7M266-D with one XP processor and am using a SATA PCI
card with a Seagate SATA disk. I was able to install XP Pro as was the
original poster. However, I cannot get the system to boot off the SATA.
I've removed all other drives, removed all except the video card and I get
the No disk operating system message when the system boots. I've put SCSI
first in the list, tried various PCI slots but still not boot! Where did
you tell your BIOS you could boot SCSI? On my Boot section of the BIOS
I've put SCSI first and did not have USB connected when installing.

Any more suggestions? I'm wondering if the motherboard (latest BIOS, too)
doesn't support this.
I installed XP on SATA disk on an Ausu board last weekend. Following
carefully Bob Harris's exceleent directions. Enen tho' you only have the 1
disk you still have to set it up as a spanning array ( JBOD). You are then
given the option of making it a boot disc or not. Worked for me!!

Clive Holden (Kent GB)
 
B

Brett I. Holcomb

That's good news - I think <G>. Where do you set it up and how. Did your
BIOS let you do it or did you have to boot to some other disk? My Asus
A7M266-D doesn't appear to know they exist - I can't find anywhere to setup
the RAID.
 
C

Clive in Kent

Hi Brett,

Brett I. Holcomb said:
That's good news - I think <G>. Where do you set it up and how. Did your
BIOS let you do it or did you have to boot to some other disk? My Asus
A7M266-D doesn't appear to know they exist - I can't find anywhere to
setup
the RAID.


SNIP

I'm not at home to check on my own machine at the moment but I seem to
remember that from the POST boot up, don't enter BIOS set up but wait for
the next screen which is the RAID screen this gives you an option of "press
F10 for RAID setup facility". Then setup your disc as a spanning RAID it
then gives you an option to make the disc bootable.

HTH

Clive in Kent
 
B

Brett I. Holcomb

You have a real card then <G>. Mine doesn't do that - nothing at all. It
appears the motherboard doesn't even recognize the card is there.

Thanks.
 
G

Guest

Brett I. Holcomb said:
You have a real card then <G>. Mine doesn't do that - nothing at all. It
appears the motherboard doesn't even recognize the card is there.

Thanks.

Well, that's kind of what seems to be a problem for my own install -- I
installed the OEM release of XPx64 on a new SATA HDD. It is conected
driectly to the Gigabyte K8U MOBO, and is currently the olny hdd in the
machine. I had a single CD-RW drive connected to the IDE secondary to use as
installation drive, but nothing else.

When I formatted the new drive, and installed XPx64, everything seemed to go
seamlessly, only now, the HDD has been assigned D:. The system boots from it
with no apparent problem, but the Device Manager still shows a phantom Drive
C: on its roster. Checking properties, it shows 0KB capacity and content,
and when I click on it, it reacts like a removable drive, asking that a disk
be inserted.

Has the original CDRW been assigned to C:? Is there anything I can do the
get the boot drive designated as C: drive, without re-formatting or
re-installing? It's only a problem when I use certain utilities who need the
C:\ path to run
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top