On my P3 rig with 256 MB of RAM, if I start Wolfenstein 3D up, it doesn't show the full RAM on the main section. In my config.sys I have himem.sys and emm386 with the RAM switch loaded.
Why would anybody care about that?
https://cloakedthargoid.wordpress.com/ - Random content on hardware, software, games and toys
wrote:Why would anybody care about that?
To show off mah sexy expensive PC100 RAM 😜
Wolf3D is a 286 application. A 286 can only support 16 MB of memory max.
So it probably simply cannot determine the actual amount of memory. Does it happen to report 16 MB?
It could also be using the XMS 2.0 API for himem.sys, which is limited to 64 MB.
It only goes up to 288 (second highest) out of the 320 (highest) in KB I assume.
wrote:On my P3 rig with 256 MB of RAM, if I start Wolfenstein 3D up, it doesn't show the full RAM on the main section. In my config.sys I have himem.sys and emm386 with the RAM switch loaded.
What else is loaded?
According to Wolfenstein website, it needs 570KB to work properly, and you can check the free memory with "MEM /C" command.
wrote:wrote:On my P3 rig with 256 MB of RAM, if I start Wolfenstein 3D up, it doesn't show the full RAM on the main section. In my config.sys I have himem.sys and emm386 with the RAM switch loaded.
What else is loaded?
According to Wolfenstein website, it needs 570KB to work properly, and you can check the free memory with "MEM /C" command.
AWE64 Gold DOS drivers and default CD Drive drivers
wrote:AWE64 Gold DOS drivers and default CD Drive drivers
Well that explains it then. Of course I still don't know if you have loaded those drivers into conventional memory, high memory area (HMA) or upper memory blocks (UMB).
If it works, don't do anything.
If it does not work, don't load CD drivers, or load them into HMA or UMB.
Yeah, the CD drivers are loaded into high memory.
AWE64 does not have to use any memory. Just run CTCM and AWEUTIL /S.
Nothing stays resident, but you don't get GM or MT32 emulation this way.
Show your config.sys and autoexec.bat
Autoexec.bat is nothing but AWE64 Gold with CTCM and Aweutil /s, mouse.com, and MSCDEX.EXE.
Config.sys:
DOS=HIGH,UMB
DEVICE=C:\Windows\HIMEM.SYS
DEVICE=C:\Windows\EMM386.EXE RAM
DEVICEHIGH=oakcdrom.sys /D:mscd001
Autoexec.bat is nothing but AWE64 Gold with CTCM and Aweutil /s, mouse.com, and MSCDEX.EXE.
See, this is why you should just paste the file instead of describing it.
There are details not described. For example, mouse and mscdex should be loaded with lh.
lh mouse.com
lh mscdex.exe /params
Also, EMM386.EXE NOEMS should give you more memory. It disables EMS, which is rarely needed.
What version of DOS and Windows is it? Are you running the game from Windows?
wrote:It only goes up to 288 (second highest) out of the 320 (highest) in KB I assume.
That is quite standard avail. memory. Don't bother with it.
Requests are also possible... /msg kixs
wrote:See, this is why you should just paste the file instead of describing it. There are details not described. For example, mouse an […]
Autoexec.bat is nothing but AWE64 Gold with CTCM and Aweutil /s, mouse.com, and MSCDEX.EXE.
See, this is why you should just paste the file instead of describing it.
There are details not described. For example, mouse and mscdex should be loaded with lh.lh mouse.com
lh mscdex.exe /paramsAlso, EMM386.EXE NOEMS should give you more memory. It disables EMS, which is rarely needed.
What version of DOS and Windows is it? Are you running the game from Windows?
DOS, and i'm just gonna leave it.
