Sometimes bugs are reported and fixed, and the corrected files are made available directly from the download page in the Patch directory.  If any of the files in that directory are more recent (indicated by a date in the first two lines of the file) than the ones in your installation, you should replace your files with the identically named files from the Patch directory and try CASPER_COMPILE again.  This may solve your problem.

Common start-up problems include not having all the SP kernels converted to binary format on the host machine, not having the other (text) kernels in the appropriate directory, not having the spice_share library properly compiled and linked on the host machine, and not having redefined the environment variables in the casper_setup and casper_personal_setup files.  Another common problem is an incompatibility between your machine and the spice_share.so library supplied with CASPER.  Other versions of the spice_share.so libraries are available from casper@casper.colorado.edu. Because of the size of the software package and particularly because of its interaction between three different language components cross-platform problems may arise.

Any time you install new CASPER source code, you must run the CASPER_COMPILE command before launching CASPER with the normal CASPER command.

If you get an error specifying the spice_share.so file on your Sun workstation, try changing the spice_share.so file to one of the alternate versions included in your casper distribution.  Go to casper/lib/sun-solr/ and
mv spice_share.so spice_share_alt1.so
then
mv spice_share_alt0.so spice_share.so
then try running CASPER again.  If this doesn't work,
mv spice_share.so spice_share_alt0.so
mv spice_share_alt2.so spice_share.so
If it still doesn't work, you may need to rebuild the spice_share.so file.

After double-checking all these against the instructions , if CASPER is still not running on your system, make a detailed report of the steps you follow and the error messages encountered and contact casper@casper.colorado.edu .  Helpful information in tracking down a problem is available by turning on the option for SPICE Error Reporting under the Utilities menu of the main CASPER widget.  If you encounter problems with CASPER, turn this on at the start of your session and send along any error messages which are displayed on your screen along with your bug report.  Additional helpful information can be had by entering

csh> printenv > temp.out

at the shell prompt you run CASPER from.  This will create a file called temp.out with all the CASPER environment variables.  Sending this information along with bug reports can also speed diagnosis of the problem.