Thanks to various expressions of interest & support, I've freshened my old ForthOS. It builds its own GDT/IDT, has a proper RTC handler, and all I/O is interrupt based (previously it was a polled system). On qemu it no longer pegs the host CPU at 100%. It's still free, open source, and so forth. Try the new image disk image (source included):
Get it at https://forthworks.com/retro/r/RETRO12-2020.7.tar.gz or gopher://forthworks.com/9/retro/r/RETRO12-2020.7.tar.gz (add .sig and .pub to the URL if you want to check the signature)
This is a minor release, see http://forth.works/share/95e3a6e7444ee03fdf23efbe309f8061 or
As a side note, I now have a Patreon at https://www.patreon.com/_crc to help support the ongoing development. As a result of this, Retro is now available for free in the iOS and Mac App Stores
I just pushed a new release of my #forth system.
I've submitted a patch to the FreeBSD ports and submitted an updated iOS version to Apple for review.
Other than bug fixes, in this release I rewrote the assembler and have hand tuned assembly for a number of words in the standard library. It's smaller and faster than before.
Finished testing everything on the new OpenBSD server; everything is working now.
I'll keep probing the old one to try to figure out the cause, of the loss of networking but at least nothing was lost.
This is a case where it's nice to be running a nearly stock OS (the only extra package I need is fossil; everything else needed is either part of the OpenBSD base or written in retro forth, making it easy to setup).
I might write something to automate setup of the various cron jobs though.
While working on my Forth this week, I rewrote the assembler in assembly, letting me fit it into my kernel so that I no longer need to inline raw machine code in the standard library.
The rewrite is a lot more efficient, reducing the memory footprint from 661 memory locations to 109.
Being able to use the assembler at any time is allowing me to hand optimize parts of my standard library of words, reducing the memory footprint and improving performance.
@djsundog In all honesty, Masto/Fediverse is the last social media network I plan to participate in. If I need to make a statement and "thought-leader," then I'll just go back to long-form blogging.
I've updated the #retro #forth DOS build.
http://forthworks.com/retro/download/RETRO.ZIP and gopher://forthworks.com/9/retro/download/RETRO.ZIP
So, the #Forth community lost another member recently. RIP Bill Muench. Along with Dr. Chen Ting, he wrote the first versions of eForth.
I sometimes wonder to myself, if, when I die, will I be the last person using Forth?
Grab the .dmg at http://www.forthworks.com/retro/download/MacRetro-2019.8.dmg.zip or from the app store at https://itunes.apple.com/us/app/retro-forth/id1317494014?ls=1&mt=12 (This is the editor based system, not the terminal version, the terminal version can be built from the standard sources)
The version in the FreeBSD ports tree is also up to date now. My pkgsrc is broken, so an update for that is on hold until I can fix it.
Retro #Forth 2019.7 is now released.
New binaries for macOS and Windows will be built from this later in the week.
Of the changes, the most notable ones are improvements to portability and building, and the addition of a sockets interface.
The iOS version is also updated: https://apps.apple.com/us/app/retro-forth-12/id1170943580?ls=1
After a couple of evenings, 7080 is working. This is a little gopher-via-http proxy. Not done, but functional for text and directories.
I'm starting work to remove the use of curl this weekend (will be testing a version using the socket words in RETRO), and will then clean everything up before adding support for binary files.
I've created a github repo for "f68k", an Forth 83 System for m68k computer (Atari ST, Amiga, Sinclair QL and OS-9). I've merged back the Amiga and Atari ST files.
This Forth system is the ancestor of f68kans, an ANS-Forth version of the same system:
Programmer. Developer of Retro Forth, Gopher servers and clients, and several iOS apps. Co-founder DC Comtech.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!