Jump to content

PreInstall nVidia drivers


dr_bowtie

Recommended Posts

Lets see if this works.....

 

I thought some of you might like some neat info....those of you that may have bought a 3-pak and got a OPK cd and wonder what you can use it for....

 

Preinstallations Involving Nvidia Nforce Drivers

Nvidia Nforce drivers seem to be a common problem lately in the newsgroups. The main issue with the Nforce driver set is they require a bus driver to be loaded before the network driver will install. For System Builders using WinPE this has proven to be a major source of confusion. The following steps are how to get the Nvidia Bus and network drivers loaded into WinPE.

 

 

1)Insert a XP SP2 OPKTools CD (WinPE) into your Technician machine and copy the WinPE folder to the harddrive. These steps also apply if you are using a Server 2003 SP1 OPKTools CD.

 

2)Copy all the files from the Toolsx86 (or Toolsx64 for x64) folder on the OPKTools CD into the WinPE folder on the harddrive.

 

3)Insert an OS CD (XP SP2 Pro or better (x64 Pro or Server 2003 SP1 is also supported)). Note: Keep the CDs mated - If you use XP SP2 OPKTools then only use a XP SP2 Pro OS CD for the next step. Likewise if you use Server 2003 SP1 OPKTools then only use a Server 2003 SP1 CD. This also goes for the x64 tools...x64 (32bit WinPE/OPKTools) with x64 Pro OS CD only.

 

4)Open a command prompt and use the MKIMG command to make a temporary WinPE image on the harddrive. Make sure you include the /PnP switch with the MKIMG command to turn on Plug and Play.

 

C:WINPE>mkimg D: C:PETEMP /PnP

 

 

5)Download the current nForce driver set from Nvidia’s website and extract the drivers to a folder called c:nvidia. If it brings up an install-shield wizard cancel it. The Nvidia folder should remain.

 

6)Located the network bus driver inf file and use the drvinst.exe tool to inject it into your Windows PE image. The Nvidia network bus driver INF file is usually called NVNETBUS.INF and should be located in the Ethernet subfolder.

 

C:WINPE>drvinst /INF:c:NvidiaEthernetNVNETBUS.INF /INJECT:C:PETEMP

 

 

Note: If in the future Nvidia ever decides to change the inf filenames into something less obvious you can determine the purpose of an INF by opening it with notepad and reading the descriptive text in the [strings] section to determine what hardware component the INF is for.

 

7)Next located the network driver inf and use the drvinst.exe tool to inject it into your Windows PE image.

 

C:WINPE>drvinst /INF:c:NvidiaEthernetNVENETFD.INF /INJECT:C:PETEMP

 

 

8)Comment out the following section in C:PETEMPi386infnvenetfd.inf. Just place a semi-colon at the beginning of each line to comment it out.

 

;section used by coinstaller and generates INF checker warning

;[FDCoInfo]

;OriginalInfSourcePath = %1%

 

 

 

9)Comment out the following section in C:PETEMPi386infnvenetfd.inf.

 

;[bDCoInfo]

;OriginalInfSourcePath = %1%

 

 

At his point, if your only issue with the Nvidia drivers is with networking, you can skip ahead to the bottom and use the OSCDIMG tool to generate a new ISO file. Otherwise, if you are also having additional problems with the Nvidia SATA or RAID drivers follow these steps.

 

Make two separate folders under C:PETEMPi386SYSTEM32 to hold the mass storage drivers and copy the driver files into the appropriate folders. This will allow you to boot from a standard or RAID controller with one CD:

 

C:PETEMPi386SYSTEM32NVRAID

disk1

idecoi.dll

nvatabus.inf

NvAtaBus.sys

nvcoi.dll

nvide.nvu

nvraid.inf

nvraid.sys

nvraidco.dll

nvuide.exe

txtsetup.oem

 

C:PETEMPi386SYSTEM32NVBUS

disk1

idecoi.dll

nvatabus.inf

NvAtaBus.sys

nvcoi.dll

nvide.nvu

nvraid.inf

nvraid.sys

nvraidco.dll

nvuide.exe

txtsetup.oem

 

 

Edit c:PETEMPi386System32NVBUStxtsetup.oem and change the [defaults] section as follows:

 

[Defaults]

scsi = BUSDRV

 

 

Edit the C:PETEMPi386System32WinPEOEM.SIF so it looks exactly like this:

 

[Version]

signature="$Windows NT$"

 

[massstoragedrivers.append]

nvfix = classpnp.sys

 

[OemDriverParams]

OemDriverRoot=""

OemDriverDirs=NVBUS,NVRAID

 

 

 

The final step is to use the OSCDIMG tool to generate and ISO file. The ISO file can then be burn used the CD recording software of your choice.

 

C:WINPE>oscdimg –BETFSBOOT.COM –n –h c:PETEMP C:NEWPE.ISO

 

 

Rob Atkinson

Support Engineer

Microsoft Corporation

Share this post


Link to post
Share on other sites

Thank you for an interesting post. Perhaps you could also shed some insight into a similar issue.

 

I have been struggling with Windows XP install onto an nf4 mobo and the F6 floppy route for the Nvidia drivers. My troubles (described in this post in detail (http://www.dfi-street.com/forum/showthread.php?t=47592) relate to how only older nvidia drivers worked. The 6.6 and 6.7 nv sata raid drivers resulted in an endless reboot cycle.

 

A reader on this board suggested that slipstreaming was flawless for him and in fact referred me to http://www.msfn.org/board/index.php?showtopic=51140. Why would slipstreaming solve a problem with what appears to be a driver issue?

 

 

Help?

 

 

Also, that discussion seems to refer to a driver and LAN conflict that you seem to be alluding to above. Are you the solution to their problem as well (see the last few posts - pages 53 and onward)

 

Please forgive me if you think this is irrelevant and I will post a new message for this issue.

Share this post


Link to post
Share on other sites

A reader on this board suggested that slipstreaming was flawless for him and in fact referred me to http://www.msfn.org/board/index.php?showtopic=51140. Why would slipstreaming solve a problem with what appears to be a driver issue?

 

Help?

 

Also, that discussion seems to refer to a driver and LAN conflict that you seem to be alluding to above. Are you the solution to their problem as well (see the last few posts - pages 53 and onward).

Here is an answer to your questions:

http://www.msfn.org/board/index.php?s=&sho...ndpost&p=482948

 

CU

Fernando

Share this post


Link to post
Share on other sites

  • 1 year later...

Probably useful information for some, so in behalf of those: thank you dr_bowtie!

 

Hm, personally it makes me happy about being able to run servers on exclusively open drivers (for security reasons a far better option anyway).

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...