Fernando 1

Have you already tried the FIXBOOT command?EDIT: If this doesn't repair your boot sector, you might have a hardware problem (hdd or RAM?). Another idea: Try to boot off the 32bit Windows XP CD with integrated nForce sataRaid drivers. When the XP Setup shows you the correct RAID partitions, format the partition, where you tried to install XP x64 and do a fresh install of Windows XP. Maybe you get a proper MBR this way.

I have often done that without getting any problems.Store the boot files (boot.ini, ntldr and ntdetect.com) somewhere before you run the fixmbr command.

This is absolutely safe, even with a RAID array.You will just get a new written MBR, no other datas will be touched.

@ HHawk: You mean, that the OS Setup cannot read the CD? Then you should burn the CD Image again, but with lower speed.

A 64bit OS like XP x64 is more sensitive regarding the RAM timings than a 32bit OS like XP. Yes, you should always take a clean source. I bet, that you will succeed with the installation, when you create a new nLited Cd with integrated nForce SataRaid drivers according my guide (first post).

It is not easy to help you with the BSOD, because this might have hundreds of reasons.My advice: Check your BIOS settings regarding overclocking and check your RAM sticks with MEMTEST or try to get Vista x64 installed with just 1 RAM stick. Regarding your previous error messages "Setup cannot copy file xyz" I have an idea: Is it possible, that you used a modified (not clean) XP x64 CD as source? Look into the i386 directory of your source CD (not the freshly nLited one). If you find a file named WINNT.SIF, I know the reason why you got the messages "Setup cannot copy file xyz.": The WINNT.SIF file contains the command for an unattended install. If Windows Setup finds a WINNT.SIF file, it is not able to copy the files of the drivers loaded by F6/floppy. Solution: You have to use a clean (original) XP x64 CD as source. If you create a bootable XP x64 CD by using a tool like nLite and you choose the "Unattended Install" option, you have to integrate the nForce textmode drivers. The F6/floppy method does not work with the "Unattended Install" option.

The answer stands within my guide (first post of this thread):

Check your RAM sticks or lower your RAM timings. You are welcome.

1. Start a new nLite session by using the actual nLite version.2. Don't use any nLited or otherwhise modified source. Take the original XP x64 CD as source for building your nLited CD. 3. Don't press F6 during Windows Setup. I would take the 64bit chipset driver package 6.86 and integrate the SATARAID drivers as textmode and the SATA_IDE as PnP driver.Good luck!

If you really tried to install Windows XP x64 with the nForce RAID driver named "NVRAID.SYS", the error message would be correct, because only the 32bit nForce RAID drivers have this name. The correct 64biit nForce RAID drivers are named "NVRDx64.SYS" or "NVRD64.SYS".Check the driver package you have used during the textmode driver integration. If you really find a file named "NVRAID.SYS", you have taken the wrong 32bit chipset driver package. NVIDIA itself has made the mistake, because the package named "nForce4_amd_6.69_winserver200364_english_whql.exe", which they offer on their FTP site and which you have downloaded, does not contain any 64bit driver. The 64bit version of the nForce chipset driver package 6.86 you get here, should be ok. Maybe you downloaded the wrong 32bit version of the 6.86 package, which is presented on the same site.

The problem is the combination of "Unattended Install" with the F6/floppy textmode driver installation method. Windows Setup doesn't find the floppy drivers, if you do an unattended install without intagrating the textmode drivers. Solution: Either don't use the unattended install option or integrate the VIA SataRaid drivers by using nLite. In the latter case don't hit F6 during XP Setup!

Your are right. It seems, that a required file is missing on your nLited CD.Look here: http://www.msfn.org/board/index.php?s=&amp...st&p=156691

I am happy, that you succeeded at least, although you tried the really hard way.....

I nearly cannot believe it, because the SataRaid drivers of the 6.53 package should run on every nForce4 RAID system.Are you sure, that your BIOS settings are OK, your nForce RAID shown as "healthy" and set as bootable? Which type (P-ATA, S-ATA1 or S-ATA2) and how many hard disk drives do you have in your system?

The last time I have manually edited these SIF files was in July 2005 and I didn't backup them. The actual TXTSETUP.SIF and WINNT.SIF files of my nLited XP CD wouldn't help you at all, because a ) they contain a lot of other informations which are not useful for you and b ) the WHQL driver integration method needs some other modifications done by nLite. Here is an easier way for you to succeed without using nLite: 1. Download the nForce chipset driver package v.6.53 from here and unzip it with a tool like WinRar. 2. Copy the content of the IDE\WinXP folder except the RAIDTOOL subfolder onto an empty floppy disk. 3. Boot from your original XP CD and press F6 when you are prompted to load SCSI drivers. 4. Load the drivers from your prepared floppy disk. You have to load both Controller drivers declared as "required". After having loaded both drivers, the XP setup should detect your RAID partitions. You won't get an endless reboot at the end of the installation. Once you have completed the XP installation, you can install all needed nForce chipset drivers by running the SETUP.EXE of the actual nForce chipset driver package suitable for your nForce chipset (probably the version 6.86). After a reboot the already installed old nForce SataRaid drivers v.5.18 will be updated to the actual version 6.66. Alternatively you can try a tool named RAID Slipstreamer. I didn't test it myself, but according to this post it should work with nForce SataRaid drivers.

I tried, but it doesn't run in windows 9x says it needs windows nt with sp4 and some version if IE I didn't know that.If you really want to create a WINNT.SIF file, you can do it manually by using notepad. Just edit the following: [Unattended] OemPnPDriversPath = "drivers\legacy" Then rename the file to WINNT.SIF and copy it into the i386 folder of your XP source directory. That is why I suggested to use a driver slipstreaming tool like nLite (needs an installed Microsoft .NET Framework) or XP Isobuilder (doesn't need .NET Framework). It is really a hard work for a newbee to manually create a bootable CD with integrated nForce SataRaid drivers. Even a small error while editing the SIF files will destroy your work at least. You are welcome.

Ah, you had already opened the DEPLOY.CAB file.Run the SETUPMGR.EXE file. Look here for further details: http://support.microsoft.com/kb/314472/en-us

Good luck!One last advice: If you integrate the nForce3 SataRaid drivers by using the 5.11 chipset driver package, don't additionally integrate the Ethernet drivers of this package. They are buggy! It's better to take the Ethernet drivers from the nForce chipset driver package v.5.10.

Are you sure to have looked into the SUPPORT\TOOLS folder of the original Windows XP CD?There must be a file named DEPLOY.CAB.

As far as I know you cannot simulate a hardware RAID configuration with VMWare. There is no reason to warry about slipstreaming the needed textmode drivers by using nLite. The integration method is well approved.

I don't know, but you should keep in mind, that the Vista nForce chipset driver packages are designed for Vista and not for Windows XP.With the TXTSETUP.SIF entries I quoted above I managed it to slipstream the nForce SataRaid drivers into a bootable XP CD. This is the way I did it: 1. Create a folder within your XP source directory like $OEM$\$1\Drivers\nVRAID (notice: you can name it "legacy" if you want) 2. Create a WINNT.SIF file by using the DEPLOY.CAB tool (within the Suppot\Tools folder of the XP CD) and add the driver path: OemPnPDriversPath = "Drivers\nVRAID" (in your case you should name it "drivers\legacy") 3. Open the TXTSETUP.SIF file (it's within the i386 folder of your source directory) and add the entries I quoted above. 4. Copy all SYS files of the nForce SataRaid driver folder (in your case the LEGACY one) into the i386 folder of the XP source. 5. Make the ISO file with a tool like Isobuster or UltraIso and burn your bootable CD That's all. Yes, if you don't find a WINNT.SIF file within your i386 directory, you have to create it. Otherwise XP Setup will not find the nForce SataRaid drivers path.

Yes.Here are the TXTSETUP.SIF modifications you have to do: [SourceDisksFiles] nvatabus.sys = 1,,,,,,4,4,1,,,1,4 nvraid.sys = 1,,,,,,4,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_10DE&DEV_008E = "nvatabus" PCI\VEN_10DE&DEV_0085 = "nvatabus" PCI\VEN_10DE&DEV_00D5 = "nvatabus" PCI\VEN_10DE&DEV_00EE = "nvatabus" PCI\VEN_10DE&DEV_00E3 = "nvatabus" PCI\VEN_10DE&DEV_00E5 = "nvatabus" PCI\VEN_10DE&DEV_0035 = "nvatabus" PCI\VEN_10DE&DEV_0036 = "nvatabus" PCI\VEN_10DE&DEV_003E = "nvatabus" PCI\VEN_10DE&DEV_0053 = "nvatabus" PCI\VEN_10DE&DEV_0054 = "nvatabus" PCI\VEN_10DE&DEV_0055 = "nvatabus" *_NVRAIDBUS = "nvraid" GenNvRaidDisk = "nvraid" [SCSI.Load] nvatabus = nvatabus.sys,4 nvraid = nvraid.sys,4 [SCSI] nvatabus = "NVIDIA NForce Storage Controller" nvraid = "NVIDIA RAID CLASS DRIVER"

What about you? You are welcome! It's an easy job, because all nForce chipsets are working the same way. The only thing to do is to integrate NVIDIA's fantastic unified nForce chipset driver package usefull for all chipsets, operating systems and other hardware configurations. Everything will work great - no requested help anymore! To be serious again: 1. Someone who reads 54 pages with more than 1.000 posts, is beyond help. The only important and still actual post is the first one of this big thread. It is not my fault, that it got such a volume, but the amount of posts and the number of views shows, that many users needed and got help here. 2. I would be glad if someone else would continue my work, because I did it long enough (since July 2005). Furthermore I don't have any nForce chipset mainboard anymore. 3. I am happy, that I got only a few comments like yours, because otherwise I wouldn't have spent so much time within this forum.

Well, your instructions didn't mention that part, so I just went ahead and added the sataraid folder alone.You misunderstood me. If you did what I have written within my guide (integration of either the LEGACY folder or alternatively the SATARAID+SATA_IDE folder), you have nothing missed. There is no need to copy any file from elsewhere into the SATARAID folder before integrating it, because the needed INF file (in this case the NVATA.INF) will be loaded by the additional integration of the SATA_IDE folder. When you have additionally integrated the SATA_IDE folder content, you have nothing to do with the NVATABUS.INF, because you got the NVATA.INF (with the same content).

That exactly is the point. Many nForce SataRaid users need to load the NVATABUS.INF or NVATA.INF, which is not within the SATARAID folder.Did you really just integrate the SATARAID folder and not additionally integrate the SATA_IDE folder content?