MSFN Forum: [OemInfFiles] - MSFN Forum

Jump to content



  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

[OemInfFiles] Successfully integrated NVRAID drivers Rate Topic: -----

#1 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

  Posted 26 June 2005 - 12:51 PM

i had previously been using the TXTSETUP.SIF method of integrating the NVRAID drivers. this would work fine in the TEXTMODE portion of setup, but once the GUIMODE setup had completed, i would get bluescreens/reboots trying to load windows for the first time. the problem was a result of the NVIDIA NForce Storage Controller not being installed during GUIMODE. since driver is not WHQL certified, setup prioritized the installation of its own Standard Dual Channel PCI IDE Controller.

after a lot of playing around, i have managed to successfully integrate the NVRAID drivers onto an x64 unattended cd. i used the 7.12 PATARAID IDE drivers from the MSI website.

please refer to GreenMachine's Space for instructions on how to make the appropriate changes for the TEXTMODE portion of setup.
these were the additions i made to TXTSETUP.SIF:
[SourceDisksFiles]
nvatax64.sys = 1,,,,,,3_,4,1
nvrdx64.sys = 1,,,,,,3_,4,1

[HardwareIdsDatabase]
"GenNvRaidDisk" = "nvrdx64"
"*_NVRAIDBUS" = "nvrdx64"
"*NVRAIDBUS" = "nvrdx64"
"PCI\VEN_10DE&DEV_008E" = "nvatax64"
"PCI\VEN_10DE&DEV_0085" = "nvatax64"
"PCI\VEN_10DE&DEV_00D5" = "nvatax64"
"PCI\VEN_10DE&DEV_00EE" = "nvatax64"
"PCI\VEN_10DE&DEV_00E3" = "nvatax64"
"PCI\VEN_10DE&DEV_00E5" = "nvatax64"
"PCI\VEN_10DE&DEV_0035" = "nvatax64"
"PCI\VEN_10DE&DEV_0036" = "nvatax64"
"PCI\VEN_10DE&DEV_003E" = "nvatax64"
"PCI\VEN_10DE&DEV_0053" = "nvatax64"
"PCI\VEN_10DE&DEV_0054" = "nvatax64"
"PCI\VEN_10DE&DEV_0055" = "nvatax64"

[SCSI.load]
nvatax64 = nvatax64.sys,4
nvrdx64 = nvrdx64.sys,4

[SCSI]
nvatax64 = "NVIDIA NForce Storage Controller"
nvrdx64 = "NVIDIA RAID CLASS DRIVER"


to successfully install the NVIDIA NForce Storage Controller in GUIMODE:
place the following files in X:\$OEM$\$$\OEMDIR
idecoi.dll    317440  17:30.14 2005-05-12 
nvatax64.inf    4125  17:28.00 2005-05-12 
nvatax64.sys  147968  17:30.14 2005-05-12

add the following lines to WINNT.SIF:
[Data]
	OemDrivers=OemInfFiles

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


please let me know if you are successfully able to use this method. ;)


#2 User is offline   jbm 

  • Senior Member
  • PipPipPipPip
  • Group: Members
  • Posts: 625
  • Joined: 16-September 04
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 26 June 2005 - 04:54 PM

:thumbup It worked, good job :thumbup
Edit: I'm using a K8NE-DLX Nforce3 MB

This post has been edited by jbm: 26 June 2005 - 04:55 PM


#3 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 26 June 2005 - 06:01 PM

good to hear! :yes:

#4 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 29 June 2005 - 02:18 PM

more detailed information about this method can be found HERE.

i would appreciate it if someone could try this method with drivers for devices other than mass storage devices. :}

#5 User is offline   Jito463 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 442
  • Joined: 01-July 04

Posted 30 June 2005 - 07:46 PM

Why would you need to? The only reason for implementing drivers in this fashion is to access drives on controllers that Windows doesn't have native support for without using a floppy. Any other devices can be loaded in other ways during setup, or even after setup.

#6 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 15 July 2005 - 08:07 PM

Jito463, on Jun 30 2005, 09:46 PM, said:

Why would you need to?  The only reason for implementing drivers in this fashion is to access drives on controllers that Windows doesn't have native support for without using a floppy.  Any other devices can be loaded in other ways during setup, or even after setup.
<{POST_SNAPBACK}>

in order to have the latest drivers installed for your devices, even if they are not WHQL.

sure you could install the devices after setup, but i'd prefer during setup. after all, i integrate drivers so that i have an unattended/slipstreamed installation. ;)

what other way was there of installing a device during setup, other than using the OemPnPDriversPath entry in WINNT.SIF? :unsure:

#7 User is offline   obeseotron 

  • Group: Members
  • Posts: 2
  • Joined: 18-June 05

Posted 18 July 2005 - 12:29 AM

I have a SATA RAID0 array on my nforce3, and I can get everything installed, but then get blue screens when I actually try to boot the new windows installation. Do you have any advice on drivers I might try with this method. I tried it with the nforce4 pata drivers you have linked here just for the hell of it, but that didn't work.

#8 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 19 July 2005 - 01:49 PM

@obeseotron:
try the official 6.66 release on the nvidia site. the SATA raid drivers are now WHQL. you should be able to integrate them without the [OemInfFiles] method.

#9 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 19 July 2005 - 03:13 PM

PhreeZ, on Jul 19 2005, 03:49 PM, said:

@obeseotron:
try the official 6.66 release on the nvidia site.  the SATA raid drivers are now WHQL.  you should be able to integrate them without the [OemInfFiles] method.
<{POST_SNAPBACK}>

Can you explain how to integrate the 6.66 drivers? :hello:

I've been searching around and I can't find anyway to integrate the 6.66 drivers for either x86 or x64. I want to know how to do it for both though, since I use x86 and x64 XP. :yes:

#10 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 19 July 2005 - 05:59 PM

@dale5605:
[OemInfFiles] should work with any version of the nforce drivers. i'm currently using it with 7.13.

the first post describes how to get the drivers integrated with x64. the link to GreenMachine's Space is especially useful. what do you need explained exactly?

#11 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 19 July 2005 - 10:09 PM

PhreeZ, on Jul 19 2005, 07:59 PM, said:

@dale5605:
[OemInfFiles] should work with any version of the nforce drivers.  i'm currently using it with 7.13.

the first post describes how to get the drivers integrated with x64.  the link to GreenMachine's Space is especially useful.  what do you need explained exactly?
<{POST_SNAPBACK}>

Well you mentioned something about how they are now WHQL and you don't need this method for the 6.66? I was wondering what is the other method?

#12 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 20 July 2005 - 08:03 AM

@dale5605:
be sure to check the link to GreenMachine's Space in my first post, if anything is unclear. just minor folder changes are needed for x64 (AMD64 instead of i386). let X:\ be the path to your setup files. i'll follow the step numbers on his site:

1) append TXTSETUP.SIF with what i posted earlier.
2) copy the SATARAID folder to X:\$OEM$\$1\DRIVERS
3) append WINNT.SIF with
[Unattended] 
   OemPreinstall=Yes 
   OemPnPDriversPath="Drivers\SATARAID"

4) run the following in a command prompt
MAKECAB X:\$OEM$\$1\DRIVERS\SATARAID\nvatax64.sys X:\AMD64\nvatax64.sy_ 
MAKECAB X:\$OEM$\$1\DRIVERS\SATARAID\nvrdx64.sys X:\AMD64\nvrdx64.sy_


that should do it. i haven't tried the WHQL SATARAID drivers personally. i have a PATARAID that i play with, so i use the corresponding drivers.

let me know if it works. :)

#13 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 20 July 2005 - 08:46 AM

The additions to TXTSETUP that you put in your first post will work for SATARAID as well? Or is that for PATARAID? Thanks :hello:

#14 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 20 July 2005 - 03:46 PM

@dale5605:
it should be good for both. ;)

#15 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 27 July 2005 - 10:17 AM

I tried it on 32bit xp and it didn't work. Haven't tried it on 64bit yet.

#16 User is offline   PhreeZ 

  • Newbie
  • Group: Members
  • Posts: 37
  • Joined: 21-May 05

Posted 27 July 2005 - 02:47 PM

@dale5605:
what symptoms are you experiencing that leads you to believe it didn't work?

you can always use the OemInfFiles entries. i know those work with 7.13. ;)

#17 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 27 July 2005 - 04:21 PM

Right at the beginning, when windows is copying files it says "can't locate nvatabus" or something like that and it fails to install.

#18 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 04 August 2005 - 08:42 AM

I don't get it, this just doesn't work. I tried it again on x64 and followed the directions in your first post EXACTLY. Then when windows is first starting up (press F6 to install RAID drivers, etc.) that part of the install, it says "cannot find nvatax64.sys, press any key to restart your computer"

#19 User is offline   jbm 

  • Senior Member
  • PipPipPipPip
  • Group: Members
  • Posts: 625
  • Joined: 16-September 04
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 04 August 2005 - 09:39 AM

dale5605, on Aug 4 2005, 08:42 AM, said:

I don't get it, this just doesn't work. I tried it again on x64 and followed the directions in your first post EXACTLY. Then when windows is first starting up (press F6 to install RAID drivers, etc.) that part of the install, it says "cannot find nvatax64.sys, press any key to restart your computer"
<{POST_SNAPBACK}>


Did you copy nvatax64.sys to the AMD64 dir?

#20 User is offline   dale5605 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 27-March 05

Posted 04 August 2005 - 02:13 PM

No I did not because I didn't see where it said to do that. Anyways I tried yet again this time I did like the last post where you pub sataraid folder into $1\DRIVERS\ instead of OEMDIR, on x64 this time and it worked. So I guess I did something wrong for x86 before and the first post method doesn't work at all for 6.66 drivers.

Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy