DOS Memory Management
os2museum.com
DOS Memory Management
1–5 of 5 posts
Re: DOS Memory Management
#2Later, V-Com Memory Commander allowed 902 KiB of free conventional memory instead of something like 623 using a number of tricks.
Re: DOS Memory Management
#3AUTOEXEC.BAT & HIMEM.SYS rulers - rise your hand if you liked it: XMS, EMS and all that - what a great time before we had unified mem, right? :-D
LOL
Re: DOS Memory Management
#4AUTOEXEC.BAT & HIMEM.SYS rulers - rise your hand if you liked it: XMS, EMS and all that - what a great time before we had unified mem, right? :-D LOL
From Wikipedia https://en.wikipedia.org/wiki/PC_game>:
>By 1993, PC games required much more memory than other software, often consuming all of conventional memory, while device drivers could go into upper memory with DOS memory managers. Players found modifying `CONFIG.SYS` and `AUTOEXEC.BAT` files for memory management cumbersome and confusing, and each game needed a different configuration. (The game Les Manley in: Lost in L.A. satirizes this by depicting two beautiful women exhaust the hero in bed, by requesting that he again explain the difference between extended and expanded memory.)
Re: DOS Memory Management
#5AUTOEXEC.BAT & HIMEM.SYS rulers - rise your hand if you liked it: XMS, EMS and all that - what a great time before we had unified mem, right? :-D LOL
From Wikipedia https://en.wikipedia.org/wiki/PC_game >: >By 1993, PC games required much more memory than other software, often consuming all of conventional memory, while device drivers could go into upper memory with DOS memory managers. Players found modifying `CONFIG.SYS` and `AUTOEXEC.BAT` files for memory management cumbersome and confusing, and each game needed a different configuration. (The game Les Manley i…