then we could easily substitute PCI\VEN_10DE&DEV_0054&CC_0104 for one of the alternate HWID's reported
with luck there might be one that is unique for each one

I agree we need people to 

devcon.exe hwids *CC_01* *Raid*

and report back!

the txtsetup entry should be simple to add to both platforms
are we sure we need it for normal slipstreaming?...

NVida drivers are the real fun A lot of confusing. It's a driver nightmare.

Even more fun:
I don't own a NVidia chipset, following are assumptions based on user reports.
My assumptions maybe false, they are based on several independend user reports.

Nvidia released different RAID driver pairs:
old: nvatabus.sys and nvraid.sys
new: nvgts.sys and nvrd32.sys
There are nice conflicts.

Nvidia released  old and new driver pack for HardwareID PCI\VEN_10DE&DEV_0054&CC_0104.

Currently there are two error sources:

One is: missing PnpInterface=5 for nvgts.sys at registry
Txtsetup.oem set PnpInterface=5. Hence generic floppy driver use PnpInterface=5.
Most likely this is missing at BartPE and regular windows installation.
Again, this is importand: this goes both to BartPE and regular windows installation.

Setting is required at textmode.
This maybe setupreg.hiv at BartPE and at regular windows installation.
A PEBuilder plugin changes setupreg.hiv.

Another one is RAID configuration:
http://ubcd4win.com/forum/index.php?s=& … mp;p=62208

A major difference: %NVRAID_DESC% HardwareID is different.
old

new

Does BIOS or a driver set HardwareID GenNvRaidDisk or SCSI\*NVIDIA*Raid* ?
Does BIOS version matter?
Does NVidia release working drivers?

Does exist PCI\VEN_10DE&DEV_0054&CC_0104 and SCSI\*NVIDIA*Raid* in real?

I understand:
at HardwareID GenNvRaidDisk use: PCI\VEN_10DE&DEV_0054&CC_0104="nvatabus"
at HardwareID SCSI\*NVIDIA*Raid* use: PCI\VEN_10DE&DEV_0054&CC_0104="nvgts5"
This is not possible at a single txtsetup.sif.
DEV_0054 is a example, there are more DEV_* in quesiton.
A decision has to be taken.

@all
Some more HardwareID list would be nice.
Get devcon.exe http://support.microsoft.com/kb/311272
Open a command prompt and run: devcon.exe hwids *CC_01* *Raid*
Post output. Thanks.

Have a wonderful day
and i hope we see you around.

PS I will see if we can slip this or something similar into our mix somehow.

see this post and let me know if it is your fix...

http://ubcd4win.com/forum/index.php?s=7 … entry61862

I did already look at that. The drivers on the identical box are not the nvgt* ones.  However this post entry in the same thread fixed the issue: http://ubcd4win.com/forum/index.php?sho … mp;p=61813

Thanks so much for your help!!!

http://ubcd4win.com/forum/index.php?s=7 … entry61862

this driver exists in DriverPack MassStorage 805

folder D\M\N\5 is a dead ringer for the HWID PCI\VEN_10DE&DEV_0054&CC_0104

[N-5]
ms_count=2
ms_1_deviceName="NVIDIA nForce 520 RAID/AHCI Controller"
ms_1_hwids="PCI\VEN_10DE&DEV_037F&CC_0104,PCI\VEN_10DE&DEV_0054&CC_0104,PCI\VEN_10DE&DEV_0055&CC_0104,PCI\VEN_10DE&DEV_044C&CC_0104,PCI\VEN_10DE&DEV_044D&CC_0106"

if you used DriverPack MassStorage 805 you should be able to see the HDDs

hmm, I wonder what I must have done / not done then. I cannot see the drives at all. I followed everything in the tutorial and the only other plugin I used was ghost. No other drivers were added besides the driver pack.

folder D\M\N\5 is a dead ringer for the HWID PCI\VEN_10DE&DEV_0054&CC_0104

[N-5]
ms_count=2
ms_1_deviceName="NVIDIA nForce 520 RAID/AHCI Controller"
ms_1_hwids="PCI\VEN_10DE&DEV_037F&CC_0104,PCI\VEN_10DE&DEV_0054&CC_0104,PCI\VEN_10DE&DEV_0055&CC_0104,PCI\VEN_10DE&DEV_044C&CC_0104,PCI\VEN_10DE&DEV_044D&CC_0106"

if you used DriverPack MassStorage 805 you should be able to see the HDDs

If only the masses shared your thoughts on that.

I am looking at it now
can you confirm that the DriverPacks mass storage plugin is present and enabled in pebuilder while i poke around?

yes it is currently enabled in pebuilder.

I am looking at it now
can you confirm that the DriverPacks mass storage plugin is present and enabled in pebuilder while i poke around?

could you please provide the HWIDS (if possable)

if you are not able to provide the HWIDS can you at least point us to an OEM driver (so we can download it) that you know works with this machine?

I am so pleased you found and used the Tutorial! looks like you read "read before you post" too... woo hoo!

Welcome to DriverPacks.
We're glad your here, and are looking forward to helping you

have a great day

I try to use resources before I go bugging real people with my problems.

Here is the requested info:

DL location: http://download.nvidia.com/Windows/nFor … l_whql.exe

NVIDIA nForce (tm) RAID Class Controller
nvraid.sys
nvraidco.dll
nvraiins.dll
ACPI\_NVRAIDBUS\3&2411E6FE&0

NVIDIA nForce4 Serial ATA RAID Controller
nvatabus.sys
idecoi.dll
idecoiins.dll
PCI\VEN_10DE&DEV_0054&SUBSYS_71251462&REV_F3
PCI\VEN_10DE&DEV_0054&SUBSYS_71251462
PCI\VEN_10DE&DEV_0054&CC_010485
PCI\VEN_10DE&DEV_0054&CC_0104

if you are not able to provide the HWIDS can you at least point us to an OEM driver (so we can download it) that you know works with this machine?

I am so pleased you found and used the Tutorial! looks like you read "read before you post" too... woo hoo!

Welcome to DriverPacks.
We're glad your here, and are looking forward to helping you

have a great day

PS moved to the BartPE forum - (still very high marks for a first post )

I'm in need of some help using the Mass Storage Driverpack w/ BartPE on an nForce4 Ultra machine using nVidia Raid0. I slipstreamed the driver pack into BartPE per the instructions at http://users.pandora.be/jtdoom/basetute … lpFile.htm I created & burned an ISO from BartPE with the driverpack. After booting the machine up with this cd none of the drives were visible.

Thx,

SocratesGS

---Edited subject--- jeff