Re: Hacking on Integer Basic, and ProDOS

[Paul Schlyter <pausch.NO@SPAM.saaf.se>]

In article <OEG8e.171$%L1.129@newssvr30.news.prodigy.com>, 
nospam@nospam.com says...

>    I like reading hacking Integer BASIC on ProDOS.  I think that it is bad 
>idea to put Integer BASIC below 48K while ProDOS is running with Applesoft 
>BASIC on ROM.  I suggest to leave Applesoft BASIC's zero page alone so you 
>can write Integer BASIC from scratch to be placed on ROM.  The new version 
>of Integer BASIC is never the same as original version of Integer BASIC. 
>New version of Integer BASIC always use "4C" in $E000 instead of "20" in 
>$E000.
>    It can still use Applesoft BASIC's zero page while they are mapped to 
>use for new version of Integer BASIC.  It means that you can put new version 
>of Integer BASIC in $D000 through $F7FF ROM rather than $E000 through $F7FF 
>so the length might be increased.
>    You boot ProDOS which it does not have Applesoft BASIC on ROM.  It will 
>still detect new version of Integer BASIC on ROM that shows "4C" in $E000 
>instead of "20" in $E000 before it will begin to load INTBASIC.SYSTEM.
>    It is what I would like to suggest my idea.  Please give us a feedback.

What would happen if one booted Apple DOS on such a machine with your 
modified Integer Basic in ROM which DOS believed is Applesoft Basic?  
Would Integer Basic programs be stored on disk with the "A" file type?
Probably - and those programs would be impossible to load on a machine
with normal Applesoft and/or Integer Basic in ROM: DOS would think the 
file was an Applesoft program, but to Applesoft the file would contain 
garbage, since Applesoft is unable to interpret a tokenized Integer 
Basic program.

-- 
Paul Schlyter,  Grev Turegatan 40,  SE-114 38 Stockholm,  SWEDEN
e-mail:  pausch at saaf dot se
WWW:     http://stjarnhimlen.se/
         http://home.tiscali.se/pausch/