Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!VMS.HUJI.AC.IL!gilf
From: gilf@VMS.HUJI.AC.IL (GIL FREUND)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Problems right off the bat
Message-ID: <31MAY91095943@vms.huji.ac.il>
Date: 31 May 91 06:59:43 GMT
References: <675432063.11@sunbrk.FidoNet>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: gilf@vms.huji.ac.il
Organization: The Hebrew university of Jerusalem
Lines: 33

In article <675432063.11@sunbrk.FidoNet>, Geoffrey.Welsh@sunbrk.FidoNet.Org (Geoffrey Welsh) writes...
> 
>>3. OPTIMIZE won't put a LOADHI command for Sidekick in my autoexec.  It
>>   made LOADHI commands for my other TSR's but not SK.  I can of course
>>   change the autoexec file myself, but why would OPTIMIZE choke on SK?
> 
>   I never trusted OPTIMIZE anyway, but you can't fault it for
>missing one opportunity.  Perhaps it determined that it was more
>memory-efficient to put other things into high memory and leave
>SK low (perhaps there isn't enough room left in high memory?)
> 
Some (actually most) TSR programs use far mor memory for loading then they
catually use for executing. The best wey to check it would be to start the 
program with loadhi and the /gs (get size) parameter. Example: 
LOADHI /GS SK
The program will then start, and after the execution ends loadhi will report
how much memory the program consumes on execusion, and how much is needs
to remain as a TSR. You will find that some TSR that need only a few k's 
to oparate, need more then 50K to start.
If you'll check each and every TSR and device driver, you are likely to 
find out that some device drivers and TSR are better placed in the begining
of the CONFIG.SYS and AUTOEXEC.BAT as they consume more RAM on execusion, 
yet leave enough high memory for other devices drivers and TSR. Doing 
you own optimizine might give you far more free memory, as OPTIMIZE itself
will not alter the CONFIG.SYS and AUTOEXEC.BAT files beyong adding the 
LOADHI statments.
If you use DESQview, another use for the GS parameter is to see how much
memory a program needs (for the DVP file). Start the program with the 
LOADHI /GS program, and use it as you normally would. When you'll exit is
LOADHI will report the maximum memory used. You can then use that number
in the DVP file.

Gil