Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!xmission!news.bbs-scene.org!macgui.com!mmphosis From: mmphosis Newsgroups: comp.sys.apple2.programmer Subject: Re: S16, OMF and Segments Date: Sat, 5 Apr 2014 17:11:14 +0000 (UTC) Organization: Mac GUI Lines: 15 Message-ID: References: <25ce127b-ac26-4a8f-80ed-7cddbec7435d@googlegroups.com> NNTP-Posting-Host: gunshin.wiredns.net Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: technocratmedia-w1.news.bbs-scene.org 1396717874 30455 74.119.145.48 (5 Apr 2014 17:11:14 GMT) X-Complaints-To: abuse@bbs-scene.org NNTP-Posting-Date: Sat, 5 Apr 2014 17:11:14 +0000 (UTC) User-Agent: Mac GUI Usenet In-Reply-To: <25ce127b-ac26-4a8f-80ed-7cddbec7435d@googlegroups.com> Xref: csiph.com comp.sys.apple2.programmer:1203 Programming the 65816 by David Eyes/Ron Lichty The 65816 has instructions to access 24 bits of memory at a time: the entire 16 Mb (16777216 bytes) of memory are available. JMP to a 24 bit address, load a 24 bit address, store to a 24 bit address. There is a "bank" register that adds that extra 8 bits to the 16 bit address space. I remember from the x86 world and the 680x0 world back then it was the tools and some of the earlier processors that set these seemingly arbitrary low limits on the address space. 32k text sizes, and 32K branch islands on the Mac, and the horrors of segmented memory on the PC. I would stay away from the idea of "segmented" memory and look at the entire big flat memory space.