Thanx for your reply and the clarification concerning the CAT files. I will test your special driver remix.
To take the content of the LEGACY folder for the integration of the nForce SataRaid drivers is maybe not the best, but certainly the easiest method. If you take the SATARAID subfolder, you have to copy the NVATABUS.INF and the NVCOI.DLL file (and maybe the both CAT files) from other subfolders into the SATARAID folder prior the integration procedure. According to my experiences you get the same (good) results by using the easier LEGACY method without any copying.
CU
Fernando

Hi All ,

I am having this error message with nLite 1.0 RC3 : "D-The object is in use elsewhere." . This occurs during the driver integration stage.

I am trying to integrate drivers version 6.70 (Nforce) from nvidia for my motherboard. The curious bit is this : Whenever I integrate the Sata Raid drivers only there is no problem, However , whenever I include drivers for other components such as the ethernet card , the SMbus drivers etc. The error manifests itself and then nLite appears to hang indefinitely

Please assist if you or anyone else can .

Best Regards,
Caspanis

I have never had such an error message.
Nuhi has written, that he fixed this error with RC3. If not, please write a post within the sticky thread about RC3 experiences, because Nuhi will not read all posts within this thread.

So... has anyone made an install package for mediashield? I've haven't had any problems with driver integration, but hate having to reinstall drivers just for mediashield... I'm new to this hacking up windoze thing... anyone? Actually, it was the need to have the nvidia drivers preinstalled that led me to nLite... I'll even share my first mistake that had my head spinning around and around... %OEM% vs $OEM$... I won't even say how long it took me to see that...

So... anyone got that mediashield package? I really need to be boxing this thing up by Monday... heh.

I don't have any experience with mediashield, because I have a mainboard which supports only Raid0 and Raid1.
AFAIK you need a board with Raid5 and at least minimum 3 Sata2 hard disk drives. Here are the details: http://www.nvidia.com/object/feature_raid.html
If your system is ready for NVIDIA mediashield and if you have confgurated a healthy Raid5 array, you should be able to integrate the SataRaid drivers as I have described in post No 1.
CU
Fernando

Err... uh... I only have two SATA-I drives, setup as RAID1. I've already got the drivers installed. That was #1 on the priority list, as I don't have a floppy drive installed on this box. Now I'm trying to add all the other junk and give it a few tweaks. The NVIDIA installer dumps mediashield on when you load the "storage driver". Ofcourse I speak of nforce4... something that has the raid controller onboard...

NVIDIA\nForce4_amd_6.70_winxp2k_english\IDE\WinXP\raidtool

In other words, no option via nvidia installer to choose that or not. Ends up in the program files dir, AFAIK. Listed in the NVIDIA program group.

I can probably come up with an installer on my own given enough time, but was hoping to throw it on a disk before it goes out the door. As I said before, kinda new to making custom windows disks. More of a linux kind of person. Still having to figure out how to get all the installers already built, to work correctly for me using RunOnceEx. An MSI for this would be great, but if it don't exist yet, it don't exist. It runs without any registry changes, right out of the dir, so I suspect it won't be too hard to make *something* work...

k (mmmmkayyyyy)...

made one. kinda quick and dirty, but it works. I still don't understand why they don't make it possible to install the package separately. whatever.

I have tried this solution to no avail, but I am afraid that I may be doing something incorrectly. Here are my system specs:

4.84 Bios, ACPI Enabled, Windows XP w/SP2
AMD Athlon x2 4200
DFI Lanparty Ultra NF4 SLI-DR
2 x Western Digital Raptor 74gb
2 x Hitachi Deskstar 250gb SATA 3gb/sec
2gb G.Skill DDR500 Ram
PC Power & Cooling 510watt PS

I downloaded nLite RC3 and tried to make several bootable iso's, but the program would freeze at the last stage and never create the iso. I instead downloaded RC1 and made 5 cds - using drivers from nforce 8.12, 6.66, 6.83, 7.13. With each CD I got a new error.

8.12 drivers - I would get a bluescreen and reboot during the windows installation
6.66 drivers - During 2nd half of Windows installation, when it says "Installing Hardware" a window would appear saying that it had found a mass storage controller and the installation would freeze
6.83 drivers - Installation would complete. After install before windows screen would get the BSOD
7.13 drivers - Don't remember what happened with these, but they didn't work

I have spent a good 10-15 hours trying to figure this out and I'm going insane. I only have 1 PC, so to check this thread I have to disable the raid array, install Windows on a single raptor drive, burn new isos, then reinitiate the raid array, only to find that the isos don't work.

The first post is great, but it is lacking very specific detail. Can you please list EXACTLY what steps I need to take, what chipset drivers to use, what unattended install settings I need to enable, etc. There was one post that went through step by step that was very helpful. Unfortunately I followed it, and had incorrectly edited the winnt.sif file and it did not work. I don't really understand the whole oemfile thing either. Could someone explain that in further detail?

Thanks so much guys for your continued effort and perserverance through this nvidia driver nightmare.

I will try to help you, unless it's not easy, because I believe, that some of your problems have more to do with your system (especially with your RAM-settings or with your 4 hard disk devices) than with nLite.
Before I can give you any advices, I need to know the following:
1. Do you have an overclocked system? If yes, is the memtest OK?
2. Is your Raid array connected to the nForce Raid Controller or to the Silicon Image Raid Controller?
3. Which of your hard disk devices are connected to the nForce Raid controller?
4. Which hard disk device (single drive or Raid array) is your boot device?
5. On which hard disk device is your partition C (boot partition)?
6. Is your Raid array "healthy"?

1. No it is not overclocked
2. All drives are connected to the nForce controller. From there I made 2 arrays, a raid 0 bootable (for OS using raptors) and a raid 1 (for files & storage)
3. All devices are connected to nForce controller
4. My raptors are the boot device and are connected to slots 1 & 2. My hitachi drives are connected to 3 & 4.
5. The C: is the raid 0 raptor array
6. Yes, when both arrays are created they appear as "healthy"

remove one of your memory chips and then try to install windows...w/ Nforce based systems...this usually worked for me....

It is not as difficult as you mean and you don't need to understand the "OemInfFiles" thing, because it is already implemented into nLite.
I suppose to do the following:
Create a bootable XP CD by using nLite RC3. If you have trouble with this version, use RC1. Take the nForce driver package 6.70 or 6.67 and integrate the content of the LEGACY subfolder as textmode driver (see post No. 1). All the other things within nLite don't matter, but if you are anxious, do nothing else than integrating these nForce SataRaid drivers. At least create the ISO file and burn it.
Then try the installation of XP from your nLited CD. If the installation fails, unplug both Hitachi drives and try again the installation. If you still have problems (BSOD), you should try to enhance the RAM voltage a little bit (0,1 V) and try it again.
Good luck!
Fernando

EDIT: The tip from rnielsen151 was a good idea. Try it with one of your nLited CD's, before you begin the new nLite processing.

Ill give it a shot. Thank you.

6.66 didn't have a legacy subfolder, but 6.67 did so I am trying those. I have the cd burned and will let you know how it goes.

YES!! IT WORKED!!!!!!! I LOVE YOU GUYS!!!!!!!!!

I'm not sure what it was, the 6.67 drivers or the extra stick of ram. I just have to remember to do this same routine if I am ever to format again.

Congratulations!
CU
Fernando
You are right, the 6.66 nForce chipset package does not contain a LEGACY subfolder (users with a SataRaid system should take the PATARAID subfolder). I meant the 6.67 package - my bad. Fortunately you have taken the right one nevertheless.

I am using an MSI MS-7185 K8N SLI X16 motherboard, which according to the nVidia driver page needs the 6.82 driver.

When I expand it, it only has a sataraid direction.

Patariad is no longer there.

Only raidtool, sata_ide, and sataraid directories exist.

Everything I have been reading shows a need to either us the pataraid drivers, or to integrate the nvatabus.inf into the sataraid directory.

I am kind of stuck as to how to build my install disk given the new structure of the updated driver file.

I have been beating this thing for over a week, and am beginning to see the bsof in my sleep.

Anybody having success with nForce4 and the kn8/sli/x16 chipset?

I have never tried the 6.82 driver package (because I don't have a SLI 2x16 mainboard), but I suppose, that you should do the following:
Copy the files NVATA.INF, NVATA.SYS, NVCOI.DLL and NVATA.CAT from the SATA_IDE into the SATARAID subfolder.
Then you can integrate the content of the SATARAID subfolder as Textmode driver by using nLite.

If you are a little bit anxious, put the content of the SATARAID subfolder (with the added files) onto a floppy disk and try to install Windows XP by using the F6 method. If your Raid array is correctly detected, you can stop the installation and create your bootable XP CD with integrated nForce SataRaid drivers by using nLite.

Good luck!
Fernando

Hi all,

Complete noob on Unattended Install here. This thread is great , and exactly what I am looking for (no floppy on my Shuttle) but very long now .. I apologise if I am asking for a clarification already answered earlier.

I have a shuttle SN26P with an Nforce4 SLI chipset and running 2 WD SATA drives in RAID0. CD/DVD drive is plugged in IDE port. I want to reinstall from scratch with a slipstream CD, and since I dont have a floppy... I have to get it right first time or I'll be in trouble.

So... just to be sure I get it right, in post #1 with the instructions, I find something slightly confusing. It says that if we choose to use the SATARAID folder, we have to copy the NVATA.INF, NVATA.SYS, NVCOI.DLL and NVATA.CAT.
Now, I am not going to use the SATARAID folder, I am going to trust Fernando 1 and use the LEGACY folder of 6.70 but just to be sure: Can you confirm it is normal that there is no NVATA.INF, NVATA.SYS or NVATA.CAT in this LEGACY folder? Also, in the LEGACY folder there is no NVRAID.CAT file but there is one in the SATARAID folder. Not needed either when using LEGACY folder for integration? (am just slightly confused since in one case with SATARAID it seems we need those, in the other with LEGACY they supposedly are not needed since they are not there).

Thx.

Trust me, you don't need to copy any file, if you just integrate the LEGACY folder of the package 6.70. You might be confused, because NVIDIA did not create LEGACY and PATARAID subfolders within their new packages as in v. 6.82 and furthermore they changed some file names, which makes it more difficult to pick up the right and necessary ones for the correct driver integration(NVATA.INF has the some function as NVATABUS.INF, NVATA.SYS has the same content as NVATABUS.SYS, CAT files are not really needed, when you take the LEGACY folder).
CU
Fernando

This Thread was SO, SO, SO Helpful for me. Thanks FERNANDO, i really aprecciate your hard work and tests.

You are welcome.
I love such a post, because normally users only give a comment within this thread, if they have a problem. But more than 33.000 viewers cannot been mistaken.
CU
Fernando

hia will this work for any riad device you are installing on say EIO AP1600 ATA133 IDE Controller Card

for example

No, this guide is only useful for NVIDIA nForce Raid systems.

ok thanks i will have a play around with the EIO AP1600 ATA133 IDE Controller Card and see if i can get it working without the floppy

The integration of the driver for this Sil IDE Controller Card by using nLite should be easy, but what has this Card to do with nForce and Raid?

Hi, nLite isn't working for me. I'm using spanish windows xp sp1 (slipstreamed & modded), and NF4 AMD drivers. nLite stucks at the preparing selected tasks stage.

Normally nLite should work with regional versions of Windows XP (in your case: Spanish Edition).
What do you mean with "modded"? Maybe is this the reason for the issue with nLite.
You should do the following:
1. Copy the content of the original XP CD (Spanish Edition) into a folder of your HDD.
2. Prepare or download SP2 (Spanish Edition) for Windows XP.
3. Then start nLite again. Begin with slipstreaming SP2 and continue with integrating the nForce SataRaid drivers according to my guide.

CU
Fernando

I mean that I added DX 9.0 and updates (svcpack.inf), drivers (using OemPnPDriversPath)...

If you are starting to create a bootable XP CD by using nLite, don't start with a "modded" system.
Begin with the original XP CD and add or remove all things later by nLite. Otherwise nLite may get problems. The same thing happens, when you change driver integrations or removals after the end of the nLite processing. In all these cases it is better to begin a new nLite processing with a clean OS.

It didn't work :|

If you want help, I need some more informations.
What kind of system to you have (chipset, Sata/Pata, Raid etc.)?
What have you done?
What happened?

I have nForce 4 SLI, with a WD Raptor SATA (plugged on nvidia sata), no raid. Lastest nLite, Windows XP 32bits.

I tried to integrate the nvidia drivers on the clean Windows XP SP1 installation, and the same happened: nLite doesn't progress, it's at the first stage, the progress bar moves, but it doesn't consume cpu or hdd.

If you have no Raid, it should be very easy, because no driver integration is necessary for the complete Windows XP install. But what you need is an integrated SP2.
So try just to slipstream SP2 into Windows XP, burn that CD with integrated SP2 and boot with it. You can install the nForce Sata drivers later (when the installation is completed).
If you want an nLited CD with integrated nForce Sata drivers, be aware to slipstream XP SP2 as first step of the nLite processing.

I slipstreamed SP2 (worked well), but the driver integration didn't work (happens the same)

How do you mean that?
What exactly happened and at what step of the installation?
EDIT:
If you are not able to install a clean Windows XP, you possibly have a hardware problem.
Did you enable the SATA ports within the BIOS?
Are the SATA HDD's recognized within BIOS?

I'm integrating drivers in the same machine I intend to install windows to. The problem is nLite: at the step "Preparing selected tasks". It slipstreams SP2 fine, but it does not integrates sata drivers. By the way, my sata hdd is working ok, under this windows partition.

Does that mean, that you can install Windows XP with the nLited CD, but without the nForce Sata drivers? Or do you have a break within the installation?
Which nForce driver subfolder did you integrate?
EDIT:
Which nLite version did you use?
How did you manage the installation on this working partition?

I would be able to install windows. If I want to add sata, I cant.


Im using windows installed on another hdd, later I installed sata drivers and the sata drive, sorry I didnt explain this very good...

You are right, it is not easy to help you because you give very little and rather unclear informations.
Why didn't you answer to my questions?
As far as I understand your posts, you did not even reach the step to install Windows XP by using an nLited CD with integrated nForce Sata drivers, because you have difficulties to create an nLited ISO image with integrated nForce Sata drivers.
If this summary is correct, then your problem is nLite and not the execution of my guide. In this case you should open a new thread within the nLite forum and explain your problem, because otherwise Nuhi would not get knowledge about this nLite problem.

By the way: Have you ever tried just to integrate the SATA_IDE subfolder of the nForce driver package 6.70 as "normal" (not as textmode) driver? Because you have no Raid system, there is no need for the raid drivers as mass controller drivers.

I would like to help you, but you should give me a chance to do it.........

CU
Fernando

Dave or Fernando, can anyone confirm the suggestion above works please? I am very interested to use this 6.82 SATARAID driver package for my regular nForce4 AMD. Some people claim in the Nvidia forums that this driver package does not generate the data corruption issues on SATA/IDE transfers that are reportedly created with older packages.
I have a feeling that since there is no Legacy folder in there, this newer package might have cleaner SATA and/or IDE drivers. I'd like to try slipstreaming with this driver version, ie without using anything in the Legacy folder. Fernando, you said 'I suppose you should do the following: Copy... and then integrate content of SATARAID' Are you positive this works with the 6.70 maybe? If so, I'll try it on 6.82 tonight.

I am pretty sure, that it will work with the 6.70 package, if you put all extra needed files (NVATABUS.INF, NVATA.CAT and NVCOI.DLL) into the SATARAID subfolder prior to the integration. This would even be better than the easy method with the LEGACY subfolder, because you have the CAT files present, which enforce the correct installation of the drivers (SYS files).
If you want to do the same with the package 6.82, there is only one problem: Within the newest nForce chipset driver packages you won't find a file named NVATABUS.INF (but a very similar file named NVATA.INF within the SATA_IDE subfolder). If you copy this file into the SATARAID subfolder, the necessary driver NVATABUS.SYS - although it is present in the SATARAID folder - will not be found by the installation routine, because the NVATA.INF points to a driver named NVATA.SYS, which is not present within the SATARAID folder. In this case you have 3 options to get a correct installation of all needed SataRaid drivers:
1) You copy both NVATA files (NVATA.INF and NVATA.SYS) from the SATA_IDE into the SATARAID subfolder (I am not sure, if it works, because the "normal" name for the nForce Sata Controller driver layed down in the SIF files is "NVATABUS.SYS").
2) you open the NVATA.INF with the editor, search for "NVATA.SYS" and rename it to "NVATABUS.SYS" or
3) you take a NVATABUS.INF from chipset package 6.67 (32bit), it contains the same SataRaid driver version 5.52.

Hope, that this is help enough.
CU
Fernando

Thanks Fernando. Will see what I can do.

OK

What was the result? Did you succeed with the LEGACY folder?

Update: I tried OPTION#1 using Win2k3 (same as WinXP) and it allowed windows to see ONE drive, and started the install....Then once it was done, and rebooted, it goes to the BIOS screen, then reboots right before starting windows

Thanks, Banshee!
Your test verifies, that option No 1 does not work the easy way (without editing the SIF files).
Did you try one of the other options? If yes, did you succeed?

YEAH! Worked brilliantly (did I forget to mention ? Sorry).

Best guide and tool I found. This thread rocks

Now I want to get rid of the IDE driver if I can and just keep the SATA. That's all.

That are really good news - Congratulations!
This will be not a problem. Go into the device manager, open the IDE ATA/ATAPI Controller, right click on NVIDIA nForce4 Parallel ATA Controller > "driver update" > not automaticly > not search, have ... > show compatible hardware. There you will find the "Standard Dual Channel PCI IDE Controller". Choose it and install it.
My personal impression about this MS driver: the nForce P-ATA (SW IDE) driver is better. I would only change this driver, if I would have a problem with it (any issue with my CDROM or DVD device), but until now everything was perfect with my IDE devices.

CU
Fernando

Okay ....

Question:

The 'legacy' method makes me uneasy, I want the best drivers possible

Will doing the legacy method with nLite then once windows is installed running the 6.70 driver installation on top of this have the same effect as if I had just used the drivers out of the sataraid folder (assuming Windows XP didn't overwrite them on install like we know it does) ??

And will this have the same effect as copying the files you specified into the sataraid folder of 6.70 BEFORE integrating with nLite?


Also if I try the copy files into sataraid folder method, since you say it is better (which I want) just not the 'easiest' .. is that all I have to do? No editing of any files or anything?


Also I see some mention in other threads of just using the 6.53 versions IDE folder to integrate or put on a floppy then just run the 6.70 installer to get the real latest drivers ... what is your opinion on this method?

When you integrate the LEGACY folder of the 6.70 package, you will get all needed drivers of this package (no need for an update later).
Just to take the LEGACY folder is the easiest method. A little bit better for the install of a Microsoft OS is it to have the CAT files within the same folder. So if you copy the NVATABUS.INF, NVCOI.DLL and NVATA.CAT into the SATARAID folder and then do the integration of this completed SATARAID folder, it might be easier for MS to take the correct drivers. No editing is necessary!
I would not propose this method, if you have an nForce Raid array, because the update of the Raid driver is not as easy as the update of a normal hardware driver.

CU
Fernando