HAM Radio 1/HamRadio.cdr/tech/droege2/errors.doc

Text File | 1986-10-14 | 8.9 KB | 301 lines

                                 Page C-1

ERRORS.DOC

This is a listing of all the error messages generated by DROEGE.  In case of
emergency, we have built in a restart procedure which will get you out of most
loops.  If the keyboard shift keys still respond, then pressing KP9 with Caps
Lock and Num Lock on will break out of most DROEGE problems and put you back
into the main menu.  One problem this does not seem to cure is overfilling a
disk.  While we close the file, the system does not at present recover.  Until
we fix this be cautious on a save.  Be sure you have enough space left on the
disk.

"CAUTION - OPERATION DANGEROUS"

You are replacing one symbol by another.  This is a global edit and if you
replace A by B then realize that you did not want to replace all A by B and
attempt to get back by replacing B by A you can get into big trouble quickly.

"DISK PROBLEM"

As below except the error occurred while attempting to write a file.  The most
common problem is not enough space left on the disk.  We are not always
successful in closing the files to give you another chance so be sure you have
enough disk space before saving the job.  Best to keep several fresh disks on
hand and grandfather, father, son them.

"DISK PROBLEM DURING LOAD"

The system encountered some disk problem while attempting to load a PCD file.
Make sure you gave a file name that exists on the default disk.  Make sure the
disk is ready, etc..  You also get the ERROR NO m AT LINE n message to give you
a clue.

"DISK PROBLEM LOADING SYMBOLS"

See DISK PROBLEM DURING LOAD.  Problems were encountered while loading a .LIB
or .PCS file.

"ERROR NUMBER m AT LINE n"

Basic has detected one of the errors in Appendix A of the Basic manual.  See
this appendix to interpret these errors.  Yes, we must confess this is written
in BASIC, with some assembly code.

"FATAL ERROR"

An unexpected error was found.  We scare you to make sure that you are
cautious.  Best not to overwrite the last job save with this, but it might
still be useable.  After this you get the ERROR NUMBER m AT LINE n error
message.

"HASH ENTRY < 0 ERROR"

This should never happen.  We hope we have fixed all the reasons for this.  You
might be able to recover with the KP9 procedure.

"HASH TABLE IS FULL -FATAL"

You have used up all the available space.  A save and reload might give you a
                                 Page C-2
few spaces.  If you have made all the entire job a symbol, saving it as a
library will clear away all the unused stuff and might gain some space,
particularly if you have symbols you don't use.  Time to send money for the
bigger version.

"INVALID SETUP.PCD FILE"

This error dumps you back into the system.  We make checks to insure that the
licensee identification has not been modified.  It is possible that your
SETUP.PCD file has an error that was not detected by the system.  If so, your
backup copy should work.  More likely you have tried to change the name and
address or other items which we do not want you to change.  True hackers should
be able to break our code scheme.  You could probably more easily hold us up at
gun point.  Either way, you are doing something amoral, if not illegal by
attempting to use the program in a way we have not authorized.   While we are
not copy protected, we want to be able to identify where you got your copy.

"JOB DATA NOT FOUND"

When loading the initial files, the job symbol was not found.  This indicates
that the file SETUP.PCS is faulty.  Obtain a backup set of SETUP.PCD and
SETUP.PCS and try loading again.  If this error occurs when loading a job, it
means that the file "JOBNAME".PCS is faulty.  Try to use a backup.  It is
difficult for either of these errors to occur unless you have been editing the
job disk files, or there is an undetected disk error.

"JOB SYMBOL NOT FOUND"

Same as JOB DATA NOT FOUND.

"LOADED SYMBOL REFERENCES AN UNAVAILABLE SYMBOL - SYMBOL PARTS WILL BE LOST"

Something is wrong with the symbol library being loaded.  Try saving each
symbol separately as a library if you are about to loose a lot of work.  You
may be able to identify the sick symbol this way.  The problem is that the
symbols do not call each other properly.  You can almost surely save all the
lowest level symbols,  and probably all but one of the higher level ones.  It
is probably worth trying if you don't have a good backup.

"MUST NAME SYMBOL  HIT KEY F01 TO NAME"

The origin key was hit before the symbol was named.

"NOTHING ENTERED"

You attempted to enter a nul label.  Try again.

"OVERFLOW-DATA BASE MAY BE FAULTY"

An overflow or division by zero has been detected.  Usually this does not hurt
the data base, but the item just entered is probably nonsense.  Delete it if
you can and reinsert the item with better parameters.  Can be caused by
defining an arc with three points in a straight line.

"PLEASE CONSIDER JOB BACKUP"

The program has completed a full survey of the data base and has just updated
the %L indication.  You will have less than the indicated %L if you have been
doing any work.
                                 Page C-3

"PLEASE NAME A SYMBOL"

Symbol locate was attempted when no symbol was named.

"STRING SPACE FULL-DELETE STRINGS"

Basic has run out of string space.  Not very likely if you have a full memory
complement, but possible on a small machine.  There is probably not much you
can do, but deleting things that use string space, like symbols and labels
might help.

"SYMBOL ALREADY CREATED MUST OPEN TO EDIT"

The symbol named as a new symbol was found on the symbol list.

"SYMBOL CLOSED"

Symbol operations have been terminated and you are now back in the job.
Anything entered will go into the job area even though the symbol data still
appears on the screen.

"SYMBOL CONNECTS TO SELF - FATAL"

You have succeeded in locating a symbol in itself.  This is a naughty thing to
do as the system would not know when to stop.  We have put in a number of
checks to prevent this and they all seem to work, still you might succeed.  If
this happens, you are put back in the initial menu and we preserve most work we
hope.  If you attempt to do this indirectly, i.e. A includes B which includes C
which includes A, the results are somewhat unpredictable, but we think we do the
right thing.  We wrote a scheme to prevent this in our spec., but we got tired
of coding.

"SYMBOL DOES NOT EXIST TO KILL"

See SYMBOL NOT FOUND.  An attempt was made to kill a symbol which was not
found.

"SYMBOL LEVEL EXCEEDS 20"

Symbols are calling symbols at level 20 or beyond.  We will make this number
larger for anyone who can think up a reasonable use for nesting this deep.  We
have never gone beyond 6 on a real job.  It is still possible that you have
found a way for a symbol to call itself.  We try to back you out gracefully.

"SYMBOL NOT AVAILABLE"

A symbol was not found when requested for placement in another symbol.  See
SYMBOL NOT FOUND.

"SYMBOL NOT FOUND"

Usually you have just entered a symbol name.  Remember the symbol names know
about upper and lower case so be sure to type a symbol name the way you entered
it.  The program has searched the symbol table and the entered symbol has not
been found.  If confused, list the symbols.  You may have forgotten your
symbol's name or made a typo while entering it.  See LSTSYM in COMMANDS.DOC and
QUICK.DOC.

                                 Page C-4
"SYMBOL REQUIRES REPAIR"

When symbols are closed they are tested for consistency.  The symbol just
closed has a problem which will cause trouble if used.  You may be able to use
it as the last symbol loaded if you are desperate.  Beware of loading it ahead
of many other symbols as there is an increasing possibility that they will be
mixed up.  We believe the error for which this test was inserted has been
repaired,  but it is a very complex part of the symbol process.  Be warned.  If
you get this error it is best to make a symbol library out of it and remake it
from scratch.  We suggest putting it on a job by itself, then opening a
replacement symbol and duplicating its data by overlaying replacement data over
it.  This works well if you don't have to do a redraw.  You may be able to
localize the offending party by opening and closing each sub symbol.  You could
also look for a symbol repairman in the yellow pages.

"SYM TABLE FULL-NEXT SYM DELETES THIS ONE"

You are at the last place on the symbol list.  Write for a version where you
are allowed to name a longer symbol list (The purchased version).  You might
try to kill a few unused symbols.  Or load the program without the labels which
take up a lot of list positions - but you can't do this if they are used.






































                                 Page C-5