Posts by crc@toot.forth.works
(DIR) Post #AG21HUtoEm70hGfNJo by crc@toot.forth.works
2022-01-31T18:35:44.696203Z
1 likes, 0 repeats
@pfm Being me, I'd write in Forth.
(DIR) Post #AG2T534EgenJcTOaSO by crc@toot.forth.works
2022-01-31T17:07:12.189106Z
0 likes, 3 repeats
I've now released RetroForth 2022.1 on retroforth.org. It's available via Gopher, Gemini, or HTTP(S).This is primarily bug fixes; I'm working on a bunch of new things, but they'll all have to wait until the summer release.---Other than this, I'm making steady progress on the new implementation & VM. It now has a functioning block editor, and I'm getting close to considering it complete enough to actually use. Snapshots of this are also on retroforth.org#forth #programming
(DIR) Post #AKFobIcwvpfOaMsWWG by crc@toot.forth.works
2022-06-07T18:30:10.919112Z
1 likes, 0 repeats
Current progress on RetroForth:On Nga, I added `tail-recurse` to allow for things like: :foo $. c:put foo ; tail-recurseI have half of the block interface (for interoperability with ilo) working (reading; haven't done writing yet).And I fixed some bugs in the glossary generation tool. On ilo, I've committed a DOS version (builds under Turbo C 2.0, compact model) and tested under Dosbox and a couple of emulators with MS-DOS and FreeDOS.I fixed bugs in handling of negative numbers, have a slightly smaller dictionary lookup word, and added more comments to the source.I think that'll be it for today; it's time to relax for a few hours.
(DIR) Post #AL7vNiXOBq6k532I76 by crc@toot.forth.works
2022-07-03T16:01:34.427734Z
1 likes, 0 repeats
I’m working with one of my sons on rebuilding & repairing a few (10-15 year old) computers I salvaged recently. We now have one working Windows system, and one with OpenBSD. There are two more not operational yet. We’ll be doing one of these as a FreeDOS system, and one running Haiku or Plan 9.
(DIR) Post #AL9zPOPOmuJcMcGyGG by crc@toot.forth.works
2022-07-04T20:44:51.425131Z
2 likes, 1 repeats
Spent another day working with my son. This time programming; we completed the core support for simple graphics (pixels, lines, rectangles, triangles, and circles so far) into the new RetroForth implementation & vm. This replaces the original prototype display code with something faster, more flexible and easier to maintain.We think the initial code will be checked into the repository later this week. He wants to get a few more words done first, and I need to write down initial documentation on the words and the implementation.
(DIR) Post #ALGQ3RcPEj5A3VEfHU by crc@toot.forth.works
2022-07-07T23:11:05.446573Z
1 likes, 0 repeats
I’ve begun removing my old repositories from GitHub. I’ll leave the read-only mirror of retroforth/Nga for now, but all of my others will be gone by tomorrow evening.I had hoped to complete this today, but actually removing the repositories has proven more time consuming than I had anticipated.
(DIR) Post #ALMXpjS8H6CHvfauAa by crc@toot.forth.works
2022-07-10T20:56:12.167890Z
0 likes, 0 repeats
Watching Arland experiment with color palettes and interface layout.He’s defined four; three of his own choosing, and one derived from the solarized colors. Looks likely that he’ll be adding several more over the coming week.
(DIR) Post #ALWpqM5nMYMHXNUfiK by crc@toot.forth.works
2022-07-15T21:29:00.641212Z
1 likes, 0 repeats
Finally starting the weekend. I’m working on documentation for the new retroforth system, and will be helping Arland try to finish the last couple of things for the graphics support.We also have some small hardware projects this weekend (mainly assembling a small, portable machine for his use).
(DIR) Post #AOxisx78PwretU7GIS by crc@toot.forth.works
2022-10-26T14:41:58.885496Z
1 likes, 0 repeats
@vertigo @xerz Looking at my archives, I have a copy of the bootsector code, which was from Dolphin 0.4.0. (The README lists this as bootsector 2.1, but the $id in the bootsect.S shows 2.3) http://forthworks.com/temp/dolphin-bootsector-2.1.tar.gz or gopher://forthworks.com/9/temp/dolphin-bootsector-2.1.tar.gz
(DIR) Post #APjOXjKtA8496GfGts by crc@toot.forth.works
2022-11-18T13:57:21.927783Z
1 likes, 0 repeats
It's a slow morning, so I'm taking some time to clean & switch inks on the fountain pens I'm currently using.
(DIR) Post #AUj2IYB80GsuIAskls by crc@toot.forth.works
2023-04-16T22:46:22.002227Z
0 likes, 0 repeats
I've finished a Common Lisp implementation of my ilo vm. This took longer than I had expected; and it's not formatted well, but I need to take a break from looking at all these parenthesis before trying to clean it up.
(DIR) Post #AViqz9nvyWY7O1VPBQ by crc@toot.forth.works
2023-05-16T18:18:57.487391Z
0 likes, 2 repeats
#FreeBSD #amd64 #assembly I've spent a couple of hours now and am quite lost on trying to debug an amd64 assembly program under FreeBSD.I ported it from Linux to OpenBSD. Then made the relevant adaptions to the system calls for FreeBSD, and when I try to run it it just exits.But if I run it under truss(1) to verify the system calls it works fine(*1). I've not been able to figure out why it works under truss, but not when run directly.I've reviewed the source, double checked all the system calls, and tried single stepping for about an hour (it's a vm for a tiny virtual cpu; it's not practical to single step indefinitely). I'm a little constrained since I'm not very familiar with lldb, and I can't get gdb to run at present (*2).If anyone has any suggestions on what to try, I'd appreciate them.(*1) there is an issue with the command line processing, but I bypassed that until the rest is working.(*2) I updated my packages yesterday and installed gdb, but running it gives only "ld-elf.so.1: Undefined symbol "rl_eof_found" referenced from COPY relocation in /usr/local/bin/gdb"(*3) a source snapshot w/makefile is at https://forth.works/temp/konilo-freebsd.tar.gz if anyone has time to take a look.
(DIR) Post #AVixSqUCxnsxsuoocK by crc@toot.forth.works
2023-05-16T20:51:06.607696Z
0 likes, 0 repeats
@zbeeble I've run into that with a couple of ISPs; not sure why. I uploaded a copy to a different server at http://forthworks.com/temp/konilo-freebsd.tar.gz which might work better.
(DIR) Post #AVixbgkSXQUsI0dX1s by crc@toot.forth.works
2023-05-16T20:52:37.178935Z
0 likes, 0 repeats
@yrabbit Thanks! I hadn't had a chance to setup a #DragonFlyBSD system yet. I'm glad to know it's working there.
(DIR) Post #AVjDTHb7lJ3rEiHfXc by crc@toot.forth.works
2023-05-16T23:50:14.034210Z
0 likes, 0 repeats
An update: it's working now (other than command line processing, which I'll look at tomorrow).I had to add code to save/restore r8, r9, r10, and rdx when performing the syscalls.
(DIR) Post #AVjDWk0ia2gmE3u892 by crc@toot.forth.works
2023-05-16T23:50:54.598647Z
0 likes, 0 repeats
An update: it's working now (other than command line processing, which I'll look at tomorrow).I had to add code to save/restore r8, r9, r10, and rdx when performing the syscalls.
(DIR) Post #AVjE1dhU5jl1dFdpAm by crc@toot.forth.works
2023-05-16T23:56:36.192640Z
0 likes, 0 repeats
@millihertz Maybe. I'll have my son help me write a bunch of things to test this much more completely.
(DIR) Post #AVr94w5mxOYNxoljgO by crc@toot.forth.works
2023-05-20T19:38:49.474022Z
0 likes, 0 repeats
@rickcarlino It should be ee-loh.
(DIR) Post #AXaT7T4RqZOU4IUqSu by crc@toot.forth.works
2023-07-11T14:17:35.508672Z
0 likes, 0 repeats
I've completed some long overdue updates to Casket, my HTTP server. It's now much faster (a test transfer that was taking over 15 seconds is now just 0.3).Some notes on the changes are at https://forth.works/casket-report.txt and the updated server is now running https://retroforth.org & my other domains.Now taking a break to brew some 玄米茶 before deciding on my next project.
(DIR) Post #AZ40hfoyvk92InwAK0 by crc@toot.forth.works
2023-08-24T18:12:15.629355Z
0 likes, 0 repeats
Due to increasing issues with this instance that I've been unable to resolve, I'm moving to @crc This instance will remain up until the end of September, though I'll likely not be posting much on it.