Path: utzoo!attcan!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: COMMODORE 8032 FORTH
Message-ID: <655.UUL1.3#5129@willett.UUCP>
Date: 15 Mar 90 02:49:41 GMT
Organization: Latest link in the ForthNet chain.  (Pgh, PA)
Lines: 27


 Date: 03-13-90 (11:44)              Number: 3023 (Echo)
   To: ALL                           Refer#: NONE
 From: CHARLIE HITSELBERGER            Read: HAS REPLIES
 Subj: BLAZIN' FORTH FOR C-64        Status: PUBLIC MESSAGE

 I have Blazin' Forth for the C-64, and the source code for the screens, 
 as well as the source code for the core kernal.  Ballantyne has put in
 enough drive support to accomodate a single 1541 drive or a 4040 drive.
 If you have 1581, RAM expanders, multiple drives, etc... you are in for
 a rude shock.  You *STILL* only get 166 blocks of virtual storage.  My
 mission, should I choose to accept it, is to make it support any type
 of drive configuration, including Creative Micro Designs Hard drive if
 I should ever get one of those.  My questions:
 1) Has this been done already?  I find it hard to believe that I am the
 only one who ever wanted more virtual blocks on Blazin' Forth.
 2)  What is a good way to set it up?  Obviously, I need a device table
 of sorts.  I was thinking four bytes per element, with one word pointing
 to the CFA of the I/O handler of that device and a starting block number
 and number of blocks.  Oops.  I meant four WORDS, not bytes.  The 4th
 word would be flags, i.e. Is the device mounted, etc...  Any suggestions
 would be *GREATLY* appreciated, as my experience in designing Forth 
 systems is very limited.
                                  Charlie Hitselberger
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'