Possible to load RAID drivers with a USB stick?

Soldato
Joined
3 Oct 2007
Posts
12,176
Location
London, UK
Possible to load RAID drivers with a USB stick? Edit: Problem loading RAID drivers

Hey all
I own the BFG 680i SLI. It is just coming back from the 2nd RMA for graphic issues :rolleyes: and this time round i want install my system over RAID. Unfortunately BFG don't ship the RAID drivers on a floppy (wish i knew why) but anyway i think my floppy drive might have bitten the dust.
I know you can update the BIOS with a USB flash drive but can the RAID drivers be loaded in the same way? Somehow i doubt it but always worth asking.
Thx for any help
 
Last edited:
Really? Is the procedure the same? Press F6 then when prompted plug-in USB stick? Do i need to set something in the BIOS for it to see USB like a floppy?

thx for your help m8

The F6 method worked for me when I had my RAID 0 setup a few years ago for XP.
 
Am havin a few problems here loading RAID drivers. I have copied the files i think i need to a floppy (floppy seems to be working now) they are
disk1
idecoi.dll
nvatabus.sys
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
txtsetup.oem

When i pop in the floppy and hit enter a few secs later i get a text error. Reads

file txtsetup.oem caused an unexpected error (512) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c.

Any idea what i might be doing wrong here??
 
Am havin a few problems here loading RAID drivers. I have copied the files i think i need to a floppy (floppy seems to be working now) they are
disk1
idecoi.dll
nvatabus.sys
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
txtsetup.oem

When i pop in the floppy and hit enter a few secs later i get a text error. Reads

file txtsetup.oem caused an unexpected error (512) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c.

Any idea what i might be doing wrong here??


the nvraid files should they be in a folder under a:\ ?


Open up txtsetup.oem, and glance down to see if it references a folder
 
the nvraid files should they be in a folder under a:\ ?


Open up txtsetup.oem, and glance down to see if it references a folder

you know i was wondering that. Should it be the txtsetup.oem and then a folder. Problem is my PC has no OS installed, i'm on my Mac laptop here. Might be a case of having to install XP normally then start again with RAID when this problem is sorted. :(
Cheers for reply

Edit: I opened it with Text Edit on my Mac and is as follows

;

; format for txtsetup.oem.

;

; Follow this format for non-PNP adapters ISA

;

; Follow the txtsetup.oem in initio for PNP adapters like PCI and ISAPNP

;

; Txtsetup.oem is a generic way to install Storage adapters to get them through

; textmode setup. Do as little as possible and allow GUI mode setup to do the

; remaining work using the supplied inf.

;

; General format:

;

; [section]

; key = value1,value2,...

;

;

; The hash ('#') or semicolon (';') introduces a comment.

; Strings with embedded spaces, commas, or hashes should be double-quoted

;





; This section lists all disks in the disk set.

;

; <description> is a descriptive name for a disk, used when

; prompting for the disk

; <tagfile> is a file whose presence allows setup to recognize

; that the disk is inserted.

; <directory> is where the files are located on the disk.

;

[Disks]

d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\



; This section lists the default selection for each 'required'

; hardware component. If a line is not present for a component,

; the default defaults to the first item in the [<component_name>]

; section (see below).

;

; <component_name> is one of computer, display, keyboard, mouse, scsi

; <id> is a unique <within the component> string to be associated

; with an option.

[Defaults]

scsi = RAIDCLASS





; This section lists the options available for a particular component.

;

; <id> is the unique string for the option

; <description> is a text string, presented to the user in a menu

; <key_name> gives the name of the key to be created for the component in

; HKEY_LOCAL_MACHINE\ControlSet001\Services

[scsi]

RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)"

BUSDRV = "NVIDIA nForce Storage Controller (required)"





; This section lists the files that should be copied if the user

; selects a particular component option.

;

; <file_type> is one of driver, port, class, dll, hal, inf, or detect.

; See below.

; <source_disk> identifies where the file is to be copied from, and must

; match en entry in the [Disks] section.

; <filename> is the name of the file. This will be appended to the

; directory specified for the disk in the [Disks] section to form the

; full path of the file on the disk.

; <driverkey> this is the name that will show under the services\driver key

; this should be the same name as the driver that is being installed.

[Files.scsi.RAIDCLASS]

driver = d1,nvraid.sys,RAIDCLASS

inf = d1,nvraid.inf

dll = d1,nvraidco.dll

catalog = d1,nvraid.cat



[Files.scsi.BUSDRV]

driver = d1,nvatabus.sys,BUSDRV

inf = d1, nvraid.inf

dll = d1,idecoi.dll

catalog = d1, nvraid.cat



; This section specifies values to be set in the registry for

; particular component options. Required values in the services\xxx

; key are created automatically -- use this section to specify additional

; keys to be created in services\xxx and values in services\xxx and

; services\xxx\yyy.

;

; This section must be filled out for storage controllers that

; are PNP adapters like PCI and ISA PNP adapters. Failure to do this

; can cause the driver to fail to load. Must also add the section

; [HardwareIds.scsi.ID] to identify the supported ID's.

;

; <value_name> specifies the value to be set within the key

; <value_type> is a string like REG_DWORD. See below.

; <value> specifies the actual value; its format depends on <value_type>

;

[Config.RAIDCLASS]



[Config.BUSDRV]



; A HardwareIds.scsi.Service section specifies the hardware IDs of

; the devices that a particular mass-storage driver supports.

;

; [HardwareIds.scsi.Service]

; id = "deviceID","service"

;

; HardwareIds.scsi.Service

; Service specifies the service to be installed.

;

; <deviceId > Specifies the device ID for a mass-storage device.

; <service > Specifies the service to be installed for the device.

;The following example excerpt shows a HardwareIds.scsi.Service section for a disk device:

;



[HardwareIds.scsi.RAIDCLASS]

id = "GenNvRaidDisk","nvraid"

id = "*_NVRAIDBUS","nvraid"

id = "*NVRAIDBUS","nvraid"



[HardwareIds.scsi.BUSDRV]

id = "PCI\VEN_10DE&DEV_008E", "nvatabus"

id = "PCI\VEN_10DE&DEV_00D5", "nvatabus"

id = "PCI\VEN_10DE&DEV_00EE", "nvatabus"

id = "PCI\VEN_10DE&DEV_00E3", "nvatabus"

id = "PCI\VEN_10DE&DEV_0036", "nvatabus"

id = "PCI\VEN_10DE&DEV_003E", "nvatabus"

id = "PCI\VEN_10DE&DEV_0054", "nvatabus"

id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

id = "PCI\VEN_10DE&DEV_0266", "nvatabus"

id = "PCI\VEN_10DE&DEV_0267", "nvatabus"

id = "PCI\VEN_10DE&DEV_036F", "nvatabus"

id = "PCI\VEN_10DE&DEV_037E", "nvatabus"

id = "PCI\VEN_10DE&DEV_037F", "nvatabus"

id = "PCI\VEN_10DE&DEV_03F6", "nvatabus"

id = "PCI\VEN_10DE&DEV_03F7", "nvatabus"

id = "PCI\VEN_10DE&DEV_03E7", "nvatabus"
 
Last edited:
all the files (except the txtsetup.oem) have to be in a folder called "disk1"

That didn't work. I had to follow these instructions for it to work

You need everything except nvuide.exe and nvuide.nvu from the sata_ide folder,
and everything from the sataraid folder. These folders are in the path:
nvidia\nforceWinXP\<version>\IDE\WinXP. Just copy those files to the floppy,
and proceed as you have been as far as pressing F6 and loading all the drivers
contained on it.


That worked. I have now installed XP over a 3 disk stripping array. Problem now is that i can't get windows to see and mount my other 2 sata drives. The Nvidia Control panel sees them and so does the Safely Remove Hardware panel. Disk Manager and Device Manager just refuse to recognize them. They are NTFS formatted and contain all my backup files.
Any ideas?

Edit: Ok i finally got XP to see them. I had to disable RAID on those 2 channels in the BIOS and presto they are seen. According to BFG this should make no difference but it obviously does.

Thx for all your help guys
:-)
 
Last edited:
Back
Top Bottom