[Coco] Frank Hogg Labs E-Forth, patched to run on the CoCo3FPGA + VCC + Jeff Vavasour's emulator

[Leslie Ayling]

Hi Stephen,

When you first start up the program, try typing:

cr .( test)

Do you get "test ok" , or "cr ?" as a result?

What do you get on a real coco with CoCoSDC vs. CoCoFPGA?

If you LOADM"EFORTH.BIN
Then eject the disk.
Then "EXEC"

The cr word should already be visible without the disk being there. 

----

If I try "1 load" on VCC 2.01, it responds with a load of "xxxx isn't unique" errors followed by "branch too long".

What *exactly* happens on CoCo3FPGA when you try loading block#1 ?

----

I'm not sure there is any need to load block#1 ?

Looks as though the extra words in block #1 have already been loaded in on the disk
that came from the coco archive.

Cheers,
Leslie


-----Original Message-----
From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Stephen Pereira
Sent: Sunday, 25 February 2018 1:17 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] Frank Hogg Labs E-Forth, patched to run on the CoCo3FPGA + VCC + Jeff Vavasour's emulator

Hi Leslie,

I got a failure right away when I performed:  1 load

The system came back with:  cr ?

Saying that it does not recognize the word cr even though it is defined and works fine in direct entry.

Screen 1 is the so-called load screen because it asks for all the rest of the screens to be loaded.  I then tried to load screen 2 (I think) directly with:  2 load

The system came back with: origin ?

The interesting thing with this one is that even when I tried direct entry of the command origin, the system still emits the error message.  I thought that the origin command is part of the base dictionary, as it is with other instances of Forth.

That’s the specifics that I can recall.  If you want me to do any experiments, just let me know what.

Thanks!

smp
- - -
Stephen Pereira
Bedford, NH. 03110
KB1SXE