HUNTI:R OPERATION
SECTION 2.9
Most types of corruption (corrupted lines, spurious line
numbers) are unrecoverable in Basic and can only be eliminated
by 'NEW',
2,9,4.2
Keyboard Lock-out
If keyboard lock-out (failure to power down) occurs, it is
necessary to power down HUNTER by removing the battery cap.
HUNTER should power-up again normally. If desired, try running
the user program, but be ready to clear any lock-out that occurs
using the above methods.
If lock-out persists, type 'NEW' after
restoring operation.
2.9,4,3
System Lock-out
In very rare cases, HUNTER may fail to restart correctly after a
mis-execution episode. This is possible in a program that uses
auto-start, see section 4.12, AUTO POWER FEATURE, and contains
an invalid system call.
Any program corruption resulting could leave the auto-start flag
set, but cause a lock-out when power-up is attempted.
The solution is to apply the 'ESC' sequence immediately after
power-up, in order to reset the auto-start flag.
2,9,4,4
File corruption
VER.V09F
Because files are not stored in Hunter's workspace (RO) area,
mis-execution episodes are much less likely to cause corruption
of this part of memory. In any case, the checksum facility
will indicate if damage has ocurred. Current experience
suggests that storing
a 'back up' file in a different memory
page virtually guarantees data integrity against the worst
possible disasters.
A checksum error can result in a "no file" message being
displayed in response to an attempt to use the file, even if the
directory entry is present. In this event, the only recourse is
to re-load the file.
PAGE 2 - 25
To Next Page
Loading...