/...TO BOLDLY GO, WHERE NO E-MAIL HAS GONE BEFORE.../
Hi Peeps!
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? ).
Snoopdos reports this happening usually with V's "Image Decoder" or
"file... something-or-other". If so, then that's poor programming,
yes?
Anyway, after a bit of thinking I've come up with a few questions:
1. Does anyone know which processor Voyager is coded for? Is it a
generic 020 or what? If so, then when are we gonna see versions for
the 040 & 060? ( That is also if there will be any further development
on NC3 - debatable at the mo... )
2. Could the problem be with any part of my hardware? Or even
software; maybe some part of DOpus or a datatype or something?
3. Has anybody else encountered a similar problem?
/ As always - views, abuse and donations welcome/ ;-)
_Jayce_
--
Jayce's Machine Setup:
Amiga A1200 in Power Tower, Z4 Busboard, 1.3Gig Hard Drive,
32x CD-ROM, Magnum '060/50 with 32Meg FastRAM, Picasso IV GFX board,
Pace 56k Modem, IOBlix Zorro II multi I/O interface,
Buddha/Catweasel MkII Zorro, Belinea 10 30 10 Multiscan monitor
DOpus Magellan II as WBR, P96
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
