Date:	Thu, 29 Jun 1995 10:34:38 -0400
From:	kagel AT quasar DOT bloomberg DOT com
To:	havemann AT uran DOT informatik DOT uni-bonn DOT de
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: XMS-Memory Probs - go32 eats 26MB
Reply-To:	kagel AT ts1 DOT bloomberg DOT com

   From: havemann AT uran DOT informatik DOT uni-bonn DOT de (Sven A. Havemann)
   Date: Thu, 29 Jun 1995 15:45:23 -0600

   Hi everybody!
   =============

   I have a tentative question:

   We have a P60 with 32MB RAM, go32m3. If we configure XMS to be 26MB, i. e.
   loading himem but NOT emm386, go32 reports these 26MB as available when
   invoked. But if we execute a binary built with gcc263, it reports "Not
   enough memory to run go32" and pretends to have only 420KB XMS left. - And
   it is not possible to execute go32 any further. - If we configure RAM to be
   EMS (emm386) it runs though I heard it's much slower that way. So is there a
   possibility to make go32 run with this much XMS memory? - My own PC has 8MB,
   and it runs fine with 6MB XMS, never had a problem...

   I know there has been an extensive discussion on memory problems >32MB, but
   sorry I didn't follow, so I'd be glad if somebody could give me a hint.

			       Many thanks, 
                               Your's, Sven.
   -


   PS. I DO have faq102, and I will read it this afternoon.
   -

The problem is not the existence or non-existence of XMS per se.  With emm386
loaded you have more DOS memory so GO32 can load.  Without emm386 you are not
using the last 64K of addressable memory for DOS, emm386 maps this to DOS
usable space.  Run "mem /c" and look at the maximum executable size with and
without emm386.  Go32 needs at least 462K, I believe.  I recently loaded
another resident program and could not run go32 because my maximum exe size had
dropped to 435K (with emm386).

-- 
Art S. Kagel, kagel AT ts1 DOT bloomberg DOT com

Variety is the soul of pleasure.  --  Aphra Behn

- Raw text -