[mfld]

Does anyone remember the art of optimising MSDOS startup to have enough free memory for games? And inspecting gorillas.bas? For me, this probably contributed to an interest to learn more and experiment. In fact, I'd like to encourage my son to a similar creative exploration, but don't how this is going to happen when pulled into the current generation of games and videos.

[endgame]

Yeah, I spent more time than I cared to admit fiddling with DEVICE(HIGH) lines, tweaking FILES= and BUFFERS=, running MEMMAKER.EXE over and over as if that would do something, but it was never the real thing. The real thing is making the machine do something I wanted instead of what the manufacturer wanted. For a kid of this generation, I'd look for games with reasonable modding APIs, perhaps something like Lua, and ideally something where playing multiplayer lets him show his creations off to his friends.

From there, look to packages like LÖVE which still use Lua but give full control over the whole game, and help him explore and wrangle the things he needs to understand to make his programming real. And if the lower levels interest him, help him dig deeper. But I think modding and scripting is probably the best place to start.

[contingencies]

Indeed: config.sys autoexec.bat, EMS, HIGHMEM, and all those terrible early sound blaster drivers, mouse drivers, network drivers... I think the one I found hardest to get running was Quarantine. But it was definitely one of the best games. So imaginative for the era. And Australian! With music from some later famous bands! https://www.youtube.com/watch?v=QwO8XWbB1Pk&list=PLA5hK1g6CN... https://www.playdosgames.com/play/quarantine

[nosioptar]

It's been a long time, but I remember it a bit.

I also remember running over to the neighbor's to make a copy of a working config file after effing up my config file. (Himem.sys?)