Hi, the DP_MassStorage_wnt5_x86-32_7066.7z driverpack seems to have solved the issue previously experienced,(at least in a virtual machine, will test later on real hardware) great work chaps. 
Moose
1 2007-06-28 22:15:59
Re: Mass Storage txtsetup Error (UBCD4Win) (9 replies, posted in DriverPack Mass Storage)
2 2007-06-27 23:55:09
Re: Mass Storage txtsetup Error (UBCD4Win) (9 replies, posted in DriverPack Mass Storage)
Hi, still getting an error with the same line I'm afraid using DP_MassStorage_wnt5_x86-32_7064.7z.
PCI\VEN_0E11&DEV_0046&SUBSYS_409C0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409B0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409A0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_40910E11="cpqcissm"
GenNvRaidDisk="nvraid"
*NVRAIDBUS="nvraid"
*_NVRAIDBUS="nvraid"
="hpcissm2"
PCI\VEN_9005&DEV_801D="adpu320"
PCI\VEN_9005&DEV_8017&SUBSYS_00449005="adpu320"
PCI\VEN_9005&DEV_8016&SUBSYS_00409005="adpu320"
PCI\VEN_9005&DEV_8015&SUBSYS_00409005="adpu320"
PCI\VEN_9005&DEV_8014&SUBSYS_00449005="adpu320"
PCI\VEN_9005&DEV_8012&SUBSYS_00429005="adpu320"
="hpcissm2" is the affected line
Moose
3 2007-06-27 22:31:01
Topic: Mass Storage txtsetup Error (UBCD4Win) (9 replies, posted in DriverPack Mass Storage)
Hi I am using the latest Base (DPs_BASE_7052.exe) and the latest MassStorage Pack (DP_MassStorage_wnt5_x86-32_7063.7z).
Building using UBCD4Win (3.05) I get an error in line 14493 of the txtsetup.sif file.
PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409D0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409C0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409B0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409A0E11="cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_40910E11="cpqcissm"
GenNvRaidDisk="nvraid"
*NVRAIDBUS="nvraid"
*_NVRAIDBUS="nvraid"
="hpcissm2.sys"
PCI\VEN_9005&DEV_801D="adpu320"
PCI\VEN_9005&DEV_8017&SUBSYS_00449005="adpu320"
PCI\VEN_9005&DEV_8016&SUBSYS_00409005="adpu320"
PCI\VEN_9005&DEV_8015&SUBSYS_00409005="adpu320"
PCI\VEN_9005&DEV_8014&SUBSYS_00449005="adpu320"
The ="hpcissm2.sys" line is the one causing the error.
Hope this helps with debugging.
Moose