|Table of Contents|
Q: I am having trouble installing and running Sci2 on a Windows PC. What should I do?
A: One common problem when initially installing Sci2 is not having a current version of Java. Sci2 runs on Java 1.6 (32 bit) or newer. If you are having trouble installing Sci2, you may want to install the latest 32 bit version of Java. Make sure you install the 32 bit version, as Sci2 will only run with a 32 bit version. You can run 32 bit and 64 bit versions of Java simultaneously. If you have the latest version of Java installed, but is not being detected by Sci2, you must specify the correct path to be used by the tool to locate the correct version of Java. You will want to target the javaw.exe file – which is likely located in the C:\Program Files (x86)\Java\jre7\bin directory, assuming you have installed Java in the default place.
Now, you will have to tell Sci2 to look in this directory. In your Sci2 installation, open sci2.ini (with Notepad or any other plain text editor), delete the contents, and replace them with this:
-vm C:\Program Files (x86)\Java\jre7\bin\javaw.exe -vmargs -Xms15m -Xmx350m
If you're installation of Java is located in another directory on your system, you'll need to replace the path to javaw.exe with the one you find on your system. Save the file in the Sci2 installation and you should be able to start the tool.
Q: I am having trouble running Sci2 on a Windows, I received an error message that starts with, "Java was started by returned exit code=13". What should I do?
A: The error message that you have received is caused by trying to run Sci2 with the incorrect version of Java required by the tool. For example, if you download the 64-bit version of Sci2, but only have a copy of 32-bit Java installed on your computer, Sci2 will try to run but it will produce this error. To solve this problem, you will need to verify the version of Java installed on your computer.
If Sci2 fails to run, and you find that Java is installed in the Program Files (86x) directory, then you have 32-bit Java installed and need to install 64-bit Java. Likewise, if Java is installed in the Program Files directory, hen you have 64-bit Java installed and need to install 32-bit Java.You will need to either try downloading the appropriate 32-bit or 64-bit version of Sci2, or install the appropriate version of Java and make sure that Sci2's instillation file is updated with the correct path to the new version of Java,
Q: I am having trouble installing and running Sci2 on a Mac OS X Mavericks or later. What should I do?
A: Recent updates to Apple's Mac OS X Mavericks have included security that prevent Sci2 from running on a machine if the program is not available from the Mac App store or an identified developer. To get Sci2 to run on your machine, you will have to change the system preferences. Instructions about how to update the Mac OS X's Gatekeeper are available at the Apple website (https://support.apple.com/en-us/HT202491).
Q: I am having trouble installing and running Sci2 on a Mac OS X Sierra. What should I do?
A: Sci2 users trying to install the tool on Mac OS X Sierra will first want to install the legacy edition of Java 6 for OS X 2015-001 (https://support.apple.com/kb/dl1572?locale=en_US).
After installation of the appropriate version of Java, You will need to update the Sci2.ini file
-startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library plugins/org.eclipse.equinox.launcher.carbon.macosx_1.1.100.v20110502 -vmargs -Xms256m -Xmx1024m
After making the modification to the Sci2.ini file, to run the tool, you will need to use the unix-executable file to launch Sci2. The Sci2 Unix Executable file is found by selecting Control on the keyboard and then click Sci2 icon, which will show a drop down menu. In the menu select "Show Package Contents". Next, in the new directory, navigate to Contents>MacOS and select the file labeled "Sci2." Selecting this file will launch a terminal window and a separate tool window.
Sci2 Locale Issues
Q: I am having trouble loading data into Sci2 and having trouble converting PostScript files to PDF files.