And ranking may load a old driver:

nforce 9.35 RAID txtsetup.oem

nforce 15.46 RAID txtsetup.oem

Old and new driver match the same HardwareID.

Given a old motherboard with PCI\VEN_10DE&DEV_03F6:
CriticalDeviceDatase connect PCI\VEN_10DE&DEV_03F6 or PCI\VEN_10DE&DEV_03F6\* to nvatabus.

The same RAID transfered to a new motherboard with the same PCI\VEN_10DE&DEV_03F6:
After above simple fix both drivers are connected at CriticalDeviceDatase.
PCI\VEN_10DE&DEV_03F6* to nvatabus
PCI\VEN_10DE&CC_0104 to nvgts

PCI\VEN_10DE&DEV_03F6* has a higher priority.
Start=0 does load all 4 nvidia storage drivers.

Booting result is unkown.

Current approach should match most cases at real life.
A clean solution requires more work. I like testing results.
A working solution should be possible at all cases.
I'm looking forward to more user requests.

Edited:
Typo 104 106

I'm rather curious still: what did we accomplish really?

Well, now we know how to fix the nvidia problem with a registry hive modification.
This can be as simple as a batch file called by DriverPacks BASE during textmode integration (or directly coded) in a newer version of DriverPacks BASE.
But you're right.  Can the newer files work on older hardware?  That would be a good test.
@urbanriot, now that the hive has the correct fix, can you try the test packs again but in reverse order?  Highest number packs first (low#=old drivers, high#=new drivers) and post your results?  It would be very time consuming on your part but would provide VERY valuable feedback to us.

System is now working, life is good, woohoooo!!

Thanks for report.
Always a pleasure to solve a riddle. Especial if half conditions are unknown.

I'm rather curious still: what did we accomplish really?

Rember the two Nvidia driver pairs:
old: nvatabus.sys and nvraid.sys
new: nvgts.sys and nvrd32.sys

There is used new driver pair at new hardware currently.

Unclear:
Does new driver pair support a RAID from old driver pair?

Question:
Does exist files nvatabus.sys and nvraid.sys at old RAID hard disks?

Small mistake - not nvata.sys, but nvatabus.sys. nvata.sys is ATA driver.

Thanks Debugger for debugging.

@urbanriot
Boot Windows 7 disc.
Which Nvidia RAID drivers are at hard disk at directory %SystemRoot%\system32\drivers ?

Not tested, no hardware:
Backup existing files.
Copy current driver files nvgts.sys and nvrd32.sys to %SystemRoot%\system32\drivers\

Run fix_nvgts_RAID.cmd at %SystemRoot%\system32\config\

@echo off
rem insert Nvidia nvgts RAID settings to offline registry
rem created by cdob
rem run at directory %SystemRoot%\system32\config\

copy system system.%random%.sav
reg.exe unload HKLM\loaded_SYSTEM >nul 2>&1
reg.exe load HKLM\loaded_SYSTEM SYSTEM 

rem detect CurrentControlSet
for /f "tokens=3" %%a in ('reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Current"') do set /a ControlSet=%%a
set ControlSet=00000%ControlSet%
set ControlSet=ControlSet%ControlSet:~-3%
echo. &echo ControlSet "%ControlSet%" used.

set ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
set CriticalDeviceDatabase=HKLM\loaded_SYSTEM\%ControlSet%\Control\CriticalDeviceDatabase
set Services=HKLM\loaded_SYSTEM\%ControlSet%\Services

echo on
@rem NVIDIA AHCI
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0106" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0106" /f /v "Service" /d "nvgts"
@rem NVIDIA RAID
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0104" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0104" /f /v "Service" /d "nvgts"

reg.exe add "%Services%\nvgts" /f /v "DisplayName" /d "NVIDIA nForce Serial ATA Driver"
reg.exe add "%Services%\nvgts" /f /v "Group" /d "SCSI miniport"
reg.exe add "%Services%\nvgts" /f /v "ImagePath" /d "system32\drivers\nvgts.sys"
reg.exe add "%Services%\nvgts" /f /t REG_DWORD /v "ErrorControl" /d 1
reg.exe add "%Services%\nvgts" /f /t REG_DWORD /v "Start" /d 0
reg.exe add "%Services%\nvgts" /f /t REG_DWORD /v "Type" /d 1

reg.exe add "%Services%\nvgts\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1


@rem RAID driver
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk________" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk________" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA_______Raid_Disk" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA_______Raid_Disk" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk_20_____" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk_20_____" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA____Raid_Disk_20" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA____Raid_Disk_20" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\*_NVRAIDBUS" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\*_NVRAIDBUS" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\*NVRAIDBUS" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\*NVRAIDBUS" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\*NVRAID20" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\*NVRAID20" /f /v "Service" /d "nvrd32"

reg.exe add "%Services%\nvrd32" /f /v "DisplayName" /d "NVIDIA nForce RAID Driver"
reg.exe add "%Services%\nvrd32" /f /v "Group" /d "System Bus Extender"
reg.exe add "%Services%\nvrd32" /f /v "ImagePath" /d "system32\drivers\nvrd32.sys"
reg.exe add "%Services%\nvrd32" /f /t REG_DWORD /v "ErrorControl" /d 1
reg.exe add "%Services%\nvrd32" /f /t REG_DWORD /v "Start" /d 0
reg.exe add "%Services%\nvrd32" /f /t REG_DWORD /v "Type" /d 1

reg.exe add "%Services%\nvrd32\Parameters" /f /t REG_DWORD /v "BusType" /d 8

rem pause
reg.exe unload HKLM\loaded_SYSTEM

Nvidia XP drivers used a driver pair nvata.sys and nvraid.sys in the past.
And files nvgts.sys and nvrd32.sys currently.

Small mistake - not nvata.sys, but nvatabus.sys. nvata.sys is ATA driver.

Unsure of the exact model, sorry, I'm not the one who originally did this. It was obviously nvidia, otherwise I wouldn't be able to read the RAID array from a Windows 7 disc.

Windows 7 CriticlaDeviceDatabase PCI#VEN_10DE&DEV_03F6&CC_0104 is connected to nvstor.
Windows 7 CriticlaDeviceDatabase *_NVRAIDBUS is connected to nvstor.

Nvidia XP drivers used a driver pair nvata.sys and nvraid.sys in the past.
And files nvgts.sys and nvrd32.sys currently.

Asus offers nvgts.sys and nvrd32.sys  too.

Which Windows XP driver relates to Windows 7 nvstor.sys?

Sorry, it's at localhost so far only. Never tested so far.
Txtsetup.sif is processed to detect a valid driver. Idea: boot PE first and insert current used driver.
Therefore: fix_hdc won't insert a proper driver without a proper txtsetup.sif

F6 USB floppy:
Did you used a PE without nvgts.sys?
Which USB floppy do you use? Does XP txtsetup.sif contain USB floppy HardwareID?
http://support.microsoft.com/kb/916196
http://www.msfn.org/board/topic/82711-u … sb-floppy/

Are you familiar with offline registry?
There is another hint post #1565: http://www.msfn.org/board/topic/51140-i … _p__823780
Boot windows 7.
You have to load offline XP registry, adjust SYSTEM\CurrentControlSet to offline settings, import the registry settings.
Un load registry hive. And copy nvgts.sys and nvrd32.sys to system32\drivers\.

Unsure of the exact model, sorry, I'm not the one who originally did this. It was obviously nvidia, otherwise I wouldn't be able to read the RAID array from a Windows 7 disc.

I'm not entirely sure if I can answer that?

I would be very interested in trying your update! (But as you said, other problem to solve first).  How do obtain it?  I was going to attempt the one in UBCD.

Well, after all these years of using PE discs, I'd completely forgotten that you could F6! So, excited, I loaded up my floppy with the appropriate drivers and... "The file nvrd32.sys could not be found". I tried both drivers on Asus site and drivers on their disc (different versions), even the 'make floppy' tool they include. Argh!

I'll try to reinterpret your suggestions tomorrow, after I've had more sleep and report back afterwards. I'm working on a week with little sleep, and I'm not entirely sure I understand, but I'm hopeful I'll figure it out.  Thank you!

The RAID array was built on a completely different board with a different onboard 'controller'

Which different onboard 'controller' did you use?
Did you used nvraid.sys or nvgts.sys at different onboard 'controller'?
Does nvgts.sys read a RAID created by nvraid.sys?

Nice a volunteer. I prepared a fix_hdc update years ago, supporting nvgts.
Never tested because of missing hardware.
You have to boot a PE first.

You may use F6 with USB floppy at UBCD4Win.
Create a new UBCD4Win: don't add mass storage drivers. Boot and load F6 drivers.

Either edit setupreg.hiv as suggested. Buit compare file names.

Or add settings as a PEBuilder plugin.
Compare http://forum.driverpacks.net/viewtopic. … 133#p31133
Back then names nvgts, nvgts5 and nvgts6 was added.
You may have to adjust old plugin to current used file name.

Then place it to i386 folder of your slipstreamed disc and start.

the thing is that without this registry key is the hard drive will not be detected regardless of any test pack.

urbanriot, can you try to run setPnpInterfaceNvgts.cmd from that post: http://forum.driverpacks.net/viewtopic. … 325#p30325 in i386 directory after slipstreaming?

I'm kind of mucking about with PE discs more than I'm needing to do any kind of slipstreaming... in fact, I don't need to slipstream at all, I'd F6 with USB floppy drive. I'd just like to get this going on a disc so I can convert the Windows controller driver on the array... I'm close to giving up, as I can simply access with a Windows Vista / 7 PE disc and copy the data that way, but I'd like to get my trusty old XP PE discs working here and make Windows boot... but I need PE accessing it first.

Is there any way to 'integrate' that command into my PE disc?  Or is there another storage controller driver pack I should try outside of the two suggested above?

Isn't that what I said about three posts above?