Back to Pack 3 and original setupreg.hiv, no hiveBTS.inf:
Textmode does detect striped disk.
Files are copied to hard disk. Reboot to GUI mode.
PNP dosn't detect a PCI\VEN_10DE&DEV_03F6&CC_0104.
Reboot: BSOD 0x7b.

Next \OEM\ files replaced: 11.09
http://www.nvidia.com/object/nforce_nf4 … 11.09.html

Installation does complete.
Used MatchingDeviceId: "pci\\ven_10de&dev_03f6&cc_0104", "*nvraidbus" and "gennvraiddisk".

Read:
Driver pair nvatabus and nvraid use HardwareID *nvraidbus.
Driver pair nvgts and nvrd32 use HardwareID *nvraidbus too.
*nvraidbus goes to both driver pairs: which setting goes to txtsetup.sif?

Continue 2: the fun starts, testing a experimental approach

Textmode files from Pack 3 still: nvatabus and nvraid
\OEM\ files replaced: 15.45 nvgts and nvrd32
http://www.nvidia.com/object/nforce_winxp_15.45.html

Textmode load drivers nvatabus and nvraid.
Gui mode PNP load drivers nvgts and nvrd32.
Installation does complete. Machine does work.
All four services nvatabus, nvraid, nvgts and nvrd32 are set to boot start=0.

DP_MassStorage_wnt5_x86-32_1102nt19.7z no disk found.

Do you like another [BusExtenders.Load] or [BusExtenders.Load] [SCSI.Load] entries?

Next step, same driver files still:
PnpInterface added to setupreg.hiv:
Disk is found at textmode. Files are copied to disk.
BSOD 0x7b at first reboot. Registry dosn't contain nvgts PnpInterface.

Next step:
PnpInterface added to setupreg.hiv. And PnpInterface set at hiveBTS.inf, txtsetup.sif adjusted.
Slightly similar to http://forum.driverpacks.net/viewtopic. … 151#p32151
Installation does finish.

HardwareIDs *NVRAIDBUS, PCI\VEN_10DE&DEV_03F6&CC_0104 and NVIDIA__Raid_Disk________ are used from nforce drivers.

Pack 17=4 instances of Unknown Disk (there is no disk in this drive) then BSOD after F3 to quit
Pack 18=4 instances of Unknown Disk (there is no disk in this drive)

That's very odd.  Packs 17 & 18 match \N7 & \N7r.  They SHOULD have worked...but didn't.

I have a sinking feeling that I'll need to merge \N7 and \N7r together.  They share some of the same files, but I have a nagging suspicion that the merge will break something (txtsetup.oem files are different).
Test version coming up!

I run the tests is also my business machine

Thanks a lot, that's very kind of you. I appreciate this conditions.

Dosn't section [Nt] refers both driver files?

Test MassStorage pack #3 should work.

As an aside, can I slipstream one of the working test MassStorage packs into BartPE (for UBCD4Win) and see what that produces when built?   At the moment in DPs_Base the pack shows as current in the 'check for updates' section but is greyed out on the 'Select DriverPacks to Slipstream' section.

That's fine.  We're only testing the .ini (txtmode) entries at this point.  Your test results will allow me to fine-tune the dpms for your HWIDs.
Unfortunately, we'll need others with different HWIDs to follow your example.

I'll transcribe your posts into the other testing thread for continuity.
THANK YOU!

All BSODs, as far as I remember, from setupdd.sys.

My computer did not explode.

Each test cycle took 10 minutes to complete, including two reboots of the PC.

I hope that this testing is of use to you.

Pack  7=4 instances of Unknown DIsk (There is no disk in this drive)
Pack  8=4 instances of Unknown DIsk (There is no disk in this drive)
Pack  9=4 instances of Unknown DIsk (There is no disk in this drive) then BSOD after F3 to quit
Pack 10=Success
Pack 11=Success
Pack 12=4 instances of Unknown DIsk (There is no disk in this drive)

My ice cream is still solid.

I'm using the first 2 of the 4 SATA connections as a striped raid array.
Device manager has the raid controller as ACPI\NVRAIDBUS\3&267A616A&0
and 2 NVIDIA nForce Serial ATA Controllers PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043&REV_A2\3&&267A616A&0&40

The DVD is on the PATA interface.

The other queries will be harder to sort out as the PC on which I run the tests is also my business machine so I can only go as far as the windows setup screen to see if partitions are visible.   To get further I would have to build a new XP setup on a new partition of the hard drive, I'm not sure what that would do to my existing dual boot with Windows 7, I'd have to check first.

Pack 3= success

This uses nvatabus.sys and nvraid.sys.
Which HardwareIds do you get running nvatabus.sys?
Do you get HardwareID "SCSI\ArrayNVIDIA__Raid_Disk___________"  still ?

Actually test pack #3 only uses nvatabus.sys in the .ini.  The nvraid.sys file is ignored during the txtmode setup.

He's doing well.  He's providing all the answers that I've asked.  We can refine the questions once the test sequence is completed by going back to specific test packs and asking specific questions.