Scripted Win2k SP4 install with SmartStart 6.40a

[Dan Morgan]

I am trying to do a scripted install of Windows 2000 Server (with SP4) with SmartStart 6.40a on a DL380 G3 with a Smart Array 5i controller but it always fails with a INACCESSIBLE_BOOT_DEVICE BSOD. I've modified the TXTSETUP.OEM (attached below) and put it in the following places:

\CPQW2K\$OEM$
\CPQW2K\$OEM$\$1\DRIVERS\SCSI
\CPQW2K\$OEM$\$1\$WIN_NT$.~LS
\CPQW2K\$OEM$\TEXTMODE

Does anyone have any ideas?

Thanks

Dan

[Jeff Mathews]

Well, my txtsetup.oem is quite a bit different so I wouldn't know where to start. Here is my copy. It works on the entire ML/DL/BL product line without any problems. Just make sure you have the following files in you textmode folder:

adpu160m.cat
adpu160m.inf
adpu160m.sys
cpqarry2.cat
cpqarry2.inf
cpqarry2.sys
cpqcissm.can
cpqcissm.dll
cpqcissm.inf
cpqcissm.sys
csb6win.cat
lsicsb6
lsicsb6.inf
lsicsb6.sys
mega2k.cat
megaide.inf
megaide.sys
nodev.inf
symmpi2k.cat
symmpi.inf
symmpi.sys
symmpi.tag

Jeff

[Dan Morgan]

Thanks for the reply Jeff, I've got all of those files. One thing I'm not sure about is should the root of the CD consist of:

\I386 - Contents of Win2k server CD I386
\CPQ - SmartStart toolkit files
\CPQW2K - as above

Thats what I got from the Toolkit documentation, but I've seen in some Usenet postings that the $OEM$ folder should be under I386.

any ideas?

thanks again

Dan

[Guillaume Ducroix]

I scripted Windows Server 2003 servers installations and the tree displayed in the toolkit PDFs is correct. I guess it's the same for W2K:
\CPQ
\CPQW2K
\CPQW2K\$OEM$
\CPQW2K\$OEM$\$1
\CPQW2K\$OEM$\$1\$WIN_NT$.~LS
\CPQW2K\$OEM$\$1\DRIVERS
\CPQW2K\$OEM$\$1\DRIVERS\SCSI
\CPQW2K\$OEM$\$1\DRIVERS\NET
\CPQW2K\$OEM$\$1\NTCSP
\CPQW2K\$OEM$\$1\QUICKLCH
\CPQW2K\$OEM$\TEXTMODE
\I386
\SERVERS