ProTools LE 6.1.1

[eon sol]

Does anyone here have silent install switches for ProTools LE 6.1.1? Surely there are some amateur musicians/studio engineers on this forum!

I've searched high and low on the Digidesign website and no dice.

Thanks for any help...

eon

[killerbee]

hi,

u could try this to get basic info out of the installer and post it here so we can see which installer this app uses.

cya

Killer Bee

[eon sol]

Unfortunately, I get an error when analysing the installer: "Sorry, unknown installer".

This looks like a run of the mill InstallShield installer, so I'm not sure why it won't recognize it.

I'll see if I can unpack it and find out anything else.

[eon sol]

I wasn't able to unpack the (setup.exe) installer but strangely, I suspect that it is already unpacked. The installer itself is only 55K in size and the installation folder has a couple of CAB files in it. I tried the switches to create an ISS file from the installer, but no joy.

There is also a setup.ini file, but nothing too interesting there unless there are some standard lines that I might be able to add to it.

Full file list:

data1.cab

data2.cab

data1.hdr

ikernel.ex_

layout.bin

setup.exe

setup.ini

setup.inx

Thanks again!

[ZoSTeR]

That's an InstallShield installer. USSF only recognizes packed IS files.

Try

Setup /r /sms /f1"c:\Setup.iss" /f2"c:\ISLog.txt"

[eon sol]

Great, these switches created the setup.iss file and I was able to automatically install the app using it. One small detail:

After the install, automatic installs of QuickTime and WMF 9 Runtime files are triggered. I aborted the installation of both of these while recording the installation, however, when playing back the installation, it still launches the WMF 9 Runtime install (QuickTime install never launches).

I could issue a taskkill command to stop the setup. Any other recommendations?

Thanks a million for the help!

eon

[eon sol]

Okay... here's the problem. A bit more of an issue than I'd thought at first.

The application installer prompts me before launching the QuickTime installer, however it launches the WMF installer automatically.

A taskkill command will not work since the application installer does not quit until the WMF installer is finished or aborted.

It seems the only way around this would be to modify whatever is responsible for launching the WMF installer.

I used ZipScan to unpack the CAB file and I thought about removing the installer for WMF, however, I was not sure how to repackage the CAB file. There doesn't seem to be an option for this in ZipScan and WINRAR doesn't recognize this type of CAB file as a valid archive (neither does Windows).

Help!

eon

[eon sol]

Update:

I downloaded the eval version of InstallShield AdminStudio and repackaged my installation files. Using the "Repackager" module, I captured the installation and created a DevStudio project. I then used the project file to build a new Windows installer package (one MSI file which packages all required files). Since it only captures the actual files copied, registry changes etc. performed during install, the QuickTime and WME Runtime installation was excluded from the new package.

I am now attempting to integrate the newly created install package into my unattended install disc, I will report back with results.

eon

[eon sol]

Success!

I added my repackaged MSI installer to my unattended CD with the following syntax in my GuiRunOnce cmd file:

ECHO.ECHO Installing ProTools LE 6.1.1ECHO Please wait...start /wait %systemdrive%\install\Applications\ProTools\protools.msi /q

For some reason, my repackaged installer did not include a couple of required MS C+ runtime files: msvcr70.dll and msvcp70.dll. I pulled these two from the original installation CAB using ZipScan, dropped them in my hotfixes folder and scripted them like so:

ECHO.ECHO Copying MS C+ Runtime Library FilesCOPY %systemdrive%\Install\hotfixes\msvcp70.dll %systemroot%\system32COPY %systemdrive%\Install\hotfixes\msvcr70.dll %systemroot%\system32

Also, the repackaged installer copies the necessary driver files for the required Digi hardware, but at that phase of the installation Windows isn't too anxious about detecting any new hardware. Therefore, I pulled the device drivers from my installation CD (only two files: dalwdm.inf and dalwdm.sys), dropped them in a driver folder and added it to my OemPnPDriversPath line. Windows detected my Digi001 hardware like a charm.

I also added a line to install the ProTools shared plugins found on the install disc. The installer executes and closes out fully automatic, so no switches were needed.

Other notes: The InstallShield AdminStudio is quite a hefty download (250MB) so this route might not be the best for dialup users.

The final size of my compiled MSI installer was ~60MB so it worked nicely for fitting onto my CDR.

I hope all of this helps anyone else who might be trying to set up an unattended installer for a Digi DAW!

eon