openbsd's httpd seems to be handling the load well.
I will read your comments if any :)
I had thought about trying this myself but gave up after realising I'd not have access to Trackdisk.device from Romwack - Didn't know about Coolcapture/Warmcapture. I guess I need to read up some more!
Regarding trackdisk.device, you might want to take a look at:
And the function calling mechanism for RomWack backend:
Ultimately, TrackdiskDevice ends up being a thin wrapper around ExecLibrary:
For performance purposes, the Floppy tool does instead use this small server written in asm:
And the python boilerplate client to talk with it:
For the BERR case, without the initial reboot, Amiga will just crash again when calls are made from the exception handler. Recovering control after a reboot is a nice and clean way to get the Amiga into a known state. It is definitely also doable without rebooting, but somewhat more involved.
Else, when entering the debugger via e.g. the extra debug menu present in workbench when loaded via "loadwb -debug", the context RomWack works with is a user context, so I just take over the user task. As long as I don't corrupt the stack (or anything else), I can even return cleanly.
There's much work to be done with the Amiga in the OSHW front, thus this is very welcome.
I intend to read your mem68k-like board's Verilog at some point in the near future. I might want to build one of these, but even if I don't, I wish to learn how it works.
; LOAD A BLOCK OF TEST CODE THROUGH THE KEYBOARD PORT :
; FOR MANUFACTURING TEST. :
; THIS ROUTINE WILL LOAD A TEST (MAX LENGTH=FAFFH) THROUGH :
; THE KEYBOARD PORT. CODE WILL BE LOADED AT LOCATION :
; 0000:0500. AFTER LOADING, CONTROL WILL BE TRANSFERRED :
; TO LOCATION 0000:0500. STACK WILL BE LOCATED JUST BELOW :
; THE TEST CODE. THIS ROUTINE ASSUMES THAT THE FIRST 2 :
; BYTES TRANSFERRED CONTAIN THE COUNT OF BYTES TO BE LOADED :
; (BYTE 1=COUNT LOW, BYTE 2=COUNT HI.) :
I sold it before I got the chance. It’s a neat machine, but not my particular niche in the retro realm.
re: Amiga, it is sad that, with 256KB of ROM, they couldn't fit a key combination to call exec's Debug() in the strap module.
I understand that, somehow, nobody thought about it.
Workbench is what it is.
> At this point, we have control again and AmigaOS is almost fully initialized, with the notable exception of dos.library (not required for doing block level I/O), which is skipped as the LSB of its RomTag structure's rt_Flags field is clear.
Tiny question, tiniest bit answer :-D
To add some context, these RomTag structures reside in ROM, so they can't be edited.
The table of residents is, however, in RAM. It should be possible to add RomTags to it, or copy the ROM ones to RAM and modify them there. Conveniently, I did not need to do so.
I guess it's the combination of computer history/nostalgia and the impressive level of knowledge that motivates me the most.
It might have something to do with my user being new. Who knows what secret rules are in place for that.
I'm hopeful this will change soon, but who knows.
I suspect you just got hit by the spam filter. (But I’m not a mod I’m just a nobody so that’s just a guess on my part.)
My pyamigadebug is backed by this debugger and the newer SAD that replaces it in AmigaOS 3.x.
Making function calls and uploading code to the Amiga and running it is made trivial by pyamigadebug. My AmigaXfer is built on this.