User manual

Eclipse User Manual
Release 4.0.1 Page 53 of 66 Eclipse User Manual
The source and destination Program ranges are not allowed to overlap.
Obviously this will not be a problem when copying between the Internal
and Card programs. However, care must be taken when copying within the same Program areas (Card or
Internal) to insure that the Source and Destination ranges do not overlap.
Empty program locations are skipped during the copy process, but the relative spacing between the pro-
grams in the source range are preserved in the destination range.
Fixing and Initializing Internal Memory
The Eclipse uses solid-state memory circuits to store programs and setup
information internally, using a long-life battery to keep the memory alive
while the Eclipse is turned off. Whenever the computer in the Eclipse
updates that memory, it performs an operation called a “checksum” and stores the result.
A checksum is a calculation whose result verifies what is stored in memory. A second run of the check-
sum calculation should result in the same value, if the memory hasn’t changed. When the Eclipse is turned
on, it runs a checksum calculation on the memory and compares the result against the stored result. If
there is a discrepancy, the Eclipse reports an error.
In the unlikely event that an “internal memory checksum error” occurs, there may be a critical problem
with what is stored in memory. Pressing SETUP page 3 UTILITY <FIX> <YES> will remove the checksum
error by forcing the new checksum result to be saved. This will not get rid of the corruption in the data,
however.
Now, you can assume that the “checksum error” was no big deal, get a cup of coffee, and go back to work
(not advised) OR you can assume something nasty is going on and take immediate action (advised). As-
suming you take the latter (smart) course of action, the first thing you’ll want to do is to save all of your
important programs to a card (see page 32) or to an external storage device (see page 51).
Internal memory “checksum errors” should occur infrequently, if ever. Should they occur more fre-
quently than “infrequently,” contact Eventide, as something is definitely amiss.
Fixing Strange Behavior, Freezes, Etc.
In the rare and unlikely event that your Eclipse starts behaving erratically or freezes, the first thing to do is
power down, let it sit for a few seconds in the corner to “think about what it did,” then power back up.
This will fix most problems.
If it won’t start back up properly, the program that was running when it
started behaving strangely is probably to blame. Power down, then
power back up while holding down the PROGRAM key. After a few seconds, the Eclipse will ask if you
want to discard the current program and load MUTE. Select
<YES>, but be warned: any changes you made
to the “current Program” or the <MOD BLOCK> will be lost.
If this does not resolve the problem, power down and then power back
up while holding down the SETUP key. After a few seconds, the Eclipse
will ask if you want to “return to factory defaults.” Select <YES> - this will fix almost all problems, but
will require you to re-enter any
SETUP values that you have changed. It will NOT erase any programs that
you have saved.