Important information for all users, who are here for the first time:
This thread has got a big volume with a lot of sites and hundreds of replies. There is no reason to waste time and to read them. All you need to know is laid down in this first post. If I get any new information, which might be important or useful, I will edit it into this post!
So this first post will always be up-to-date!
Last update: 09/02/2008


Introduction:

The problem:
None of the Pre-Vista Windows Operating Systems do contain drivers, which are able to detect and to use any nForce RAID Controller. Unless the suitable nForce Sata/PataRAID drivers are separately presented by the user, the OS installation fails, because the OS Setup doesn't find the RAID device and its partitions.
The traditional way to provide the needed drivers is the F6/floppy method, but this method has some severe disadvantages:

1. A floppy drive is needed, but not available at many actual desktop computers and notebooks.
2. Floppy disks are the worst data storage media regarding the file integrity. Bad floppy disks are the main reason for corrupted driver files.
3. Even if you load the correct nForce driver and the RAID is detected by the Setup, the OS installation may end with a BSOD or endless reboot loops.
   The reason for this phenomenon is the fact, that the MS Operating systems prefer to install the MS IDE Controllers and drivers instead of the special NVIDIA nForce S-ATA/P-ATA ones, which are absolutely needed for Sata/PataRAID systems. At the beginning of the installation procedure (during the TEXTMODE part) the loaded nForce textmode drivers are accepted and able to detect the SataRAID/PataRAID Controller, but after the first reboot - during the hardware installation part of the installation - the correctly detected nForce S-ATA-/P-ATA Controller may be replaced by the absolutely wrong MS Standard Dual Channel PCI IDE Controller. The consequence is a system crash at the last reboot.

The better alternative is the integration of the needed textmode drivers into a bootable OS CD. Only this way the user can be sure to succeed with the installation of the OS onto an nForce RAID array. Nevertheless the developers of the driver integration method had to solve the above specified problem (see point 3). Until 2005 the correct installation of the needed Controllers and drivers needed addtional manual work of the user. They only succeeded after having created special folders and edited some SIF and/or OEM files.

The solution:
The safest and easiest way to get the problematic nForce textmode drivers properly installed is to integrate them by using a tool like nLite. All actual versions of nLite (Since v1.0 Final) have incorporated a special method, which guarantees the successful OS installation onto any nForce RAID system (if the user observes some rules layed down below). The replacement of the correct nForce Controllers and drivers by the "wrong" MS IDE ones will be prevented by the incorporated suppression of the MS IDE drivers during the hardware detection part of the OS installation.
Advantages:
- fully automatic method (without creating new directories or editing SIF or OEM files)
- support of not digitally signed textmode drivers
- without restriction of any kind during the use of nLite

Here is the way how to do it:



Important Requirements:

You only will succeed with the integration of the nForce SataRaid drivers, if you have

• a correctly created nForce RAID array (shown as "healthy" and set as bootable, for further information look here)
• an up-to-date mainboard and nVRaid BIOS (= MediaShield IDE ROM), which is part of the mainboard BIOS. Actual nVRaid drivers may need a Raid Bios v. 4.81 or higher.
• a stable system (proper RAM modules and stable BIOS settings)
• an original (=untouched) OS CD as source (don't use or reuse a source, which has already been processed by nLite!)
• a proper working IDE-connected CD or DVD drive
• an enabled ACPI power management (within BIOS, don't disable it by nLite settings).

Tips:

1. You can see the nVRaid BIOS (=MediaShield) version of your system on the second boot screen. If you can't get a Raid BIOS version v. 4.81 or higher after having flashed the latest mainboard BIOS, you might get problems with the integration of the latest nForce SataRaid drivers.
2. The successful integration of the nForce SataRaid drivers into a bootable OS CD requires the presence of the latest available Service Pack (SP) of the used OS. If your OS CD does not contain any SP, you should integrate the latest SP as first step, when you are going to create your nLited CD with integrated nForce SataRaid drivers.
3. XP 32bit (x86) only: If possible don't try to slipstream SP3 into an XP SP1 or SP2 CD. In this case it's better to take an original ("Gold"/RTM) OS CD without any SP as source for slipstreaming SP3 and the nForce SataRaid drivers. Otherwise you may get problems during the installation of the nLited CD.
4. It is a good idea to unplug all unnecessary external hardware devices during the installation of the OS with integrated nVRaid drivers.
5. If you have any hard disk drive outside your RAID array or a plugged-in USB stick, you may get the problem that the MS Setup routine tries to install the master boot record (MBR) onto that non-RAID device, although you have set the RAID array as first bootable hard disk drive within BIOS. The only sure way to prevent this is to unplug these non-RAID devices during the installation of the OS. After the successful installation they can be reconnected without any problems.

Now possible for nearly everyone:

Get actual WHQL certified nForce SataRaid drivers from scratch

The above mentioned and approved methods to integrate the nForce SataRaid drivers into a bootable XP CD were primarily documented by me in July 2005. Meanwhile NVIDIA has released a lot of new nForce chipset driver packages with WHQL certified nForce Sata and Raid drivers. You can find them within the SATARAID and SATA_IDE subfolders. The problem was, that users with some (mostly LEGACY mode) nForce SataRaid systems obviously could not use them during the installation (to avoid BSOD's or endless reboot loops at the end of the OS installation). They had to take the not digitally signed LEGACY drivers.

After a lot of new tests with the current version of nLite I figured out, that it is possible to get the newest WHQL certified nForce SataRaid drivers installed even onto LEGACY mode nForce SataRaid systems, when you do a special combination of the nForce SataRaid driver integration:

• Integration of the SATARAID subfolder (from the suitable nForce chipset driver package) as TEXTMODE driver and additionally
• Integration of the SATA_IDE subfolder (from the same nForce chipset driver package) as PnP driver!

At the end of the successul OS installation I had a flawlessly running XP (32/64bit) or W2k3 (32/64bit), all nForce IDE drivers (the SATA and RAID ones) were WHQL certified.

Advantages of the WHQL driver integration method:

• A running Windows XP is optimally prepared for a later upgrade with Vista, when it has WHQL certified SataRaid drivers from scratch (Vista Setup looks for the drivers which were installed first of all during the XP installation).
• By using this new method you will get at the end the MS IDE instead of the NVIDIA P-ATA (=IDE s/w) driver (a lot of nForce users have troubles with the NVIDIA ones). Remark: If you don't want the MS IDE drivers, you can easily replace them by the NVIDIA IDE driver after the end of the OS installation.

These findings are a big step forward for nearly all users with an nForce SataRaid system. This new method works with nearly every nForce chipset (except nForce2 and nForce3).

1. nVRaid Driver Choice and Preparation:

Although nLite allows the correct integration of the actual nForce SataRaid drivers and prevents the installation of the wrong MS IDE standard drivers, the biggest problem is the creation of the optimal nVRaid driver prepackaging. The choice of the best driver version and combination depends on the system (Chipset details and Raid BIOS version) and the OS. NVIDIA has complicated all this, because they often change the composition of their driver packages and even the names of the files for not understandable reasons. Nevertheless I found a solution, which should be suitable for nearly everyone.

A. Preparation for the WHQL driver integration method:

• Normal option for mainboards with any nForce chipset (except nForce2 and nForce3):
  The preparation is very easy, because all you need is the suitable actual nForce chipset driver package.
  You can find the newest and probably best nForce chipset driver combination pack for all nForce 4-6 series chipset mainboards within this post.
  Alternatively you can search for a suitable driver pack at NVIDIA's drivers homepage. In this case you should know the exact name of your nForce chipset (look into your mainboard manual or google for it). If you want to use the official nForce chipset driver pack, which NVIDIA is offering for your chipset, you should go here and choose the correct "Product Type" (take "nForce"), "Product Series" (chipset generation), "Product" (special chipset) and "Operating System" (OS you are going to install).
  Download the nForce chipset driver package of your choice and unpack it by using a tool like WinRar or 7-zip.
• Alternative option for socket 754/939 mainboards with an nForce4, nForce4xx or nForce5xx chipset:
  Some of the nForce chipset packages offered by NVIDIA are already old. If you want new and suitable nForce IDE drivers from scratch, you should choose this WHQL driver choice option.
  Fujitsu-Siemens has published very good and stable nForce IDE drivers v.6.99 dated 05/15/2007. They are WHQL signed and usable for all mentioned nForce chipsets. Users, who want to integrate these drivers, should download the suitable (32bit or 64bit) SATARAID and SATA_IDE packages from the FSC support sites.
  
  Here are the links to the 32bit packages, usable for XP, W2k and W2k3:
  32bit nForce SATARAID drivers v.6.99 WHQL and 32bit nForce SATA_IDE drivers v.6.99 WHQL.
  
  And here are the links to the 64bit packages, usable for XP x64 and W2k3 x64:
  64bit nForce SATARAID drivers v.6.99 WHQL and 64bit nForce SATA_IDE drivers v.6.99 WHQL.
  
  Unpack both SATARAID and SATA_IDE packages and store them somewhere. You will need them for the later driver integration. The extracted "SATA_RAID F6 driver disk 32/64Bit" folder contains the SATARAID textmode drivers (has a TXTSETUP.OEM file), whereas the "SATA DRIVER 32/64Bit" folder is similar to the "SATA_IDE" folder (contains just the nForce S-ATA driver as PnP driver).

B. Preparation for the traditional LEGACY driver integration method:

Get the newest nForce IDE drivers onto nForce2 or nForce3 chipset mainboards (suitable for nForce4 PataRaid systems too)
If your mainboard BIOS contains an appropriate nVRaid BIOS version (4.81 for nForce2/3, 4.84 for nForce4), it is possible to get the newest 32bit nForce SataRaid drivers v.6.99 dated 05/15/2007 installed onto an "old" nForce2 or nForce3 SataRaid system. Owners of an nForce3 chipset mainboard or an nForce4 PataRaid system even have the chance to run XP x64 or W2k3 x64 by using the modified 64bit nForce IDE drivers v.6.99.
To make it easier for you I have customised the nForce IDE drivers 6.99, put the needed files into a LEGACY folder (to make clear, that they are modified and not WHQL anymore) and uploaded them to Rapidshare.
You can download the small LEGACY driver package, which is suitable for the OS you are going to install (32bit or 64bit), here:
modded 32bit nForce LEGACY drivers v.6.99 (usable for XP, W2k and W2k3)
modded 64bit nForce LEGACY drivers v.6.99 (usable for XP x64 and W2k3 x64).
Unzip the package by using a tool like WinRar or 7-zip and store the LEGACY folder somewhere.

Other suitable nForce LEGACY IDE drivers ("last chance" drivers for problematic chipsets)

A. LEGACY drivers for XP, W2k and W2k3 (32bit):

• Users with an nForce2, nForce3 or nForce4 chipset, who don't succeed with the previously mentioned drivers, should download this nForce chipset driver package containing nForce IDE drivers v.6.67. Although this package was mainly designed for Vista Beta2, it works flawlessly with XP, W2k and W2k3 too.
  Unzip the package by using a tool like WinRar or 7-zip and store the IDE\driver\LEGACY subfolder somewhere. You will need no other preparation.
• Users with an nForce2 chipset can take this official nForce chipset driver package v.5.10 (usable for Windows XP and Windows 2000).
• Users with an nForce3 chipset will find here the latest official 32bit nForce chipset driver package 5.11 (usable for Windows XP and Windows 2000)
  Warning: Don't use the Ethernet drivers of this package, they are broken!

B. LEGACY drivers for XP x64 and W2k3 x64 (64bit):

• Users with an nForce3 or nForce4 chipset can take one of the available x64 NVIDIA nForce chipset driver packages v.6.67. For the integration into an XP x64 CD you should take the one you get here, whereas users, who want to create a W2k3 x64 CD, should take the one you get here.
  Just unzip the suitable package and store the LEGACY subfolder somewhere.
• The only 64bit nForce chipset driver package published by NVIDIA for nForce3 chipsets is the very old Beta package v.6.25. You can get it here.
  Unzip the package and store the IDE\WinXP folder somewhere.
• Users with an nForce3 or nForce4 chipset mainboard, whose nVRaid BIOS cannot be updated, may try the old and not natively 64-bit nForce package 6.56 (downloadable here).
  Just unzip the package and store the IDE\WinXP folder somewhere.

2. Processing with nLite:

This is what you should do:

• Ensure that you have installed the newest nLite version and that you have administrator rights.
• Create a new folder somewhere on any available hard disk drive and name it as you like (for example "XPCD" or "XPx64CD") .
• Copy the whole content of the original OS CD into the just created folder. Don't use any already nLited or modded source.
• Open nLite and do what you want, but you must choose the button "Integrate Drivers".
• Within the "Integrate Drivers" part of nLite you have to hit the "Insert" button, choose the "single driver" option and point to your just prepared nVRaid driver subfolder LEGACY or SATARAID (depending on the driver integration method you are going to use) as textmode drivers. You will get the following popup window:
  Click to view attachment
  If you have an nForce SataRaid system, you have to take both of the nForce Sata/Raid Drivers/Controllers (NVIDIA RAID CLASS DRIVER and NVIDIA nForce Storage Controller) nLite shows within a popup window as "required". To make it easier for you, nLite has already enabled both needed drivers. (Notice: Users with a non-Raid nForce S-ATA system, who want/have to integrate the nForce S-ATA driver as TEXTMODE, should only load the required "NVIDIA nForce Storage Controller".)
• For users with an nForce 5xx or 6xx chipset mainboard I recommend to integrate just the content of the SATARAID subfolder as textmode driver. The additional integration of the SATA_IDE subfolder is not needed and may not work with all of these new nForce chipsets.
• If you are using the new mixed SATARAID/SATA_IDE integration method, you have to integrate the SATARAID subfolder as textmode driver and additionally the SATA_IDE subfolder of the same package as PnP driver.
  Important notice: The additional integration of the SATA_IDE subfolder is not the best choice for all nForce SataRaid users. Users, who don't want to additionally integrate the SATA_IDE subfolder should pay attention, if they are using any nLite version released before v.1.4 Final: Some former nLite versions (v.1.2 until v.1.3 Beta) have done the additional integration of the SATA_IDE subfolder automatically, when users offered the SATARAID subfolder of a complete nForce chipset driver package. Since nLite v.1.3 RC this automatic behaviour has been replaced by a popup window question during the driver integration processing. With nLite v.1.4 Final even the popup window regarding the additional integration of the SATA_IDE subfolder has been removed. This may avoid irritations with users, who don't want or don't need to additionally integrate the SATA_IDE subfolder.
• Users, who want or have to use the LEGACY driver integration method, should just integrate the LEGACY subfolder of their prepared driver package (see above). They may not integrate any other IDE subfolder (neither SATARAID nor SATA_IDE).
• Since nLite v. 1.0 RC7 you have the choice between a single driver or a multiple driver folder integration. You should integrate the nForce SataRaid drivers with the single driver option. Only this way you can be sure, that nLite integrates the correct driver subfolder which you have prepared earlier.
• Then you can integrate the other nForce drivers (SMBus, Ethernet etc.) as "normal drivers". Only users with an nForce4 system may take them out of the same NVIDIA chipset package they used for the integration of the SataRaid drivers. Users with an nForce2 or nForce3 system have to integrate these drivers (and the GART ones) from special packages suitable for their chipset.
• Tip: If you want to integrate any graphic adapter driver, take a WHQL-certified version (Warning: don't take Forceware v. 91.33 - you may get endless reboots at the end of the install!).

• Let nLite create the ISO file and burn it as bootable CD. If you are using the burning software Nero, just choose "Recorder" > "Burn Image" and point to your just created ISO file. Burn at no more than 8x(DVD) or 24x(CD) and choose the "Verify" option to avoid any burning errors!

At the end you will have a bootable 32bit or 64bit Windows OS CD with integrated NVIDIA Sata/Raid drivers - no F6 and no floppy will be necessary.


Tips for the Installation of the OS:

• Make sure that your BIOS settings are ok. You will only be able to install the OS by booting off your nLited CD, when the CD-ROM device with your nLited CD is set as first bootable device.
• Before you begin with the installation of the OS by using your nLited CD, make sure that there is no floppy within your floppy drive, no USB stick within any USB port and no Memory Card within your Card Reader.
• If you are using more than 2 GB of RAM, it is a good idea to remove 1-2 sticks during the OS installation (otherwise you may get a lot of errors during the OS Setup). Once the OS is up, they can be reinserted.
• Don't hit F6 and don't insert a driver floppy if you install an OS by using a CD with integrated nForce SataRaid drivers!

Good luck!


CU
Fernando





The easiest way to get the Raidtool installed is by running the SETUP.EXE of the associated nForce chipset driver package, but by doing this all nForce IDE drivers of the package will be installed too (and maybe replace the better and currently working ones).
In these cases you have to use another way to get full access to the MediaShield/RAID software (NVIDIA Control Panel) after having completed the OS installation.
Here is the guide for the manual installation of the nForce Raidtool (on the basis of a post from nForcersHQ forums member TheMaxx32000):

• Run your just installed OS.
• Create a new folder named "RAIDTOOL" somewhere within your currently running OS partition (for example within the directory "\Program Files")
• Search for the RAIDTOOL folder of the actual 32bit/64bit XP/W2k/W2k3 nForce chipset driver package
• Extract the RAIDTOOL.cab into the just created RAIDTOOL folder of your OS partition
• Open the RAIDTOOL folder with the extracted files
• Doubleclick the REGRAID.BAT (you will find it in older Raidtools) or REGRAIDSEDONA.BAT (actual file name of the Sedona type Raidtool) to register the Raidtool Services
• Run the NVRAIDMAN.EXE (normal MediaShield) or NVCPLUI.EXE (Sedona type NVIDIA Control Panel)

Now you will see the MediaShield Control Panel. It should also appear as NVIDIA Control Panel within the Vista Control Panel, but if it doesn't, try to install nTune on top.
For further information about the abilities of the NVIDIA MediaShield software you should open the MediaShield help file (as .chm or .pdf), which you will find within the extracted raidtool files.
Suggestion: You should create shortcuts to the .EXE files of the RAIDTOOL folder and put them into your Startmenu folder. This way you will get an easy access to all services of the MediaShield/Raidtool.

Annex II

Tips for users with a non-Raid nForce S-ATA system

• The actual versions of Windows XP (32/64bit) and Server 2003 (32/64bit) should be able to detect nForce S-ATA Controller connected hdd's without any 3rd party drivers, provided that you have done the needed BIOS settings (you have to choose the IDE mode of the S-ATA Controllers). So normally there is no reason to hit F6 or to integrate the nForce SATA drivers as TEXTMODE drivers.
• Nevertheless it is possible and useful to integrate the nForce SATA drivers as normal device (=PnP) drivers into an nLited CD. The way is simple: Just integrate the content of the SATA_IDE subfolder of the actual nForce chipset driver package, which is designed for the special nForce SATA chipset of your mainboard (look at NVIDIA's driver page). This PnP driver integration is very easy with nLite. Just click at one of the INF files you find within the SATA_IDE folder, it doesn't matter which one.
  
• New and important for users with an AHCI capable mainboard:
  Some actual nForce chipsets (for example nForce 520, nForce 630a/610a or nForce 630i/610i) have advanced S-ATA features named "AHCI". If your RAID Controllers are disabled and the S-ATA Controllers are set to "AHCI Mode" within the mainboard BIOS, the SATA drive(s) is/are not detected at the beginning of the OS installation, unless the required special nForce S-ATA drivers have been loaded or integrated as textmode drivers. Vice versa users with an AHCI supporting nForce chipset mainboard will only be able to get the actual AHCI supporting nForce S-ATA drivers installed, if the NVIDIA S-ATA Controllers are set to "AHCI Mode" within the BIOS before they are going to install the OS.
  Choice of the suitable driver and integration method:
  Users with a non-RAID, but AHCI capable nForce chipset system should look into the SATA_IDE folder of the unzipped nForce chipset driver package, which is suitable for their mainboard chipset. If you find there a file named TXTSETUP.OEM, you should integrate just the content of the SATA_IDE folder as textmode driver.
  Alternatively you can integrate the SATARAID folder (which always has a TXTSETUP.OEM) as textmode driver (similar to the instructions for real SataRaid systems), but in this case only the offered "NVIDIA nForce Storage Controller (required)" should be loaded during the textmode driver integration part of the nLite processing. Don't load the "NVIDIA RAID Class Driver (required)", if you don't have an nForce RAID.
  Attention: These options are only valid, if the NVIDIA RAID Controllers are disabled within the BIOS. Otherwise you have to use the "normal" SataRaid driver integration method as layed down above (SATARAID as textmode driver and SATA_IDE as PnP driver).
• Some mainboards (for example ASUS ones) have no SATA, but only SATARAID ports. Have a look into your mainboard manual, if you have to enable SATA and RAID within your BIOS, even when you have not built a RAID array. In this case you should integrate the SATARAID folder of the suitable nForce IDE drivers and load both "NVIDIA nForce Storage Controller" and "NVIDIA RAID Class Driver" (as written above for real nForce RAID arrays).

are you using the newest driver to test it?

nForce4 AMD Edition (6.66) - Windows XP Professional x64

Version: 6.66
Release Date: July 15, 2005
WHQL Certified

International
File Size: 38 MB
WHQL Certified

THANK YOU!

Very good of you Fernando 1. I will surely give this a try. I am sure this info will be helpful to Nuhi in future releases. Whatever happened in beta 5 im sure will be fixed in the next release as you proved beta 4 works fine. Perhaps the info you just stated can be automatically done by nlite in the future with the created of directories, placing of files etc. I will give this a try shortly and let you know!

Yes, I tested it with these drivers from the chipset package 6.66 (32-bit on Windows XP and 64-bit on Windows XP x64 Edition).

The package is published as WHQL-certified, but the drivers, which make the biggest problems integrating them into a CD, the NVATABUS.SYS (32-bit) and NVATAX64.SYS (64-bit) are not!

this method doesnt work with the NF3 nvraid drivers either (Shuttle SN95G5) and using the 6.56 driver set on xp64. Also doesnt work with the lastest official set, 6.25

Same reboot on startup as was occuring with the other method.

Hi, Thanks Fernando for your work, but can you clarify something...

nvatabus.inf is only found in this nForce4 folder... IDE\WinXP\PATARAID

I want to install SATA RAID which I assume should come from... IDE\WinXP\SATARAID where the only INF file is called nvraid.inf (not nvatabus.inf)

Can you clarify what INF and directory I should be using to slipstream drivers for a SATA RAID drive array?

Thanks.

I have tried this with the SATA drivers from Nvidia Release 6.53, it worked , Motherboard is an A8N-Sli Deluxe. just needed to change nvatabus.inf to nvraid.inf and it worked without a hitch

Thats right! You have to take the nvatabus.inf file from the folder PATARAID.
I will clarify this in my first post.
CU
Fernando

This is confusing (sorry if I'm an id*** but this really is not clear)...

You've clarified that nvatabus.inf must come from PATARAID folder (even for a SATA RAID array which makes no sense but I will trust you on this)... What about the other two files (idecoi.dll and nvatabus.sys)? Does it matter where they come from?

Also, When you say "integrate the latest NVIDIA Sata/Raid drivers as textmode drivers" ... What freakin directory are you integrating in nLite?
- \PATARAID or \SATARAID?

Why are you using PATARAID drivers to setup a SATA RAID Array?

You are right - it seems to be confusing, but this exactly is the trick of the method I described here in this thread. The [OemInfFiles] method enforces the installation of the needed, but still not WHQL-certified driver NVATABUS.SYS and prevents, that Windows XP installs the wrong MS Standard-IDE-Controller driver.

When you have a SATA RAID system, you have to integrate the files of the subfolder SATARAID as TEXTMODE driver by nLite. (When you have a PATA RAID system, you have to take the files from the subfolder PATARAID.)

Nevertheless you have to copy the file nvatabus.inf from the subfolder PATARAID into the fresh created subfolder OEMDIR. This file is not a driver, but it is needed to give MS informations how to install the driver NVATABUS.SYS. When you look into the subfolder SATARAID, you can find the needed driver NVATABUS.SYS, but no information file for this driver (NVATABUS.INF). That is the reason, why you have to take the one from the PATARAID subfolder.

Hoping, that I did not confuse you more than before
Fernando

That explains it... Thanks!

So even if I am using SATA Raid I will still need to copy the nvatabus.inf from the PATARAID folder?

Thanks.

Yes!
Otherwise the necessary driver NVATABUS.SYS would not be installed and your system would not work after the installation.

This is quite a discovery for me as I am facing problem installing Windows on Raid with F6. Maybe it is becoz I did not copy nvatabus.inf to the diskette that make the installation fail.

Thanks a lot.

You did save my day!! After using the file "nvatabus.inf" from the subfolder PATARAID, my Raid-0 is up and running again.

Thank you very much.

When using your suggestion and nlite should i select oem preinstall option in nlite when doing the unattended setup?

Yes, let it as it is (activated).

arggg!
Im still getting the bsod and reboot failure after install, using Nlite B4, and your solution and using the 7.13 drivers!

the 6.53 works perfectly when using nlite b5 without any other modifications. Why dont later ones do that?
I checked the all the folders in the 7.13 package all the files seem to be the same wether its pataraid, sata_ide or sataraid, how come?
And why is the 6.53 only one folder for everything?

Just Wonderng if this can be applied to an already slipstreamed SP2 Volume Lisenced XP cd (off my work place) or does it have to be an OEM. My copy does not have the WINNT.SIF in the i386 folder, only a TXTSETUP.SIF Within this file there is no section [Data], only a [SetupData].

Anyone know if the same changes to the files mentioned can be done, and if it will work...

Thanks for a great guide...

Because NVIDIA changed the structure of the nForce drivers (for example by building seperate subfolders for PATARAID, SATARAID and so on).

You find several identical files in different folders, but the content of the folders is different.

See above. NVIDIA seperated the files later, because there could be some misunderstanding between the inf-files and the different drivers, when they were all together in 1 folder.


You can use an already slipstreamed SP2 VLK version of Windows XP - no problem at all..
There is no WINNT.SIF within an original Windows CD. This file has to been created by the user or is automaticly done by a tool like nLite, when you create an Unattended Install CD. So if you use nLite and do not use the option "unattended Install" there will be no WINNT.SIF. It is built after the end of the processing procedure of nLite. So, if you interrupt nLite without letting finishing his work, you won't see a WINNT.SIF.
The TXTSETUP.SIF exists on a normal CD, but nLite writes a lot of things into this file about the drivers. Let nLite finish, then you can see a lot of informations in this file.

Why wont beta 5 work with the 6.66 drivers if i do the method you outlined? Beta 5 will work fine with the older 6.53 drivers though wont it? I saw a couple of users mention it worked fine for them.

Your first question can only be answered by Nuhi.
Here is what he has written about the small changes between beta4 and beta5 concerning hardware (HW) detection and the integration of chipset drivers:

It may be, that nLite beta5 works fine with some old nForce Sata Raid drivers. I did not test it. NLite will definitely not work with the nForce chipset packages 6.66 and higher).
So if you want to integrate the old chipset drivers (between v. 5.10 and v. 6.53), you can try nLite beta5 without making any changes I described in post 1 of this thread.
But normally people want to have the newest drivers (although they are not always the best), when they build up a new system. A later upgrade of Sata Raid drivers is not so easy and maybe dangerous too in some cases.

Hey Fernando1!
Can you explain the differences in those two txtsetup.oem below

the first one is from the 6.53
and the second one is from the 7.13, but 6.66 is the same too.


6.53

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV <----
driver = d1,nvcchflt.sys,FILTER
inf = d1, nvatabus.inf <---
dll = d1,idecoi.dll
catalog = d1, nvata.cat

in the 6.53 there is both driver and inf entries for nvatabus.sys (marked with arrows)
--------------------------------

7.13

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV <---
inf = d1, nvraid.inf <---
dll = d1,idecoi.dll
catalog = d1, nvata.cat

The 7.13 just have an entry for the nvatabus.sys, and an entry for nvraid.inf instead.

I have now tried to slipstream those 7.13 raiddrivers like a hundred times now with different configurations, using your solution and nlite B4, and using only nlite b4 and nlite b5, but nothing seems to work.

What i wonder is would installation of the 7.13 drivers work when doing the
installation the old fashioned way with the F6 method, without copying the nvatabus.inf to the sata_raid folder??

You may try it and I will try to integrate the SataRaid drivers from v. 7.13 into Windows XP with nLite once more.
A better help would be possible, if I knew your hardware combination (chipset of your board, Sata Raid or Pata Raid).

Although I am not an expert in configurating txtsetup.oem files I will try to answer your first questions too:
You cannot compare a txtsetup.oem file, which is dedicated for all chipset combinations (Sata/Pata/SataRaid/PataRaid) as in packet v. 6.53, and a txtsetup.oem file from a special subfolder (SATARAID, PATARAID and SATA IDE) as you will find it in the v. 7.13 (Question: From which subfolder did you take the 7.13 OEM-file?).
The other big difference between both driver packages is the missing of the filter driver nvcchflt.sys in the newer NVIDIA chipset driver packages.

i got the oemfile from sata_raid folder.

And im running an Amd 64 3200 cpu on a DFI Lanparty UT 250, which has the Nforce 3 Ultra chipset.

Yes, youre right, one shouldnt compare apples with bananas...

But my point is, if i was to make a driver floppy for my sata raid to install winxp32 with the F6 method which files would i have to copy to the floppy? is it enough with the sata_raid folder files?
The point being is there something wrong with the driverpackage? , i mean the official 6.66 is similar in layout and would surely work for updating when your systems online, but would it work when using the F6 method and new install? since that .inf file obviosly isnt where it should be.

You are certainly right. The NVIDIA nForce drivers are making a lot of problems.

I just googled a little bit and found a very interisting message for all owners of a pc with nForce3 chipset and a Sata Raid system within this page:
http://www.nforcershq.com/forum/latest-dri...-3-vt60240.html

In one of the posts you can read, that it is possible to install the drivers from the package 7.13 on a mainboard with an nForce3 chipset, but you have to take the ones laying in the PATARAID subfolder (they even work for Sata systems). If you use the files laying in the SATARAID subfolder, you will get a crash of your system.

Would you test this using my method? The only difference would be, that you take the drivers from the PATARAID subfolder as Textmode drivers. That would be very helpfull for all owners of nForce3 chipsets.
Maybe it is easier for you to test it with F6 method. Put just the files from the PATARAID subfolder of the 32-bit 7.13 onto a floppy!

Thank you Fernando!
Ill try that and get back to you in awhile.
Thanx for the tip

Here is my experience slipstreaming 6.66 SATA RAID drivers on XP SP2 Install CD...

First let me say that Fernando, you Rock for figuring this out.

I think it is worth pointing out (assuming I am correct) that the integration of drivers in nLite (which is the first step) is really only to address the Text Mode portion of Windows Install. This is what saves you from having to use a floppy and F6 during initial setup. For whatever reason (lack of WHQL certification I believe) it does not then use these same drivers later for Windows GUI mode installation.

The first time I tried this process, for some reason, nLite did not grab the file nvatabus.sys for inclusion in the install. As a result, half way through loading the text mode drivers, it said "nvatabus.sys file not found" and halted. I redid the process and this time verified that nLite had grabbed the file by checking in the I386 folder for nvatabus.sy_. It worked fine the second time.

The second part of your process where you are copying files to the OEMDIR folder is for the Windows GUI mode install. After doing some research this is a common technique for installing non WHQL certified drivers during Windows GUI mode install.

Overall, it worked well for me the second time. I not only integrated the RAID drivers but also used nLite to integrate the rest of the nForce drivers. Note that when integrating other nForce drivers you only need to select one INF in each of the relevant subdirectories you want to integrate... nLite grabs everything in that directory regarless of what INF file you select for integration.

Good luck to others.

If someone knows how to install the NVRAID Windows tool after slipstreaming the driver install, I would be keen to know.

I have now tried slipstream with your solution and used the pataraid drivers instead. But still BSOD!!

I read the post that your referring to at nforcershq, but it doesnt say if it works when doing a fresh install using the F6 or slipstreamed.
Because i can update the raiddrivers manually when online, so it cant be the wrong drivers.

I made it work when using the F6 but using the txtsetup.oem from the patadraid and using drivers from sataraid and copy that nvatabus.inf from pataraid to sataraid.

But i cant get it to work when slipstreaming it.

AFAIK this tool das not make a Raid, it only shows it.
So you can install this tool as every other program, when you have installed your slipstreamed OS.

Thank you for your comment. When you have done such a work, it really is a good feeling, that somebody posts, that he has got it working too.

Meanwhile I tested the method described in the first post once again using the NVIDIA chipset package 7.13. It worked flawless on my nForce4 Sata Raid system.

Then I made another test with nLite 1.0 beta5 trying to integrate the SataRaid drivers without the [OemInfFiles] method. This time I used the 7.13 drivers from the (for Sata Raid systems wrong) PATARAID folder as Textmode drivers. Result: endless reboots!
Conclusion: To take just the drivers from the PATARAID subfolder is not the solution for the problems.


Maybe you have to change only the txtsetup.oem in the subfolder SATARAID and then it works? The system can grab the nvatabus.inf from the $OEM$ folder during GUIMODE section, so you do not need to put it into the SATARAID subfolder.
Do you like to test this?

well, i dont know if i really understand, do you mean i dont copy the nvatabys.inf to the sataraid folder but only to the OEM dir?
Would that make a difference?
I have compared the txtsetup.oem files from pata and sata and the only
difference is the nvatabus.inf entry and a catalog file entry
I have now changed the txtsetup.oem in the satafolder so it also have the nvatabus.inf entry and removed the nvraid.inf, because it is already there under the [Files.scsi.RAIDCLASS] section.

It was this way i made work with F6 method but havent been able to slipstream it.

And many thanx for your help it is much appreciated.

fernando, you have made about 5 seperate threads regarding nvraid integration, just use 1 thread, add replies when you find new things out, it saves alot of hassle for us and nuhi.

You may try to copy the nvatabus.inf into the SATARAID folder too, but as you realized by F6 method, MS does not need this file during the first (Textmode) section of setup. Everything is okay, when your Raid array is correctly detected (as 1 hard disk drive) during this section.
During the next part of installation (GUIMODE) the setup routine can grab the nvatabus.inf (necessary for installation of nvatabus.sys) from the folder X:\$OEM$\$$\OEMDIR. So it will not be necessary to put the nvatabus.inf into the SATARAID subfolder. But you can do it nevertheless.

I know only about 3 threads opened by me and running now.
It will not be easy to continue with 1 thread, because the integration of the drivers into a 32-bit OS is another thing as the integration into a 64-bit system.

The 3rd thread with my experiences during the tests with nLite b5 can surely be closed, although this thread will be the most interesting for Nuhi and his team.

How can I do it? Can the topic starter change the title of the thread?

I just got a Junior (>50 posts), 5 minutes ago I was a Newbee.

YEEHAA!!
Thats the way to go!! Now it works!!!

Thanx, Fernando!

Thnx Fernando, I'll give it a try...

Congratulations, Metalljens, and thank you for your patience.

How have you done it at least? Did you only change the textsetup.oem or did you copy the nvatabus.inf into the SATARAID folder too? Which chipset driver package version did you use?

The answers may be important for other users with nForce3 systems. Thanx for your reply.

I used the sata_raid 7.13 drivers, and first used nlite to integrate the drivers and did your solution with an oemdir and copied the nvatabus.inf from the pata_raid folder ONLY to the oemfolder and changed the section below in sata_raids txtsetup.oem to look like this:

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf <--- old value was nvraid.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat

Thank you, Metalljens. You helped us finding a resolution for the owners of nForce3 mainboards. I will mention this special way for nForce3 users within my first post.

To make it clear for everyone: Metalljens meant nvatabus.inf (instead of nvata.inf) and txtsetup.oem (instead of oemsetup.txt).

@ Metalljens:
If I am not right, please correct me.

By the way: It will not be necessary to copy the txtsetup.oem file into the OEMDIR folder, because this file is only usefull during TEXTMODE part of installation.

Yes, youre completely right, guess im gone blind about those filenames hehe...

@ Metalljens:
Please have a look an post 1 with the description of the driver integration.
I added your experience as nForce3 user.
Is it correct and easy to understand, what I have written?
AFAIK it's easier for many users to copy a file than to edit something into a file.

Yes, but those txtseup.oem arent exactly the same, the one int pataraid folder has an entry of catalog file which the the sataraid doesnt

This is the pataraid txtsetup.oem

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat <--- this file doesnt exist in the sata_raid txtsetup.oem , nor physically in the sataraid folder either

This is the sataraid txtsetup.oem below

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat <---- see, the sataraid has another catalog file.

But maybe you could just copy that catalog file to the sataraid folder? I dont know.

Well, this is the two sections from my working txtsetup.oem:

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat

To other users, there are more entries in the txtsetup.oem, so DONT just copy this into a new text file and name it txtsetup.oem, you have to open the original or make a copy of the origina txtsetup.oem and paste it in the right place

nforce4 6.66 on A8N-SLI Premium integration succeeded with no concerns using 1.0b5

My System:

ASUS A8N-SLI Premium, AMD FX-55 Clawhammer processor, ASUS EAX850XT PE 256mb PCIe, Audigy 2 ZS, Sony LCD SDM- HS95PS, DVI, Corsair TwinX1024LL 3200 Professional, 4*WD 74G Raptors in RAID0 on nforce4 chipset, Lian-Li PC-75 case, 2*LG 4163 DV-RW, Panosonic floppy, Sycom 1000va UPS, Enermax EG701AX-VE SFMA 2.0 (600W) Power Supply, Labtech 580e 5.1 THX speaker system, HP Deskjet 940C

@ Metalljens:

Thank you very much for your important correction. I did not realize the other changes in txtsetup.oem.
According to your suggestion I changed this point in post 1.


@ RickSteele:

Thank you for your information. I don't have any idea, why you succeeded with the driver integration using nLite 1.0 b5 and others not.
Did you really take the original versions of the driver package 6.66 without any changes in one of the txtsetup.oem files?

Well I didn't want to have to use beta 4, but this did work for me.

anyone know how to add multiple OEM inf's ?

[OemInfFiles]
OemDriverFlags = 1
OemDriverPathName = "%SystemRoot%\OemDir"

OemInfName = "fasttx2k.INF"
OemInfName = "UlSata.inf"
OemInfName = "viapide.inf"


?

Look here:
http://www.msfn.org/board/index.php?showto...ndpost&p=343023
CU
Fernando

Hi

Tried your Guide but got the following Error:

GUI-Modus Setup wurde begonnen.
Interne Setupdatenstrukturen sind beschädigt (Phase 0).
GUI-Modus Setup wurde aufgrund eines schwerwiegenden Fehlers beendet.

setuplog.txt shows the following:

Time,File,Line,Tag,Message
08/21/2005 20:05:34.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6434,BEGIN_SECTION,Installing Windows NT
08/21/2005 20:05:36.859,d:\xpsprtm\base\ntsetup\syssetup\wizard.c,1568,,SETUP: Calculating registery size
08/21/2005 20:05:36.859,d:\xpsprtm\base\ntsetup\syssetup\wizard.c,1599,,SETUP: Calculated time for Win9x migration = 120 seconds
08/21/2005 20:05:36.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6465,BEGIN_SECTION,Initialization
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6585,BEGIN_SECTION,Common Initialiazation
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1674,BEGIN_SECTION,Initializing action log
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,GUI-Modus Setup wurde begonnen.

08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1679,END_SECTION,Initializing action log
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1764,BEGIN_SECTION,Creating setup background window
08/21/2005 20:05:37.046,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1775,END_SECTION,Creating setup background window
08/21/2005 20:05:37.046,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1826,BEGIN_SECTION,Initializing SMS support
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1835,,Setup: (non-critical error): Failed load of ismif32.dll.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1837,END_SECTION,Initializing SMS support
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1868,BEGIN_SECTION,Shutting down power management
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1871,END_SECTION,Shutting down power management
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1950,BEGIN_SECTION,Processing parameters from sif
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find msdosinitiated.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,632,,SETUP: Upgrade=0.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,633,,SETUP: Unattended=0.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find uniqueness.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find AccMagnifier.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find AccReader.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find AccKeyboard.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Interne Setupdatenstrukturen sind beschädigt (Phase 0).

08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Schwerwiegender Fehler
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,:

08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Interne Setupdatenstrukturen sind beschädigt (Phase 0).

08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,
***


08/21/2005 20:05:58.640,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,GUI-Modus Setup wurde aufgrund eines schwerwiegenden Fehlers beendet.

So what is the problem ????


MfG Benny

It has nothing to do with the integration of the nForce SataRaid drivers.
There is a mistake in WINNT.SIF.
Make a new nLite CD.
CU
Fernando