mmu_manHey, you're missing #RetroRepairRoundup with @MuseumJoe @RonsCompVids @gutbomb @1Bit @I80386sx @TrinasTechnobabble …
YouTube
Regionales Retro-Rechenzentrum
Davide BucciSomeone reported a bug on #SilkDust. It appears only in the versions of the game where all the parts are spliced together in a single executable (Amiga, Macintosh, Atari ST, etc.).
The game can be finished, but there is an object that is not shown in the inventory (but can still be used) and there are some quite misleading messages. If you are stuck in part 2 read this: https://itch.io/post/12785724 #TextAdventure #IndieGame #retrocomputing #Amiga #Mac68k
The game can be finished, but there is an object that is not shown in the inventory (but can still be used) and there are some quite misleading messages. If you are stuck in part 2 read this: https://itch.io/post/12785724 #TextAdventure #IndieGame #retrocomputing #Amiga #Mac68k
@shyra is streaming right now:
https://www.youtube.com/live/cPE7LlriqUY
https://twitch.tv/techambrosia
LIVE - Let's chat about old Macs, old software, and the 80s / 90s in general!
Let's recap this #PowerBook 520c!
Recapping my PowerBook 520c
@ry @kalleboo Ooooh, Think Pascal.
Back in … 1989? a club colleague introduced me to the local uni’s computer lab, filled with Mac II. Base config, 13" color screen with 640x480 in 256 colors, with Hypercard and Think Pascal on it. And some word processor.
Coming from the Atari ST, the Mac II wasn’t much faster than what I had, and the GUI was theoretically similar.
But ThinkPascal felt sooo much more advanced due to the tight integration of its source level debugger into the IDE. On the ST, debuggers weren’t integrated yet into the UI, and were cumbersome to use.
So Think Pascals step-by-step debugger and variable inspection in windows were mind-blowing for me ("how to they do this in supervisor mode, and yet have full access to high-level OS/grafport/window calls?" -- little did I know how hacky System 6/7 were).
These memories.
#retroprogramming #retrocomputing #macos #mac68k #atarist #pascal
So, the only thing I hate more than people forcing me to published unfinished work because they are redoing what I spend nights already doing, is people wasting time doing what I already did…
https://github.com/mmuman/cad-mac-pb500-pwrconn
#Mac68k #PowerBook #PowerBook5xx #RetroComputing #3DPrinting
Still needs a few tweaks but…
USB-C power adapter for the #PowerBook 5xx…
(note it doesn't provide charge)
@kalleboo @me_ What always made me wonder (not having programmed System 6/7 back in the days): There _were_ applications that handled memory allocation dynamically (e.g. some versions of Graphicconverter), and some text editors where I forgot the names, where it was _not_ necessary to adjust the memory allocation for an program in the Finder manually.
This dynamic memory API/functionality capability seemed to be added to System 7 back then. It always occured to me that RAM Doubler was a cure for programs that didn’t use newer APIs but the “old” pre System7 way of allocating memory fixed through settings in the Finder.
But, this is obsevation is deduction and guessing. Would be great to read here from someone with actual knowledge of the memory manager of System 7.
Perhaps @Cdespinosa can help or reach out?
@MrTechGadget Aaah, I tend to forget about enabling 32 Bit still after all these years. And isn’t the IIsi the machine, where you’d setup a 1 MB RAM disk, left unused, with a special driver for the IIsi, to use up the onboard RAM of 1 MB, that’s much slower due to video access, compared to the SIMM slots? What’s the name of that special RAM disk again?