On Mon, Nov 25, 2024 at 7:39 PM Alfred M. Szmidt <
ams@gnu.org> wrote:
Other stuff would be fixing the disk code to be more robust, it right
now will crash usim if you have LOCAL-FILE loaded, since that tries to
access disk unit 4 -- and if that doesn't exist, usim crashes. There
is also this: https://tumbleweed.nu/r/usim/tktview/031d408d22
The disk code is as you probobly saw .. not very good, and very
hackish.
I also realized if I do (print-disk-label 1) when I have only one disk it crashes. The fix for these in disk.c does not look too complicated but I couldnt find all information required. I tried for example stopping the transfer and setting the disk status to an error if the requested disk unit is not available, but I couldnt make it work. I am not sure where/how the error should be returned and also I am not sure how the caller normally behaves i.e. what happens actually when (print-disk-label 1) was used, does it give an error?
Cool things would be adding Color TV support or printer support.
Printer I have no idea but color TV should be pretty straight-forward on the usim side.
Since you mentioned TV, one more question. Is there a need to keep x11 and sdl1 backend in the code ? I guess no reason for sdl1 but I am not sure about x11, is there a platform without sdl2 or a reason to use x11 over sdl2 ?