On 2/6/07, Hex Star <hexstar at gmail.com> wrote:
What does a unimplemented trap bomb error message
mean? As in, what happened
to cause it? Thanks! :)
If you got a bomb, shouldn't there be numbers associated with it?
Those can be extremely useful in debugging these sorts of problems
(yes... even AmigaDOS' Guru Meditation numbers, despite their
reputation).
The generic answer is that the MacOS for the 68K used trap vectors as
a way for applications to call system routines, and that for whatever
reason (software incompatibility, corrupt RAM, etc.), the app jumped
to a trap vector in low mem that was never set to point to some useful
routine. I.e. - it most likely still contains either a default vector
to an "unimplemented" catch-all routine in the OS, or it points off
into the weeds and something else caught it (like an odd-address trap
or other 68K-centric trap). I don't know MacOS well enough to narrow
it down further, but it sounds as if (presuming you don't have any
hardware faults and your OS isn't corrupt on disk) the application in
question is expecting some OS routine to be there and it isn't, the
most likely cause is that your app is newer than your OS.
Hope this untangles some of the mystery,
-ethan