[Metalljens]

Yes, youre completely right, guess im gone blind about those filenames hehe...

[Fernando 1]

@ Metalljens:
Please have a look an post 1 with the description of the driver integration.
I added your experience as nForce3 user.
Is it correct and easy to understand, what I have written?
AFAIK it's easier for many users to copy a file than to edit something into a file.

[Metalljens]

Yes, but those txtseup.oem arent exactly the same, the one int pataraid folder has an entry of catalog file which the the sataraid doesnt

This is the pataraid txtsetup.oem

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat <--- this file doesnt exist in the sata_raid txtsetup.oem , nor physically in the sataraid folder either

This is the sataraid txtsetup.oem below

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat <---- see, the sataraid has another catalog file.

But maybe you could just copy that catalog file to the sataraid folder? I dont know.

Well, this is the two sections from my working txtsetup.oem:

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat

To other users, there are more entries in the txtsetup.oem, so DONT just copy this into a new text file and name it txtsetup.oem, you have to open the original or make a copy of the origina txtsetup.oem and paste it in the right place

This post has been edited by Metalljens: 23 July 2005 - 12:20 PM

[RickSteele]

nforce4 6.66 on A8N-SLI Premium integration succeeded with no concerns using 1.0b5

My System:

ASUS A8N-SLI Premium, AMD FX-55 Clawhammer processor, ASUS EAX850XT PE 256mb PCIe, Audigy 2 ZS, Sony LCD SDM- HS95PS, DVI, Corsair TwinX1024LL 3200 Professional, 4*WD 74G Raptors in RAID0 on nforce4 chipset, Lian-Li PC-75 case, 2*LG 4163 DV-RW, Panosonic floppy, Sycom 1000va UPS, Enermax EG701AX-VE SFMA 2.0 (600W) Power Supply, Labtech 580e 5.1 THX speaker system, HP Deskjet 940C

[Fernando 1]

@ Metalljens:

Thank you very much for your important correction. I did not realize the other changes in txtsetup.oem.
According to your suggestion I changed this point in post 1.


@ RickSteele:

Thank you for your information. I don't have any idea, why you succeeded with the driver integration using nLite 1.0 b5 and others not.
Did you really take the original versions of the driver package 6.66 without any changes in one of the txtsetup.oem files?

This post has been edited by Fernando 1: 23 July 2005 - 11:53 PM

[dale5605]

Well I didn't want to have to use beta 4, but this did work for me.

This post has been edited by dale5605: 27 July 2005 - 07:43 PM

[idioteque]

anyone know how to add multiple OEM inf's ?

[OemInfFiles]
OemDriverFlags = 1
OemDriverPathName = "%SystemRoot%\OemDir"

OemInfName = "fasttx2k.INF"
OemInfName = "UlSata.inf"
OemInfName = "viapide.inf"


?

This post has been edited by idioteque: 31 July 2005 - 06:38 PM

[Fernando 1]

idioteque, on Aug 1 2005, 01:38 AM, said:

anyone know how to add multiple OEM inf's ?

Look here:
http://www.msfn.org/board/index.php?showto...ndpost&p=343023
CU
Fernando

[benny12345]

Hi

Tried your Guide but got the following Error:

GUI-Modus Setup wurde begonnen.
Interne Setupdatenstrukturen sind beschädigt (Phase 0).
GUI-Modus Setup wurde aufgrund eines schwerwiegenden Fehlers beendet.

setuplog.txt shows the following:

Time,File,Line,Tag,Message
08/21/2005 20:05:34.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6434,BEGIN_SECTION,Installing Windows NT
08/21/2005 20:05:36.859,d:\xpsprtm\base\ntsetup\syssetup\wizard.c,1568,,SETUP: Calculating registery size
08/21/2005 20:05:36.859,d:\xpsprtm\base\ntsetup\syssetup\wizard.c,1599,,SETUP: Calculated time for Win9x migration = 120 seconds
08/21/2005 20:05:36.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6465,BEGIN_SECTION,Initialization
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6585,BEGIN_SECTION,Common Initialiazation
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1674,BEGIN_SECTION,Initializing action log
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,GUI-Modus Setup wurde begonnen.

08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1679,END_SECTION,Initializing action log
08/21/2005 20:05:36.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1764,BEGIN_SECTION,Creating setup background window
08/21/2005 20:05:37.046,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1775,END_SECTION,Creating setup background window
08/21/2005 20:05:37.046,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1826,BEGIN_SECTION,Initializing SMS support
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1835,,Setup: (non-critical error): Failed load of ismif32.dll.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1837,END_SECTION,Initializing SMS support
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1868,BEGIN_SECTION,Shutting down power management
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1871,END_SECTION,Shutting down power management
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,1950,BEGIN_SECTION,Processing parameters from sif
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find msdosinitiated.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,632,,SETUP: Upgrade=0.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,633,,SETUP: Unattended=0.
08/21/2005 20:05:37.062,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find uniqueness.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find AccMagnifier.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find AccReader.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find AccKeyboard.
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Interne Setupdatenstrukturen sind beschädigt (Phase 0).

08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Schwerwiegender Fehler
08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,:

08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Interne Setupdatenstrukturen sind beschädigt (Phase 0).

08/21/2005 20:05:37.078,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,
***


08/21/2005 20:05:58.640,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,GUI-Modus Setup wurde aufgrund eines schwerwiegenden Fehlers beendet.

So what is the problem ????


MfG Benny

[Fernando 1]

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

Hi
Tried your Guide but got the following Error:
GUI-Modus Setup wurde begonnen.
Interne Setupdatenstrukturen sind beschädigt (Phase 0).
GUI-Modus Setup wurde aufgrund eines schwerwiegenden Fehlers beendet.
So what is the problem ????

It has nothing to do with the integration of the nForce SataRaid drivers.
There is a mistake in WINNT.SIF.
Make a new nLite CD.
CU
Fernando

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