Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Fernando 1

Integration of NVIDIA's nForce RAID and AHCI drivers

Recommended Posts

douirc, to make mine work I had to also add the nvatabus.inf driver from the legacy folder (using the most recent chipset driver from nvidia, not sure which). Once I did that my driver problems were solved.

hmm...so first i did single driver and pointed to IDE\WinXP\legacy and chose nvatabus.inf, which nlite returned nForce Storage Controller (required) and RAID Class Driver (required). I chose only the first (nForce Storage Controller) in textmode driver and hit ok. This then filled the driver window with a single entry called Mode: TXT - BUSDRV with Type: HDC. Then I chose single driver again, this time going to IDE\WinXP\sataraid and chose nvraid.inf, which nlite returned the same two options: nForce Storage Controller (required) and RAID Class Driver (required). I chose only RAID Class Driver (required), which updated my driver list to include two more entries: Mode: PNP Type: HDC and Mode: TXT-RAIDCLASS Type: SCSI Adapter. Is that right?

If you look at my previous post you'll note that there is another issue, and that involves disabling some of the drivers in the bios. With at least the Asus A8N32 board, and possibly other nforce4 boards, if you disable the parallel port because it’s not going to be used it messes up the USB. Mine was so bad it caused a brief BSOD and then reboot on the first windows boot after all the driver loads, and each subsequent boot attempt. If there is nothing plugged into ANY USB ports then you’re fine. All it took to crash mine was a single USB mouse.

I have two device plugged into USB: My external CD-ROM and my USB Hub in my MSFT keyboard (that my mouse plugs into). I can definately try unplugging the hub and mouse for installation purposes.

If yours is working with an F6 floppy load why are you attempting this method?

Ever since I've put watercooling in my system I've lost all room for devices like CD-ROM and Floppy. The CD-ROM was easy since it's sitting on my desk and connected via USB, but my floppy is hanging out of the case while i'm trying to get raid working. i'd rather put it back in the closet and just use a CD every time i need to reinstall the OS (which happens often with me).

Share this post


Link to post
Share on other sites

sadly, it didn't work :(.

quick question...anyone able to make this work using a USB CD-ROM? I'm wondering if this only works with an IDE drive, not USB?!?

Edited by douirc

Share this post


Link to post
Share on other sites

i FINALLY figured it out! unlike what the instructions say, i didn't slipstream SP2 and it finally worked! i made a copy of the floppy that came with the mobo, ran nlite and skipped the service pack option. i then pointed to the nvidia folder on the floppy using the 'single driver' option and choose the nvatabus.inf file, which listed every raid driver on the floppy. i only chose the first two: NVIDIA NForce Storage Controller and NVIDIA RAID CLASS DRIVER. I created the iso file, burned it to disk and everything worked fine.

so...what can't i get it to work with SP2? I know my SP2 file is good 'cause i use it all the time when upgrading my XP to XP-SP2. The filename is WindowsXP-KB835935-SP2-ENU.exe. I'd love to know how to make this work WITH sp2 instead of without it.

Share this post


Link to post
Share on other sites
so first i did single driver and pointed to IDE\WinXP\legacy and chose nvatabus.inf, which nlite returned nForce Storage Controller (required) and RAID Class Driver (required). I chose only the first (nForce Storage Controller) in textmode driver and hit ok.
This was not correct. You should have taken both required Controller drivers.

Share this post


Link to post
Share on other sites
so first i did single driver and pointed to IDE\WinXP\legacy and chose nvatabus.inf, which nlite returned nForce Storage Controller (required) and RAID Class Driver (required). I chose only the first (nForce Storage Controller) in textmode driver and hit ok.
This was not correct. You should have taken both required Controller drivers.

well, i took both the first time and it failed. then i read above someone suggesting to take the nvatabus.inf from IDE\WinXP\legacy and take nvraid.inf from the IDE\WinXP\sataraid directory, which also failed. i've tried numerous combinations, all of which failed.

what's shocking to me is the method that worked without sp2 doesn't work with sp2. you would think it shouldn't matter, but somehow sp2 is throwing off my slipstream and crashing my installation. next i was going to try using an already slipstreamed sp2 disk and adding the raid drivers to that, instead of starting with a bare xp disk and adding sp2 followed by the drivers. maybe that will do the trick. i'm quickly running out of combinations, so any suggestions on how to do this to include sp2 using the method mentioned above that worked for me is greatly appreciated.

Share this post


Link to post
Share on other sites
so first i did single driver and pointed to IDE\WinXP\legacy and chose nvatabus.inf, which nlite returned nForce Storage Controller (required) and RAID Class Driver (required). I chose only the first (nForce Storage Controller) in textmode driver and hit ok.
This was not correct. You should have taken both required Controller drivers.

well, i took both the first time and it failed. then i read above someone suggesting to take the nvatabus.inf from IDE\WinXP\legacy and take nvraid.inf from the IDE\WinXP\sataraid directory, which also failed. i've tried numerous combinations, all of which failed.

what's shocking to me is the method that worked without sp2 doesn't work with sp2. you would think it shouldn't matter, but somehow sp2 is throwing off my slipstream and crashing my installation. next i was going to try using an already slipstreamed sp2 disk and adding the raid drivers to that, instead of starting with a bare xp disk and adding sp2 followed by the drivers. maybe that will do the trick. i'm quickly running out of combinations, so any suggestions on how to do this to include sp2 using the method mentioned above that worked for me is greatly appreciated.

ok, i have to apologize. you were right! i recreated the disc last night, included sp2, pointed to IDE\WinXP\legacy using 'single driver' and grabbed both NVIDIA nForce Storage Controller and NVIDIA RAID Class Driver and it worked. Not sure what I did wrong last time, but now it's working. The catch is obviously not using the \sataraid directory at all, but just using the \legacy directory. if all you need is the legacy directory, what's the \sataraid directory for, anyway?

Share this post


Link to post
Share on other sites
The catch is obviously not using the \sataraid directory at all, but just using the \legacy directory. if all you need is the legacy directory, what's the \sataraid directory for, anyway?
You will not get WHQL certified nForce SataRaid drivers by using the LEGACY subfolder drivers, but this is not really a big disadvantage unless you try to upgrade to Vista.

Share this post


Link to post
Share on other sites

Fernando, in nLite, I remove all the drivers supplied by Windows XP with NO exception (cause I have my own new drivers for every hardware). My question is, do you think Windows XP installation is gonna succeed if I integrate my downloaded nForce4 RAID drivers even though I removed all Microsoft supplied drivers?

To put the question in a plain manner, Does RAID need any driver supplied by Microsoft?

Share this post


Link to post
Share on other sites
To put the question in a plain manner, Does RAID need any driver supplied by Microsoft?
nForce SataRaid systems don't need any Microsoft driver. Nevertheless I would not recommend to delete the MS Standard Dual Channel PCI IDE Controller drivers, if you are using any IDE devices (CD-ROM or DVD). Reason: Many users have reported about problems with NVIDIA's P-ATA drivers (nForce4 Parallel ATA Controller = IDE s/w) and obviously got better results with the fully compatible MS Standard Dual Channel PCI IDE drivers.

Share this post


Link to post
Share on other sites

Hey guys,

Sorry I haven't touched base here in a few days. This site is supposed to notify me when messages are posted but it only does so occasionally.

douirc, sounds like you're on your way to success! Sorry I wasn't here for you man. You shouldn't have any problems with USB as long as you have NOT disabled your parallel port (and possibly some of the others but I think it's mainly the P-port).

Merry Christmas to All!

Share this post


Link to post
Share on other sites

Ok I am having major problems with nLite right now. I integrated the drivers and installed flawlessly at college. Unfortunately I need to do a reinstall here at home and don't have the disc. I had the .ISO I made. So I burned it to a CD and attempted to install. I get the error that NVATA.SYS is missing. So I figured oh well, this probably just needs the driers re-integrated.

When trying to reintegrate drivers I now always get Access Denied to the "<REGISTRY PARAMETER>" of the driver that I am trying to integrate. This install is fast losing steam and functionality. Can someone please help me??

-Kevin

Share this post


Link to post
Share on other sites
Ok I am having major problems with nLite right now. I integrated the drivers and installed flawlessly at college. Unfortunately I need to do a reinstall here at home and don't have the disc. I had the .ISO I made. So I burned it to a CD and attempted to install. I get the error that NVATA.SYS is missing. So I figured oh well, this probably just needs the driers re-integrated.

When trying to reintegrate drivers I now always get Access Denied to the "<REGISTRY PARAMETER>" of the driver that I am trying to integrate. This install is fast losing steam and functionality. Can someone please help me??

It was not a good idea to integrate drivers into an already nLited ISO file. Furthermore different nForce chipset RAID systems need different driver combinations. As you can see within the first post of this thread, it is not possible to create an "omnipotent" nLited CD usable for all nForce SataRaid systems.

You should create a new nLited CD using the original Windows XP source and integrate the special nForce SataRaid drivers I have recommended within the first post of this thread for your hardware configuration.

Edited by Fernando 1

Share this post


Link to post
Share on other sites
Ok I am having major problems with nLite right now. I integrated the drivers and installed flawlessly at college. Unfortunately I need to do a reinstall here at home and don't have the disc. I had the .ISO I made. So I burned it to a CD and attempted to install. I get the error that NVATA.SYS is missing. So I figured oh well, this probably just needs the driers re-integrated.

When trying to reintegrate drivers I now always get Access Denied to the "<REGISTRY PARAMETER>" of the driver that I am trying to integrate. This install is fast losing steam and functionality. Can someone please help me??

It was not a good idea to integrate drivers into an already nLited ISO file. Furthermore different nForce chipset RAID systems need different driver combinations. As you can see within the first post of this thread, it is not possible to create an "omnipotent" nLited CD usable for all nForce SataRaid systems.

You should create a new nLited CD using the original Windows XP source and integrate the special nForce SataRaid drivers I have recommended within the first post of this thread for your hardware configuration.

Crap, my original XP CD was damaged. I still have my CD-Key that I use, but I use a friends CD. I don't know if I can get a CD that isn't damaged....

Ill see if my Dad or one of my friends has a CD I can borrow. If not, is there any problem you know of by integrating the drviers into 2000 and then upgrading to XP?

My problem is that my disc got scratched on the file autofmt.exe which apparently performs the formatting of the HDD. So I have no way of formatting it other than installing 2000 first and then going to XP.

As for the drivers, I am aware that different chipsets require different drivers. I have an Nforce 4 Ultra Chipset. This worked last time I did it, but all of the sudden I am running into problems :(

-Kevin

Edited by Gamingphreek

Share this post


Link to post
Share on other sites
Crap, my original XP CD was damaged. I still have my CD-Key that I use, but I use a friends CD. I don't know if I can get a CD that isn't damaged....

Ill see if my Dad or one of my friends has a CD I can borrow. If not, is there any problem you know of by integrating the drviers into 2000 and then upgrading to XP?

My problem is that my disc got scratched on the file autofmt.exe which apparently performs the formatting of the HDD. So I have no way of formatting it other than installing 2000 first and then going to XP.

I assume, that your nForce4 RAID array is correctly created and set as bootable.

In this case you will be able to find easier ways to get your RAID partitionated and formatted.

If neither a friend nor your father will let you create a customized nLited XP CD for you with their computer, you still have the possibility to get XP installed by F6/floppy method (provided that your pc has a floppy drive and you still have the RAID driver disk from the manufacturer of your mainboard).

A clean install of an OS is always better than an upgrade.

Share this post


Link to post
Share on other sites

:hello: hello everybody!

i'm expecting my new Abit AN8 32 SLI motherboard (Si3132+nvraid) in a few days and i've been reading posts related to the unattend installation of the nforce4 SATA drivers - i dont own a floppy and i need to install the stuff on my SATA drive. apparently there are some serious problems with the SATA controllers (found out too late, wouldnt have ordered it but oh well :unsure: ). anyway i already have my viasraid set up and working on my winxp sp2 customized CD (for my old board that i'm still using) and i was wondering if anybody has the text files and folder structure for the nvraid. i prefer not to use any program to do the setup, i'm happier when i know exactly what and where to add rather than hope some utility will do the job correctly :w00t:

my current/future drive config: seagate 160GB sataII (3gbps) -- using a jumper now to slow down to 1.5gbps due to motherboard limitations, seagate 120Gb IDE, NEC 8xDVD, liteon 32x cd-writer, both IDE.

here's what i set up (will test in a few days when i get the board). i'm using the latest 6.86 nforce4 drivers from their site. :whistle:

----------------------

WINNT.SIF:

[unattended]

OemPreinstall=Yes

OemPnPDriversPath="Drivers\SATA\VIASRAID;Drivers\SATA\SI3132;Drivers\SATA\sataraid;Drivers\SATA\sata_ide"

DriverSigningPolicy=Ignore

OemSkipEula=Yes

NoWaitAfterTextMode=1

NoWaitAfterGUIMode=1

[Data]

UnattendedInstall=Yes

MSDosInitiated=No

AutoPartition=0

[GuiUnattended]

OEMSkipWelcome = 1

OEMSkipRegional=1

[userData]

ProductKey="***"

FullName="***"

OrgName=""

[Componets]

AutoUpdates=off

msmsgs=off

msnexplr=off

zonegames=off

[Networking]

InstallDefaultComponents=Yes

[identification]

JoinWorkgroup=MSHOME

[shell]

DefaultStartPanelOff = Yes

DefaultThemesOff = Yes

Home_Page=http://www.google.com

----------------------

TXTSETUP.SIF:

[sourceDisksFiles]

viasraid.sys = 1,,,,,,3_,4,1

SI3132.sys = 1,,,,,,3_,4,1

nvatabus.sys = 1,,,,,,4,4,1,,,1,4

nvraid.sys = 1,,,,,,4,4,1,,,1,4

[HardwareIdsDatabase]

PCI\VEN_1106&DEV_3149 = "viasraid"

PCI\VEN_1095&DEV_3132&SUBSYS_31321095 = "SI3132"

PCI\VEN_1095&DEV_3132&SUBSYS_710A1462 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_B0021458 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0CA9105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_3009148C = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_88881019 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_819F1043 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_09781019 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_716A1462 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_715A1462 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0CAB105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0CAD105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0C8F105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0C8D105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0C8B105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0C89105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0C87105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_81F0104D = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_722A1462 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_02391154 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_63001462 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_63101462 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_2C0B17F2 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_00226409 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_0D10105B = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_820E1043 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_2A4A103C = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_31321A57 = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_31321A5F = "Si3132"

PCI\VEN_1095&DEV_3132&SUBSYS_1000131F = "Si3132"

PCI\VEN_10DE&DEV_008E = "nvatabus"

PCI\VEN_10DE&DEV_00D5 = "nvatabus"

PCI\VEN_10DE&DEV_00EE = "nvatabus"

PCI\VEN_10DE&DEV_00E3 = "nvatabus"

PCI\VEN_10DE&DEV_0036 = "nvatabus"

PCI\VEN_10DE&DEV_003E = "nvatabus"

PCI\VEN_10DE&DEV_0054 = "nvatabus"

PCI\VEN_10DE&DEV_0055 = "nvatabus"

PCI\VEN_10DE&DEV_0266 = "nvatabus"

PCI\VEN_10DE&DEV_0267 = "nvatabus"

PCI\VEN_10DE&DEV_036F = "nvatabus"

PCI\VEN_10DE&DEV_037E = "nvatabus"

PCI\VEN_10DE&DEV_037F = "nvatabus"

PCI\VEN_10DE&DEV_03F6 = "nvatabus"

PCI\VEN_10DE&DEV_03F7 = "nvatabus"

PCI\VEN_10DE&DEV_03E7 = "nvatabus"

GenNvRaidDisk = "nvraid"

*_NVRAIDBUS = "nvraid"

*NVRAIDBUS = "nvraid"

[sCSI.Load]

viasraid = viasraid.sys,4

SI3132 = SI3132.sys,4

nvatabus = nvatabus.sys,4

nvraid = nvraid.sys,4

[sCSI]

viasraid = "VIA Serial ATA RAID Controller(Windows XP)"

SI3132 = "Silicon Image SiI 3132 SATALink Controller for Windows XP/Server 2003"

nvatabus = "NVIDIA nForce Storage Controller (required)"

nvraid = "NVIDIA RAID CLASS DRIVER (required)"

----------------------

directories:

i copied the makecab compressed sy_ and uncompressed sys files into the 386 dir and the full drivers for sataraid, sata_ide and SI3132 into the drivers dir (along with the viasraid).

i know that this line SI3132.sys = 1,,,,,,3_,4,1 needs compressed drivers and this line nvatabus.sys = 1,,,,,,4,4,1,,,1,4 needs the uncomressed sys (from what i've read on these and other forums) so i'm curious if that's gonna work. i only tested the first format with compressed files up to now.

----------------------

as you see i basically used the same setup as my currently working viasraid sata driver. so now i'm wondering if i should change anything like use OemInfFiles for the driver installations or remove some stuff from OemPnPDriversPath or just leave it as it's now.

any suggestions? :blink: a copy of your (working) setup files and dir would be greatly appreciated!

Thanks!

Edited by WrongTurn

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×