First, you should read FAQ #238 to see if it applies in your case. That FAQ was written with JTurbo in mind, however it may very well apply to any InstallAnwhere-based installer running on Windows 2003, so if that's your case you should try that FAQ first (even if you're not using JTurbo).
If it does NOT apply, or it DOES apply but does not cure the problem, then the problem may be due to an operating system feature that's new in Windows 2003 SP1 & Windows XP SP2. That feature is called
Data Execution Prevention (DEP). It serves to prevent viruses and
other malicious code from ever executing.
Programs that Windows deems to be malicious are stopped cold, and not allowed to run at all.
It's possible to configure DEP so that it excludes certain programs, leaving them
alone to do as they wish. To populate the list of applications that DEP will
allow to execute, navigate to:
My Computer / Properties / Advanced / Performance Options
That's where you should add the program(s) you wish DEP to leave alone.
If the program that you add to that list is an installer, then after you successfully
install you may want to consider adding that program's uninstaller to the list also.
That way its uninstaller will be allowed to execute should you or someone else ever need to
uninstall the product.
Here is a more detailed description of how to find the DEP settings plus more information about them:
Open the System Properties dialog:
Once there, go to the Advanced tab. Click the
button labled "Settings" in the category/group labeled "Performance".
This brings up the "Performance Options" dialog. Go to the "Data Execution Prevention" tab
of that dialog. There are two options for DEP:
- For a Win XP sp2 machine, one way to bring up this dialog is to go to My Computer and click "View System Information".
- For a Win 2003 sp1 machine, one way to bring up this dialog is to go to the Control Panel, and choose System.
In our experience, having the 1st option selected alleviates all
DEP-related problems from occuring on the machine.
The Win XP Professional Help dialog had this to say about DEP:
- Turn on DEP for essential Windows programs and services only
- Turn on DEP for all programs and services except those I select
Data Execution Prevention (DEP) helps prevent damage from viruses and other security threats that attack by running (executing) malicious code from memory locations that only Windows and other programs should use. This type of threat causes damage by taking over one or more memory locations in use by a program. Then it spreads and harms other programs, files, and even your e-mail contacts.
Unlike a firewall or antivirus program, DEP does not help prevent harmful programs from being installed on your computer. Instead, it monitors your programs to determine if they use system memory safely. To do this, DEP software works alone or with compatible microprocessors to mark some memory locations as "non-executable". If a program tries to run code?malicious or not?from a protected location, DEP closes the program and notifies you.
DEP can take advantage of software and hardware support. To use DEP, your computer must be running Microsoft Windows XP Service Pack 2 (SP2) or later, or Windows Server 2003 Service Pack 1 or later. DEP software alone helps protect against certain types of malicious code attacks but to take full advantage of the protection that DEP can offer, your processor must support "execution protection". This is a hardware-based technology designed to mark memory locations as non-executable.
By default, DEP is only turned on for essential Windows operating system programs and services. To help protect more programs with DEP, select Turn on DEP for all programs and services except those I select.
If none of this helps you then you may find the following information to apply in your case:
Some possible workarounds or ways to try to solve this problem include:
- Run the installer on another machine and then copy the installed folders to the target machine. Since JTurbo is really just a set of JARs (often only 1 JAR is needed/used by people... JTurbo.jar) and a set of examples and documenation... this is fine to do.
- Try running the installer on the problem machine but either:
- uninstall the JVM there first and maybe reinstall a different JVM version before trying to run the installer
- try running the installer from the command line as described in section 1.3.1 of the JT 2005 Installation Guide (this involves holding down the control key)
Or perhaps do so by typing the name of the installer on the command line (not double-clicking) and passing the "-i console" option or maybe even the
LAX_DEBUG=true option or maybe even the LAX_VM option as Macrovision describes on their webpage