Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpfcso!hpldola!ppa
From: ppa@hpldola.HP.COM (Paul Austgen)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DESQview 386 problem
Message-ID: <11250145@hpldola.HP.COM>
Date: 9 Jul 90 21:26:43 GMT
References: <268acbc5-65comp.sys.ibm.pc@oneb>
Organization: HP Elec. Design Div. -ColoSpgs
Lines: 17

> / hpldola:comp.sys.ibm.pc / mlord@bwdls58.bnr.ca (Mark Lord) /  1:48 pm  Jul  5, 1990 /
> In article <11250142@hpldola.HP.COM> ppa@hpldola.HP.COM (Paul Austgen) writes:
> 
> 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.
> 
My point was, which I didn't get across very well,  that
OPTIMIZE isn't a very good thing to use at all.  I recommend
running it once to give one an idea what it is trying to do, and to
get the syntax examples.  Then, start with a clean file, and add
your own so you have things under control.  Just jamming in a RAM
statement as OPTIMIZE does is just not elegant enough.  Also, it
messed up my Prompt declaration.  The deal is that the program is
trying to edit an ascii file without human intervention.  Just
too many factors to be likely to work correctly.