Re: New draft version of o65 file format

From: Gabor Lenart (
Date: 2005-04-01 12:05:20

On Fri, Apr 01, 2005 at 01:19:06AM +0200, fachat wrote:
> On Thu, Mar 31, 2005 at 11:45:53PM +0200, Ullrich von Bassewitz wrote:
> > On Thu, Mar 31, 2005 at 09:14:09PM +0200, fachat wrote:
> > > I have uploaded the final draft of v1.3 to the web
> > 
> > Small correction:
> fixed. Please look over the CPU codes again, 
> 65C02 was already there, only named "CMOS 6502", I renamed it too.

Well, a little comment :) If you have reserved bit combinations for other CPUs as well,
please donate an "official" combination for at least Z80, 8086 and 80286? I'm asking this
because this is only a minor modification in the draft (does not change meaning any existing
bytes, bits, only some bits are already resrved for CPU type). Because otherwise I *can*
use reserved combinations however it wouldn't be optimal since some others may start using
the same combo for other CPU, causing incompatibility at target CPU detection by some loaders
of eg Z80 systems. Currently, I'm intrested in the above CPUs so I'm asking these. Please
note that "zero page" is quite meaningless in case of these CPUs, and also the stack can
take a whole 64K in theory, so comments may need to extend that zero page notion is not
implemented in case of these CPUs, and stack size - like with 65816 - can be represented
in 2 bytes (it's not problem though the format already use this). Also I think it should be
also noted that CPU type specification is mainly based on current usage of the o65 format
(this is because some people may ask, why exactly THESE cpu types are defined and why some
other not, etc).

- Gábor

       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.