OK, my latest attempt at using Dale's suggested method actually WORKS. Very little was different from the previous attempt, all of the settings in nLite were identical, added drivers was the same, etc.... But it caused the re-boot problem before, and this time it does not.

This is about as predictable as the weather, stock-market, and my girlfriend!



Dale, it's good to hear you experienced the same "missing .dll" install errors and/or the BSOD errors...as they say, misery loves company...hee hee... so at least now I know it's (probably) not a problem compounded by some of my brand-new equipment going tits up...

When you say to only include the nvatabus.inf and the raidtool folder, can you clarify? I think what you must mean is to *not* add the additional files such as nvata.inf, nvata.sys, etc.... Can you list the contents of your sataraid folder just so I can compare it to mine? That way I can make sure I'm not leaving anything in there that might be causing the still-present device manager question marks/errors/wizard pop up boxes/blah blah...

I took your advice and had nLite remove the SCSI/RAID drivers in nLite's "Drivers" section and the 4 separate IDE drivers in the "Hardware" section. I'm betting this has something to do with how this method seems to work (at least some of the time...am still not sure why it worked this time and not the last time...)

EDIT: After all of this I just had to laugh my butt off uncontrollably for awhile. Why does it suddenly feel like my $2000+ gaming rig is being held together by gum, string, and duct tape? THANKS NVIDIA!

There are only small differences between that, what Dale did and that, what works for me and a lot of other people. We all used the [OemInfFiles] method, which was integrated the first time into nLite by version Beta6.
The problems Mjswoosh was writing about, occured during the first (TEXTMODE) part of the installation. During this setup part the installation procedure of Dale and me is nearly identical, because we have very similar hardware.


It really can have something to do with it, if you removed the Microsoft STANDARD-IDE-ATA/ATAPI-CONTROLLER, because this wrong driver is installed by Windows Setup instead of the correct NVIDIA nForce IDE Performance driver NVATABUS.SYS.
Is it really possible to delete this driver by nLite? If yes, that would be a good idea anyway.

@mj

My folder looks like this (except it should be WinXP not Win2k )

http://teamicenine.com/images/IceNine/protag/nvraid.bmp

@Fernando

I simply select everything in the "drivers" section of nLite to remove.

Oh and I had a brain fart and thought the ide crap was included in there, sorry about that.

Besides selecting to remove all drivers I also select to remove these under the "hardware support" section.

ALI IDE Bus Driver
CMD IDE Bus Driver
Intel IDE BUS Driver
Toshiba IDE Bus Driver
VIA IDE Bus Driver

Perhaps removing those things is what allows me to successfully install without the reboot loop.

The raidtool folder will not be necessary.

But now to the driver removal by nLite:
The longer I think about what Dale has written the more I believe, that the removal of certain drivers could be a very easy way to solve a couple of nVRaid problems.
Tomorrow I will test these things.

dale5605, you are onto something, by removing BUS Driver nlite breaks default Windows signature for their IDE drivers and by that it makes it equal to other third party txtmode drivers...thus nvraid gains priority...now if Fernando 1 you can confirm ?

Thx for the reply Fernando. Is it not everyone getting this exact same problem then? It's very bizarre - without making any handmade changes - simply slipstreaming SP2 onto an original XP source folder, adding's Ryan's latest updates, and then integrating all the nvidia drivers (E'net, SATA, RAID etc), I seem to have a perfectly healthy OS at the end of installation (give or take the odd random reboot). I stress however that I can go through hours and hours of games, putting my CPU at full load almost constantly, yet the system's perfectly stable. Just letting it idle however will indefinitely result in a crash at some point, usually within a couple of hours.
Update: For some reason, when transcoding avi's using Nero VisionExpress to put to DVD, it can never complete a DVD, whenever I get back to the machine, 1.5 hours later or so, it's rebooted itself. I'm not 100% sure whether this is related to the initial reboots you guys seem to be having or not.

Not sure how you guys diagnose these things exactly, if it helps, i can post my presets etc, both for those of you that can't get you're systems to work, and for me, who's fondly remembering the days I last had a stable system...it was a AMD XP 2000+, with a known faulty 512mb of RAM, which didn't bother it in the least, and an FX5200. Oh the memories...

Please help us and others to find the reason for the different handling of nVRaid systems by the Windows Setup routine on different systems and/or different nLite settings.

Very interesting are the following details:
1. What sort of Raid system do you have (nForce3/nForce4, Sata/Pata)?
2. Did you remove any drivers by nLite? If yes, which ones?
3. Which version of the nForce chipset driver package did you use?
4. Which driver subfolder (SATARAID/PATARAID) did you integrate as Textmode driver?
5. Have you made any modification within the driver subfolder (by editing the TXTSETUP.OEM or copying other files into the folder), before you used it?
6. You have written, that you integrated SATA and RAID. Did you integrate them by choosing the both required drivers after pointing to the SATARAID /PATARAID subfolder or did you integrate them within 2 different steps?

Well since fatalzaviour was able to integrate with no extra changes like me he probably removed those ide and scsi drivers? I'm hoping that is the case because that would confirm this maybe being the solution.

But I believe the problem he is speaking of is completely unrelated. Fatal, set your options to not automatically reboot when the system crashes. Then when it does crash you will see the blue screen and then note what that error message is. That will point you in the direction of the problem. But the rebooting we are talking about with regards to nvraid integration is just after the install of windows, not after windows has already been up and running for a few hours.

Within the next days I will try to find out the driver or driver family which has to be removed by nLite to prevent the conflict with not WHQL-certified NVIDIA Raid drivers.

But to make it clear: The removal of all or a lot of the standard drivers from the Windows CD would not be a good idea for everyone. If Mjswoosh really removed MS standard drivers, he should not be surprised, that the Windows setup routine has interrupted the installation by asking for several DLL-files and that he has seen yellow question marks in his hardware device manager.

The best solution for our problem is to find an easy way for everyone to integrate the not WHQL-certified nVraid drivers into a bootable complete Windows XP CD with the option, that it contains all standard drivers and all standard features. People, who are using tools like nLite, want to be free in their decision, what they want and what they don't want, and a lot of people change their mind about these things.........

CU
Fernando

My latest attempt using the OemInfFile method + removing the built-in SCSI/IDE drivers seems to work (at least on the surface).

I believe the reason this attempt finally worked for me (& the last 2 attempts using the OemInfFile method did not) is because I did not use any of the SATARAID files at all...I only used PATARAID files when integrating with nLite and also in the OEMDIR directory. Since all of these files appear to be identical I am not sure why it would make any difference. However, this is the only difference in my method between the previous 2 times that did not work and this time that did finally work. I will re-test this again in my next nLite build by using the SATARAID folder files and just copying the correct nvatabus.inf over from the PATARAID folder and see if it results in the "missing .dll files" problem again.

1. The system seems to correctly identify the hard drive as NVIDIA STRIPE. I looked at the device driver in Device Manager and it appears to be WINDOWS\System32\DRIVERS\nvraid.sys.

I loaded up drivers for my wi-fi PCI card and took some time to transfer various files and apps over from another PC this system. No problems with that or basic computer operation.

2. However, Device Manager shows SCSI & RAID Controllers as "Unknown Device". I tried the "Update Driver" option several times but with no luck. Regardless of which RAID driver I try to load, it tells me every time that it cannot load the driver for the device.

3. It seems that trying to load the drivers for this "Unknown Device" and/or trying to remove it from Device Manager causes the "endless re-boot" problem. This particular system load was working perfectly and I re-booted several times without incident...BUT after I tried to load the drivers for the "Unknown Device" and/or when I tried to remove the device and then re-boot it started endless re-boots again.

Fernando & Dale...do either or both of your Device Managers show the SCSI & RAID Controller as "Unknown Device"? I'm wondering if removing the standard SCSI/RAID drivers with nLite causes this Device Manager issue? Or does your Device Manager correctly display NVRAID?

Time to try another slipstream/re-load....

What do you mean you "changed" the nvatabus.inf to nvraid.inf?

In case DrTweak doesn't check back any time soon, does anyone else care to let me know what he meant by this?

Ok, some information that may be useful to you then:
It's an Asus A8N-SLI Deluxe (nForce 4 SLI chipset), and the raid array is a RAID 0 SATA with 2x 80gig Seagate 7200.7s. I'm using the 1013 bios, which has the nvraid 4.84 bios.
I didn't remove any drivers with nLite, not MS or any others.
I used Forceware AMD 6.66 (32-bit).
I integrated the SATAraid subfolder for the Textmode driver.
I made no modification to the driver subfolder (I was going to edit the Txtsetup.oem as you suggested, but thought it looked like a bit too much hassle, and thought I'd give it a whirl and see if it worked without editing first.
I can't quite remember, but I'm 90% sure I just pointed nlite to the Sata_ide drivers first, and then the Sataraid drivers 2nd (I need both sets, as I also have a Maxtor 250gig on the 3rd controller for storage). I did select all the options on nlite, tweaking etc. but for the most part I left these unchanged and just skipped past them. I added my cd key, network name etc. but didn't make any huge changes. Just let me know if I can provide any more information other than this.

On a side note, is there a way to get rid of the US language, and just install the UK bits? I can add the UK, and tell it to use it, but I can't seem to find the US language to remove in nlite. I'm thinking it uses the US language during install, but I'd like to remove it if possible.

I think Dr Tweak means that he just changed the name of the .inf file.

Btw, I completely sympathise with you woosh. It seems that no (semi) cutting edge system that I put together these days is completely problem free. It's rather annoying....

@fatalsavior, that's nvidia for you...

@Fernando
I seriously doubt his "missing dll" problem is related to my method in any way.

Using my method I get absolutely no missing file errors whatsoever, no problems with windows, no errors or question marks or anything weird in the device manager, nothing wrong whatsoever.

And why do you think there is any harm in removing those windows ide drivers? It doesn't hurt the system like you imply it would. My computer runs better without them. If you have a nvidia chipset why would you want to keep VIA, Intel, CMD, etc. drivers in there? They do no good at all on a nvidia chipset, and you could have absolutely no use for them whatsoever. So I fail to see the concern here.

I see both POVs. For me, removing all other IDE drivers seems like a harmless exercise, if I'm going to install a new board, then it's likely I'll format and use a fresh version of windows. With the A8N-sli deluxe, it's unlikely I'll ever need any more storage controllers, so I'm not going to miss them.
For people that don't know what they're doing however, I suppose it could lead to problems, removing more than necessary, dependencies on other system devices. IDE controller drivers are one of the things I'd feel very comfortable removing, it's almost a dead cert you won't be needing them in the future. Is there any disadvantage at all of removing them?

1. As long as I integrated the nVraid drivers by [OemInfFiles]-method, I have never had any yellow question mark or an "Unknown Device" within the Device Manager. The Device Manager always showed the correct NVIDIA nForce4 Serial ATA Controller and the correct NVIDIA nForce Raid Class Controller.
2. Today I have tested to integrate the nVRaid drivers with nLite Beta6 without any "handmade" changes posted within post 1, but with the removal of the standard SCSI/Raid drivers by nLite. Result: Endless reboots. So this is not the trick for an easy nVRaid integration for everyone.
As a second test I just deleted the ATAPI.SYS (as atapi.sy_) from the I386 folder and the standard SCSI/Raid drivers. Result: Endless reboots again.

So the search for the exact combination of removing special drivers and doing special settings to prevent any "handmade" changes is not yet finished.

It's not SCSI drivers that are connected, it's the IDE drivers.
Best would be to remove both.

I cannot find a special option to remove the IDE drivers by nLite. There was only a combination of SCSI drivers and something else and I removed that combination.

Why bother doing that? The missing file that is needed to do the install this way is called nvatabus.inf, right? So, I don't understand why he'd rename it...

Yeah, just to clarify, I never experienced the "missing dll" problem using your method. I experienced the "missing dll" issues during my first couple attempts at using the OemInfFiles method. My last attempt, however, at using the OemInfFiles method went through perfectly. Unfortunately, Device Manager still shows the "Unknown Device" in the SCSI & RAID DEVICE section....

This is the part that still has me stumped. I seem to be able to get the system to load just fine using BOTH methods, but for whatever reason Device Manager still gives me an "Unknown Device" in the SCSI & RAID DEVICE section. UGH. I keep thinking I must be doing something wrong, but I've honestly followed both methods through several times exactly as shown and continue to have this issue....

The IDE drivers can be removed individually in nLite's HARDWARE section (not in the DRIVERS section).

So I guess I'm the only one with this "Unknown Device" issue in Device Manager, huh? WTF am I doing wrong?

Wooosh, what board have you got. I believe you've posted it somewhere, and I think it may have been an A8N-sli deluxe, but I may just be making that up... If so, is that the only unknown device that you have in the system. If you right click, properties etc. and go to the device ID, what's the string that it gives you there? My current train of thought is that it's nothing to do with the RAID array, and it's the ATK 0110 Acpi Utility, the driver for which is part of Asus's AI overclock software (you don't have to install it all, just extract it and point windows to the driver). However, I may have got this all wrong, and just gone off on another of my ramblings...

BTW, I'm well aware that this has nothing to do with SATA, RAID, or any serious device issues for that matter. Do you have any 'known' devices showing in device manager, namely Nvidia nForce RAID Class Controller and Nvidia nForce4 Serial ATA RAID Controller. If so, that should be your lot and it wouldn't surprise me if windows has placed the Acpi Utility there just to play silly b*ggers with you.
Hope this is of some help

I'm using the BFG nFORCE4 Ultra board. The "unknown device" appears underneath the SCSI & RAID DEVICE section. It is the only unknown device in the Device Manager. The ID string for it is: ACPI\_NVRAIDBUS\3&2411E6FE&0

So, it appears that the system at least knows it is an nVIDIA RAID device! (can u detect my sarcasm?) What I don't understand is why I cannot use the Update Driver option to successfully load the drivers? I also tried loading the drivers using the 6.66 package within Windows but that didn't work either. Basically, it's as if Device Manager knows there is an NVIDIA RAID controller but something is preventing it from letting me load the correct drivers. This makes me think that I am somehow doing something wrong with one of the .inf files during the nLite CD creation phase and this is causing some kind of error telling the system that the drivers are actually located somewhere where they are actually NOT located (or something like that). But, then, even that wouldn't explain why I can't just use the 6.66 driver package within windows, would it?

The relevant known devices as they appear in my Device Manager:

Disk drives:
NVIDIA STRIPE 372.61G

IDE/ATA ATAPI CONTROLLERS:
NVIDIA nFORCE4 Parallel ATA Controller
NVIDIA nFORCE4 Serial ATA Controller
NVIDIA nFORCE4 Serial ATA Controller

SCSI and RAID Controllers:
***Unknown Device*** with ID string of ACPI\_NVRAIDBUS\3&2411E6FE&0

Sound, Video, and Game Controllers:
NVIDIA® nFORCE™ Audio Codec Interface

System Devices:

nForce4 Hypertransport Bridge
nForce4 PCI-Express PCI Root Port
nForce4 PCI-Express PCI Root Port
nForce4 PCI-Express PCI Root Port
nForce4 PCI-Express PCI Root Port
NVIDIA nForce PCI System Management
**********************************
Unless I'm mistaken there should be more than one nVIDIA entry under the Sound, Video, & Game Controller section. I'm also missing an ethernet/lan adapter entry even though I have repeatedly tried to integrate it. On the plus side, the drivers for my Gigabyte Radeon X800 XL successfully integrated and installed and DO appear in the Display Adapters section.
**********************************

Thanks for all the input! I'm a little frustrated but am actually having a little fun with this. It's certainly providing a few laughs at nVIDIA's expense, even if I'm the one that's dumb enough to spend this much time beta testing their hardware for 'em!

ok, I'm starting to think I must be doing something wrong during the nLite creation phase. Here's the process I've used:

1. nLite 1.06b --> int. RyanVM's hotfixes, int. nFORCE4 6.66 / ATI Catalyst 5.8 / Netgear WG311T wi-fi drivers, remove WINDOWS SCSI/RAID & IDE drivers (& a bunch of other stuff. Final nLited WindowsXP size = 295MB). I add all 4 "patches" and several of the tweaks. I use "FullUnattended" and "Oem Preinstall".

During the integrate section I point directly to the nFORCE .inf files in the AudioDrv, Ethernet, SATARAID, sata_ide, and SMBus sub-folders.

2. Here is the relevant file structure for my finished nLite XP cd: X2PVOL_EN\$OEM$\$$\OEMDIR

3. OEMDIR Folder Contents: idecoi.dll, nvatabus.inf, nvatabus.sys, nvcoi.dll, nvide.nvu, nvraid.inf, nvraid.sys, nvraidco.dll
(all files copied directly from the 6.66 SATARAID sub-folder except the nvatabus.inf which was copied from PATARAID sub-folder)

4. Then I go to the X2PVOL_EN\I386 sub-folder and modify the WINNT.SIF file as instructed with the following 2 lines as shown:

OemDriverPathName = "%SystemRoot%\OemDir"
OemInfName = "nvraid.inf","nvatabus.inf"

5. I don't use nLite to create an ISO. I use the Microsoft Corporation.img file and burn the CD in Mode 1 in NERO.

******************************

I honestly don't see what I'm doing differently than the rest of you guys so am a bit of a loss here!

Thoughts: am I somehow creating a faulty folder/sub-folder structure? Does my CD directory structure somehow look differently than it should? Do I need to copy the files from PATARAID folder instead of the SATARAID folder into the OEMDIR? Does it make a difference if you use the files from the SATARAID folder or the PATARAID folder? I wouldn't think it should matter as long as you make sure to copy the nvatabus.inf file as well. Do I need to modify and/or rename any of the .inf files?

Once I get into Windows I continue to have the "Unknown Device" in the SCSI and RAID Controllers section as well as missing an ethernet/lan device entry. I feel like I must somehow be mis-directing the .inf file during the nLite creation phase so that when windows looks for these driver files it is looking in the wrong place.

Ahhh...fun, fun, fun with nVIDIA RAID!!!

EDIT: I just noticed that for some reason when windows first starts it actually identifies it as a "SCSI Device" down in the System Tray. When I try to use the Update Driver section it also identifies it as a "SCSIAdapter". Then, after manually trying to install the 6.66 driver package it identifies it as NVIDIA RAID CLASS device in the system tray (but still "SCSIAdapter" in Device Manager when I try to use update driver). Not sure if this is significant, but I thought I should mention it.

Hmmm, very bizarre. I'm afraid I can't be much help for now (It's 2am here now and I've done 40miles of cycling today...) but I'll just contribute a little...
Should there be any nvidia related bits in Sound, Game etc.? Certainly not sound I should imagine, Nvidia didn't incorportate sound into the NForce4 did they, I know on the Asus and most other makes, (all apart from MSI I believe) Realtek 850 codecs were used, so I would start by not integrating them. (AFAIK anyway - please correcy/flame me if I'm wrong).
When you try and integrate the E'net drivers, does nlite add them, but when you come to install windows, they've disappeared, or does nlite complain from the start. For me, it was just a simple case of integrate, et voila! they worked. Certainly when you come to install the driver package in windows, you should be able to get these installed. Have you tried installing them in safe mode?

Don't integrate Sata_ide folder also lol. That will probably only cause you problems. Just integrate sataraid folder with nvatabus.inf added.

I'm pretty sure that is your problem because windows can't properly integrate duplicate files. And when you are integrating both those folders they are all duplicate files. So the result is probably some kind of hybrid driver which manages to allow you to use your raid array but can't indentify properly in device manager.

Oh and just a small tip, delete the "NAM" folder inside the "ethernet" folder before you integrate the ethernet driver. It is just the crap installer for nvidia's crap "hardware" firewall. Takes up a lot of space.

Very strange, because that's exactly what I did, as mentioned, without modifying the Txtsetup.oem, or creating an OEM dir, yet, windows works absolutely lovely...up to the occasional restart. Checking in device manager, all drivers provided by nvidia, and all seem ok.
Have you tried an install of the drivers in safe mode yet wooosh?

Does nlite copy that folder then, even if you just point it to the Ethernet driver? You learn something new every day.

When you select a .inf nLite integrates that directory and subdirectories also...

Mjswoosh, you have done everything correctly.
The reason for your "Unknown Device" should lay somewhere else.
After having googled with your mentioned ID string, I found this:
http://forums.guru3d.com/showthread.php?th...goto=nextnewest
What is about your BIOS (is it actual, correct settings)?
What is about ACPI (activated or not)? Did you make any ACPI presettings by nLite section "Unattended Install"?

EDIT:
Within the DFI-Street Forum I just found something, with might be very interesting for us all:

Ok, got it working! WOO HOO! Wow, that only took 3 days!

The only thing I changed was the following:

1) The only files I left intact in the OEMDIR folder are: nvatabus.sys, nvatabus.inf, idecoi.dll. I deleted the rest.

2) I modified the WINNT.SIF file to read:

OemDriverPathName = "%SystemRoot%\OemDir"
OemInfName = "nvatabus.inf"

I'm not exactly sure why it didn't need the nvraid.inf/nvraid.sys files in the OEMDIR folder...but for whatever reason it seems to be working correctly now. Anyone have any idea why this works & why the other other method (including all of the other files) didn't? Maybe it has something to do with the fact I integrated the sata_ide file as well? I'd guess Dale is onto something that somehow it created a weird hybrid driver file and WinXP didn't know where to look for the RAID drivers... SO, I guess if this is true then you can EITHER integrate the sata_ide file OR include the rest of the files in the OEMDIR folder, but not both?

Can anyone else verify what their Device Manager entries look like so I can compare mine? I now have the following 2 entries in my DM:

NVIDIA Network Bus Enumerator
NVIDIA Network Bus Enumerator

SCSI and RAID Controllers
NVIDIA nForce™ RAID Class Controller

****************************
EDIT: The only remaining problem was that for some odd reason the nForce4 ethernet drivers did not load up despite the fact I integrated them every time. I thought this very odd. It turns out the default setting in the latest BFG bios is MAC LAN: "OFF". I re-checked it twice just to make sure I'm not an even bigger i*d*i*o*t than I already thought! haha When I load "optimized defaults" in the BIOS it turns the mac lan *OFF*. Is this normal for the nFORCE4 chipset? I've never ran across a BIOS that turns the built-in LAN off by default...

Congratulations, this is totally correct.

Everyone...THANKS SO MUCH FOR YOUR HELP!!! I'm not sure why this latest method works without all the other files in the OEMDIR folder, any ideas? But it does work, so that's the important part!

People with an nForce4 SataRaid system will need only those 3 files you have left within the OEMDIR folder.
The other files are just copied, because it's easier than to pick up special files and maybe people with other Raid/Sata systems need other files. AFAIK these not needed files do don't influence the integration of the nVRaid drivers.

EDIT:
Mjswoosh, it is not easy to explain, why you succeeded this time.
Fact is, that you succeeded by creating the $OEM$\$$\OEMDIR folder as I have described in post 1 of this thread.
The simply removal of some files out of the OEMDIR folder has not been the solution. I just tested it again. The removal of these files do not influence anything.
Please give uns an answer to the following questions:
1. Have you made any changes concerning your BIOS (new version, new ACPI-settings etc.)?
2. What was your nLite setting within the section "Unattended Install", when nLite asked for "Computer Type"? Did you leave it as Default ("automatic") or did you choose a specific computer (ACPI-) type?
3. Is it possible, that you made - concerning "Computer Type" - another setting than before?

Thanks!

It works for me without oem folder, just integrating nvraid drivers with Nlite beta 6!

I used the 7.13 sataraid drivers, just copied the nvatabus.inf from the pataraiddriver folder, and i also have nvata.inf and nvata.sys from the sataide folder dont know if they are needed but Nlite puts them in the NLDRV folder anyway.
I also removed the scsi/raid and ide drivers with Nlite
This is with a DFI nforce 3 ultra d motherboard with nvraid bios 4.79
I also managed to integrate raid drivers for my silicon image 3114 pci adapter at the same time and works just fine.

Yes, if you remove the critical drivers, which are favoured by MS during installation, it is possible to integrate the nVRaid drivers without using the [OemInfFiles] method. I tested it and it worked with my system (nForce4) too.
The problem is, that you might get "Unknown Devices", because some other needed drivers may not be installed.
CU
Fernando

I followed all the instructions

plz tell me if I done something wrong

1.Changed txtsetup.oem in pataraid folder
2.Integrated with nlite pataraid,sataide,sataraid
3.Changed the winnt.sif
4.Copied all the content from pataraid,sataide,sataraid to \$OEM$\$$\OEMDIR

I have a Shuttle AN50R with Nforce3 without raid array
I want to integrate all the graphics and Nforce3 drivers
PS: the sataraid,pataraid,sataide drivers I used where from the Nforce4 package

heres my preset :

Why did you integrate all IDE\WinXP subfolders (PATARAID, SATARAID, SATAIDE)?
If you have S-ATA drives, but no Raid system, you only will need the SATARAID subfolder for the Textmode driver integration. nForce3 S-ATA systems are supported by NVATABUS.INF.
But before you integrate the drivers from the SATARAID subfolder you should open the file txtsetup.oem from the folder SATARAID with the editor, go to the section [Files.scsi.BUSDRV] and replace the name nvraid.inf by the name nvatabus.inf.
Within the OEMDIR subfolder you should only copy the files from the PATARAID subfolder.

All the other drivers (Ethernet, Gart etc.) have to been taken from nForce chipset packages suitable for nForce3 systems.

big thanks fernando ! Ill try that and gives some info then

I have a Gigabyte K8NXP-SLI mobi with latest bios F9, however raid bios is 4.81. Is there anyway I could update the raid bios to 4.84?

The Raid BIOS is a part of the mainboard BIOS. So the easiest way to get an uptated Raid BIOS v. 4.84 is to check, if there is a new mainboard BIOS.

Theoreticly the integration of a new Raid BIOS into a mainboard BIOS can be done by the user (you only need the new nVRaid BIOS and a special tool), but the consequences in the case of the failure are so great, that I would never give the advice to do it yourself.

You have either to wait for a new mainboard BIOS or to take an nForce chipset driver package lower than v. 6.66.

CU
Fernando

Even though 6.66 is working for me on nvraid 4.81

I'm curious where you got the information that 6.66 drivers won't work with nvraid older than 4.84 fernando. Because it works fine for me.

Dale, as we already know, you are a lucky man, but there are a lot of others in the world.

I got the information about the correlation between the nForce Raid driver version, the nVRaid function and the Raid BIOS version from a lot of people.
Look here:
http://www.msfn.org/board/index.php?showto...ndpost&p=385843
and here:
http://www.planetamd64.com/lofiversion/index.php/t10928.html
and here:
http://forums.nvidia.com/index.php?showtop...t=0&#entry44505

That is why I have put this information into post 1 of this thread.

CU
Fernando

This was an important information for all users of a NVIDIA Sata/Raid system

It really makes sense to let nLite remove those IDE drivers, which are causing the problems with the nVRaidSata drivers, because in this case there is no need for creating an OEMDIR folder and no need to edit something within WINNT.SIF.
The only handicap of this method is, that the removal of too many or the wrong drivers may cause new yellow questionmarks within the Device Manager.

Meanwhile I have tested this "Driver-Removal-Method" on my nForce4 SataRaid system - and I have got it to work without any problems (no endless reboots, no yellow questionmarks, no error popups!

As a consequence I have added this new method into post 1 of this thread.
So there are at least 2 easy methods to integrate the nVRaid drivers into a bootable CD by using nLite.

Thanks to Dale and Metalljens for their posts. They gave me the push to try this method.

CU
Fernando

Hey, Fernando...

I got it working as you described in Driver-Removal-Method after several iterations with nLite. I tried a **lot** of different driver/OS combinations before I read your post. Finally got the NVRAID drivers to work with a clean nLite Windows XP SP1 Slipstream install. Otherwise, all your other instructions worked perfectly. Thank you for making it possible to install Windows XP on my new nForce SATA RAID array!

My configuration (thanks to you):

Motherboard: MSI Neo4 Platinum PCIe (not SLI)
Processor: AMD Athlon 64 X2 3800+ (dual core)
Disks: 2 Western Digital Raptor SATA (70GB)
Operating System: Windows XP (32 bit) installed on nForce4 SATA RAID!

Thanks again!

-=Bob :-)

has anybody tried integrating the SATA drivers for non raid setup on a Nforce 2 motherboard? i have 1 PATA and 1 SATA drive in my system and want to make nlite cd that i can install the SATA drive as the boot drive. i have an Abit AN7 motherboard and would like instructions on what folders i need to integrate. i read through the thread and frankly it has me a little confused i have the latest nlite installed and ready. thank you

Although I have no nForce2 motherboard in use, I think, that you can take the PATARAID subfolder. The nForce2 Serial Ata Controller is supported by the NVATABUS.INF.

Fernando 1,
stupid question if i may i have integrated the SATA driver into my install CD but am wondering - in order for the SATA drive to work in windows it needs the controller driver installed to be seen by windows. you know the silicon image driver, do i need to integrate it also??