Coding to the ][, Coding to the ///?

[lyricalnanoha <lyricalnanoha@usotsuki.hoshinet.org>]

Now that I've gotten some very limited /// stuff running (thanks to 
MESS)...I've been thinking of trying to code to the ///.

Fortunately, getting software to the emulated /// is a snap.  I'd just use 
the same strategy as I use for the ][, using the emulated ][+ from 
ApplePC.  Save to a ProDOS disk, boot on the ///.  The questions become a 
bit more complex here.

1. I assume the 40x24 text mode works similarly to the ][.
   Running on MESS, part of the text screen would periodically get 
"colorized", and I suspect the color memory is stored on text page 2. 
This would mean that I'd want to place my memory floor at 3K, not 2K, when 
running on the ///.

2. Console I/O?
   I might just take the code I used when first porting Symbasic, then 
alter it to use the $24/$25 memory addresses like the Apple ][ firmware 
uses.
   Also - charset loading?

(Random: I wonder if it's possible, at all, to get around the ///'s nerfs 
and load DOS 3.3 and FPBASIC up in native mode. o.o)

3. SOS API vs. PRODOS API?
   This won't really come into play until I'm sufficiently familiar with 
ProDOS's API, though.

4. SOS.INTERP?
   I suppose it's a matter of knowing file type, load address, if it needs 
a header, etc.?

-uso.