Jason Hillage is getting confused:
> I've noticed that Voyager has been coming up with a few errors on
> my system lately. When it doesn't crash, it gives me a recoverable
> alert ( usually 0100 000F - somethin' to do with exec I believe? ).
Guru 0100000F is "Memory header not located". Probably due to trashed
RAM.
> Snoopdos reports this happening usually with V's "Image Decoder" or
> "file... something-or-other".
Snoopdos is not the tool to be determining when that sort of error
happens. It is useful for "file not found" errors and suchlike.
Enforcer or Mungwall clones are better.
> 1. Does anyone know which processor Voyager is coded for? Is it a
I dunno if its 020+ or plain 68000, but the cpu-intesive bits have
modular code optimised for each processor, automatically.
> 2. Could the problem be with any part of my hardware? Or even
> software; maybe some part of DOpus or a datatype or something?
Very likely. I've found it objects quite strongly to some patches and
not to others. The FBlit util ought to have "V" disabled and it needs
Executive to be configured for it. Its perfectly stable here with
other patches like Birdie, MCP, VisualPrefs, some of FBlit, as well
as utils like DOpus MagII. Just check you aren't running anything too
offensive and its an up-to date version.
> 3. Has anybody else encountered a similar problem?
Many ppl have problems. :-) Usually some clever and helpful person
on this list manages to provide a solution!
Can you give some more info? You say this happens "lately" - since you
installed what? Which version of V are you running? Are you sure you
installed it all correctly? etc etc....
Cheers,
Ian
===
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
