www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/08/11/19:09:09

Date: Thu, 11 Aug 94 13:20:32 CDT
From: salbrech AT olympus DOT eecs DOT nwu DOT edu (Steve Albrecht)
To: djgpp AT sun DOT soe DOT clarkson DOT edu, sasbnb AT unx DOT sas DOT com
Subject: Re: pbmplus problem solved.

> There is just one more rather serious problem, however. Using emm386 
> with the noems option, I got 628k free. As soon as I remove the noems
> and rerun memmaker, I get only 505k free. 
 
> Does anybody know how I can have some expanded memory without paying
> such a high price in low memory?
 
>> I had memory problems using windows 3.1 and qemm 6. I ~fixed them by
>> upgrading to dos 6.22, using memmaker to load everything high, and
>> not using qemm.
>> ...
>> To my horror, however, ppmtotga (go32?) now gives a segmentation
>> violation immediately upon execution as does the ppmmerge file which I
>> copied and renamed to make ppmtotga. I then switched to QEMM and
>> commented out himem and emm386, but got the same result which seems to
>> point to dos itself.

I believe there were some patches to QEMM v6, but they have been removed
from ftp.qdeck.com:pub/qemm/patch and replaced by QEMM v7 patches.  Perhaps
Quarterdeck support or someone on the net would provide them to you?  Or you
could consider updating your QEMM to v7.04.  Can't guarantee that this will
fix your (unspecified) "memory problems", but you will get a more aggressive
memory manager out of the deal.

It sounds like you are trying to load more things high than memmaker can
find space for without the big 64K chunk that "noems" gives you.  You might
try specifying the devicehighs and loadhighs in a different order(or
eliminate some!).

You might use a memory mapper(qemm includes one) to see how memmaker has
utilized your upper DOS memory.  This could provide clues on how to reorder
your devicehighs and loadhighs(or convince you to drop memmaker). 

Both QEMM and 386MAX(Qualitas) are smart about reordering your devicehighs
and loadhighs for you so that this sort of problem doesn't happen.  I have
heard that later versions of Memory Commander from V-Communications(Stevens
Creek, CA) also excels in this regard.

Regards,
Steve Albrecht
salbrech AT eecs DOT nwu DOT edu
73657 DOT 1342 AT compuserve DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019