[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Apple II error codes
- Subject: Re: Apple II error codes
- From: dempson@actrix.gen.nz (David Empson)
- Date: 1996/07/24
- Newsgroups: comp.sys.apple2
- Organization: Empsoft
- References: <4srkef$1e6@rock101.genie.net>
In article <4srkef$1e6@rock101.genie.net>, l.middleton3@genie.com (Lee A.
Middleton) wrote:
>There is a NDA that lists all of the error codes. It doesn't give the
meanings
>but describes what the number stands for.
>
>I have a question about one of them: When I try to run Omega GS for my Second
>Sight, I get Systen Error $1101 wgich means id not found- Segment/Application/
>Entry not found.
Each GS/OS application file can be divided internally into several
"segments". A common division would be one or mode code segments, and at
least one data segment (though there are small programs that put
everything in a single segment).
One possible reason for this error would be if you had a damaged
application that was missing a specified segment, or a buggy program was
requesting a segment number (or name) which doesn't exist in the file, or
the program has been patched in some way which has stopped it from
working.
In addition, GS/OS applications are able to call up other "load files"
(types $B3 to $BE) which contain executable code in one or more segments.
These can be tightly bound into the program when it is created, or the
program can manually load the other file. This is quite common with some
games, which have an initial startup application that display a title
screen, then they load one or more executable files which are the actual
game.
A second possible reason for this error is if the program is asking for an
associated load file which does not exist, has been renamed, has been
moved to another directory, etc., or if the application is asking for a
segment in another load file which doesn't exist (e.g. if the file has
been replaced with a different version), or the disk has been renamed and
the full pathname was specified by the program, etc.
Any of these causes is more likely than a damaged file.
The third possible error refers to an "entry". This might be a reference
to a "jump table entry", which is somewhat too technical to describe, and
it isn't likely to be the problem (unless a file has been damaged).
--
David Empson
dempson@actrix.gen.nz
Snail Mail: P.O. Box 27-103, Wellington, NEW ZEALAND