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

[Leslie Ayling]

Hi Stephen,

Thanks for the bug report.

At least we're moving in the right direction...

> I first found that it does not want to load screens of code from “disk”.  It returns an error, not understanding a word very early on in the load process.  
> Curious because the word it complains about is defined in its dictionary.  Hmmm.

Can you give me a specific example of a screen number you are unable to load, and the error message you get back?
That will help me identify exactly what is going on.

I tried listing blocks in VCC, and it seems to work properly.
Example:
--------------------------------------------------------------------------
  ok
15 list
Block # 15
0 ( i/o extensions                               12:47 pm cee 23jan84
1
2 : width................ etc. etc.

--------------------------------------------------------------------------


> I suppose that it may not like working with Drivewire as the disk system on the CoCo3FPGA?

Not yet anyway....

After disassembling the program, it's clear to me that the eForth program takes over the machine completely, 
and uses its' own drivers for everything. The keyboard driver being just one example.

Probably makes use of some hardware feature in the disk controller that Coco3FPGA doesn't emulate.

See if we can't get it sorted :)

Cheers,
Leslie
VK2LR


 

-----Original Message-----
From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Stephen Pereira
Sent: Sunday, 25 February 2018 8:14 AM
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

Got it!  Excellent!  Thanks *very* much.

Initial report:

I loaded this patched version onto my CoCo3FPGA system, and it came up!  Yay!  

However, there seems to be some issues with the system running on the CoCo3FPGA platform.  I first found that it does not want to load screens of code from “disk”.  I returns an error, not understanding a word very early on in the load process.  Curious because the word it complains about is defined in its dictionary.  Hmmm.

I find that this Forth also complains about the same words if I attempt to use them as direct entries.  Too bad!  This is certainly a great leap forward, but it has not yet achieved a fully working system on the CoCo3FPGA - for me, anyway.  Has anyone else tried?

Just to be sure, I loaded up E-Forth on my CoCo 3 from my SDC.  Yes, it runs, and it loads the screens in from disk (at least until it reports a “Branch Too Long” error).  So, E-Forth seems to work as described on my physical CoCo 3, and it now comes up properly on my CoCo3FPGA, but it seems to have other issues on that platform that continue to get in the way.

I suppose that it may not like working with Drivewire as the disk system on the CoCo3FPGA?  Maybe.  I am curious why it complains about some of the words already defined in its dictionary, though.

Thanks a million for all your effort on this.  It sure was nice to see E-Forth come up on a nice clear screen with the CoCo3FPGA.

If anyone else has tried this and you get different results, please let me know!

smp
- - -
Stephen Pereira
Bedford, NH  03110
KB1SXE