Re: EMM386 not installed - protected mode software already running.

[Steve Cohen <stevecoh1@comcast.net>]

On 10/19/2010 10:55 AM, Mike McCarty wrote:
> Steve Cohen wrote:
>> More on the "Hoo Boy this is going to be interesting" front:
>
> [...]
>
>> DEVICE=C:\DOS\EMM386.EXE frame=none x=C000-C7FF x=E000-E7FF [Y,N]?Y
>> EMM386 not installed - protected mode software already running.
>>
>> What does this mean? What protected mode software is already running?
>
> None. The environment of DOSEMU provides a DPMI w/o having to
> load a driver, so it has the same effect as though a driver
> were loaded, however.
>
> Mike

OK, trying to wrap my head around this though the 20-year fog.  EMS, 
XMS, UMB, DPMI.  Yecch.

I've tried commenting out the
	DEVICE=C:\DOS\EMM386.EXE frame=none x=C000-C7FF x=E000-E7FF
line.  This gives me the "No UMBs" error on the first devicehigh= call

As can be seen from my earlier posts, this application, as designed, 
made use of HIMEM.SYS, EMM386.EXE, etc.  This does not appear to be 
compatible with DOSEMU as configured out of the box.

Looking for opinions here.  Would you think I am best off trying start 
from Freedos and tweak memory as needed or from MS-DOS?  If I use MS-DOS 
under DOSEMU what is the solution to add UMBs?  Or, am I best advised to 
avoid all this UMB and devicehigh stuff and just try to load them 
"normally"?

Here is the config.sys I am trying to load:

BREAK=OFF
FILES=30
BUFFERS=30
STACKS=9,256
DOS=HIGH,UMB
LASTDRIVE=V
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE frame=none x=C000-C7FF x=E000-E7FF
  DEVICEHIGH=C:\DOS\SETVER.EXE
  SHELL=c:\command.com c:\dos\ /E:1024 /P
  DEVICEHIGH=C:\NFS\PCNFS.SYS
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\LANMAN\PROTMAN.SYS /I:C:\LANMAN
  REM INTEL ETHERPRO16
DEVICEHIGH=C:\LANMAN\EXP16.DOS
DEVICE=C:\LANMAN\NFS-NDIS.SYS