There was this game I wanted to play that required a lot of memory. My dad didn’t want to spend more money on the computer so I spent a few days hacking the bios, config.sys and autoexec.bat to make sure only the bare minimum was met with drivers for the sound blaster and the mouse loaded and enough RAM left for the game to load.
Absolutely is/was. It’s how most of the engineers I know, including myself, got started with computers that led us to the career we have today in tech.
I’m just trying to block out trauma from winsock.dll and figuring out IRQ conflicts.
There was this game I wanted to play that required a lot of memory. My dad didn’t want to spend more money on the computer so I spent a few days hacking the bios, config.sys and autoexec.bat to make sure only the bare minimum was met with drivers for the sound blaster and the mouse loaded and enough RAM left for the game to load.
Making the game play was engineering at the time.
Absolutely is/was. It’s how most of the engineers I know, including myself, got started with computers that led us to the career we have today in tech.
Anyone else remember Memory Commander?
I suspect that all this program did was push stuff to the hard drive or faked how much free RAM you had to games.