this post was submitted on 12 Dec 2024
1412 points (98.5% liked)
196
18191 readers
487 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Where're all the DOS kids at?! 5 hours and 66 comments, but not a single mention yet.
Never mind solving problems with Windows; shit gets real when the thing boots to a
C:\>
prompt and you need to know things like the difference between CGA/EGA/VGA/Hercules graphics modes and WTF an IRQ is just to install your games in the first place.Kids these days don't know the pain of trying to get enough free conventional memory to run something.
I was talking to a friend just the other day about that. I remember some application we used to reconfigure autoexec.bat to optimize it for one type of memory or the other, but I can't remember the name of the application (I think it came with the OS), and I can't remember what the different memory types were called either.
IIRC the application was just "edit.com", as in "edit autoexec.bat". The different kinds of memory were expanded memory, extended memory, and the high memory area; high memory was useful regardless which of the other two you were using, and those two were for the most part kind of interchangeable. You also typically had to mess with config.sys, which handled some things like the mouse driver. It was really common to have specific floppy disks that had only those two files on them (well, and were set to be bootable), so that if you needed a particular configuration for some game--maybe you didn't load the CD-ROM driver, since that took up a lot of precious low-memory kilobytes--you could leave your normal setup alone and just stick your custom boot disk in for that program. Some programs were really tricky to make enough room for, even if you had a ton of RAM, because that privileged low ram area was so hard to manage.
I figured it out - it was memmaker. It automatically edited autoexec.bat (and possibly also config.sys, I'm not sure).
Ah, yeah, I think that may actually have been a paid program. It was something folks were willing to pay not to have to do, because, as I say, it was surprisingly tricky to manage the memory below 640K.
Well, at least in our case, it wasn't something that we bought. I'm pretty sure it came with our MS-DOS.
Oh, you're right, it's right there in the link you shared--it was built in to MS-DOS, but only from version 6 on. I must have misremembered it as paid because it was something we didn't have, and then later we did.