6502.org

I've been decompiling this figForth binary, mostly with editor macros and such (read: no automation) and mostly for my own edification. Does anybody know what the legal status of such source code is? Could I put it up on github?

I'm still looking for my old fig-Forth listings, but I did find the fig-Forth Installation Manual of November 1980. It says:
According to what was the FIG web site, http://www.forth.org/ , "Although FIG as an organization has dissolved, this website will continue to reflect the on-going interest in Forth." I imagine the P.O. Box 1105 address is no longer valid. I'm sure a notice crediting FIG (sans address) will still be appreciated.

Technically, these 2 statements are at odds with each other:
If something is public domain, then there are no prerequisites at all in using it in any way.

Yes, I did a double-take when I read that as well. Since FIG no longer exists as a corporate entity, I think it's largely a moot point.

I put the mostly decompiled source code for this PET figforth up in a subdirectory of the github.com/chitselb/pettil project. It builds on Ubuntu with the xa65 cross assembler. I haven't figured out how the tape and disk i/o words work yet, working on that.

I did a little demo video of its operation, at http://wilsonminesco.com/calcs/TapeDriveDemo.mp4 . Pardon the shaky picture. The little camera is awfully hard to hold still with one hand and doesn't have image stabilization. Cutting back on the caffeine might help too. A few points of interest:

• Looking carefully, you can see the the reels turn. Each little burst is 256 bytes. You'll hear the whir of the motors as well, especially when it fast-forwards or rewinds. The program file I'm storing is 2065 bytes long. It took less time to record the file than it did to check and update the FAT. It's a BASIC program for simulating a high-pass 5th-order active filter.
• In the video, the HP-71 computer has one of my hand-written keyboard overlays on it, for one of my sets of custom key assignments. I have another for my text editor, and another for my Forth work. Without a keyboard overlay, it looks like this:
  
  This is the first computer I used Forth on (although this particluar program was not in Forth).
• The spin out to the first available space to put the file on the tape was short, since I just formatted the tape and this was the first file. You can specify how many files you want room for in the FAT, but if you don't, the default is 128 files. No subdirectories. It spins so fast that going clear to the other end of the tape only takes a few seconds, and it stops on a dime when it reaches its destination.
• The system lets you have as many mass-storage devices connected on the interface loop as you could want; but in this case I only had one, so there was no need to specify a device number or volume label.

If by "commie" you mean Commodore, then 64Forth for the Commodore 64 could use disks or tape. It had 16 block buffers. ( That's right, sixteen buffers! ) plus a communication buffer. 64Forth was a superset of Fig Forth that was on cartridge and started at address $8000. the block buffers were from address $C000 - $FFFF. 64Forth used the communication buffer to access the block buffers by temporarily switching out the I/O and Kernal ROM while copying to/from the communication buffer and one of the block buffers. IIRC all 16 blocks could be read from tape or all 16 could be saved to tape. As for disk blocks, 64Forth used Commodore relative files.
[Edit: I'm so used to 'kernel', I overlooked C64's use of 'kernal'.]