The C64 OS Programmer's Guide
c64os.com
c64os.com
Genuine question… Could Commodore have made an OS like this in 1982, if they had today’s perspective?
- Devices were addressed by a primary address (0-31) and secondary address (meaning=device specific)
- You had basic I/O calls: OPEN, LOAD/SAVE (read/write a block of memory), CHRIN/CHROUT (read/write a character), READST (get I/O status), and CLOSE.
- You had the default input and output device and those could be redirected to a file (CHKIN/CHKOUT)
- It was totally possible to open the keyboard for input (device 0) and screen for output (device 3) and get basic buffered terminal-like I/O.
Now if you want to talk about windowed event-driven GUI, now that was crazy for 1982. But Commodore 64 users were lucky to get the above, as Commodore was all about cost cutting, time to market, and underpricing the competition with the 64. Developing a GUI-like environment would have been seen as an unnecessary cost - after all Commodore 64 was stuck with BASIC 2.0 which was primitive even for the time (other Commodores had higher BASICs). That's why an external entity like GEOS really had to come along and do it, because Commodore just wanted to sell as many as possible, and they did that spectacularly well.
> C64 OS has one goal. Make a Commodore 64 feel fast and useful in today’s modern world.
Lol. That this is even conceptually possible blows my mind.
Is the "D & D Roller" on the context menu what I think it is?
[1] https://twitter.com/gregnacu
[2] https://hackaday.com/2022/07/28/new-os-for-commodore-64-adds...
- C64 https://style64.org/c64-truetype
- MSX http://www.ateijelo.com/blog/2016/09/13/making-an-msx-font
- Cool Retro Term https://github.com/Swordfish90/cool-retro-term
(Besides, even real SID chips are different from each other.)
is there a plan to make printed copies of the guides available?