5 ms·
> Then I learned about boot disks. And with DOS4/GW all problems were gone. Actually, I think MS-DOS 6.0 added CONFIG.SYS boot menus, which made it unnecessary
by DrJokepu 8y ago
> Then I learned about boot disks. And with DOS4/GW all problems were gone.
Actually, I think MS-DOS 6.0 added CONFIG.SYS boot menus, which made it unnecessary to mess around with boot disks (but it didn't help with your dad discovering that you have been messing with the CONFIG.SYS).
- rvanmil 8y agoBoot menus were great, I remember having many of them optimized for different games. Also MEMMAKER.EXE, I spent a lot of time playing with that tool squeezing out the last byte of memory :)
- Keyframe 8y agoHah, I love this. You've reminded me of something I completely forgot it existed. Yet, at that point in time, it was almost everything daily computer usage revolved around.
- gerdesj 8y ago"Actually, I think MS-DOS 6.0 added CONFIG.SYS" No, config.sys was a thing from day 1. Getting the bloody memory setup on MS stuff right was a nightmare and wasted a lot of time.
- akavel 8y ago"...added config.sys boot menus", is what the parent comment says
- gerdesj 8y agoI have an idea about what I'm on about: https://www.novell.com/coolsolutions/tools/14053.html https://www.novell.com/coolsolutions/tools/14053.html (I'm Jon)
- jackfraser 8y agoYeah no I'm sure you do, but you didn't read the comment, he's talking about the native INI-style syntax for boot menus baked into the DOS 6.0 kernel that allows you to specify multiple different CONFIG.SYS sections, and lets you pass an option to your AUTOEXEC.BAT containing the config name so it can finish the job off. A must for anyone who ran a different config for different scenarios. I often ran without CD-ROM drivers to get a couple K more memory for the pickiest programs.
- ChrisClark 8y agoBut not in this case, the menu system was not there on day 1.