[Krenath]

I'm trying to make an unattended installation that includes the driver for my external USB CRDOM Drive.

The driver file can be downloaded from:
ftp://ftp.micro-solutions.com/software/ba...ver/pnp407c.exe


Normal installation displays a fairly standard InstallShield wizard, but it won't generate an ISS file when the pnp407c program is run with -R or -f1 "<whatever>.iss" command line switches. Maybe it's a version of Installshield that's too old for something as high-tech as an ISS file?

It can be extracted by WinRAR, and extracts into three subdirectories since it contains multiple drivers as well as a 'finder' application so it knows what driver to install. Were it a straightforward single driver, I'd probably have used IExpress by now.

Anyone got any suggestions?

[raskren]

I just looked at the contents of the driver package and it looks like the best way to install this would be to use OemPnPDriversPath in winnt.sif. Just dump the contents of the Drivers folder onto the proper directory of your CD.

[OldMan]

I have extracted the files using WinRAR and ran setup.exe -R from the run cmd and this is what it produced:


setup.iss

[InstallShield Silent]
Version=v5.00.000
File=Response File
[File Transfer]
OverwriteReadOnly=NoToAll
[DlgOrder]
Dlg0=12036-0
Count=1
[12036-0]
Result=1
BootOption=0

Have you extracted your files and then ran the setup -R command? Just a thought.
Note: Your .iss file will show up in X:\Winnt or Windows where X is your system drive.

The Old Dude