Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!cbfsb!cbnewsb.cb.att.com!feg
From: feg@cbnewsb.cb.att.com (forrest.e.gehrke)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Problems right off the bat
Message-ID: <1991May24.124648.5430@cbfsb.att.com>
Date: 24 May 91 12:46:48 GMT
References: <1991May23.203923.4683@cunixf.cc.columbia.edu>
Sender: news@cbfsb.att.com
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 34

In article <1991May23.203923.4683@cunixf.cc.columbia.edu> stone@cunixb.cc.columbia.edu (Glenn Stone) writes:
>I just got DV386 and have encountered these problems with it and the 
>programs bundled with it:
>
>1. MANIFEST reports DOS 4.00 although DOS's VER reports 4.01 (it IS 4.01).
>

Because when MFT looks at the boot record it finds 4.00.  MS never
changed it to 4.01.

>2. BUFFER won't run, saying it needs DOS 2 or 3.
>

You didn't read the manual, old boy.  For msdos 4.+ you use
buffers /x to get QEMM to move them into expanded memory.

>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?
>
Probably because SK is too big to move.  Perhaps if you name it first
in your list of TSR's it will be loaded high, but then some other 
TSR's won't make it.  You may also have to fiddle a bit to create 
the largest possible space for SK to be moved up.  Look the manual 
over to see how this can be done. OPTIMIZE isn't always smart enough 
to handle this kind of problem.  QEMM always wants to place the page 
frame at E000.  You may have to force this elsewhere; I had to force 
it to start at CC00.

Another thing to consider is that more space is needed to load a
TSR than its eventual size (the manual explains this, too).


Forrest Gehrke feg\@dodger.att.com