W2K SYSPREP 1.1 - Adding Support for 3rd Party SCSI Controllers

  • Thread starter Thread starter Eric N. Young
  • Start date Start date
E

Eric N. Young

Sorry to cross-post...

I have been using SYSPREP 1.1 and W2K (SP3) to created a unified OS
image deployed across 30+ standard models of desktop, laptop and
Engineering class workstations for the past couple years, and am
having issues with adding support for a Adaptec SCSI Card 29320LP -
Ultra320 SCSI for an HP xw4100 systems into our existing image. I was
successful in doing something similar with the xw5000 and xw8000 5-6
months ago, but an hitting a road block this time around.

I have identified that the card is of type
PCI\VEN_9005&DEV_8014&SUBSYS_00449005&REV_03\4&3A321F38&0&48F0:
Adaptec SCSI Card 29320LP - Ultra320 SCSI (used devcon.exe to acquire
this value).

I have downloaded the latest driver for this card and placed in a
standard location within our image for SCSI drivers. (c:\oem\scsi\a1).

I have appended the DevicePath registry value of the system with the
appropriate value. (%SystemDrive%\oem\scsi\a1)

I have now updated the [SysprepMassStorage] section of the
c:\sysprep\sysprep.inf with the value(s), acquired from the
ADPU320.inf.

PCI\VEN_9005&DEV_801D="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801E="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801F="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8010="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8011="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8012="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8014="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8011="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801C="c:\oem\scsi\A1\ADPU320.INF"

Next I ran SYSPREP (c:\sysprep.exe -pnp sysprep.inf) against the
target system, and uploaded via GHOST after SYSPREP completed.

Finally, I downloaded this updated image to a new xw4100, and get this
wonderful BSOD = STOP: 0x0000007B (0xEB41384C, 0xC0000034, 0x00000000,
0x00000000) INACCESSIBLE_BOOT_DEVICE.

I have recompiled this several different ways and continue to get the
BSOD, any ideas? I had a similar problem with the xw5000 and xw8000
several months ago, but cannot master it with this new xw4100 and
Adaptec SCSI Card 29320LP - Ultra320 SCSI.

Note: I am also getting a similar error with an XP PRO image and the
same system.

Thanks,
Eric N. Young
 
The Boot.ini before and after the compilation are identical:

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect

I would not have expected this to change as a result of running
SYSPREP as outlined below, and many of our other SCSI-based systems
work fine with this updated image.

Am I missing something here???

Thanks,
Eric N. Young

Rick said:
Eric N. Young said:
Sorry to cross-post...

I have been using SYSPREP 1.1 and W2K (SP3) to created a unified OS
image deployed across 30+ standard models of desktop, laptop and
Engineering class workstations for the past couple years, and am
having issues with adding support for a Adaptec SCSI Card 29320LP -
Ultra320 SCSI for an HP xw4100 systems into our existing image. I was
successful in doing something similar with the xw5000 and xw8000 5-6
months ago, but an hitting a road block this time around.

I have identified that the card is of type
PCI\VEN_9005&DEV_8014&SUBSYS_00449005&REV_03\4&3A321F38&0&48F0:
Adaptec SCSI Card 29320LP - Ultra320 SCSI (used devcon.exe to acquire
this value).

I have downloaded the latest driver for this card and placed in a
standard location within our image for SCSI drivers. (c:\oem\scsi\a1).

I have appended the DevicePath registry value of the system with the
appropriate value. (%SystemDrive%\oem\scsi\a1)

I have now updated the [SysprepMassStorage] section of the
c:\sysprep\sysprep.inf with the value(s), acquired from the
ADPU320.inf.

PCI\VEN_9005&DEV_801D="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801E="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801F="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8010="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8011="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8012="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8014="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8011="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801C="c:\oem\scsi\A1\ADPU320.INF"

Next I ran SYSPREP (c:\sysprep.exe -pnp sysprep.inf) against the
target system, and uploaded via GHOST after SYSPREP completed.

Finally, I downloaded this updated image to a new xw4100, and get this
wonderful BSOD = STOP: 0x0000007B (0xEB41384C, 0xC0000034, 0x00000000,
0x00000000) INACCESSIBLE_BOOT_DEVICE.

I have recompiled this several different ways and continue to get the
BSOD, any ideas? I had a similar problem with the xw5000 and xw8000
several months ago, but cannot master it with this new xw4100 and
Adaptec SCSI Card 29320LP - Ultra320 SCSI.

Note: I am also getting a similar error with an XP PRO image and the
same system.
Click to expand...

Have you checked your boot order? Does boot.ini match
the system hardware?

RickW
Click to expand...
 
What I was wondering is, do the systems that aren't working have
any IDE hard disks installed? And if so, is the boot order in the
system bios set to SCSI first?

RickW

Eric N. Young said:
The Boot.ini before and after the compilation are identical:

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect

I would not have expected this to change as a result of running
SYSPREP as outlined below, and many of our other SCSI-based systems
work fine with this updated image.

Am I missing something here???

Thanks,
Eric N. Young

Rick said:
Eric N. Young said:
Sorry to cross-post...

I have been using SYSPREP 1.1 and W2K (SP3) to created a unified OS
image deployed across 30+ standard models of desktop, laptop and
Engineering class workstations for the past couple years, and am
having issues with adding support for a Adaptec SCSI Card 29320LP -
Ultra320 SCSI for an HP xw4100 systems into our existing image. I was
successful in doing something similar with the xw5000 and xw8000 5-6
months ago, but an hitting a road block this time around.

I have identified that the card is of type
PCI\VEN_9005&DEV_8014&SUBSYS_00449005&REV_03\4&3A321F38&0&48F0:
Adaptec SCSI Card 29320LP - Ultra320 SCSI (used devcon.exe to acquire
this value).

I have downloaded the latest driver for this card and placed in a
standard location within our image for SCSI drivers. (c:\oem\scsi\a1).

I have appended the DevicePath registry value of the system with the
appropriate value. (%SystemDrive%\oem\scsi\a1)

I have now updated the [SysprepMassStorage] section of the
c:\sysprep\sysprep.inf with the value(s), acquired from the
ADPU320.inf.

PCI\VEN_9005&DEV_801D="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801E="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801F="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8010="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8011="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8012="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8014="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_8011="c:\oem\scsi\A1\ADPU320.INF"
PCI\VEN_9005&DEV_801C="c:\oem\scsi\A1\ADPU320.INF"

Next I ran SYSPREP (c:\sysprep.exe -pnp sysprep.inf) against the
target system, and uploaded via GHOST after SYSPREP completed.

Finally, I downloaded this updated image to a new xw4100, and get this
wonderful BSOD = STOP: 0x0000007B (0xEB41384C, 0xC0000034, 0x00000000,
0x00000000) INACCESSIBLE_BOOT_DEVICE.

I have recompiled this several different ways and continue to get the
BSOD, any ideas? I had a similar problem with the xw5000 and xw8000
several months ago, but cannot master it with this new xw4100 and
Adaptec SCSI Card 29320LP - Ultra320 SCSI.

Note: I am also getting a similar error with an XP PRO image and the
same system.
Click to expand...

Have you checked your boot order? Does boot.ini match
the system hardware?

RickW
Click to expand...
Click to expand...
 
Back
Top