Cenbe
The CTCP self-ping/watchdog timer appears to be working correctly; this is a major win! #Commodore64 #GEOS #IRC
Making backups before tomorrow's testing of the latest build of geoIRC. #Commodore64 #GEOS
I'm trying to find a way to tell if I'm still alive on an IRC server by sending myself a CTCP PING. This is the output with it implemented as a slash-command; the reverse-video lines will be silenced. Next step is to set up another GEOS process timer to start when I log on to a server... #commodore64 #GEOS
Disaster strikes after removing the push/pop of a #GEOS pseudoregister that didn't appear necessary. Aliens have fouled my screen! #commodore64
An attempt (a few years ago) at converting a photo of my cat to a GIF, then importing it as a #GEOS bitmap on my #Commodore64.
Turre@morgan @psf
This. People used to be proud of the software they created! And for good reasons too.
I have fond memories of C64 GEOS by Berkeley Softworks which later became GeoWorks. There was an interview in I think Compute's Gazette on their work on GEOS, how their engineers would take a routine and try to shave off clock cycles and bytes of memory use. And do it several times per each routine. It was such an amazing environment on the ridiculously constrained hardware. And now we have emulators for that stuff running inside the browser, consuming several gigabytes of memory.
One of the fondest memories of it is a when I returned a larger history homework project written with GeoWrite (I think in 1990), and the teacher asked me to stay after class for a chat. I was dreading some disciplining, although wasn't sure for what. Instead he was genuinely amazed at the print quality and just wanted to know what equipment I had used to do it. He was something between flabbergasted and disbelief when I told him it was entirely done on a Commodore 64. He said his expensive new PC couldn't produce anything like it.
What I didn't tell him was that GeoWrite didn't have scandinavian letters, so I had to add the dots over ä and ö manually 😄