|
|
UNINSTALL INSTRUCTIONS |
To uninstall CPU software from local network servers and clients, see Uninstall (Server) and Uninstall (Client).
To uninstall CPU Simulation Software, click on the Start button
.
On the Start menu, select Programs
.
From the list of program folders, select CPU
Simulators 
(or the name of the equivalent program folder).
|
From the CPU Simulators menu, select Uninstall CPU Simulators. |
 |
When the uninstall program asks, confirm that you want to uninstall CPU Simulators.
If you have saved any simulator setups, printed any simulator pages, or even simply opened Sound Lab, the uninstall program will not delete everything in the folder CPU Simulators.
If the uninstall program informs you that it could not delete everything, click on the Details button to learn what it did not delete.
If you intend to reinstall CPU Simulation Software, move the temporary folders to the Trash along with any other files not uninstalled that you want to delete. Then empty the Trash. You can reinstall into the existing CPU Simulators folder. Also, see the Reinstallment Note below.
If you do not intend to reinstall CPU Simulation Software, move the entire folder CPU Simulators to the Trash. Then empty the Trash.
Reinstallment Note
If you are replacing a Single User Installation with a Multi-User Installation (or vice-versa), save only setup data files (if you used Save HTML, setup data files have the extension .setup0). Load the setup data files into the original simulators using the Standard Menu (Apple-click on the simulator and select Load). Then use Save HTML again.
The reason that you don't want to save the HTML files (the files with the extension .htm) is that the directory structure of CPU Simulation Software differs between the Single-User and Multi-User versions. Consequently, the references to other files in the HTML code differs and web (HTML) pages from one installation will not work with the other installation.
The various Javascript configuration files (those files with the extension .js) are the same in both versions (Exception: configuration.js differs). If you have edited any of these files, save them and replace their duplicates in the new installation.
Copyright © 2000 San Diego State University Foundation