UNSOLVED
L
lancegaydon
2 Posts
0
6612
July 22nd, 2008 11:00
Windows 2003 sp2 PE 1950 sysprep perc 6/I Integrated
We have been using a 1950 with a different controller to do the initial image and have also tried a 750, both produce the same result.
We are getting a blue screen when trying to boot this up. We are using the R165739.exe drivers, we have updated the firmware for the controller as well but it did not help.
Does anyone see an error in my below sysprep line or have something else we can try? What switches or lines should I run the sysprep.exe with? Right now I am just doubleclicking it and doing a reseal.
The Mass Storage line in our sysprep.inf is the following.
[SysprepMassStorage]
PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028 = "C:\sysprep\Perc6\oemsetup.inf", "DELL PERC 6/i Integrated RAID Controller", "percsas.sys"
salucchi
2 Intern
•
275 Posts
201
0
Posted August 14th, 2008 11:00
Hi,
I grabbed all the controllers for the PERC6 family and dumped them into my sysprep.inf as such
PCI\VEN_1000&DEV_0060&SUBSYS_1F0A1028=c:\dell\...
PCI\VEN_1000&DEV_0060&SUBSYS_1F0B1028=c:\dell\...
PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028=c:\dell\...
PCI\VEN_1000&DEV_0060&SUBSYS_1F0D1028=c:\dell\...
PCI\VEN_1000&DEV_0060&SUBSYS_1F111028=c:\dell\...
Basically after the c:\dell\... point to the path where the driver (oemsetup.inf is located) and all should be fine. One thing I noticed when I built a new image with the perc6 was that I have statements in my sysprep.inf for the perc2, 3, 4 and 5 also. The perc5's driver is very similar to the perc6. I ended up deleting the perc5 statement from my sysprep.inf and just added the perc6 (see above) and my image booted with no issues. Prior to doing this my system blue screened also. I believe it saw the perc5 driver and thought this was the driver for the perc6 and tried to load it but it would fail. Hope this helps.