mirrorbird (09:37:21)
+ reserve a little RAM for IPC

Agemixer (09:35:32)
mirrorbird: thinking out loud in fact i guess, in fact, it makes sense to share most the same areas and use full available RAM etc, except that another instance of BASIC could be used for programming WHILE executing that basic program in another

plc (09:20:06)
moin o/

communicator (09:18:10)
o/

Agemixer (08:56:29)
same I/O area, but I/O disabled (so it writes/reads from RAM)

Agemixer (08:55:08)
so the same atea, the first one writes to i/o while the another writes to RAM (so thetes no need to modify the basic code)

Agemixer (08:53:45)
Or uf only 2 basic instances: no need to swap i/o or color RAM except when you switch to this another "background" instance

Agemixer (08:50:42)
i/o area $d000-d030, nothing to swap with SID, color RAM the biggest chunk ($d400-d800), those can be revealed as RAM and swap from there, so more than 2 basic instances could be possible

Agemixer (08:47:40)
basically the $000-$300 area and I/O swap, but then the timers cannot be much mangled via basic. Which is quite a rare case thought.

Agemixer (08:44:53)
mirrorbird: i had a thought, it is possible to make a c64 basic V2 multitasking, but it makes all the basic instances way slower, and less memory... lotsa i/o and BASIC registers and states swapping.

Genlock Intro

PRI (Volker Meitz)

plc

Time Left: 4:48