Fernando 1

What exactly do you mean by "one by one"? It doesn't look like I have a choice when it comes to integrating "both" drivers.He obviously meant, that he just integrated the SATARAID driver folder and no other nForce drivers.Notice: Tommaso has a mainboard with an nForce590 chipset. These chipsets do not need the SATA_IDE drivers to get XP installed.

Which mainboard do you have and which nForce chipset is it using?

Yes! If you are not sure, you should have a look into your mainboard manual.

Thanks for your post. Your remarks about the NTFS boot block size and the abilities of the NVIDIA MediaShield software are quite interesting and useful for experts like you. On the other hand you should consider, that I started this thread in July 2005 for owners of an nForce Sata/Pata-RAID system, who just wanted to get a working 32bit OS like Windows XP, Windows 2000 or Server 2003 with the newest drivers from scratch. After having read your post there are some questions remaining: 1. Why didn't you integrate any Service Pack into your Windows XP before beginning the OS installation? 2. What is the advantage/disadvantage of changing the default boot block size? 3. Which boot block size would you recommend for the "normal" user? Cheers! Fernando

Thank you, Tommaso, for your helpful and friendly report.According to your experience I have modified my guide (first post of this thread) to avoid similar problems of other users with the same nForce chipset. Thanks again! Fernando

It should be no problem to get a dual-boot PC with Vista x64 and Windows XP.My advices regarding the XP installation: 1. You should use default BIOS settings (no overclocking) while installing an OS. 2. Take/borrow an original untouched XP CD (without SP) or with integrated SP2 as source for creating a CD with integrated nForce SataRaid drivers. 3. Try to remove the X-Fi card during the XP installation. Concerning Vista x64 you should wait for better nForce chipset drivers.

Your "solution" is worth to be tried, if redrumy3 doesn't have a 64bit OS.I just wanted to certify dead0's speculation about the reason why redrumy3 got the error message by just slipstreaming the SP2 EXE file into XPx64 from within a 32bit OS.

You are right, you need to run a 64bit Windows OS.

Maybe you got the trouble because SP1 was already integrated.If you have the original XP x64 version (without SP1), try to use this source.

Thanks for your reply clearing up the device which was responsable for your problems. It is probably not a driver issue, but a hardware or firmware one. Your example shows, that it is not always a good idea to buy newest hardware technology.My advice: Ask the Seagate support for a solution. CU Fernando

So your installation ends always at the point of the first reboot (after Setup had loaded all files, but before the real installation and hardware detection begins). Is that right? That was a good idea.If you can get access to your broken XP installation (for example by booting with an MS-DOS or Windows Start floppy disk), you should look into 2 files of the WINDOWS directory: SETUPERR.LOG (has it any entry?) and SETUPLOG.TXT (interesting are only the last lines).

What exactly happened? I don't agree with you.I believe, that something else is responsable for your trouble. Check your BIOS settings (S-ATA ports should run in IDE and not in RAID mode), your S-ATA cables and the MBR of your hard disk drive.

Since you don't have a RAID array, you should be able to install Windows XP SP2 without hitting F6 and loading any special drivers.Look into your BIOS and check all IDE, S-ATA and RAID settings. Your S-ATA hdd and your IDE drive (CD-ROM) should be correctly recognized, RAID should be disabled. 1. You can check it by using the SeaTools from Seagate.2. No, this is very implausible as you don't have any IDE hdd. My suggestion: Check the BIOS settings and then try to install XP by booting off CD without hitting F6.

This did not work. I tried one disk with just the sata_ide folder added in, and I tried another disk having the sata_ide plus the ethernet and smbus drivers. The result is the same. After WinXP formats and copies files over, it restarts and gets hung in a re-boot loop.As you have no RAID, normally you don't need to load or integrate any textmode driver, when you want to install XP with integrated SP2.Your issue probably has another reason, but it is not easy to detect from far away. Questions: Are you sure, that your RAM sticks are ok? Check them with MemTest and try to remove one of them during the XP installation. Which driver did you load via F6 when you have successfully installed XP Pro? Did you add any new hardware since that time?

Answer 1: \nForceWinXP\11.09\MCP61\IDE\WinXP\sata_ide \nForceWinXP\11.09\MCP61\IDE\WinXP\sata_raid Answer 2: I don't want to create a RAID. I want my SATA drive to run Windows XP. It appears that SATA and RAID are very closely related when it comes to nForce chipsets, but my goal is to get WinXP to recognize and use my SATA drive. Solution for you: Don't integrate the SATARAID, but only the SATA_IDE subfolder of your nForce chipset driver package.

Which nForce chipset driver IDE subfolder did you load?Why did you create a RAID with just one single hard disk drive?

You posted within a 2 years old thread, which is not actual anymore.This thread will help you: http://www.msfn.org/board/index.php?showto...t=0&start=0 CU Fernando

Not all viewers of this thread had problems with NVIDIA's nForce RAID drivers, but at least nearly all of them succeeded with the creation of a bootable XP CD with integrated nForce SataRaid drivers.

Are you sure, a ) that you have set the correct BIOS settings after the last BIOS update (after flashing a new BIOS, you always get the "default" settings) and b ) that your floppy drive is working correctly? There is no need to rebuild the RAID array, if the RAID utility says it's "healthy". Yes - >300.00 users cannot be wrong! It is not necessary to create more than 1 nLited CD. If your nVRAID BIOS version is 4.84 or higher, you should integrate the SATARAID+SATA_IDE subfolder of the 32bit nForce chipset driver package 6.86.

Did you get the message "File txtsetup.oem caused an unexpected error (1024)..."?If yes and provided, that you booted off the clean (not modified or nLited) XPx64 CD, you probably took a wrong or corrupt driver combination. You either have done something wrong or you really have a hardware/configuration problem. There is a way to exclude the latter: 1. Download the old and not really native 64-bit nForce chipset driver package v. 6.56 (you get it here), unzip it and copy the content of the IDE\WinXP folder onto an empty floppy. 2. Try to install XPx64 by booting off the original XPx64 CD and loading the just prepared floppy drivers by hitting F6 at the begin of the OS installation. If even this standard and safe XPx64 installation fails, you probably have a hardware problem. First option: Check your RAM sticks!

Why don't you just follow my guide?Nearly 100.00 users cannot be wrong!

Thanks for your report.As you have realised, not all owners of a mainboard with an nForce RAID system will get endless reboots at the end of the installation, when they are using the F6/floppy method and load actual nForce SataRaid drivers. Nevertheless the integration of the nForce SataRaid drivers into a bootable CD by using a tool like nLite is an easy, safe and comfortable method for all users with such hardware configuration.

Please give us more informations:Which mainboard and which nForce chipset S-ATA ports are you using? Do you have a RAID array? Which driver did you integrate?

Another idea: From which source did you grab the drivers when you integrated them?Maybe the source drive was not OK or at least the driver path was too long (too many characters). Create a directory C:\SATARAID and put your favorite nForce SataRaid driver folders into that directory. Then run nLite again and try to integrate those drivers. After having created your nLited CD you can delete the driver folder.

I really have no idea concerning the reason for your message, but I found some links that might help you solving your problem:1. http://consumer.installshield.com/kb.asp?id=Q108488 2. http://forums.cnet.com/5208-7590_102-0.htm...ssageID=1429873 If you want further help, please post your experiences within this thread: http://www.msfn.org/board/index.php?showto...mp;hl=Parameter Maybe Nuhi or someone else can help you. CU Fernando