[benny12345]

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

This post has been edited by benny12345: 21 August 2005 - 02:09 PM

[Fernando 1]

benny12345, on Aug 21 2005, 09:07 PM, said:

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:

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

This post has been edited by Fernando 1: 22 August 2005 - 01:16 AM

[benny12345]

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

[Fernando 1]

benny12345, on Aug 21 2005, 09:55 PM, said:

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

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

[benny12345]

Ok

Where can i find the nLite FAQ ??

[Fernando 1]

benny12345, on Aug 21 2005, 10:17 PM, said:

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-nl...dex.php?act=idx

[RoyceStuart]

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.

[benny12345]

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

[Fernando 1]

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

This post has been edited by Fernando 1: 31 August 2005 - 01:06 PM

[nuhi]

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

[Fernando 1]

nuhi, on Aug 31 2005, 08:07 PM, said:

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.

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

This post has been edited by Fernando 1: 01 September 2005 - 12:58 PM

[cantankerous]

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.

[nuhi]

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.

[cantankerous]

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.

[dale5605]

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"

This post has been edited by dale5605: 01 September 2005 - 09:51 PM

[Fernando 1]

dale5605, on Sep 2 2005, 04:46 AM, said:

Are you on a nforce3 board or something fernando?
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

This post has been edited by Fernando 1: 02 September 2005 - 08:29 AM

[dale5605]

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.

[dale5605]

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.

[Fernando 1]

dale5605, on Sep 2 2005, 08:43 PM, said:

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.

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

[cantankerous]

yea this sure seems handmade to me lol.