Path: utzoo!utgpu!cunews!bcars8!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DESQview 386 problem
Message-ID: <3731@bwdls58.UUCP>
Date: 5 Jul 90 19:48:41 GMT
References: <268acbc5-65comp.sys.ibm.pc@oneb> <11250142@hpldola.HP.COM>
Sender: mlord@bwdls58.UUCP
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 15

In article <11250142@hpldola.HP.COM> ppa@hpldola.HP.COM (Paul Austgen) writes:
>Rather than using the RAM statement raw, you have to decide where
>the memory conflicts are.  I used Manifest, and it even missed a
>conflict.  Get rid of the RAM statement, and use RAM= with trial
>and error.  (Or use EXCLUDE=).   I have shadow ram, and I let the
>machine allocate it, rather than shutting it off.  

Beware of using multiple RAM= statements when using the OPTIMIZE thingie.
It has trouble with this, but fails to tell you about it!

Instead, use RAM by itself, along with INCLUDE= and EXCLUDE= as appropriate.

 ___Mark S. Lord______________________________________________
| ..uunet!bnrgate!bmerh614!mlord | These are my opinions only.|
|________________________________|____________________________|