general error:any other error occurred. Most probably you haven't
enough memory left to create the new session database.
The heap memory used for lists and program code is exhausted and even
garbage collection cannot reclain sufficient space.
Look for non-terminating recursion or try to increase heap size via the
Memory sizes dialog.
The memory for the items in a user interface list set by
lst-set-list
couldn't be allocated. There's no dynamic heap memory left.
An attempt to resize the memory block for heap, atoms, reals or output
failed. You might not have enough free memory or your memory is too
fragmented. The previous memory size is used. As during changing
the memory size temporarily memory for both old and new block
is needed, you can try to avoid this bottleneck by first changing to
the smallest possible size, leave the dialog, re-enter it, and now change
to the originally desired size.
The vector couldn't be allocated as a DB record in the LispMe DB, all
DB heap has been used.
The string couldn't be allocated as a DB record in the LispMe DB, all
DB heap has been used.
The memory used for floating point values is exhausted and even
garbage collection cannot reclain sufficient space.
Try to increase FP size via the
Memory sizes dialog.
The foreign type is using a type tag which is too large, it should be
less than MAX_FOREIGN_TYPES.
The port is using a type tag which is too large, it should be
less than MAX_PORT_TYPES.
[U] User Interface Errors
The form specified in a
frm-popup or
frm-goto call
does not exist. Perhaps you opened the wrong resource DB with
set-resdb?
The id given does not denote an object in the current form.
Look for a typing mistake or for having attached the wrong handler
to the form.
Your event handler needed more time than allowed to process an
event. Maybe you wrote an endless loop?
The user interface object with this id in the current form is
not of the right kind, e.g. you tried to use a field function like
fld-set-text with a pushbutton.
A frm-goto call is
not allowed until
frm-popup has been
called once at least.
No more than 6 nested calls of
frm-popup are allowed
for memory reasons. (The PalmOS UI guidelines ...)
You should use
frm-goto to switch
between forms at the same level.
[L] Loader Errors
A memo to be loaded must consist of a sequence of
define forms. No other
expressions are allowed.
This message is not from LispMe itself (obviously :-), but from
orphan starter applications which have been left after removing LispMe.
You can delete them, too, or (better) re-install LispMe!
The reload command can't be used for one of these reasons:
- no memo has been loaded yet
- the last environment frame results from an interactive define
- a pop command has already removed the last memo
Just use the ordinary load button in this case.
The mini-application, which starts LispMe with the session database,
could not be created. Probably you don't have enough memory left on your
Pilot, or (less probable) an application with this name already exists.
See here about database naming
issues.
The Aportis DOC file to be loaded contains an invalid version number
(compression method) in its header. Please inform the provider of the
DOC editor used.
Others Errors
The stack of loaded memos or entered
definitions is already
empty, you can't pop anymore.
You pressed the break button to
interrupt a running evaluation. The interrupted process cannot be
resumed.
Only 32 parallel sessions are allowed at any time. Just delete
unneeded sessions.
To run LispMe, you need PalmOS 3.0 at least
(Palm III/V/M100/M500, Handera, Sony Clié,
Handspring, or similar) or an upgraded older Pilot at least.
Support for PalmOS2 has been canceled,
as the memory restriction are to severe with PalmOS2. This message
box can't be tapped away.
This message can have three causes:
- reading a deeply nested list (about 30 levels deep)
- compiling a very complex expression
- garbage-collecting a deeply nested list (about 50 levels)
All these things are done internally by recursive functions consuming
some of the (very limited!) Pilot hardware stack. To avoid overwriting
memory and crashing your machine, a stack check caused this error.
Don't confuse this with recursive functions in LispMe itself, they
don't use the hardware stack but the heap, so a non-terminating
(non-tail) recursion in LispMe causes
this error.
You may sometimes get this error when loading a memo (the compiler
needs some stack) and a garbage collection is invoked (needing further
stack). Tap Cancel in this case and invoke
Menu/View/Memory usage, which forces a garbage collection and
try to load the memo again.
You must select any session by tapping its name before issuing any
button command.
The internal format of the session database selected doesn't match
the format of the session databases used by the installed LispMe version.
You either installed a newer version of LispMe without deleting older
session DBs or you installed a 3rd-party LispMe app in an old format.
In this ask for either an updated session DB or (better) for the source
code. Another possible reason for this error is a prior crash of LispMe
so that the session couldn't be pickled anymore. To avoid possible
havoc in this case, LispMe doesn't allow continuing crashed sessions.
The session name recorded within the LispMe starter application doesn't
exist anymore or the session has a format incompatible with the
LispMe version installed. This can happen when you deleted the session database
with a third party tool, but didn't touch the starter app itself,
or when you transferred only the starter app without the session database.
Another possibility is that you installed a newer LispMe version and
didn't delete any older sessions.
See here how sessions and
starter applications work.
[H] HanDBase errors
You can't use any HanDBase function when HanDBase is not installed.
(What did you expect?) Go to the
HanDBase homepage to obtain it.
The HanDBase API returned the error code indicated. A list of HanDBase
error codes is here.
[N] Net errors
The net library function indicated (used for socket communication)
returned an unexpected error, which is displayed in hex. To find the
meaning of the error code, have a look at the header file
System/NetMgr.h in the Palm SDK at mark ErrorCodes.
The lowest two hex digits of the error code denote the exact reason.
Warnings and user queries
This error (notice User Error in the title bar) is generated by
a call to the error
procedure. The text printed in the message box is the argument to
error.
This message box (notice User message in the title bar)
is generated by
a call to the message
procedure. The text printed in the message box is the argument to
message.
Your current evaulation created a lot of output (either by
display or
write, or by a long
return value). In any case, all output not fitting into the selected
Output Size, will be omitted and the last character visible in the
output field will be a ... to indicate truncation.
Tap OK to re-initialize LispMe memory. All loaded memos and other
data will be cleared and you'll have a virgin heap.
Tap Cancel if you selected
Reset Heap by accident,
Tap OK to delete the session and its database.
Tap Cancel to abort.
Fatal Errors
OK, these errors are not fatal for your Pilot, but for LispMe. LispMe
can't continue to work when one of these errors occurred.
Can't create LispMe DB
When starting LispMe the first time, it tries to create its database
containing heap etc. memory. When this fails, LispMe can't work. You
should delete some applications or databases to have more memory or
use a defragmentation tool if your memory is too fragmented (not with
PalmOS3).
No memoDB?
The MemoPad database was not found. Now this is very strange...