if have got a hp-omnibook-4150 and want to run dos7.0 with emm386. When starting emm386.exe the system dies. I think i have to exclude some memory areas, but which?
I tried x=c800-dfff (i have to do this on my thinkpad) but it does not help.
You could try this (Only if yourvideo card is 8 mg or less): DEVICE=C:\WINDOWS\EMM386.EXE X=C000-C7FF I=EE00-EFFF I=E000-ECFF I=B000-B7FF M3 A=64 H=128 D=256 RAM AUTO ALTBOOT
Have you ever tryed anternatives to emm386. I have 623 kb with everything high. The files you would need are HIRAM.EXE and UMBPCI.SYS. I believe these will work on Dos 5 on up. USBPCI.SYS only uses 240 byts (ok). It does have one draw back. If your soundcard is PCI based it won't work because it needs EMM386. These are also others: CTMOUSE.EXE uses only 3k SHSUCDX.exe uses only 13k (CDROM replacement for MSCDEX.EXE (48k)) VIDE-CDD.sys uses only 5k (Universal CDROM driver)
So even if you use EMM386 consider using alternative drivers to boost cmem. If you want these files I will send them anong with their respective command switches and my autoexec.bat and config.sys.
if have got a hp-omnibook-4150 and want to run dos7.0 with emm386. When starting emm386.exe the system dies. I think i have to exclude some memory areas, but which?
I tried x=c800-dfff (i have to do this on my thinkpad) but it does not help.
HIRAM.EXE is useless here is because you load the drivers in a wrong order. HIMEM.SYS is loaded in low memory. Then HIRAM.EXE searches for memory but doesn't find anything and ends. Then UMBPCI enables the memory that is intended as shadow RAM and installs a HIMEM extension with the function 'request XMS UMB'. When the first devicehigh comes, DOS calls 'request XMS UMB' and grabs alls XMS UMBs and makes DOS UMBs from it.
Load UMBPCI first. It will enable the memory and unload itself. Load HIRAM then. It will find the memory enabled by UMBPCI and install a small HIMEM 2.0 handler with the function 'request XMS UMB'. You can load HIMEM.SYS high then with DEVICEHIGH=C:\WINDOWS\HIMEM.SYS. The 'devicehigh' causes DOS to call 'request XMS UMB' to get all XMS UMB and it makes the well known DOS UMBs from it. And it loads high HIMEM.SYS. As soon as DOS called 'request XMS UMB' HIRAM.EXE unloads itself because it's not longer needed. When HIMEM.SYS loads a little bit later, it checks first if there is already a HIMEM driver. Because HIRAM.EXE unloaded itself before, everything is good and you have loaded high HIMEM.SYS.
> HIRAM.EXE is useless here is because you load the drivers in a > wrong order. HIMEM.SYS is loaded in low memory. Then HIRAM.EXE > searches for memory but doesn't find anything and ends. Then > UMBPCI enables the memory that is intended as shadow RAM and > installs a HIMEM extension with the function 'request XMS UMB'. > When the first devicehigh comes, DOS calls 'request XMS UMB' > and grabs alls XMS UMBs and makes DOS UMBs from it.
> Load UMBPCI first. It will enable the memory and unload itself. Load > HIRAM then. It will find the memory enabled by UMBPCI and install > a small HIMEM 2.0 handler with the function 'request XMS UMB'. You can > load HIMEM.SYS high then with DEVICEHIGH=C:\WINDOWS\HIMEM.SYS. > The 'devicehigh' causes DOS to call 'request XMS UMB' to get all > XMS UMB and it makes the well known DOS UMBs from it. And it loads > high HIMEM.SYS. As soon as DOS called 'request XMS UMB' HIRAM.EXE > unloads itself because it's not longer needed. When HIMEM.SYS loads > a little bit later, it checks first if there is already a HIMEM driver. > Because HIRAM.EXE unloaded itself before, everything is good and you > have loaded high HIMEM.SYS.
OK Bundy's back> First I want to thank Uwe from Germany. His help was greatly appriciated. Now the results. I have 624k with CDROM and mouse loaded high.
Here's MY CONFIG.SYS: DOS=HIGH,UMB devicehigh=C:\SYSTEM\umbpci.sys DEVICE=C:\SYSTEM\HIRAM.EXE DEVICEHIGH=C:\WINDOWS\HIMEM.SYS
> HIRAM.EXE is useless here is because you load the drivers in a > wrong order. HIMEM.SYS is loaded in low memory. Then HIRAM.EXE > searches for memory but doesn't find anything and ends. Then > UMBPCI enables the memory that is intended as shadow RAM and > installs a HIMEM extension with the function 'request XMS UMB'. > When the first devicehigh comes, DOS calls 'request XMS UMB' > and grabs alls XMS UMBs and makes DOS UMBs from it.
> Load UMBPCI first. It will enable the memory and unload itself. Load > HIRAM then. It will find the memory enabled by UMBPCI and install > a small HIMEM 2.0 handler with the function 'request XMS UMB'. You can > load HIMEM.SYS high then with DEVICEHIGH=C:\WINDOWS\HIMEM.SYS. > The 'devicehigh' causes DOS to call 'request XMS UMB' to get all > XMS UMB and it makes the well known DOS UMBs from it. And it loads > high HIMEM.SYS. As soon as DOS called 'request XMS UMB' HIRAM.EXE > unloads itself because it's not longer needed. When HIMEM.SYS loads > a little bit later, it checks first if there is already a HIMEM driver. > Because HIRAM.EXE unloaded itself before, everything is good and you > have loaded high HIMEM.SYS.
