|
|
|
|
|
|
|
Last updated 24 October 2000 Note: Macintosh users do not need the CPU PC Installer Patch (which doesn't work on Macs anyway!). CPU users working on PCs need the CPU PC Installer Patch to fix a problem introduced by a recent Microsoft security upgrade to their Java Virtual Machine (Java VM). Because of this upgrade, all the files (known as JAR files) that contain the CPU software must be named in the classpath. If a JAR file has its name and location in the Java VM classpath, then any HTML (web) page on the computer can use software. Previously, only cpu.jar (the CPU "engine" used by all simulators) and soundlab.jar had been named in the Java VM classpath. The CPU PC Installer Patch places the names and locations of the remaining JAR files (ripplelab.jar, enm.jar, lnc.jar, fm.jar, ces.jar, and spm.jar) in the classpath. Without this patch, users with the most recent (year 2000) versions of the Microsoft Java VM or Internet Explorer cannot run CPU simulators except under special conditions. We suggest, though, that ALL PC users download the CPU PC Installer Patch. To apply the CPU PC Installer Patch:
CPUClasspathPatch.exe places a file called ClearCPUClasspath.exe in your main software installation folder (normally the folder CPU Simulators). When you need to uninstall CPU Simulation Software (including CPU IntroPak), run ClearCPUClasspath.exe first. You can clear CPU classpaths without first using the patch by downloading ClearCPUClasspath.exe separately. To do so, click on the link below. Server (Local Network)
Installation. You MUST run
CPUClasspathPatch.exe BEFORE running the
program MiniInstallerServer.exe because the classpath
patch modifies a file used by the mini-installer program.
You ONLY need to run
CPUClasspathPatch.exe once on the CPU server. You
DO NOT need to run it when you perform client
installations. |
The CPU Project -
Copyright ©2000