Fernando 1

OK, in this case the discussion about missing or wrong BIOS settings seems to be obsolete.You probably have set the optical drive (CD/DVD-ROM) as first bootable device and the HDD as second one, haven't you? Yes,but you may not hit any key while rebooting. So you think, that your XP source is not ok? That would be an explanation for the strange behaviour of the Setup process.

So you came to the point where you have to decide, where you want to get the OS installed. Is this correct? If yes, have your hdd(s) and their partitions been correctly detected? Did you hit a key when prompted while rebooting? You should not do that. Hitting a key only makes sense during the first boot off the CD/DVD. You certainly mean drives and not "drivers". Yes, the nForce S-ATA Controllers, where your S-ATA hdd's are connected, should be enabled within BIOS, otherwise your hdd's won't be detected at all by any OS you want to install.I don't believe, that you have to enable RAID too, since you obviously haven't built a RAID array. Nevertheless you should have look into your mainboard/pc manual.

If this happened at the end of the installation (at last reboot), have you tried to boot in safe mode (by hitting F8) and look into the Device Manager for any yellow marks?Did you see any error message? You can get it, when you hit F8 while booting and choose the option "don't reboot at system failure". Did you take the correct nForce IDE drivers? The 11.09 chipset driver pack is suitable for MCP51 (with CPU socket 939) and MCP61 (with AM2 CPU socket) chipsets. Since you obviously have an nForce 430 chipset mainboard with an AM2 CPU socket, you have to integrate the drivers of the MCP61 directory. No, but rather less.If you had chosen the nForce IDE driver folders from the correct directory (MCP51 or MCP61), you can try to integrate just the SATARAID driver folder as textmode (without the additional integration of the SATA_IDE driver folder). Some nForce chipsets need the SATA_IDE drivers separately, some don't like them.

Yes, you have to replace the "Standard Dual Channel PCI IDE Controller", which is managing your S-ATA hdd's in IDE mode, by the Serial ATA Controller (Intel or Silicon Image) where your S-ATA hdd's are connected.Open your Device Manager and look into the IDE ATA/ATAPI Controllers section. Right click onto the Controller you want toreplace and do a driver update by loading your specific Sata driver. After the reboot your S-ATA hdd's will be managed by the third party S-ATA Controller.

You are welcome! CU Fernando

1. You have to take a driver folder with a file named TXTSETUP.OEM in it.2. Integrate the content of this driver folder as TEXTMODE by using nLite. 3. Don't hit F6 while installing the OS. Good luck! Fernando

This is a wellknown issue of the Windows Setup routine, that it prefers the natively IDE connected hdds and sometimes ignores the HARD DISK BOOT PRIORITY settings of the BIOS.You can prevent this issue by unplugging/disabling your IDE/P-ATA connected hdd before you are going to install the OS.

Yes. No.

Have you tried to slipstream the Service Pack into Windows XP x64 from within a running Windows XP (32bit)?That wouldn't work. You will only be able to integrate a Service Pack into a 64bit Windows OS while running a 64bit OS.

It makes me happy, when I can help others. This should be no problem at all (unless you change from a 32bit OS to a 64bit OS), because all actual Intel S-ATA Controllers are using exactly the same driver named IASTOR.SYS and the same information files. All you have to do is enabling all Controllers during the Intel textmode driver integration. It would be possible, but I wouldn't do that.Reason: Users want the newest/best drivers and a small sized OS CD. Both things are not possible by creating and integrating an AIO textmode driver package. 1. It would take a lot of time to search and to collect the actual textmode drivers of all storage controller chips, that ever have been manufactured. As soon as you have them all together, you have to start again from scratch, because there are already new ones out. 2. An AIO textmode driver package would have a big size, which has to be integrated into the OS CD/DVD, although each user will only need just 1 single driver of this big package. Have a nice day too! Fernando

Thanks for your post.You are right - the recent INTEL Matrix Storage Manager package doesn't support ICH5R SATA RAID Controllers. To help future users with such RAID Controllers I have added a new download link to the already extracted "newest" ICH5R SATA RAID drivers dated 10/12/2005. You obviously got them already installed.Thanks for your request and thanks to Lancelot_Real for his help! By the way: It would be no problem for me to add the HardwareID's of the INTEL ICH5R SATA RAID Controllers into the newest Intel Matrix Storage Manager drivers packages, but by doing this the drivers would loose their WHQL stamps for all users. That is why I have uploaded the original WHQL signed ICH5R RAID drivers separately. CU Fernando

You can!

Hello Tom,thanks for your interesting and useful report. This certainly will help other users with similar problems. I have put a link to your how-to description into my nForcersHQ forum thread. You obviously didn't install the RAIDTOOL v9.99, which is part of my NF4-7 AHCI pack. You should manually replace the RAIDTOOL v663 (should have been v6.95) by v9.99 using my new AHCI driver package. Fine, that I could help you with this package.CU Fernando

Thanks for your final success report, but it is not the primary intention of this forum and this thread, that users at least boot off the original OS CD and load the textmode drivers by F6/floppy.My impression: "Much Ado About Nothing" (William Shakespeare). CU Fernando

Thank you for the flowers. What I have done was not for NVIDIA, but for the customers of their nForce chipsets and the users of their drivers. Hello Tom,thanks for your interesting and detailed report. I cannot give you any concrete advice how to solve your problem. There are so many possible reasons for it, that it is not easy to find out the real one. There are nForce SataRaid users who have a rock stable system from scratch and others who only have problems. Nevertheless I will try to give you some advices: 1. Have a look onto your PSU. Many pc problems can easily be solved by a new PSU. The most important thing is not the power itself, but the ability to provide exactly the voltage (not more, not less), which is needed by the different devices. 2. Maybe you should have a look into this thread and try the new nForce IDE drivers v9.98. Good luck! Fernando

That is true. You should never use a modified (for example an already nLited) CD as source, if you are going to create an nLited CD.This is what I have written within my guide (first post of this thread): Users, who are asking for help here, should have read and followed my guide.

I doubt, that the new Silicon Image S-ATA driver is the reason for that error message.Are you sure, that your DVD Burner and the previously burned CD is ok? About ACPI.....default was already selected, the available options are the following:-ACPI Multiprocessor x64 -ACPI Uniprocessor x64 OK. ACPI Multiprocessor x64 would have been the correct one, but if you have chosen "default", Windows Setup will detect it by its own. You may try it.If this doesn't help either, you should take any IDE CDROM drive from somewhere or borrow it from a friend, connect it to the IDE port and install the OS from there. Once the OS is up, you will be able to use your SATA DVD Burner again.

Sorry, old question...I selected TextMode for Silicon Image and only half of the two options....there was 1 for "Itanium" processor and 1 for x64 multi-processor. I choosed only x64 multi-processor.For the nVidia SATA/RAID Drivers I selected both TEXTMODE rows with "required" at the end. Everything regarding the textmode driver integration seems to be ok. No. I got the latest BIOS version, maybe I need the latest Silicon Driver too in addition.I'll try that......too! That's a good idea.Good luck! Fernando

First nLite DVD I tried was:Silicon Image Drivers I went to download : Silicon Image 3132 Serial ATA Driver V1.0.5.0 for Windows 64bit XP/2003(WHQL) From: Motherboard/AM2/M2N32-SLI Deluxe/IDE/ http://dlsvr03.asus.com/pub/ASUS/misc/ide/..._SATA_V1050.zip Here you can get the newest textmode SATA drivers for your Sil3132 S-ATA chips. Exactly same 0x0000007B error. I'll send you a picture of it tonightNo file name within the message? Never been able even to install Windows without Silicon Image Drivers. I mean, with x64 and that RAID 0 configI am a little bit unsure about that, because it is a long time ago when I have used a Silicon Image S-ATA port. AFAIK Windows XP (32/64bit) is able to detect and to manage all non-AHCI SATA1 devices by using the MS Standard Dual Channel PCI IDE Controller, but maybe you are right and you will need to load/integrate the Silicon Image S-ATA textmode driver.

M2N32 motherboard got 2 SATA/RAID controllers.....1st is nVidia, 2nd is silicon image. I've put both on my nLite disk nVidia RAID drivers (since that controller is on RAID mode) and Silicon Image Sata drivers (since that controller is on sata mode). (I got my DVD drive plugged into Silicon Image controller) That is what I needed to avoid Windows install BSOD - > both controller drivers. But now I got the reboot loop sh** Which Silicon Image S-ATA driver did you integrate (give me the download link) and how did you do it (as textmode or PnP)? I ask this, because Windows XP x64 shouldn't have a problem to detect the S-ATA connected DVD drive without any third party drivers. Tell me more about ACPI vs nLite and ACPI vs BIOS....I took a quick look at my BIOS and found nothing about ACPI.BIOS will be no problem, if you leave the default settings untouched.When you are working with nLite, you get the option of different "Computer type" settings. You should either choose the correct setting (depending on your processor type, but with ACPI support) or leave it at "automatic" or "default". I'll try rather than to put both controller drivers on an nLite disk.....only use the nVidia SATA/RAID controller. I mean, I'll unplug the DVD Drive to the Silicon Image controller and desactivate the controller. Then I'll plus the cd drive on the nVidia controller.I'll thy to load only nVidia drivers with f6 method since I got only one divers to insert. "since I got only one divers to insert"....is the only advantage of nLite in this post is to be able loading several drivers at the same windows installation? If you want, you can integrate more than 1 textmode driver by using nLite.It might be a good idea to generally connect the DVD Burner with a Silicon Image S-ATA port, because this way you get a clear separation between your SATA2 hdd's, which are working in RAID mode and your DVD drive, which is running in SATA1 mode and doesn't need any Silicon Image drivers. One more thing: Please try to get the error message of your infinite reboot loops. It is quite easy to get it: Just hit F8 a few seconds after the reboot and choose the option "don't reboot at system failure". Then you can read the BSOD message and maybe see the driver which causes the BSOD.

I got a 0x0000007B error that tells me to run chkdsk. It is a storage device error. Need precision?No, not necessary. This sort of BSOD is a very common one and mostly related to a memory issue. Seriously, I already installed WinXp 64 bit and even 32 bit on the same system without any issue. When I say Installed, I mean, tested with benchmarks. I had a lot of problem in the past with memory with another system and I don't think it's the case....Also, the error I get is about HDD anyway....I'll do it if it is the last available solution......man changing a ram bracket in that monster is insane !!!It is not a good idea to build a monster where you cannot easily remove any hardware like a memory stick.I am still very confident that the removal of 1 or 2 sticks could be able to solve your problem. Should the extra drivers cause interference?This is possible with nForce 5-7 RAID systems. The installation of the nForce SataRaid drivers at actual nForce systems is managed by one single INF file, which is associated with the nVRAID driver within the SATARAID folder. Only older nForce SataRaid systems additionally need the nForce S-ATA driver INF file (which you only find within the SATA_IDE folder) to get the nForce SataRaid drivers installed. The integration of the unneeded SATA_IDE driver folder might be critical with NF5-7 chipsets. What do you mean? Because overclocking mess up the southbridge? (I did no overclocking)The installation of an OS is a very complicated thing. Especially 64bit Windows Operating Systems need fully compatible memory sticks and rock stable BIOS settings. Your S-ATA connected DVD Burner might be a problem while installing an OS onto an nForce SataRAID array. I had to remove my previously built-in S-ATA DVD Burner, because it was impossible to get any OS installed onto my RAID by booting off this device. Why have you done that? Are you not sure, if you have created a NVIDIA or a Silicon Image RAID? What about your Power Management settings?You should have enabled ACPI within your BIOS and within your nLite settings. Good luck! Fernando

Really fine system, but obviously no luck with the OS installation. Have you tried to remove 1 or better 2 of the memory sticks during the installation?I am nearly sure, that this will solve your problem. It would have been a good idea to take a picture from that BSOD. Did you get any error message? If, yes, which one? You probably should only integrate the SATARAID folder as textmode and nothing else. You may try it, if the removal of the memory sticks doesn't help. That is not enough. You need a rock stable system (no overclocking and rock stable memory sticks).

Did you hit F6 and load any driver by floppy?If yes, this was the reason for the issue. The textmode drivers have to be integrated into the OS CD, when any unattended install option was used.

You should give us some informations about your system (mainboard, chipset, sort of hdd's etc.) and what you have done.

Fine, that you have solved your problem and thanks for giving us a step-by-step description how you succeeded.This will help other users with a similar problem. CU Fernando