[Coco] NitrOS9 and 6309 code

Gene Heskett gheskett at shentel.net
Sat Jun 1 12:41:14 EDT 2019


On Saturday 01 June 2019 08:22:39 am Allen Huffman wrote:

> On May 31, 2019, at 10:52 PM, L. Curtis Boyle <curtisboyle at sasktel.net> 
wrote:
> > It still think “Bad Module” should be reserved for a damaged module
> > (bad length, CRC, Header parity, etc.) vs. for wrong CPU. This would
> > make it easier for beginners to know whether they have accidentally
> > mixed a perfectly good 6309 module on a 6809 system, vs. trying to
> > figure out if a module has gotten corrupted.
> >
> > My thoughts, anyways.
>
> Does 6809 not have a Bad CRC error already? I later OS-9, Bad Module
> is returned when you try to load a perfectly good binary that is from
> the wrong version of OS-9, or a PC executable ;)

That should not be an error unless the change was done with a binary 
editor such as ded, and the change was saved with a w, but a v wasn't 
done which would have fixed all that. So the O.P. got nibbled on. 

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>



More information about the Coco mailing list