Date:	Thu, 21 May 92 20:49:58 +0200
From:	Gordon Beaton <gordon AT Minsk DOT DoCS DOT UU DOT SE>
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	GCC with DOS
Status:	O

Actually, *I* don't feel that I have a problem with my configuration.
GCC *works* on my system - Compaq 386/20e, 4MB, 160MB, 
Compaq DOS 5.0, 4DOS 4.0. GCC 1.06 (version of April 18, 1992).

But since I've gotten a few responses regarding my earlier
comment, I will try to clarify what I meant.

Firstly:

Thomas Greve writes:

> - (as stated before:) EMS emulators coexist with go32, *only* if you
>   omit the noems switch, not `even'. 

Sorry, 'even' was a mistake, I had edited the text, and the word got left
behind when it should have been removed.


OK.

The following works for me:

shell=c:\dos\4dos.com c:\dos /e:1600 /p
country 046,437,c:\dos\country.sys
device=d:\win\himem.sys
dos=high
device=c:\dos\ansi.sys
files=50
buffers=30
switches=/W

(shell=command.com works too)

The only resident program I run is keyb.com.

However, if I add one of the following lines I get the v86 error from
go32 (note the absence of 'noems' or 'ram'):

device=cemm.exe
-or-
device=emm386.exe

Info Spotter 2.50 reports that the processor is now in protected
mode, and go32 reports the same thing.

Now if I change the shell back to command.com, it runs in real mode, and
go32 is happy.

Until, that is, I run 4Dos.com, after which go32 complains and
InfoSpotter once again tells me that the processor is in protected
mode. Even AFTER EXITING 4Dos.com.

This has been a short summary of what I learned while trying (and
eventually succeeding) to get djgpp to run, and should explain my
earlier answer to Apollo Wong - dump the emm driver.

And although it probably doesn't belong in this forum, if there's 
anyone who can explain why the mere presence of emm386 (or Compaq's 
cemm.exe) causes 4dos to behave this way, I would be interested to know.

Gordon

- Raw text -