Have you tried typing (pasting) that initial transcript back in to see if you duplicated the bug? It's a great transcript, but it doesn't show the entire history of the session that actually had the bug.
I think it would be helpful to see if it replicates from the cold start of the image.
(I assume the "compiled" message are from Tali Forth...)
jgroth wrote:
Cool.
The reason I'm so interested in Tali Forth is that I'm building a 65C02 SBC and I want Tali Forth to be the OS so to speak, if that makes any sense. So the SBC will have a VT100 terminal serial interface, so no graphics, just plain 80x24 text display (the project is called Micromite and the url is
http://www.siliconchip.com.au/Issue/2014/July/Micromite%2C+Pt.3%3A+Build+An+ASCII+Video+Display+Terminal) and an IDE interface.
The inspiration for this project is an 80s computer called Jupiter ACE and I wanted to build something similar to that. Tali Forth is the first Forth I've come across that is 6502 based and platform independent and easily ported to an SBC.
Hence my interest in Tali Forth.
Tali needs some extras though like IO words so you can read, write files and directories. Store and load word definitions (not sure how to do that though, but this is early days in the project).
What were you planning to use for the IDE interface? If it's a raw block device, then implementing file support will be more difficult, as you have to implement a filesystem. But I'm pretty sure I've seen interfaces that let you interact with a DOS formatted flash cards using a high level serial protocol (SPI I think?). That, obviously, would be much easier. If you simply have the IDE drive as a block device, then initially you could just use the basic BLOCK I/O provided in early Forths.
I'm surprised you didn't find the original 6502 Fig Forth, but there's likely not a simple binary that "just works" in something like py65, and the raw assembly may not work with a modern assembler. It would be close, as it's pretty basic 6502 assembly. But out of the box, drag and drop, no. Plus it would have to be ported to something like py65 anyway (which isn't difficult, I ported mine readily -- not to py65, but my own).