InstallshieldLimitations page for other limitations.
The first thing to try is installing a more recent JVM.
If, under NT with JDK1.3, you get the following message when you run the installer:
L'linstruction 0x77ff7741b emploi l'adresse m?moire 0x00000034 la memoire ne peeut pas etre "read".Then be sure that Sun's java.exe is in your path before the Microsoft java.exe.
Ultimately, you may find it easier to download the source Ptolemy II distribution, install Cygwin and a JDK and then rebuild by scratch.
If you are interested in trying to debug Installshield, below are some notes
JVM VerificationThe Installshield installer verifies the version of the JVM, runs the installer and then adds Installshield launchers to your Start Menu. The launchers then also verify the JVM and start up Vergil.
You can generate a log file that contains the Java verification steps by running the following command in Cygwin Bash:
e:/ptII1_0_1setup.exe -is:logfile c:/tmp/log.txtBy reviewing the output, you might be able to determine where the Installer is looking for the JVM
Note that the Installshield launchers also verify the JVM.
ExtractionThe Installshield installer and launchers contain several files that can be extracted with the
bash-2.03$ ./ptII1_0_1setup.exe -is:extract bash-2.03$ ls Verify.class ptII1_0_1setup.jar sun_win32_131001.jvm ibm_win32_122.jvm sun_win32_122.jvm sun_win32_131002.jvm ibm_win32_130.jvm sun_win32_13.jvm sun_win32_13101.jvm input.tag sun_win32_13001.jvm sun_win32_13102.jvm instructions.txt sun_win32_13002.jvm sun_win32_131b.jvm launch.txt sun_win32_13003.jvm ptII1_0_1setup.exe sun_win32_131.jvm bash-2.03$You can try running the installer by hand, without running the verification step:
java -jar ptII1_0_1setup.jarNote that the Installshield launchers will still try to verify the JDK version, so they are unlikely to work if the Installshield installer fails.
If the installer hangs part way through, try running in console mode:
java -jar ptII1_0_1setup.jar -console
Another workaround would be to start Vergil by hand, see Troubleshooting Vergil.
Command Line argumentsThe Windows Installshield .exe files can take the following command line arguments:
- Extract the components from the .exe file.
- Unknown, probably for input files.
- After JVM resolution, bring up a window that will display the contents of standard out. Another workaround is to run the installer in a DOS or Bash shell
- Unknown, could be a way to specify which JVM to use. Unfortunately The Installshield verification step is likely to reject non-standard JVMs
- Send log output to
logfileTo generate a log file, run
e:/ptII1_0_1setup.exe -is:logfile c:/tmp/log.txt
- Run in silent mode?
tempdiras a temporary directory.
- Print out the version of the installer?