Jump to content

VolksForth X16 3.9.4

   (1 review)

2 Screenshots

About This File

VolksForth Readme

VolksForth is a 16bit Forth System produced by the German Forth Gesellschaft e.V.

The main repository lives here: https://github.com/forth-ev/VolksForth

Major development of this system was done between 1985 until 1989. The VolksForth Project was revived in 2005 with the goal to produce a managable Forthsystem for computer systems with restricted system resources.

Some modern Forth Systems were influenced by or were derived from VolksForth (GNU-Forth, bigForth).

The current Version of VolksForth is 3.81. Version 3.9.x will be interim versions on the way to sync all VolksForth targets and move towards compliance with the 2012 Forth standard.

Version 3.8.x is based on the Forth 83 standard, Version 4.00 will be based on the current 2012 Standard (https://forth-standard.org).

At this time VolksForth is available for this Systems:

  • VolksForth MS-DOS (Intel x86 architecture i8086/i186/i286/i386/i486 etc)
  • VolksForth 6502 (Commodore 64, Commodore Plus 4, Commander X16, Apple 1, Apple ][, Atari XL/XE)
  • VolksForth Z80 (CP/M, Schneider CPC)
  • VolksForth 68000 (Atari ST, Amiga with EmuTOS)

 

Copyright

The VolksForth Sources are made available under the terms of the BSD Lizenz - http://www.opensource.org/licenses/bsd-license.php

The Handbook is Copyright (c) 1985 - 2020 Forth Gesellschaft e.V. ( Klaus Schleisiek, Ulrich Hoffmann, Bernd Pennemann, Georg Rehfeld, Dietrich Weineck, Carsten Strotmann).

(most of the Information is still in german. We are planning to provide future versions with englisch documentation)

Have fun with VolksForth the VolksForth Team


What's New in Version 3.9.4   See changelog

Released

Version 3.9.4 migrates the Commander X16 version of VolksForth to the Kernal version R41 and the new prototype #2 board.

It also reduces the use of and dependency on Kernal variables in RAM. One dependency on the location of IOStatus (0x0289) is still needed; I'll open a discussion with Michael Steil about this as I believe it'll need a fix in the Kernal to an old CBM Kernal bug.


try_it

Yes

try_it_start_prg

v4th-x16

try_it_license

BSD 2-Clause "Simplified" License
  • Like 1
 Share


User Feedback

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest

Moto Rola

   1 of 1 member found this review helpful 1 / 1 member

Not a review yet, just a question:

„load, thru, +load, +thru were removed from the v4th versions like the x16 version that don't have block/buffer disk access”

But actually... why VForth for x16 „doesn't have block/buffer disk access”? What about traditional Forth screen support? And blocks used as „memory expansions”?

Response from the author:

The problem with block access on the X16 is basically that the Commodore DOS (and afaik also the X16 Kernal/DOS) doesn't have an equivalent to fseek(), i.e. you can't directly load the 20th block in a file without first reading the 19 blocks before. On the C64/C16+1541 this is solved by direct disk access, i.e. the Forth blocks are mapped directly onto disk sectors, like in classic bare-metal Forth systems that run without an OS. I kind of doubt that this would work very nicely on an SDCard for the X16. The only alternative then would be REL files, which come with their own flavours of clumsiness in everyday life, iirc. Tbh, I haven't investigated this direction too much yet.

Link to review
×
×
  • Create New...

Important Information

Please review our Terms of Use