Mail Archives: djgpp/1996/05/04/14:18:22
Folks: This is a general question that has me stumped about
the old GO. (No, I can't upgrade to DJGPP V2, altho I *really* like
to,
just for the sake of usg CWDPMI.) I've done all of the setup of
DOS boxes
under Windows 3.1 to get DJGPP *and* EMTEX to work under Windows.
There
are certain limitations (usu due to extended memory apparently
getting
fragmented after awhile, so I shut down the DOS window and re-load
it) but
I can still work.
However, a small weirdie just cropped up and every time it
does
it leaves me clueless, bec it defies what I *thought* I knew about
GO. I wanted to setup all of my DOS box .PIFs to be able to run
DJGPP
executables, specifically GZIP386. Ok, I setup the .PIF to alloc 2
MB
XMS req'd w/ a 4 MB XMS limit. Shud be enuf, right ? Wrong. Now,
GZIP386 reports the CPU is REAL or V86 mode (just as it would under
plain DOS) and won't load at all ! I'm not sure what I've changed
about
my system to make GO behave this way and to complicate matters, I
can't
immediately reload DJGPP on the system, to thoroughly debug this
anomaly.
This is the EMM386 driver line from my CONFIG.SYS:
EMM386.EXE NOEMS I=EE00-EFFF
1) It *was* my understanding that this setting prevents GO
from
getting VCPI memory at all, so one must run DJGPP V1 apps from
inside
a properly config'd DOS box under Windows. Correct ? Otherwise, GO
will bitch about being in Real/V86 mode.
2) Besides getting DJGPP V2 or another memory manager, is
there
a way to config EMM386 so that it will reliably give GO the PM
memory
it wants in DOS *and* Windows ?
=====================================================================
==
The continued survival of the human race, despite its own
stupidity,
is the strongest argument for the existence of a benevolent God.
=====================================================================
==
- Raw text -