Hello katiebabes...Welcome to bleepingcomputer
Photo Explosion 2.0 requires:
Windows 98, 2000, Me or XP
Pentium 166 Mhz or Faster
32 MB RAM
CD-ROM Drive I've found 4 possible solutions from the manufacturer NOVA Development here:If still have trouble please post back..And some common causes and repairs after these http://www.novadevelopment.com/Support/Faq/pkw.aspx#q6
Why do I get an Error "1607: Unable to install InstallShield Scripting Runtime" when trying to install the program?
This issue occurs on some systems depending on the system configuration. Please try the following instructions in order to help solve this issue:
NOTE: When performing any installation, please make sure that you have Administrative privileges for the computer. If you are unfamiliar with this, you may need to consult the documentation that comes with your computer, or contact your System Administrator
Restart your computer. Sometimes, an installation is running at the same time, or one of the files or services on the computer is in use. Once the computer has restarted, re-insert the first CD and start the installation over again.
Install the InstallShield InstallScript engine. To do this, you will need to click on the following link to download the IsScript.zip file:http://support.installshield.com/kb/files/...94/IsScript.zip
When prompted to Run or Save the file, select the Save option and select a location to save it, such as your desktop. After the file has completed the download, double-click on the file to open it. Extract the IsScript.msi file to a location, such as your desktop. Once that is extracted, double-click on that file to run the IsScript installation. After this installation has been performed, reboot your computer and try to install the software again.
Try to register the Windows Installer service on the computer. To do this, click on the Start button and select the Run option. In the Open field on the Run window, type the command that is appropriate for your version of Windows:
Windows 98 or Me:
After you have done this, reboot the computer and start the installation over again.
Verify that the Installer folder in the Windows directory is not set to Read-only. To do that, go to the Start button and select the Run option. On the Open field in the Run window, type one of the following that is appropriate for your version of Windows:
Windows 98, ME, or XP:
Click on the OK button. Once the Explorer window is open, right-click on the Installer folder on the left side of the screen. Select the Properties option from the pop-up menu. On the Folder Properties window, make sure that the Read-only option is un-selected. Click on the OK button. If prompted, select the apply changes to this folder, subfolders, and files. Click on the OK on that window, as well.
From here, reboot your computer and start the installation over again.
----------------------------------------- Common causes and fixes
This issue occurs on some systems depending on the system configuration and privileges set for the user. Listed below are some common causes of this error message:
The user does not have administrative privileges on the machine. This pertains to Windows NT, 2000, or XP machines.
The ALLUSERS property is not set appropriately for the IsScript.msi file. This is only true for the installation of Express 3.54 itself. Express 3.54 setup is based on InstallScript, leading to this error message.
Permissions are not set appropriately on the Installer folder in the Windows folder.
An older version of InstallShield Express 3.x is installed on the machine, and the older version fails to uninstall properly. This usually happens when upgrading Express from an older version to a newer one.
Multiple instances of files Msiexec.exe or IDriver.exe may be running in memory.
The Windows Installer Service may not be properly installed or configured on the machine.
The installation is trying to remove a file that is locked on the machine. This issue generally occurs when setup is being removed using the 'Remove' option of the Add Remove Programs applet on Windows XP, 2000, or ME.
Listed below are some suggestions that may help eliminate this error message. You may need to try all or some in order to work around the error message.
Make sure that you have administrative privileges to run the setup on the machine. To run InstallShield Express 3.5 SP4 setup, users need full admin privileges on Windows NT, 2000, and XP machines.
Download and run IsScript.msi. This file internally sets the ALLUSERS property, which is known to fix the issue in some cases. After downloading the attached file, replace the IsScript.msi shipped with InstallShield Express 3.5 SP4 setup with this updated version. The file IsScript.msi can be found in the same path as InstallShield Express 3.5 SP4 Setup.exe.
Make sure that the Installer folder in the Windows directory on the machine is not read only. The path to the installer folder is typically C:\Winnt\Installer on Windows NT, 2000, and XP machines and C:\Windows\Installer on Windows 9x and Me machines. Right-click on the Installer folder and select Properties. Make sure that it is not read only. On some machines, the Installer folder may be hidden. Before searching for this folder in the above path, make sure to show hidden files and folders in the Windows Explorer options.
You may want to manually uninstall any previous version of InstallShield Express 3.x from the machine before installing the new version. If the uninstallation fails, use MsiCleanUp utility to uninstall the old product. You can download MsiCleanUp from MSDN at 290301 Description of the Windows Installer CleanUp Utility.
Launch the Task Manager to see if multiple instances of Msiexec.exe or IDriver.exe are running on the machine. You can launch the Task Manager by pressing Ctrl+Alt+Delete. You should have at least one instance of these files running as these engine files drive the setup. However, if you see more than one instance of Msiexec.exe or IDriver.exe, it could be the cause of the issue. If this is the case, reboot the machine and run the installation again.
Run the file InstmsiA.exe on Windows 9x or Me or InstmsiW.exe on Windows NT, 2000, or XP to install and configure the Windows Installer Service on the machine. These files can be found in the same path as Setup.exe for the InstallShield Express 3.5 SP4 setup. If the issue persists, register the file Msiexec.exe manually on the machine. To do this, run the following command-line option in the Start > Run command or command prompt of the operating system:
Windows 9x, Me or XP:
If your installation is trying to uninstall a file that is in use, the Windows Installer Service throws the File In Use Dialog. However, when you attempt to uninstall the installation via the Remove option of the Add/Remove Programs applet (ARP), the Windows Installer setup runs the uninstallation in a basic User Interface mode, which does not display the File In Use Dialog, displaying error 1607. As a workaround, you may want to disable the ARP Remove option in the installation. This forces users to uninstall via the Change option of ARP, which will notify the user when a file is in use. To disable Remove option from ARP, open your project in Express and:
Click on Organize Your Setup > General Information.
Set the Disable Remove Button Attribute to Yes.
In some instances, this issue has known to be fixed by lowering the system resolution. For example, from 1280 x 1024 to a lower resolution of 800 x 600. You can access the display settings to change the resolution by right clicking on the desktop and selecting Properties. Select the Settings tab to change the resolution.
Let us know if and what worked
Edited by boopme, 26 November 2005 - 10:27 PM.