Jump to content

Recommended Posts

Posted

During the txtmode setup I am trying to install the HP 6I controller, I have created the

I386\$OEM$ folder and <root>\$OEM$

Both with the TXTMODE folder with all the files needed.

and in the unattend.txt I have

;SetupMgrTag

[Data]

AutoPartition=1

MsDosInitiated="0"

UnattendedInstall="Yes"

AutomaticUpdates=1

[unattended]

DriverSigningPolicy=Ignore

ExtendOemPartition=1

FileSystem=ConvertNTFS

KeyboardLayout="US"

UnattendMode=FullUnattended

OemFilesPath=c:;.\;.\I386;..\$oem$;

OemPreinstall=Yes

OemPnPDriversPath="drivers\net;drivers\scsi;drivers\video"

OemSkipEula=Yes

DisableVirtualOemDevices=Yes

OverwriteOemFilesOnUpgrade=No

TargetPath=\WINDOWS

[MassStorageDrivers]

"Smart Array 5300 Controller" = OEM

"Smart Array 5i, 532, 5312 Controllers" = OEM

"Smart Array 6i, 641, 642, 6400, 6400EM Controllers" = OEM

"Adaptec AIC-789X/AHA-3960 Ultra160 PCI SCSI Card" = RETAIL

"Compaq Drive Array" = RETAIL

"Compaq Fibre Channel Host Controller" = RETAIL

"Compaq Smart Array Controller" = RETAIL

"LSI Logic PCI Fibre Channel/LSI Logic PCI-X Ultra320 SCSI Host Adapter" = RETAIL

"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = RETAIL

[OEMBootFiles]

txtsetup.oem

cpqciss.dll

cpqcisse.cat

cpqcisse.inf

cpqcisse.sys

cpqcissm.cat

cpqcissm.dll

cpqcissm.inf

cpqcissm.sys

However, during the file copy portion of the txt setup it fails to copy over any of the files listed in the [OEMBootFiles] it states

Setup was unable to copy the following file xxxxxxxx.xxx

I have tried everything to get the OemFilesPath=to be correct, but I am at my wits end. So I need some help as I can't think straight anymore.

Any assistance would greatly be appreciated.

  • 3 weeks later...

Posted

Does your txtsetup.oem have the same exact string found in unattend.txt?

"Smart Array 6i, 641, 642, 6400, 6400EM Controllers"

Does your cpqcissm.inf have the same exact string found in unattend.txt?

"Smart Array 6i, 641, 642, 6400, 6400EM Controllers"

What I'm trying to say is match unattend.txt and txtsetup.oem to what is found in cpqcissm.inf.

Also, be wary of .DLL's. They can sometimes be a problem with mass storage drivers in unattended installs.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...