this post was submitted on 21 Mar 2024
587 points (97.3% liked)
Funny: Home of the Haha
5764 readers
409 users here now
Welcome to /c/funny, a place for all your humorous and amusing content.
Looking for mods! Send an application to Stamets!
Our Rules:
-
Keep it civil. We're all people here. Be respectful to one another.
-
No sexism, racism, homophobia, transphobia or any other flavor of bigotry. I should not need to explain this one.
-
Try not to repost anything posted within the past month. Beyond that, go for it. Not everyone is on every site all the time.
Other Communities:
-
/c/[email protected] - Star Trek chat, memes and shitposts
-
/c/[email protected] - General memes
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.