Solution: Try restarting several times by typing "WC" on the WC keyboard. If by the sixth try or so it still won't start, wait ten minutes and try again. While waiting, try logging into the prospero machine from another network machine, to make sure that it is accepting telnet sessions.
Solution: Try typing "startup" several times in succession. If this doesn't work, try typing "WC RESTART", followed by two more "startup"s. If the problem is disk synchronization, follow the directions below.
Solution: Users occasionally note that they are having difficulty getting the data disks between the WC and IC to synchronize on startup. If full reboots are not solving the problem, you can attempt to force synchronization of the disks manually: Check the WC status screen. Near the middle of the screen is a box with disk synchronization information. If any of the machines' names are followed by the word "-SYNCH", follow the directions below.
>WC REQ INITDISK
in the caliban console window.
>IC REQ INITDISK
Note: If the instructions above don't help, then it may be the case that the WC was not able to detect the IC disks on startup. The only fix is to follow the TIFKAM startup procedure.
There is some scant evidence that attempting to change readout parameters during readout may cause these crashes to occur more frequently. You may want to avoid doing commands like EXP, ICSCALE, or moving mechanisms while acquiring images.
There is even scanter evidence that rebooting the IC may be more effective in preventing these crashes then simply restarting the IC as described above.