Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Integration of NVIDIA's nForce RAID and AHCI drivers

* * * * * 4 votes

  • Please log in to reply
1989 replies to this topic

#1
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ all users with a NVIDIA nForce RAID or AHCI system:

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: 04/05/2012
Changelog:
  • updated: modded 32/64bit "Actual nForce Driverpacks for XP" (now v9.0)
  • updated: modded 32/64bit "Non-AHCI nForce Performance Packs for XP" (now v9.0)
  • updated: modded 32/64bit "Special MCP65-67 nForce Driverpacks for XP" (actual: v9.0)
  • updated: modded 32/64bit "nForce LEGACY Remix Packs" (now v9.0a resp. v9.0)
  • changed: all download links (all files now hosted at a quick ftp server)



Introduction

The problem:
None of the Pre-Vista Windows Operating Systems do support the S-ATA Controller features RAID ("Redundant Array of Independent Disks") and AHCI ("Advanced Host Controller Interface"). Unless the suitable nForce Sata/PataRAID or AHCI drivers are separately presented by the user, the OS installation fails, because the OS Setup doesn't find the related RAID/AHCI drives and their partitions.
The traditional method to provide the needed drivers by F6/floppy has some severe disadvantages:
  • A floppy drive is needed, but not available at many actual desktop computers and notebooks.
  • Floppy disks are the worst data storage media regarding the file integrity. Bad floppy disks are the main reason for corrupted driver files.
  • The F6/floppy method doesn't work at all with some "LEGACY mode" nForce RAID systems. Even if the user loads the correct nForce drivers and the RAID is detected by Windows Setup, the OS installation may end with a BSOD and endless reboot loops.
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 or AHCI system. 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 nForce S-ATA/P-ATA 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 or AHCI 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 built-in 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

Who needs to load/integrate which nForce IDE driver subfolder?
You can get NVIDIA nForce chipset deskop computers and laptops with the following variations:
  • non-RAID/AHCI nForce systems (RAID/AHCI not supported or disabled):
    Users with such system don't have to load/integrate any nForce IDE drivers.
  • nForce RAID systems (SataRAID or PataRAID):
    NForce Users with enabled RAID settings within the BIOS need to load/integrate the LEGACY (for NF2-4 chipsets) or the SATARAID subfolder of the suitable nForce chipset driverpack as TEXTMODE driver. Users with an old "LEGACY mode" nForce RAID system, who want to integrate the SATARAID subfolder, additionally have to integrate the SATA_IDE subfolder as PnP driver to prevent a BSOD at the end of the OS installation.
  • nForce AHCI systems (S-ATA Controllers set to AHCI mode):
    The actual nForce chipsets (MCP65 and up) do support the enhanced features (NCQ etc.) of the new S-ATA standard AHCI. If the NVIDIA nForce S-ATA Controllers are set to "AHCI mode" (instead of "IDE mode") within the BIOS, users have to load/integrate the suitable SATA_IDE subfolder as TEXTMODE driver. Only the new generation of nForce S-ATA drivers named "NVGTS" do support the AHCI features and can be integrated as textmode driver. Suitable SATA_IDE subfolders contain a TXTSETUP.OEM file.

Here is the way how to do it:

Integration of NVIDIA's nForce RAID and AHCI drivers
by using nLite


Guide for Windows XP and Windows Server 2003 (32/64bit)



A. Integration of the nForce RAID drivers
(if the OS will be installed onto any RAID partition)


Short form guide
(for hasty users, who want a quick result)

If you want to create a bootable OS CD, which will detect your RAID and be successfully installed onto it, you should do the following:
  • Get the actual nLite version from here and install it (.NET Framework 2.0 or equivalent is needed).
  • Download and unzip one of the following already prepared drivers (the choice depends on the OS, which shall be installed, and the nForce chipset of the destination desktop/laptop):
    a. Windows XP or Windows Server 2003 (32bit)b. Windows XP x64 or Windows Server 2003 x64:
  • Create a folder named "nLiteCD" (or similar) somewhere and copy the whole content of the original OS CD into it.
  • Start nLite > point to the content of the just created folder as source > hit the buttons "Drivers" and "Bootable ISO".
  • When the task "Drivers" comes > hit "Insert" > choose "Single driver" > point to the prepared SATARAID resp. LEGACY driver folder.
  • Click onto any of the shown INF files > a popup window will come up.
  • Both shown "required" NVIDIA products should be highlighted (already done by nLite) > hit "OK".
  • Only needed for some NF4-5 RAID systems after the integration of the SATARAID drivers: integrate additionally the SATA_IDE folder as PnP driver.
  • Let nLite burn the Image directly onto an empty CD ("General" > "Mode" > "Direct Burn").
  • Boot off the created CD, choose the destination partition, do a quick NTFS formatting and install the OS.
  • Have fun!

Detailed RAID drivers integration guide
(for users, who want the best possible results or who ran into problems)


Important Requirements:

You only will succeed with the integration of the nForce Pata/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 v4.81 (NF3) resp. v5.60 (NF4) 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 (a S-ATA connected optical drive should not be connected with an nForce S-ATA Controller which are set to RAID or AHCI mode)
  • an enabled ACPI power management (within BIOS, don't disable it by nLite settings).


Tips:
  • 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 Pata/SataRaid drivers.
  • The successful integration of the nForce Pata/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 or the last SP, you should integrate the latest SP as first step, when you are going to create your nLited CD with integrated nForce Sata/PataRaid drivers.
  • XP 32bit (x86) only: If possible don't 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 Raid drivers. Otherwise you may get problems during the installation of the nLited CD.
  • It is a good idea to unplug all unnecessary external hardware devices during the installation of the OS with integrated nVRaid drivers.
  • 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.


1. Preparation and driver choice



If you are not already running the latest version of nLite, you should download it here and install it (.NET Framework 2.0 or equivalent is needed).

The next step is the preparation of the nForce textmode driver for the later integration. The choice of the "best suitable" nForce IDE driver version and subfolder mainly depends on the nForce chipset details, the RAID configuration (SataRAID or PataRAID) and maybe on the nVRaid BIOS version of the destination desktop/laptop.
NVIDIA is offering for all nForce chipsets complete driverpacks with included nForce SataRAID drivers. You will find them, if you go here, choose "nForce" (NF5 and up) or "LEGACY" (NF1-4) as "Product Type" and then choose your special nForce chipset and the OS you are going to install. Unfortunately NVIDIA's official nForce driverpacks are not always the best choice for nForce RAID users. Either they do not work at all (example: NF4 RAID), they are outdated (example: NF2-3 RAID) or they don't provide the best possible performance (valid for nearly all NF chipsets).

Since January 2008 I am offering alternative nForce drivers and driverpacks, which are actual, but maybe better than NVIDIA's official ones (for details you may look here). The used drivers themselves (=SYS files) were developed and released by NVIDIA, but for unknown reasons the manufacturer didn't add the HardwareID's of all supported nForce IDE devices. That is why I customized the associated INF/OEM files to make them compatible with as many nForce chipsets as possible. This modification doesn't touch the driver's function and the loss of Microsoft's digital signature (WHQL) has no impact on the driver's installation (thanks to nLite's built-in textmode driver integration method).

For the later integration I recommend to prepare the following actual and approved nForce textmode drivers, which are optimized for being used with nForce RAID systems:

a. Windows XP or Windows Server 2003 (32bit)
  • for nForce2/3/4 SataRAID and nForce2/3/4/5 PataRAID systems:
    >32bit nForce LEGACY drivers v6.99 mod by Fernando (download link)<
    This LEGACY textmode driver package contains the newest non-AHCI capable nForce IDE drivers v6.99 dated 14th May 2007. Since I have added all needed HardwareID's, this package will support all "LEGACY Mode" nForce2-5 RAID systems ("LEGACY Mode" means, that the NVIDIA nForce RAID Controllers of the mainboard do support Pata- and Sata-RAID simultaneously).
  • for nForce 430/410 (MCP51), nForce 590/570/550/680i/650i/780i/750i (MCP55) and nForce 430/405/400 (MCP61) SataRAID systems:
    >32bit nForce IDE drivers v9.99.09 mod by Fernando (download link)<
    Within the small package you will find the nForce IDE drivers v9.99.09 dated 01/17/2008, which have been customized by me to make them compatible with all NF4-7 chipsets. These drivers will give your nForce RAID system the best possible performance. Usually only the SATARAID driver folder will be needed for the later integration, but some users with a LEGACY Mode nForce RAID system may have to integrate both included driver subfolders (SATARAID as textmode and SATA_IDE as PnP driver).
  • for nForce 560/520 (MCP65) and nForce 630a (MCP67) SataRAID systems:
    >32bit nForce SATARAID drivers v10.3.0.46 WHQL (download link)<
    These are NVIDIA's latest nForce IDE drivers, which do fully support MCP65 and MCP67 chipsets.
  • for all other nForce SataRAID systems:
    >32bit nForce SATARAID drivers v11.1.0.43 WHQL (download link)<
    These are NVIDIA's latest WHQL certified nForce IDE drivers v11.1.0.43 dated 04/09/2010. I recommend to use these new drivers for users with a SataRAID system and an MCP73-79 chipset mainboard. Users with an MCP51, MCP55 or MCP61 chipset mainboard may take them too, but I am not sure, that they will get a better performance than with the modified nForce SATARAID drivers v9.99.09.

b. Windows XP x64 or Windows Server 2003 x64
  • for nForce3 250/nForce4 SataRAID and PataRAID systems:
    >64bit nForce LEGACY drivers v6.99 mod by Fernando (download link)<
    The package contains the newest natively 64bit nForce IDE drivers, which have been customized by me to make them usable with all "LEGACY Mode" nForce RAID systems from nForce3 up. Even MCP51, MCP55 and MCP61 PataRAID systems are supported by them.
  • for nForce 430/410 (MCP51), nForce 590/570/550/680i/650i/780i/750i (MCP55) and nForce 430/405/400 (MCP61) SataRAID systems:
    >64bit nForce IDE drivers v9.99.09 mod by Fernando (download link)<
    Within the package you will find the nForce IDE drivers v9.99.09 dated 01/17/2008, which have been customized by me to make them compatible with all NF4-7 chipsets. These drivers will give your nForce RAID system the best possible performance. Usually only the SATARAID driver folder will be needed for the later integration, but some users with a LEGACY Mode nForce RAID system may need both included driver subfolders (SATARAID as textmode and SATA_IDE as PnP driver).
  • for nForce 560/520 (MCP65) and nForce 630a (MCP67) SataRAID systems:
    >64bit nForce SATARAID drivers v10.3.0.46 WHQL (download link)<
    These are NVIDIA's latest nForce IDE drivers, which do fully support MCP65 and MCP67 chipsets.
  • for all other nForce SataRAID systems:
    >64bit nForce SATARAID drivers v11.1.0.43 WHQL (download link)<
    These are NVIDIA's latest WHQL certified nForce IDE drivers v11.1.0.43 dated 04/09/2010. I recommend to use these new drivers for users with a SataRAID system and an MCP73-79 chipset mainboard. Users with an MCP51, MCP55 or MCP61 chipset mainboard may take them too, but I am not sure, that they will get a better performance than with the modified nForce SATARAID drivers v9.99.09.
After having downloaded the suitable driverpack and unzipped it with a tool like WinRAR or 7-Zip everything is prepared for the later integration procedure.



2. Processing with nLite:



This is what you should do, before you start nLite:
  • Create a new folder somewhere on any available hard disk drive and name it as you like (for example "nLiteCD") .
  • Copy the whole content of the original OS CD into the just created folder. Don't use or reuse any already nLited or modded source.
  • Check, if you have already running the latest nLite version. If not, download and install it.
Now you can begin with the nLite processing:
  • Start nLite.
  • Choose your language > hit "Next"
  • Hit the "Browse" button, find the path to your just created folder "nLiteCD" (or similar) > click onto the folder name. Now you can see the OS details inclusive the eventually already integrated Service Pack version > hit "Next".
  • Don't import or enable any presets > hit "Next".
  • Now you will get the Task Selection page.
    You can enable all offered tasks (not recommended for newbees), but you have to enable the tasks "Integrate Drivers" and "Create Bootable ISO".
    Recommendations:
    • You should additionally choose the task "Integrate Service Pack", if the OS SP version is not actual.
    • Don't enable any other tasks, unless you are already familiar with nLite and nearly sure, that the nLite CD will work with your system (the more you are adding, tweaking or removing, the more difficult is the search for the reason, if the OS installion should fail).
    > hit "Next"
  • When you get the "Drivers Integration" page > hit "Insert" > choose the "Single driver" option > point to the prepared SATARAID or LEGACY folder with the suitable nForce Sata/PataRAID drivers > hit onto any of the shown INF files (=files with the suffix ".inf").
  • Now you will get the following popup window:
    Attached File  Textmode_Driver_Popup_nLite.jpg   34.99KB   1206 downloads
    Both listed "required" NVIDIA products ("NVIDIA RAID CLASS DRIVER" and "NVIDIA nForce Storage Controller") have to be enabled. Usually nLite has already highlighted both of them and set the integration mode to "TEXTMODE" (if not, you should do it manually) > hit "OK"
    Important: Users with an NF3-5 chipset RAID system, who had just integrated the SATARAID folder, may need to additionally integrate the content of the SATA_IDE subfolder of the same driverpack as PnP driver to get the OS properly installed.
    If you have integrated all needed nForce Sata/PataRAID drivers > hit "Next"
  • Let nLite start its processing > hit "Yes"
  • After the successful nLite processing > hit "Next"
  • As last step you will get the "Create Bootable ISO" page. Within the "General" section you can choose the "Mode".
    You have the options "Direct Burn" (burns the image directly onto an empty CD/DVD), "Burn Image" or "Create Image" (default setting).
    If you don't want, that nLite burns the Image itself, you should let nLite create the ISO file by hitting the "Make ISO" button.
    After having chosen the storage place and -if applicable - a special name for the ISO file > hit "Store".
  • At this point nLite has finished its work.
If nLite hasn't already burnt the Image onto a CD, you have to burn the stored ISO file as bootable Image by using a burning tool.
You will get the best results with Nero Burning ROM, when you choose the options "Recorder" (on top task bar) > "Create Image...." > point to the ISO file nLite has created > hit "Burn".
Tip: Burn at no more than 8x(DVD) or 24x(CD) and choose the "Verify" option of Nero to avoid any burning errors!

At the end you will have a bootable 32bit or 64bit Windows OS CD with integrated NVIDIA Sata/PataRaid 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!



B. Integration of the nForce AHCI drivers
(only valid for AHCI supporting nForce mainboards with enabled AHCI)


Actual nForce chipsets (MCP65 and up) do support the advanced S-ATA-Features (z.B. NCQ) of the AHCI standard. Users of such systems usually have the BIOS option to set the nForce S-ATA Controllers to "AHCI Mode" instead of the "IDE Mode" (which doesn't require any separate textmode drivers). If AHCI is enabled, Windows Setup will not detect the S-ATA hdd('s) unless the needed AHCI drivers will be loaded (F6) or have been integrated into the OS CD.

If you try to get Windows XP or Server 2003 (32/64bit) installed onto a non-RAID nForce chipset system and should realize, that Windows Setup doesn't find any hard drive, the following procedure will be successful for nearly all users:
  • get the actual version of nLite from here and install it (.NET Framework 2.0 required)
  • depending on your nForce chipset and the OS you are going to install, download and unzip one of the following drivers:
  • create a folder named "nLiteCD" or similar and copy the whole content of the OS CD into that folder
  • start nLite > point to the just created "nLiteCD" folder as source
  • choose the tasks "Integrate Drivers" and "Create Bootable ISO"
  • when the "Driver Integration" task comes up > hit "Insert" > choose "Single driver" > point to the prepared SATA_IDE subfolder
  • check any of the shown INF files
  • now you see the following popup window:
    Attached File  nForce_AHCI_driver_popup_with_nLite.jpg   36.02KB   510 downloads
    let the "NVIDIA nForce Storage Controller (required)" enabled > hit "OK"
  • let nLite burn the Image directly onto an empty CD/DVD
  • boot of the just created CD > choose the destination partition > do a quick NTFS formatting > install the OS
  • have fun!

C. Most common problems during the OS installation


If you have followed my guide until this point, you can be rather optimistic, that you will get the OS perfectly installed onto your nForce RAID or AHCI system, but the success is not guaranteed.
These are the most common mistakes/errors, which will cause a failure of the OS installation:
  • The prepared CD doesn't boot. ("Hit any key to boot off CD/DVD" message is missing).
    Reason: Either you haven't set the correct boot device order within the BIOS or you didn't burn the ISO file correctly.
    Solution: The CD/DVDROM device has to be set as 1st bootable device and the ISO file has to be burnt as bootable Image (see above).
  • Windows Setup doesn't detect the RAID or the SATA drives, which were set to "AHCI Mode".
    Reason: You obviously didn't integrate the "suitable" textmode drivers or didn't choose the needed Controllers during the integration procedure.
    Solution: Check the exact chipset name of your mainboard, the BIOS settings and the sort of the S-ATA Controllers, where your hdd's are connected (example: you can't get Silicon Image S-ATA Controllers working with nForce drivers and vice versa).
    After having found the "correct" textmode drivers you have to restart the integration procedure from scratch (don't reuse the nLited source again!).
  • You get a message like "The file NVxxx.SYS is corrupt."
    Reason: You obviously mixed the 32/64bit textmode driver version or you didn't use a clean source.
    Solution: Start the nLite processing again from scratch with a clean source and integrate the correct 32/64bit textmode driver version. XP, W2k and W2k3 can only be installed by using 32bit textmode drivers, whereas the 64bit Operating Systems (XP x64/W2k3 x64) need 64bit drivers.
    You get an error message like "Cannot find file NVxxx.SYS".
    Reason: You either didn't integrate the textmode driver or you tried to additionally load it by F6/floppy method.
    Solution: Don't hit F6 when prompted, if you have integrated the textmode driver.
  • The OS installation fails at last reboot with a short BSOD and endless reboots.
    Reason: You either didn't choose the correct driver integration method or your optical drive is connected to a S-ATA port, which is set to RAID or AHCI.
    Solution:Connect the optical drive to a non-RAID/non-AHCI S-ATA port or take an IDE connected CD/DVDROM drive for the OS installation.
Aside from the previously mentioned problems there are some other sources of error:
  • not correctly configurated RAID or wrong BIOS settings regarding RAID/AHCI
  • wrong BIOS settings regarding the "HARD DISK BOOT PRIORITY" (solution: the RAID/AHCI drive has to be set as first bootable hard disk)
  • presence of additional hdd's outside the RAID/AHCI device (solution: disconnect all non-RAID/non-AHCI hdd's during the OS installation)
  • plugged-in USB sticks, floppys, memory cards etc. (solution: unplug them all before you start with the OS installation)
  • faulty RAM sticks, overclocking or > 3 GB of RAM (solution: check the RAM with Memtest, no OC'ing, removal of RAM sticks during the OS installation)
  • hardware malfunction (broken or not really connected S-ATA cables, poor PSU etc.)

D. After the successful OS installation


Once the OS is up, you should install the complete "suitable" nForce chipset driver set. The best suitable driverpack is that one, which contains the same version of nForce IDE drivers as the integrated ones (v6.99, v9.99.09 or 11.1.0.33, if you had followed my advices).
Here are the download links to the related complete nForce chipset driver packs:

a. XP/W2k3 (32bit)b. XP/W2k3 (64bit)
That's all - I hope, that you will succeed with the integration of the drivers and with the installation of the OS onto your nForce RAID or AHCI system.

Good luck!
Fernando


Important notice:
This guide contains a lot of links to drivers, which have been modified by me to make them usable for nForce chipset users. As you certainly understand, I cannot overtake any warranty for the function and the quality of the drivers. You may use them nevertheless, but at own risk.




Annex I

MediaShield/Raidtool installation guide


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 SATA RAID array outside the OS partition

Here are some advices for such users:
  • Users with an nForce Sata-RAID array, who are going to install any OS onto an IDE or non-AHCI S-ATA drive, which is outside the RAID, should not integrate any nForce SataRaid drivers. They will be able to get the OS installed without any problems.
  • Once the OS is up, you should run the installer of the suitable nForce chipset driver package. After the reboot, the RAID array normally will be detected by the OS.
  • If the OS should not show the RAID device and their partitions, you should do the following:
  • Open the Device Manager and check, if you see the "NVIDIA nForce RAID Controller" within the "SCSI and RAID Controllers" section. If not, you haven't enabled the NVIDIA RAID Controllers within the BIOS.
  • If you see the "NVIDIA nForce RAID Controller", you have to open the "IDE ATA/ATAPI Controllers" section and look for the "Standard Dual Channel PCI IDE Controllers", where your RAIDed SATA hdd's are connected to.
  • Right click onto these Controllers and do a driver software "update" until you see the compatible devices.
  • Choose the "NVIDIA nForce Serial ATA Controllers", if they are shown as compatible.
  • After the reboot your OS will see and will be able to work with the datas of the RAID array.

Edited by Fernando 1, 05 May 2013 - 05:06 AM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E


How to remove advertisement from MSFN

#2
gunyunzi

gunyunzi

    Newbie

  • Member
  • 15 posts
  • Joined 17-June 04
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

#3
cantankerous

cantankerous

    Newbie

  • Member
  • 16 posts
  • Joined 14-September 04
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!

#4
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

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

<{POST_SNAPBACK}>


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!
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#5
noen

noen
  • Member
  • 5 posts
  • Joined 18-July 05
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.

Edited by noen, 19 July 2005 - 05:57 PM.


#6
virtualrain

virtualrain

    Newbie

  • Member
  • 10 posts
  • Joined 19-July 05

2. Copy the following files (you find them in the IDE\WINXP folder of your NVIDIA chipset driver package) into the just created folder "OEMDIR":
idecoi.dll
nvatabus.inf
nvatabus.sys



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.

#7
DrTweak

DrTweak
  • Member
  • 1 posts
  • Joined 19-July 05
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

#8
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64



2. Copy the following files (you find them in the IDE\WINXP folder of your NVIDIA chipset driver package) into the just created folder "OEMDIR":
idecoi.dll
nvatabus.inf
nvatabus.sys

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.

<{POST_SNAPBACK}>

Thats right! You have to take the nvatabus.inf file from the folder PATARAID.
I will clarify this in my first post.
CU
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#9
virtualrain

virtualrain

    Newbie

  • Member
  • 10 posts
  • Joined 19-July 05

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

<{POST_SNAPBACK}>


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?

Edited by virtualrain, 20 July 2005 - 01:23 AM.


#10
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

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?

<{POST_SNAPBACK}>

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

Edited by Fernando 1, 20 July 2005 - 02:39 AM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#11
virtualrain

virtualrain

    Newbie

  • Member
  • 10 posts
  • Joined 19-July 05

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

<{POST_SNAPBACK}>


That explains it... Thanks!

#12
Evofighter

Evofighter
  • Member
  • 5 posts
  • Joined 20-July 05



2. Copy the following files (you find them in the IDE\WINXP folder of your NVIDIA chipset driver package) into the just created folder "OEMDIR":
idecoi.dll
nvatabus.inf
nvatabus.sys

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.

<{POST_SNAPBACK}>

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

<{POST_SNAPBACK}>


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

Thanks.

#13
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

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

Yes!
Otherwise the necessary driver NVATABUS.SYS would not be installed and your system would not work after the installation.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#14
Evofighter

Evofighter
  • Member
  • 5 posts
  • Joined 20-July 05

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

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

<{POST_SNAPBACK}>


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. :thumbup

#15
Evofighter

Evofighter
  • Member
  • 5 posts
  • Joined 20-July 05
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. :D

#16
Metalljens

Metalljens

    Newbie

  • Member
  • 17 posts
  • Joined 21-July 05
When using your suggestion and nlite should i select oem preinstall option in nlite when doing the unattended setup?

#17
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

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).
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#18
Metalljens

Metalljens

    Newbie

  • Member
  • 17 posts
  • Joined 21-July 05
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?

Edited by Metalljens, 21 July 2005 - 03:38 PM.


#19
poPsi

poPsi
  • Member
  • 2 posts
  • Joined 21-July 05
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...

#20
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

the 6.53 works perfectly when using nlite b5 without any other modifications. Why dont later ones do that?

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

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?

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

And why is the 6.53 only one folder for everything?

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.

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].

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.

Edited by Fernando 1, 21 July 2005 - 04:52 PM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#21
burningrave101

burningrave101
  • Member
  • 7 posts
  • Joined 29-June 05
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.

Edited by burningrave101, 21 July 2005 - 08:33 PM.


#22
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

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:

Only thing changed is order of HW ID entries...and I can not believe how important this seems for Nforce line of controllers.
...even small driver version difference makes a difference for them.

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.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#23
Metalljens

Metalljens

    Newbie

  • Member
  • 17 posts
  • Joined 21-July 05
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??

#24
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

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.

Edited by Fernando 1, 22 July 2005 - 09:02 AM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#25
Metalljens

Metalljens

    Newbie

  • Member
  • 17 posts
  • Joined 21-July 05
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.




1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users


    Baidu (1)