XP does not recognize SATAII drive

[Goose7]

I know I'm doing something wrong, but I have tried to do a dual boot on a Vista computer. Slipstreamed SP2 and tried to add SATA drivers. I partitioned my harddrive, did everything for the setup, made the XP partition E. For some reason XP does not see my SATA harddrive and E partition and installs on my Media disc 1, which is H. I have read topics on slipstreaming XP controller dive and SATA drive into XP. One said SCSI/RAID should be removed first, another said they should not be removed, someone else said write this into this file, which is a file that XP does not want to open by the way. No one really goes into detail, like most of us that would like to use nLite to slipstream have got to be computer techs. I think a lot of that info was kind of old or for someone that knows a lot about computers. I would like to know a up to date and easy way to get XP to see my SATA drive. I have a Gateway GT5432 computer with a Elitegroup MCP1P main circuit board. 2.60gig AMD Athlon 64 x2 Dual Core, WDC WD32 00AAJS harddrive, Nvidia nForce Serial ATA Controller(2x). I also have a Asus SATA DVD dive and a Atapi ATA drive.

Need a Big Hint

Goose7

[spacesurfer]

First, do you know where your SATA drivers are? You need to find the drivers first as XP does not have SATA drivers built in. Usually, your SATA drivers are provided on your motherboard drivers CD. Find these first.

Then, there are two options for XP to recognize your SATA drivers.

1) First, you need to copy these drivers to a floppy. The txtsetup.oem file goes in the root of the floppy. Leave everything as is. When XP setup starts, it will display a message that says "Press F6 to load third party drivers..." or something like that for 2 - 3 seconds. You need press F6. Then, after XP loads the built in drivers, it will ask you to insert the floppy. Insert it. Then it'll ask you to choose the device. Choose the device. If the drivers were correct, then XP will display that drive as an option to install XP to.

2) Alternate way is to integrate the drivers using nLite so you won't have to press F6. It shouldn't bee too hard. Just follow directions with nLite.

[Mordac85]

Also, you may want to check the BIOS to see if your system is using AHCI instead of ATA mode for the SATA operation. XP doesn't support AHCI natively and can give you a headache until you get the drivers loaded (e.g. F6 option above) but ATA mode may be a workaround for you.

[Dpac415]

I have been having some major issues getting XP to recognize my drives under a RAID setup. I am trying to setup a RAID 0 with 2 150GB Raptors and followed every instruction/forum I could find on the subject to no avail.

MB: Intel D955XBK

HDD: 2 x Western Digital Raptors 150GB

CPU: Pentium D 3.0 Ghz

Mem: 2 GB Stick 667 SD DDR2 RAM

I downloaded the latest floppy from Intel with the SATA RAID Drivers and created a floppy, which I install via F6 Command. There is a selection for 4 different drivers. I have tried each and it accepts, but when it goes to load windows it states it cannot find any Hard Drives. My Bios sees both drives and allows me to Cntrl I and create the RAID 0

XP will only recognize my drive if I leave it in IDE Mode under Drive Selection. The only problem with this is you can't initialize RAID if you load XP in IDE mode. If you try to download the Matrix Storage Software from Intel after you install with IDE it will state that your hardware does not support it.

I have tried all combinations of BIOS settings I can think of and get the same error each time.

If anyone has any suggestions, please assist.

[Mordac85]

F6 will show the drivers it finds on the floppy, but doesn't tell you if they're the one(s) you need. That's the correct method in this case, since the notes from the current driver from Intel says you have to unpack the drivers, v7.8.0.1012 avail here, and use the F6 method. However, if you look at the drivers for this MB it shows the Intel Matrix Storage Manager, but also an integrated Silicon Image controller.

Maybe you can boot to a PE CD and run devcon to find the actual PCI ID of the controller? Then check the INF's for the PCI ID (grep up to the DEV section usually e.g. PCI\VEN_8086&DEV_2922).

[Dpac415]

Thanks for replying Mordac85,

I can download a PE CD, but I have never used one before. Which would you recommend? Does it provide you with a menu with the selection "DEV section"? Once there, it will tell me my PCI ID? If so then I can match it to the Intel Sites related driver and select it. It is strange though. I have selected one of each of the files I am prompted with after F6 is selected in the window (below, but I only get a selection of 6 and not sure which ones because I'm not in front of my box). Yet setup still does not see my drives.

I have ran diagnostics on both drives, CPU, and Memory as well, and all are performing stable. I read through every intel article I could find related to RAID and SATA and tech support was useless. If this doesn't work the only other thing I can try is to Slipstream it, and if that doesn't work.......I guess I will try another MOBO?? Geeez, setting up a RAID 0 shouldn't be this difficult!

- Intel® 82801IR/IO SATA RAID Controller (Desktop ICH9R)

- Intel® 82801IR/IO SATA AHCI Controller (Desktop ICH9R)

- Intel® 82801HEM SATA RAID Controller (Mobile ICH8M-E)

- Intel® 82801HEM SATA AHCI Controller (Mobile ICH8M-E)

- Intel® 82801HBM SATA AHCI Controller (Mobile ICH8M)

- Intel® 82801HR/HH/HO SATA RAID Controller (Desktop ICH8R)

- Intel® 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)

- Intel® 631xESB/632xESB SATA RAID Controller (Workstation ESB2)

- Intel® 82801GHM SATA RAID Controller (Mobile ICH7RM)

- Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M)

- Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)

- Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)

[Mordac85]

What I was getting to w/devcon was to verify you actually are using the Intel controller and not the SI one. But from the list it looks like you may have the Intel one.

As for PE, I'd recommend BartPE, but that's assuming you can't currently boot to the system in any way. You can use a utility like devcon or Unknown Devices to scan the system's hardware. Both can give you the PCI ID of the RAID controller and from there we'll know if we're trying to run the SI controller with the Intel drivers.

If you have the Intel controller I'd recommend pulling the driver from them directly (link in previous post) and verify the PCI ID string you found is listed in the driver's INF. If so, that should work just fine.

Warning: Technical Geek stuff ahead

As for the DEV section, I was referring to the PCI ID string found in the driver INF file. No menus or GUIs to make it simple, you just need to use notepad and read the file. A PCI ID is broken down into standardized sections. There is a hardware ID and a specific device ID. The hardware ID can be such things as PCI, ROOT, HDAUDIO, USB, etc, followed by a slash and the device ID string. The Device ID, for specific hardware, will usually have a vendor (VEN_8086) and a device (DEV_2922) at the very least and sometimes seperated by additional items like subsystem (SUBSYS_02111028), revision (REV_02) and, in some instances a specific instance (\3&172E68DD&0&FA) separated by ampersands (&). MSDN ref is here. String all that together and you get something like:

PCI\VEN_8086&DEV_2922&SUBSYS_02111028&REV_02\3&172E68DD&0&FA

The driver INF will normally only need to match on the vendor and device (PCI\VEN_8086&DEV_2922), but sometimes may be defined more specifically if they need to do something special for a particular chip. If you find that part of the PCI ID in the driver INF you're trying to use, then you have the correct driver and the problem most likely lies elsewhere in the build process.

Edited December 18, 2007 by Mordac85

[Dpac415]

I found the string below using notepad and confirmed it is correct:

PCI\VEN_8086&DEV_2682&CC_0104.DeviceDes% = iastor_Inst_RAID, PCI\VEN_8086&CC_0104

I'm still having the same problem though. I will create a slipstream tonight and try it.

Any other suggestions on what could be the cause?? I'm worried that it will not even recognize the drive(s) after the slipstream.

[Goose7]

Thanks Spacesurfer,

I have tried that already. Slipstreamed drivers, formatted my XP partition for E and now XP sees my E partition as I. I have heard that some XP will make thier own partition letter assignment. I just hate that it throws all my other disc letters out of wack. Thanks again and Happy Holidays to everyone.