#f83 — Public Fediverse posts

I'm currently checking out options for doing a little coding on a #MSX1 system (real and emulated, when abroad). There's an adapted #F83 #Forth here (https://github.com/janaite/msx-forth83/tree/master) but while it's working, it's not optimized for 40 colum mode. And on MSX1 you only have 40 columns.

Then there's a #BASIC compiler from the former, dutch "#MSX #Club #Gouda" named #Mozart which compiles your MSX BASIC code and gives you some speed improvement - it's here (https://download.file-hunter.com/Program%20language/Mozart%20-%20Compilador%20BASIC%20para%20MSX%20(1990)(Cibertron%20Software)(br).zip).

And, of course there's #TurboPascal3 for MSX which does support 40 column mode (run TINST.COM to set up screen). It's also here (https://download.file-hunter.com/Program%20language/Turbo%20Pascal%203.01a.DSK.zip)

Aside from that you could use a C compiler like #SDCC or #BDSC under #MSXDOS1 ...

I guess I'm a little lost here ...

so I am currently trying to get the CP/M version of #F83 #Forth by #Laxen and #Perry to do what I want.

The problem is that I can use BLOCK, UPDATE and SAVE-BUFFERS and any new data written to a block is preserved for the current session. But as soon as I quit Forth and call it up again, using the block file I've just modified, the changes are gone as if they have never been written to disk.

Any ideas?!

I'm not proud of this, but I was in a hurry and it works (now the clock cycle police are after me 🚔​ )...

EDIT: to put the icing on the cake, I re-named it 8RSHIFT ... gotta go ...

#F83
#Forth
#QuickAndDirty
#AndYouWantItDirty
#RetroProgramming
#HowNotToDoIt

So #gForth has been inspired by #VolksForth which is based on #F83 - is this roughly correct?!

#Forth

Using #openMSX to prepare a custom 360KB disk image (MSX1 machine with MSX-DOS 1.80) for my #Sony #HitBit machine that will include #ZSM #assembler and #F83 #Forth ...