Apple II fig-FORTH
regi...@retronym.de
LISTING RELEASE 1.1 V 1.0 August 1981 from http://www.forth.org/fig-forth/contents.html
(It's the Apple port of the 6502 fig-FORTH version for the Rockwell
System-65).
I would like to run the run this Apple II version.
Have someone the binary?
If not, the source listening was developed with the public domain "TED
II+" text editor and assembler. Where can I find this software? I've
got the source of the Rockwell System-65 version and would make the
neccessary adjustments.
thank you
Dietmar
Michael J. Mahon
> I downloaded the PDF of the APPLE II fig-FORTH ASSEMBLY SOURCE
> LISTING RELEASE 1.1 V 1.0 August 1981 from http://www.forth.org/fig-forth/contents.html
> (It's the Apple port of the 6502 fig-FORTH version for the Rockwell
> System-65).
>
> I would like to run the run this Apple II version.
>
> Have someone the binary?
If worse comes to worst, it's only (!) seven pages of hex dump to
type in. ;-) (See my web page for a hex dump reader that will
read Apple II memory contents in hex so you can easily verify what
you have typed in. ;-)
> If not, the source listening was developed with the public domain "TED
> II+" text editor and assembler. Where can I find this software? I've
> got the source of the Rockwell System-65 version and would make the
> neccessary adjustments.
The assembly code looks completely standard, with no use of macros
or local labels. As a result, almost any 6502 assembler will assemble
it--possibly with minor adjustments to pseudo-ops.
-michael
NadaPong: Network game demo for Apple II computers!
Home page: http://members.aol.com/MJMahon/
"The wastebasket is our most important design
tool--and it's seriously underused."
schmidtd
(lots of) other FORTHs out there. One recent example is:
http://www.geocities.com/oneelkruns/qforth.html
John B. Matthews
<81e1da84-05e1-4505...@e25g2000prg.googlegroups.com>,
regi...@retronym.de wrote:
> I downloaded the PDF of the APPLE II fig-FORTH ASSEMBLY SOURCE
> LISTING RELEASE 1.1 V 1.0 August 1981 from
> http://www.forth.org/fig-forth/contents.html
> (It's the Apple port of the 6502 fig-FORTH version for the Rockwell
> System-65).
>
> I would like to run the run this Apple II version.
>
> Have someone the binary?
This ProDOS version was derived from fig-forth:
http://home.woh.rr.com/jbmatthews/a2/proforth.html
John
--
John B. Matthews
trashgod at gmail dot com
home dot woh dot rr dot com slash jbmatthews
Charlie Springer
(in article <nospam-2B716D....@news-server.woh.rr.com>):
> In article
> <81e1da84-05e1-4505...@e25g2000prg.googlegroups.com>,
> regi...@retronym.de wrote:
>
>> I downloaded the PDF of the APPLE II fig-FORTH ASSEMBLY SOURCE
>> LISTING RELEASE 1.1 V 1.0 August 1981 from
>> http://www.forth.org/fig-forth/contents.html
>> (It's the Apple port of the 6502 fig-FORTH version for the Rockwell
>> System-65).
>>
>> I would like to run the run this Apple II version.
>>
>> Have someone the binary?
>
> This ProDOS version was derived from fig-forth:
>
> http://home.woh.rr.com/jbmatthews/a2/proforth.html
>
> John
>
Fig for the Apple II is the original Bill Ragsdale implementation (and is
historically interesting) and is a very clean little Forth. The AIM-65/RM-65
Forth is nearly identical except for system specific stuff and IIRC was done
by Dave Bolton and Sandy Bumgarner starting with the Fig listing. The AIM and
Fig versions were written for a 4K memory map and did quite a few things to
save space at the expense of speed. Somewhere I have a little notebook of all
the definitions that can be sped up by making small changes. The Rockwell ran
from ROM and could use an AIM-65 with 1K of RAM.
Note that the AIM manual has a wonderful example of dense Forth source code.
The full block disk I/O for adding a drive is in one 1K block of text. I have
about five AIM-65's and a bag of 20 Meg HP Kittyhawks and will have to add
them some day.
http://www.regnirps.com/Apple6502stuff/r65c02.htm
-- Charlie Springer
John B. Matthews
Charlie Springer <R...@regnirps.com> wrote:
> On Tue, 29 Jan 2008 10:56:26 -0700, John B. Matthews wrote
> (in article <nospam-2B716D....@news-server.woh.rr.com>):
[...]
> > This ProDOS version was derived from fig-forth:
> >
> > http://home.woh.rr.com/jbmatthews/a2/proforth.html
[...]
> Fig for the Apple II is the original Bill Ragsdale implementation (and is
> historically interesting) and is a very clean little Forth. The AIM-65/RM-65
> Forth is nearly identical except for system specific stuff and IIRC was done
> by Dave Bolton and Sandy Bumgarner starting with the Fig listing. The AIM and
> Fig versions were written for a 4K memory map and did quite a few things to
> save space at the expense of speed. Somewhere I have a little notebook of all
> the definitions that can be sped up by making small changes. The Rockwell ran
> from ROM and could use an AIM-65 with 1K of RAM.
>
> Note that the AIM manual has a wonderful example of dense Forth source code.
> The full block disk I/O for adding a drive is in one 1K block of text. I have
> about five AIM-65's and a bag of 20 Meg HP Kittyhawks and will have to add
> them some day.
>
> http://www.regnirps.com/Apple6502stuff/r65c02.htm
Sweet. The source I was given so long ago had no comments and was very
fragile. I found the original source only recently:
<http://home.comcast.net/~wrodiger/FIG6502.ASM>
<http://www.forth.org/fig-forth/fig-forth_6502.pdf>
Back then, I wrote a ProDOS Assembler macro to automate the check for a
dictionary entry having a PFA that crossed a page boundary:
NAME
DFB &1
DCI &2
IFEQ >*+3
LST ON
FAIL 2,'PFA=xxFF'
FIN
This permitted code such as this:
L22 NAME $83,'LIT' ; <--- name field
DW 00 ; last link marked by zero
LIT DW *+2 ; <----- code address field
In contrast to the original:
L22 .BYTE $83,'LI',$D4 ; <--- name field
.WORD 00 ; last link marked by zero
LIT .WORD *+2 ; <----- code address field
I also added some screen editing, 65C02 and ProDOS system/MLI support.
Years later, I tried to resurrect the Forth screen editor, but gave up
and wrote one in Kyan Pascal! :-)
Charlie Springer
(in article <nospam-AA821C....@web.aioe.org>):
>
> Years later, I tried to resurrect the Forth screen editor, but gave up
> and wrote one in Kyan Pascal! :-)
It is strange, but my old MVPForth PADS system screws up when I switch to 80
col on the platinum //e's I picked up in the last few years. Everyone says
they are the same, but I get 80 col sized characters with 40 col spacing. It
works right on older systems.
-- Charlie Springer
P.S. PADS has a much more sophisticated editor.
Steven Hirsch
> On Thu, 31 Jul 2008 08:03:36 -0700, John B. Matthews wrote
> (in article <nospam-AA821C....@web.aioe.org>):
>
>> Years later, I tried to resurrect the Forth screen editor, but gave up
>> and wrote one in Kyan Pascal! :-)
>
> It is strange, but my old MVPForth PADS system screws up when I switch to 80
> col on the platinum //e's I picked up in the last few years. Everyone says
> they are the same, but I get 80 col sized characters with 40 col spacing. It
> works right on older systems.
Might that be a function of enhanced //e vs. original firmware? All the
platinum //e's are enhanced, but I still run into a lot of the older style
that aren't.
Steve
Charlie Springer
Rockwell System65. Well, I finally found one (Not AIM-65, System65 Box) but
with no docs or software though it has 5.25 inch drives. I would like to get
it going.
Please let me know what you have.
Thanks,
Charlie Springer
John B. Matthews
Charlie Springer <R...@regnirps.com> wrote:
Referring to his original post,
<http://groups.google.com/group/comp.sys.apple2.programmer/msg/dc18d8ace4
d699f8?hl=en&dmode=source>,
I understood Dietmar to say he'd downloaded the System-65 version in PDF
format (22 MB): "Translated from the FIG Model by W. F. Ragsdale; with
input-output given for the Rockewell System-65."
<http://www.forth.org/fig-forth/fig-forth_6502.pdf>
Charlie Springer
(in article <nospam-D4CB5A....@news.motzarella.org>):
> I understood Dietmar to say he'd downloaded the System-65 version in PDF
> format (22 MB): "Translated from the FIG Model by W. F. Ragsdale; with
> input-output given for the Rockewell System-65."
Go it! And it does have I/O and memory map set up for the Rockwell System65.
Thanks.
-- Charlie Springer