Setup.iss

[Akinlolu Watters]

Theproblem was that my msi project was a Basic MSI Project, as opposed to InstallScript and InstallScript MSI projects. This kind of project does not support reading a response file (aka setup.iss). However, there is a way to perform silent installation for the .msi / setup.exe file:

Using the /f1 option enables you to specify where the response file is (or where it should be created) and what its name is, as in Setup.exe /s /f1"C:\Temp\Setup.iss". Specify an absolute path; using a relative path gives unpredictable results. The /f1 option is available both when creating a response file (with the /r option) and when using a response file (with the /s option)

have yo tried simply just using setup.exe -s as the command line........considering all files are in the one package...then the setup.exe -s command will use the setup.iss by default without having to use any further parameters such as -f1C:\ etc........

Have you tried copying both the .iss file and executable to the root of the c drive through a batch file as part of a task sequence and then run a command line also as part of the same task sequence that will execute the executable in the c drive along with the parameters to run the iss file....this will work...you could also have 3rd part to this task sequence that will remove the files from the local pc once the other 2 parts have finished.

I am trying to automate the deployment of Adobe Illustrator 10 to multiple PCs.

I am running the "setup.exe -r" to generate an InstallShield response file "setup.iss".

When I run the silent install, the Setup.log file reports a "ResultCode=-3" which is "Required data not found in the Setup.iss file" I have also modified [OEM SETUP] section in the ABCPY.INI file to read NO instead of YES to suppress all user prompts. I have also tried filling in the "UserName=" UserCompany=" and "UserSerialNumber" lines.I am using an account with full local admin priviledges to record and test the silent install.Any help would be greatly appreciated.Cheers.

I don't believe that Illustrator will do "silent installs". Others have indicated as such in prior notes. "Normally it shouldn't be so hard because like the other adobe products there is an abcpy.ini file where you can provide the necessary info for the setup. (and then run setup -s)""But for adobe illustrator supplying the license code through this ini file does not work. (license code is correct however) I also tried the AEIT tool to create an abcpy.ini file but this does not work either."Bob

I think that there are 2 custom message dialog boxes which are causing the automated install to halt & abort.The 1st is the message "To avoid restarting your system after installation, please close all Adobe applications before proceeding". And

The 2nd is the message "QuickTime 4.1 or later is not installed on this system. It is recommended... blah blah balh".I modified the ABCPY.INI file to set all [OEM INSTALL] "Display" lines to answer NO except for "DisplayUserInfoDlg=" which I set to YES. I also imported the serial key directly into the registry, so when I ran the setup.exe without the "-s", the serial key was actually read from the registry and entered into the Serial key field and all dialogs were suppressed except the User Info (which I set to not be suppressed) and the two message dialog boxes I stated above. Which leads to the conclusion that these message boxes DO NOT respond to the ISS file.ADOBE PLEASE FIX THIS.That really sux! Now I have to actually get off my ass and walk around to all 20 PCs and install them manually! lol

Unfortunately, the installer will fork a separate process and exit, meaning it will return immediately even if you run it under start /wait . This makes it useless for scripting purposes. Luckily, there is another switch, /sms , which will cause the installer to pause until the installation completes.

The /f1filename switch allows you to specify a fully-qualified alternate name for the setup.iss file. Note that there must be no space between the /f1 switch and the file name. This switch works both with /r to create the file and with /s to read it.

/silent does appear to work, but the computer automatically restarts, which is not an option for us. /r is broken. Kind of frustrating that the installer was switched to installshield, and yet doesent support installshield flags correctly.

Hi all, is there any news on the install switches?

The package seems to be created with InstallShield, but none of the usual switches seems to work?!

A proper documentation would be much appreciated

Sketchup support replied to the ticket I submitted that the /silent switch will work but has to be run from an elevated command line or script and will install the defaults of English and C:\Program Files\SketchUp\SketchUp 2020 as the install directory. They suggested downloading the full installer and that you want to make sure the following prerequisites are installed before running the silent install.

Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.23.27820

KB2999226 - Windows 7 Only

Microsoft .NET Framework 4.5.2

Solution (at least it worked for me) for silently installing on Windows 10 without a restart:

This is what my installer looks like. I have the latest visual c++ redistributable (14.24.28127) in my install directory, and the .net framework 4.5.2. I call them both silently with no restart flags, and only after installing those, call Sketchups installer. This does not cause a restart and installs Sketchup. I havnt been able to test it as it doesent support running on a virtual machine, but I can at least get to the license agreement screen. Looks like that is the only way to do this silently without a restart being needed.

I have been trying to create an add on installer that uses the silent install option for a week without any success. I have been creating all of my add on installers' setup.exe files using InnoSetup. There seems to be no way to do a silent install when using InnoSetup to create the setup.exe file as it appears the zip file required as the parameter file needs to be a compress iss (InstallShield Script) file. Is this really the only option? I have looked at SAP's add on installers for 64 bit add ons and that is what is contained in their zip files.

I then switched to InstallShield and cannot seem to get this to work either. Depending on how I compile the setup.exe file with InstallShield, I either get no install happening so the add on registration process times out or I get the error "Add-on executable file not found". This has been very frustrating. I thought I had made some headway as for the first few days I was unable to make the calls required to notify B1 that the install/uninstaller had completed (EndInstall/EndUninstall in the AddOnInstallAPI_x64.dll). Apparently there is no way to call the 64 bit functions so I was forced to create a wrapper of that DLL and now call an executable that calls them so that is now working. Why on Earth is it so difficult to get a simple install process working with B1? It has been a struggle since version 2004 a decade ago and has never gotten any better unless one wants to use the generic installer which is so out of date it's ridiculous.

If anyone can please point me in the right direction that would be super. I would prefer to continue using InnoSetup if possible but as it appears you cannot do a silent install without an InstallShield Script parameter file I don't think that's an option. Now that I've scripted an InstallShield installer, I would just like to know what I'm doing wrong so I can get my add on registered. Please help!!!

I was able to figure out how to do silent installs with InnoSetup. Compile the InnoSetup script and then run setup.exe /saveinf:"C:\setup.iss" to create your parameter script. This script file needs to be zipped and provided as the parameters file in the AddOnRegDataGen.

Step through the complete TRACE32 installation process, the record will be saved in the setup.iss file.

3. Start a silence TRACE32 installation with the following instruction on a different PC:

To create a silent setup, you must be logged into the computer with a log in account that has administrative privileges.

Users who run the silent setup must be logged into their computers with a log in account that has administrative privileges.

Also, if you own the Origin Concurrent Network package, you must let users know the host name or IP address where your Origin FLEXnet service is running.

After setup.exe -s is run, a file named setup.log is created. If a problem is encountered with the silent installation, send this file along with the setup.iss file to OriginLab, at reg...@originlab.com

-If a Concurrent Network package, the user must enter the FLEXnet server's host name or IP address in the licensing dialog box.

-If a node-locked Group package, the user must activate a license from the OriginLab website, using the License Activation dialog box. (They have seven days to activate the license.)

After setup.exe -s is run, a file named setup.log is created. If a problem is encountered with the silent un-installation, send this file along with the setup.iss file to OriginLab, at reg...@originlab.com

3a8082e126