Date   : Tue, 01 Dec 2009 00:50:30 +0000
From   : jgh@... (Jonathan Graham Harston)
Subject: Tube - I/O processor memory questions

Kevin Bracey wrote:
> It looks like someone had the bright idea of squidging memory up further
> to give more language space; leaving 300-7FF free, but that didn't reach
 
No, that was so that all of &3xx could be used by the 65Turbo
system (nb: *not* the 65C12 internal coprocessor) that extended
(zp),Y addressing by using a third byte in page 3 to generate an
18-bit address. See mdfs.net/Docs/Comp/6502Emuls/List
 
> you've clearly got a lot more leeway - effectively that gives you the
> option to use all of 200-3FF. Unless we find that something really
 
As long as you never access a vector by making a MOS call or
allowing an interupt, event or error to occur, and never allow a
host error to occur.
 
-- 
J.G.Harston - jgh@...                - mdfs.net/User/JGH
NOBODY expects the MACRO ARGUMENT INQUISITION!  Our chief weapon is
unexpected addressing modes... unexpected addressing modes and local
branches out of range.  Our two weapons are unexpected addressing modes and
local branches out of range and quoted argument lists.  Our *three* weapons
are unexpected addressing modes, local branches out of range, quoted
argument lists, and an almost fanatical devotion to the pope.  *Amongst* our
weapons are such elements as unexpected addressing modes, local branches out
of range... I'll come in again.