Jump to content

Integration of NVIDIA's nForce RAID and AHCI drivers


Fernando 1

Recommended Posts


anyone know how to add multiple OEM inf's ?

[OemInfFiles]

OemDriverFlags = 1

OemDriverPathName = "%SystemRoot%\OemDir"

OemInfName = "fasttx2k.INF"

OemInfName = "UlSata.inf"

OemInfName = "viapide.inf"

?

Edited by idioteque
Link to comment
Share on other sites

  • 3 weeks later...

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Edited by benny12345
Link to comment
Share on other sites

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

Edited by Fernando 1
Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 :no:

Link to comment
Share on other sites

  • 2 weeks later...

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

Edited by Fernando 1
Link to comment
Share on other sites

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

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...