toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

218
active users

#retrocoding

0 posts0 participants0 posts today

I've successfully built the recent version of #VolksForth for the #Commodore64 and have created a #d64 #disk #image which also contains all relevant sources as text files (in SEQ format) so they can be loaded and compiled using the new INCLUDE word. So now VolksForh-C64 supports text files and clasic blk storage.

I've also included #vi65 which is a clone of the #vi editor for the C64. It comes in versions with 40, 53, 64 and 80 columns. I have provided all of them but recommend the 64 column version for various reasons.

(I'll upload the final image to csdb.dk once I'm happy with it)

#RetroCoding
#Forth

About #COMAL for #Amiga ...
---
I can't understand how it is possible that I missed this language so advanced for the time.
I'm rewriting the manual to share it in HTML format (and also to understand this language in more depth), and from what I see it seems incredible for those times...

How is it possible that it has been almost forgotten? Or maybe it's just me who has never met this language on my path.

I'm getting the urge to use it for something 😁

For those of you who are interested in my latest project, #dxbbs you may like to know that I've done some code clenaup, renamed existing variables and introduced new ones, especially for the message base files. this is in preparation of handling multiple message bases.

I've also implemented "message flagging/unflagging" in combination with the msg_purge routine. The latter takes some time to process all messages since it actually creates a re-indexd copy of all files for the selected message base.

So I thought it would make sense to "flag" messages for deletion, effectively excluding these from being listed or read and then have the option to physically delete them and re-arrange the message file during a maintenance window, where there is enough planned downtime for such an action.

Let me note that the code is by no means an example for proper #forth programming. I'm not there yet, but in case you are interested, here's the link:

gitlab.com/ufud-org/rc2014-dxf

#z80
#bbs
#rc2014
#cpm
#dxforth
#retrocoding

GitLabbbs · main · lodger-c64 / rc2014-dxforth · GitLabGitLab.com

... an update from the trenches:

the code snippet which has been loosely resembling #BBS core functionality (the one I once wrote in #DXForth) has seen a few updates recently.

so now "DX BBS" is able to read and output ASCII text files (it could only read #Forth screen blocks before).

I've also fixed several issues where a connection drop would sometimes allow the next caller to "capture" the previous session.

Next on the list will be the whole "post-a-message" process: writing an index file entry for each new message and storing the corresponding message text etc.

long distant future design goals (so far):

(+) implement DX Forth SIO/2 driver

(+) implement a stable (disconnect proof) BBS program loop

(+) stay true to pure ASCII output only, no fancy escape squences or colors - just like RBBS / RCBBS do

(+) implement text (ASCII) file output

(-) store BBS configuration in plain ASCII text file

(-) implement mesage posting procedure

(-) implement message reading procedure

(-) implement message maintenance procdure (delete msg.)

(-) implement user database

(-) implement user database maintenace procedure (delete / modify user)

(-) implement simple user ACL / flag system

(-) implement (x)modem transfers

I don't have a real roadmap, my motivation may vary and the above is just what I think are the minimum requirements for a classic CP/M based bulletin board system. To give you an impression: it should resemble what #rc2014 #rcbbs does at the moment.

#rc2014
#cpm
#retrocoding
#forth
#bulletinboardsystem
#funwithforth

Dear Retro-Computing followers,

just in case you are wondering: I'm currently very, very busy in 64-bit cloud land and at the moment, there's no end in sight ... 🔭

Unfortunately, this also means that I'm not getting any #RetroComputing or #RetroCoding stuff done. There are a few projects in the pipeline but right now I don't know when I will be able to get back to these.

Believe me, I'd rather spend a few hours twisting my brains writing #Forth code for fun than dive into the hell that is #IaC and #Azure ...