What has the winnt.sif look like if i dont want to make an unattended install ? I had no winnt.sif in my i386 folder at all..

I just created one and put only the following line in it:

[Data]
OemDrivers = OemInfFiles

[OemInfFiles]
OemDriverFlags = 1
OemDriverPathName = "%SystemRoot%\OemDir"
OemInfName = "nvatabus.inf"


Is something missing ??

MfG Benny

Did you really read in my description, that you should create a file named WINNT.SIF?
You should make an "Unattended Install CD" by nLite and - as a result - nLite creates a file named WINNT.SIF. Then you can add the lines you have written into that file.

CU
Fernando

So that it looks like this:


[Data]
Autopartition = 0
FloppyLess = 1
MsDosInitiated = 0
UnattendedInstall = Yes
OemDrivers = OemInfFiles

[Unattended]
UnattendMode = DefaultHide
UnattendSwitch = No
OemPreinstall = Yes
OemSkipEula = Yes
FileSystem = *
WaitForReboot = No
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
TargetPath = Windows
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore

[OemInfFiles]
OemDriverFlags = 1
OemDriverPathName = "%SystemRoot%\OemDir"
OemInfName = "nvatabus.inf"

[GuiUnattended]
OEMSkipRegional = 1
OemSkipWelcome = 1

[Components]

[UserData]

[Networking]
InstallDefaultComponents = Yes


Which entries can be deleted, cause dont want an unattended Windows-Install-CD.

What does:

OemSkipEula = Yes
FileSystem = *
WaitForReboot = No
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
TargetPath = Windows
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore


MfG Benny

1. If you can install your nVRaid drivers with F6 and floppy, you do not need to create an unattended install. An "unattended install" does not mean, that everything is done for you during installation. The installation routine lets you choose the partition where the OS should be installed and you can decide, if you want to format this partition and the file system (NTFS or FAT32).
2. Please read the nLite FAQ, if you do not unterstand the lines in WINNT.SIF.

As I know, that you are German, here is my description in German language:
http://www.winfuture-forum.de/index.php?sh...ndpost&p=362434

CU
Fernando

Ok

Where can i find the nLite FAQ ??

Look here:
http://www.nlite-guide.com/index.php/NLite...usf%FChrlich%29

Here is the link to the German nLite forum:
http://www.german-nlite.de/index.php?act=idx

I just wanted to give out my deepest thanks to the hard work put into finding this solution. After many headaches from searching elsewhere this thread got me exactly where I wanted to be. The drivers intergrate perfectly on my ECS Nforce4-A939. Again, thank you kindly.

Got it working....but after the installation of windows after multiple reboots (planned) the system refused to boot and just showing a mouse arrow over a completely black screen, the next time it just showed the blinking _ on the left top of the screen, another time it boots fine.....

back to 6.53 for now....

MfG Benny

I just tested, if the new version Beta6 of nLite has brought the full integration of the NVIDIA SataRaid drivers.

The bad message:
The installation of Windows XP with an unattended install CD created by nLite 1.0 Beta6 failed, because I got again my wellknown endless reboots at the end of the installation.

The good message:
Because of the integration of parts of the [OemInfFiles] method into the Beta6 version of nLite, it will be easier than ever to get a perfect Windows XP CD with fully integrated nForce SataRaid drivers.

As a result of my findings I modified the description of the method in post 1 of this thread.

I am nearly sure, that the problems with the nForce Raid drivers will be resolved by the next version of nLite.

CU
Fernando

Here is how the things are, find driver which has nvatabus.inf in it or copy it from some subfolder when driver expanded (and all files within that folder) and just integrate, it will work. No need for $oem$, nlite already makes nldrv which is for same PNP purpose.

Some users tested without any tweaking and it worked...so maybe you should all compare which nvraid versions do work "from the box".

I am not sure, that there is no need for the $OEM$\$$\OEMDIR folder. AFAIK is the presence of the NVATABUS.INF file not very helpful during TEXTMODE section, but necessary during GUIMODE section of the installation.
Tomorrow I will test it by copying the NVATABUS.INF file into the SATARAID subfolder, before integrating the SataRaid drivers as Textmode drivers.

Nevertheless should "nvatabus.inf" been added within the [OemInfFiles] section of the WINNT.SIF for systems with nForce4 SataRaid .

EDIT:
As Nuhi proposed, I just tried to integrate the drivers from the PATARAID subfolder (which have NVRAID.INF and NVATABUS.INF inside). The result was: endless reboots. But I was astonished, that the OS install routine detected my SataRaid Array within TEXTMODE part of the installation.
As I recognized now, nLite Beta6 does integrate both INF-files into the [OemInfFiles] section, when you integrate the PATARAID instead of the SATARAID drivers. But due to a reason I don't know, the full integration of the nVRaid drivers is not realized by nLite Beta6.
So we have still to do some manual work.....

let me know how you make out Fernando. Your method on the first page works FANTASTIC. I too had endless reboots yesterday if I did nothing but integrate normally. After following Fernando 1's easy instructions on the first page to my already created image I was into my new windows is near minutes without a hiccup. Good work Nuhi and Fernando, you have made my day and my formats much better to look forward to.

Fernando 1, huh still didn't work for you guys...weird...for some it helped fully.

Ok, I hope we will solve this soon ... but without $oem$ if possible.

Gonna contact you when I'm ready, thanks.

thanks for the patience and continued support on this matter Nuhi. I know you must be quite frustrated and had enough of this whole **** nvraid business. I am glad we at least have an option with the $OEM$ whereas before we had nothing. If you could get it to work without the manual directory structure then by all means please see what you can do. If you need a tester I am always ready and willing.

I don't see how the nvraid is a problem anymore. Are you on a nforce3 board or something fernando?

I have tested twice on actual install. Once I tried just integrating sataraid folder without using nvatabus.inf and it failed with endless reboots.

Then I first put nvatabus.inf into sataraid folder and integrated sataraid folder and it worked perfectly just like that. Didn't have to do anything extra.

This was all done with the 6.66 WHQL drivers.

I did not use "oem preinstall" option.

Also, if it matters I used unattended mode "DefaultHide"

My board has an nForce4 Ultra chipset (DFI Lanparty NF4 Ultra-D).
For my last tests I used the 6.66 driver package too (the nvatabus.sys is not WHQL!).
Since I use nLite Beta6, I take the default options for the unattended install (with activated "Oem Preinstall" and as "FullUnattended").
This weekend I will try it the way you have done it (precopy the nvatabus.inf into the SATARAID subfolder and with disabled "Oem Preinstall"). As you may have seen some posts above, just to take the PATARAID subfolder does not work for me.

EDIT:
I just tried to integrate the SataRaid drivers by the way dale5605 had described above. I copied the nvatabus.inf into the SATARAID subfolder, integrated the drivers from the SATARAID subfolder as textmode drivers, deactivated "OEM PreInstall" and choosed "GuiAttended Install".
Result: Endless reboots!
So this is not the solution for all users.

CU
Fernando

GUIattended? I use defaulthide, but I don't think those should matter anyway? If I understand correctly what I have heard then as long as you are doing an unattended option instead of no unattended then you are ok.

But I will give benefit of the doubt maybe something else is the problem. I know that I removed with nLite all IDE drivers such as Intel, VIA, etc. I also removed RAID/SATA drivers.

Ok I think I have solved the problem, some of this may or may not be unnecessary but should work.

Hopefully this will work for you fernando, otherwise I am not sure what we are doing differently since we have same motherboard and same drivers and same nLite.

This is what I do:

Take folder: E:\nforcedrivers\IDE\WinXP\sataraid

and cut and paste it to a safe place like the desktop

Now copy nvatabus.inf from "pataraid" folder into "sataraid" folder.

Now copy nvata.inf AND nvata.sys from "sata_ide" folder into "sataraid" folder.

Now copy the "raidtool" folder (yes the actual entire folder itself) and paste that INSIDE "sataraid" folder.

It should install properly and everything.

Now when windows loads up device manager should give you an error. Click ok and then device manager will pop-up saying it needs to install PATA controller or whatever. Click "install automatically(recommended)" and let it install it. It will pop-up again for SATA controller or whatever. Again let it install.

Now everything should be properly installed and you should have no problems.

That seems to be an interesting method. I will try it tomorrow.
What I cannot understand is, that you wrote you were able to create a Windows XP CD with integrated nForce SataRaid drivers by using nLite Beta6 without any "handmade action" .

yea this sure seems handmade to me lol.

This is the same reason why I cannot understand why it doesn't work for you. Nuhi fixed nvraid integration so now it works through nLite and you don't need the handmade stuff anymore, works for me.

You could try just putting the "raidtool" folder into sataraid along with nvatabus.inf.

I know those 2 in there worked for me. Maybe raidtool folder is your problem.

This should work for you fernando.

Go into the extracted folder from the driver package. Then go into "IDE" and then either "Win2k" or "WinXP" whichever your OS is.

Go into the "pataraid" folder and then copy "nvatabus.inf".

Go to "sataraid" folder and paste that file in.

Copy the entire "raidtool" folder INSIDE the "sataraid" folder.

If you have done this correctly this is what you should see.

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

You should not select the oem preinstall option.

@ Dale:
Thank you very much for your several posts.

I know, that you really want to help us all, but, I'm sorry to say, your posts are a little bit confusing for me.

Once you wrote this:

Then you wrote this:

Within the next post you propose this:

Your next idea:

And this was your last recommendation:


At least I decided to do exactly, what you recommended within your last post.

Result: Endless reboots!

Dale, please think about the following:
1. There is no need to help me, but others. I don't have any problem integrating nForce SataRaid drivers into a bootable Windows XP CD (see Post Nr. 1 within this thread). What I am trying, is to search for an easy method for those people, who had no success with the full integration of these drivers by nLite.
2. Your message, that the integration of nVRaid drivers is fully supported by nLite Beta6, is definitely wrong. Fully supported means, that it can be successfully used by all users with nVRaid systems and no special preparations of the files/drivers/packages are necessary. Even you have done some "handmade" changes or preparations of the driver folders and special nLite settings (although you do not know exactly which ones).
3. If there really would be a need for the raidtool folder within the SATARAID folder, no user with an nForce SataRaid system could install XP via F6/floppy method (not enough space on the floppy).
4. The main problems for users with nVRaid systems are resolved, when they want to install Windows XP. The new version of nLite (Beta6) makes it very easy to integrate the awfull NVIDIA drivers into the 32-bit OS. But there is still a lot to do for users, who want to integrate the native 64-bit drivers into an 64-bit OS. Please help us to find an easy solution for Windows XP x64!

CU
Fernando

Are you doing this on x64 then?

I haven't even tried it on x64 yet, because my x64 install is already good the way I like it.

I have tried it before without nvatabus.inf or raidtool folder or anything else and it did work. So I think nLite is doing it fine, I don't see why it would be any different for you. But it appears to work fine for me whether I add a few of those files, none at all, or a whole bunch like I said before. I got those few device manager errors one time but it has still worked.

I must be doing some right or getting lucky or something.

Yes, but nLite Beta6 does not work with XP x64.
Look here:
http://www.msfn.org/board/index.php?showto...ndpost&p=383241


That is the newest version of what you have done. If this one is correct, why did you write, that it is necessary to copy the nvatabus.inf and the raidtool into the SATARAID subfolder?????

Yust be happy with your XP with integrated nVRaid drivers. As you may have seen within this thread, other users with an nForce SataRaid system are not so lucky as you.....

I was trying to suggest things to make it work for others.

And yes I am very happy that it works for me

If others are unlucky that is their problem

im having problems integrating my sata drivers on my XP pro 32bits windows
Ive read the instructions by fernando but the nvraid drivers I need are for Nforce3 so I dont have any pataraid folder so how do I integrate Nforce3 sata drivers for XP Pro 32bits?

Sorry if it has been asked before

Thanks in advance

Do you have a Raid array?
If yes, you can do it as I explained it in post 1 of this thread. There is even something said about users with an nForce3 chipset mainboard.
You can take the SATARAID drivers from the nForce chipset driver package v. 6.66. nForce3 Sata controllers are supported by that drivers.
CU
Fernando

sorry I dont understand ...
No I dont have a raid array I just have one sata drive but everytime I try to integrate the sata drivers from Nvidia the harddisk is not detected (I dont have a floppy drive )
Please explain me how to integrate the drivers for Nforce3

Thanks for your help

Have you tried it with the PATARAID subfolder (from the nForce chipset package 6.66)?
Although you have no Raid, there is a SATA driver (nvatabus.sys) within that folder, which is suitable for nForce3 chipsets.

Please post here the result of your work. This way you can help other users with an nForce3 SATA system.

Yeeehaw !!!

Thanks a lot Fernando 1, works everithig fine with Asus K8N (Nforce3), I just folow your first post. Great job !!!

Hi Willdoicu,
thank you very much for your posting.
Your comment verifies, that the method described in my first post works even with mainboards, which have an nForce3 chipset.
For other users with an Nforce3 SataRaid or PataRaid system would it be very helpfull, if you would answer the following questions:

1. Do you have an nVRaid array with S-ATA drives or P-ATA drives?
2. Which nForce chipset driver version did you use?
3. Which subfolder (SATARAID or PATARAID) did you use, when you integrated the textmode drivers?
4. Did you change something within the TEXTSETUP.OEM file? If yes, what?

CU
Fernando

[/quote]



my answers :
1. I have a nVRaid array with S-ATA drives
2. I've used nForce Win2K/XP driver package 6.66 for SATARAID,PATARAID and Sataide. I was integrated also nForce drivers from package 5.10 for Ethernet, Gart, MemCtl, SMBus.
3. I've use subfolders "sata_ide" and "sataraid" to integrate and "pataraid" in \$OEM$\$$\OEMDIR.
4.yes I-ve changed "inf = d1, nvraid.inf" with "inf = d1, nvatabus.inf" on "[Files.scsi.BUSDRV]" section from SATARAID subfolder.
That is all. Thank you again !!!

I am really stuck with this guys and need some help. I have tried Fernando_1's way twice and dale5605's way once. All three attempts have ended in repeated bluescreens.

I have,
ASUS A8N-SLI Deluxe (BIOS 1011 / nVraid v4.81)
A64 3500+ Venice
2x Western Digital 74gb Raptors

I have tried using the 6.66 package of nForce4 drivers, included the pataraid directory contents in the OemDir, integrated the sataraid and sata_ide drivers with nLite (1.0 b6), etc. I can't figure out what I could be doing wrong.

I can't believe how hard it is to get a stripe working with my raptors, I have never had so much trouble with a raid array before.

You can't install the nForce Raid drivers from the chipset package 6.66 with an nVRaid Bios v. 4.81. What you need is a Raid Bios version 4.84!

If Asus has no newer Bios version, you have to take drivers from an nForce package lower than 6.66.

Ahh ha, I wasn't sure exactly what you meant in your first paragraph (on the first post), now it makes sense. Cool, I will update the BIOS now, I was just avoiding it because my BIOS is so heavily tweaked I hate to clear the CMOS It's worth it though if it means being able to get this fricken raid working!

Please post the result of your work within this thread.
Good luck!
Fernando

Umm Fernando, I am on 3/10 bios with 4.81 nvraid and 6.66 drivers.

Odd?

What BIOS are you running that got you 4.84 nvraid?

I have a DFI Lanparty UT NF4 Ultra-D with the Bios from 06/23/05. This Bios includes the Raid Bios version 4.84.

Updating the BIOS did the trick. I have 4.84 NV RAID now, and it worked on the first try using your method on the first post.

Thanks!

Could someone please clarify what errors they're actually getting when they try to slipstream SATA NVRAID array drivers into an WinXP SP2 (32-bit) cd. Without making any text-mode modifications, simply using nlite to integrate the drivers, windows appears to have installed fine, and I can run apps, games etc. all day long. However, upon leaving it, sometimes immediately after booting, sometimes 3 hours after...it randomly reboots. Is this the constant rebooting that people are having problems with, or is it straight after booting XP that most people find their PCs flaking out?
Cheers

I don't know, if somebody could successfully integrate the nVRaid drivers into Windows XP by using nLite Beta6 without any "handmade" changes. All my tests failed at the end of the installation procedure by endless reboots of my computer, even when I rebooted in safe mode.
So the answer is: The issue appears straight during the installation of the OS, there is no chance to use it.
The reason for this issue is, that the Windows XP setup routine installs the wrong driver (Standard PCI IDE Controller) during the GUIMODE part of the installation.
The [OemInfFiles]-method, which is able to prevent this strange behaviour, has not been completely implemented into nLite Beta6.

Hi there Fernando~

First of all, let me say THANK YOU SO MUCH for your contributions to helping all of us figure this out. I believe it is very irresponsible of nVIDIA to release such an obviously *broken* NVRAID driver, but thanks to you and other users there is a chance that many of us will actually get to use the wonderful RAID features on our nForce3/4 motherboards.

Unfortunately, I must report the [OemInfFiles]-method does not work for me yet.

I have tried re-doing the entire process 6 or 7 times (I've lost count now!): I re-transferred 2 different XP SP2 source CDs, re-did the nLite process multiple times, re-typed the [OemInfFiles]-method into the WINNT.SIF file many, many times just as you said to do, etc...

Unfortunately, I keep getting multiple errors during the install process. The main problems occur during the initial file install phase right after the drive formats (before it gets to the WinXP GUI). The primary problems are "missing .dll" errors in which I am instructed to hit [enter] if I want to keep going or [esc] to abort the install. Of course, I always hit [enter]. In some cases the install will get "stuck" on a particular missing .dll and I am forced to abort the install. In other cases, the file install will successfully finish at 100% but then at the very end the machine will BSOD with mention of some problem with a particular file.

I just tried Dale's method (no OemInfFiles) and was able to get the system to boot into windows. At first I thought the install was totally successful, but unlike Dale's personal experience my install did *not* successfully find or install the NVRAID files once WinXP loaded up. In other words, device manager shows the typical question marks for missing drivers and when I try to force the system to look for system changes it just brings up the same dialogue box that tells me the system had a problem finding the correct drivers for the nFORCE4 RAID device, blah blah.

In short, the [OemInfFiles]-method does not work for me (yet). If you (or anyone else here) can give me some insight as to what might be causing the repeated "missing .dll" and BSOD errors during install I'd greatly appreciate it.

Dale's method of simply integrating the files will at least let me get into windows, but for now it appears I'll have to manually install all drivers once I get there. This isn't too bad of a solution if it truly activates NVRAID (am still not there yet).

I'll keep tweaking and working to see if I can get things to work. Any further help with the [OemInfFiles]-method will be greatly appreciated!

Of course, it'd be nice if nVIDIA would pull their heads out of their collective butts and give us a RAID driver that actually works so we don't have to waste our time doing this kinda crap...I'm not real happy that I've had to waste TWO DAYS messing with RAID which is advertised to work as an "out-of-box" feature...

Before I can help you, I need some informations:

Are you really sure, that Windows Setup missed DLL-files? Or is it possible, that the system asked for CAT-files?
Did the setup always ask for the same or for different files?
What is your system (nForce3 or nForce4 chipset, PataRaid or Sataraid)?
Which nForce chipset driver package version did you use?

1. Yes, the system asks for various "missing" .dll files, *not* cab files.
2. Setup seems to ask for different, random .dll files each time.
3. A couple of times install totally stopped due to a "missing .dll" file and hitting [enter] did nothing. Those 2 times I had to hit [esc] to abort install. However, most of the time hitting [enter] resumes install. This is very strange since most of the time it seems as if the system is saying, "I can't find this file...OH, NEVER MIND, now that you hit the [enter] key I just found it!"
4. My motherboard: BFG "BFGRNF4U" nForce4 Ultra
5. BIOS: 0719 = nVRAID 4.84
6. nFORCE drivers = 6.66

**********************
Since I last posted I have re-tried Dale's method 2 more times, adding more drivers each time. Initially, I thought this method to be successful since I could boot into WindowsXP right after finishing install. However, after re-booting the system reverts to continual re-boots.
**********************

Further Information Regarding Dale's Method:

My last effort successfully loaded the nForce sound drivers & ATI Catalyst 5.8 drivers in the *first* boot up sequence.

However, when WinXP starts the "Found New Hardware Wizard" pops up. The message reads:

"Cannot Install this hardware. There was a problem installing this hardware: NVIDIA nFORCE RAID Class Controller. An error during the installation of the device. The installation source for this product is not available. Verify that the source exists and that you can access it. Click Finish to close the wizard."

There is no option to do anything but click "Finish".

Since Windows seems to have successfully loaded the nForce/Ethernet drivers, Device Manager shows all of the question marks are now gone.

Device Manager/Disk Drives *correctly* shows I have "NVIDIA STRIPE 372.61G"

However, SCSI and RAID Controllers shows "Unknown Device", which correlates to the aforementioned "Found New Hardware Wizard". If I scan for new devices, the same wizard pops up time after time. None of the NVIDIA RAID drivers available seem to work.

In short, this method does not work for me since it does the continual re-boot process.

I am nearly sure, that your problem has nothing to do with nLite or the method how to integrate the "ugly" nForce SataRaid drivers.

My suggestions:
Change your cd player and create a new unattended install CD.
If this doesn't change anything, there is something wrong either with your RAM (check them) or power supply (strong enough?), with the temperatures within your pc case (maybe the 2 hard disk drives are too close together) or you are an overclocker, which has reached the limits (take Bios defaults settings).

Tweakin, pay attention you have ASUS A8N-SLI Deluxe no DFI !!!

That is right, but he succeeded even with an ASUS board. Haven't you seen this reply by Tweakin?

I think you are probably correct to some extent. It crossed my mind it could be a problem with my CD-RW media (Sony 4X) or possibly the DVD burner I'm using on the other system (Pioneer), or maybe even the DVD-RW players on my new system (NEC). There are LOTS of possible problems! And since it seems "random" I thought the same thing you do.

However, the only thing that doesn't make sense to me is why would the CD-RW burns of WinXP using Dale's method work just fine and get all the way through the install process without showing the same "missing .dll" errors? I used the same equipment, even the same media (I just wrote over the top of the same 3 CD-RWs for all 9 attempts so far...).

If it really is a problem with my equipment you would think that the problem would occur using both the OemInfFile method -AND- Dale's integrated method, correct?

But the errors only occur when using the OemInfFile method.

PS: All of my equipment is running at normal spec, not overclocked.

mjswoosh, I also get those errors when I tried it the one time I did it that way. However after I installed those drivers I did not experience that reboot problem you are speaking of. Usually that problem only occurs after windows installs and you never make it into windows in the first place. I would recommend only adding in the nvatabus.inf and raidtool folder into your sataraid directory and leaving out the other stuff. You won't get the device manager errors that way, I really only suggested that as a *possible* solution to people having lots of problems. But I would just stick with the aforementioned.

Fernando you mentioned that windows is install the wrong ide driver being the cause for the problem.

I know I remove ALL drivers with nlite, this includes all the various ide drivers and the scsi/raid drivers.

Does this have anything to do with it?

I'm just curious as to what is causing these different results to be achieved.


Again, I can get my raid array working fine with nlite 1.0 b6 with no "handmade" changes.

Some things that may or may not be significant.

-Using nvidia 6.66 drivers
-Using nvraid 4.81 drivers loaded on my mobo
-Remove ALL drivers with nLite and integrate all my own
-Do not check "oem preinstall" box
-Use DefaultHide unattended method
-Integrate RVM1.3.1 + WMP10 + Addons


Oh and I didn't realize the 6/23 BIOS has the newer nvraid version because I didn't see it mentioned anywhere in the changes. I am considering flashing to that BIOS but everything is working the way it is now and I don't really feel like messing it up.