I just got this IBM 755c laptop configured to have 600k of free memory and then everything has gone into the toilet when I turned on the laptop this morning. For example running any DJGPP games (tried Doom, doom2, duke3d, descent) all give an error "DOS/16M error [2]: not a DOS/16M executable". Other non DJGPP games still work fine.
I stripped my config files down to a bare minimum:
Even with the stripped down config it says I have 0 available upper memory. Whatever is causing that is probably causing all these other problems.
In the bios was a test program that tests the system board, ram, display, hard drive, etc. It reported no errors.
I also tried both C:\DOS\EMM386.exe and C:\WINDOWS\EMM386.exe. Both load and appear to be working, meaning I can run it from the command prompt and it says it is active.
I tried memmaker and it says MemMaker cannot continue, No upper memory was created.
Update:
I noticed in MSD that anything I include, like I=B000-B7FF I=E000-E5FF, snows up as "RAM" instead of available, used UMB or free UMB.
So next what I did was startup with F5 to skip autoexec and config.sys. I ran MSD again and can see that B000-B7FF is available along with C000-DFFF, E000-EFFF is marked possibly available. Now I reboot and look again and those errors are marked as RAM, except for D000-DFFF which is correctly marked as Page.
Update 2:
I wanted to test if my hard drive or files have gone bad. I created a dos boot disk from another working dos 6.22 machine and I included himem.sys and emm386.exe. First I tried "emm386.exe ram" and in MSD B800-CFFF was marked as RAM. Next I added I=E000-E7FF X=C000-CFFF. After rebooting MSD shows C000-CFFF empty and E000-E7FF marked as RAM.
Why is emm386 incorrectly marking things as RAM instead of UMB?
I stripped my config files down to a bare minimum:
Code:
config.sys:
DEVICE\C:\DOS\SETVER.EXE
DOS=HIGH,UMB
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE RAM I=B000-B7FF I-E000-E5FF I=C800-CFFF
FILES=30
LASTDRIVE=Z
STACKS=9,256
DEVICEHIGH=C:\IBMVESA\VESA.EXE
DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS
autoexec.bat:
C:\DOS\SMARTDRV.EXE /X
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\DOS
SET TEMP=C:\DOS
In the bios was a test program that tests the system board, ram, display, hard drive, etc. It reported no errors.
I also tried both C:\DOS\EMM386.exe and C:\WINDOWS\EMM386.exe. Both load and appear to be working, meaning I can run it from the command prompt and it says it is active.
I tried memmaker and it says MemMaker cannot continue, No upper memory was created.
Update:
I noticed in MSD that anything I include, like I=B000-B7FF I=E000-E5FF, snows up as "RAM" instead of available, used UMB or free UMB.
So next what I did was startup with F5 to skip autoexec and config.sys. I ran MSD again and can see that B000-B7FF is available along with C000-DFFF, E000-EFFF is marked possibly available. Now I reboot and look again and those errors are marked as RAM, except for D000-DFFF which is correctly marked as Page.
Update 2:
I wanted to test if my hard drive or files have gone bad. I created a dos boot disk from another working dos 6.22 machine and I included himem.sys and emm386.exe. First I tried "emm386.exe ram" and in MSD B800-CFFF was marked as RAM. Next I added I=E000-E7FF X=C000-CFFF. After rebooting MSD shows C000-CFFF empty and E000-E7FF marked as RAM.
Why is emm386 incorrectly marking things as RAM instead of UMB?
Last edited: