Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!news.cs.indiana.edu!maytag!xenitec!geoffw
From: geoffw@xenitec.on.ca (Geoffrey Welsh)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Problems right off the bat
Summary: Don't worry, be happy
Message-ID: <1991May27.145315.18790@xenitec.on.ca>
Date: 27 May 91 14:53:15 GMT
References: <1991May23.203923.4683@cunixf.cc.columbia.edu>
Organization: Xenitec Consulting Services, Kitchener, ON, CANADA
Lines: 28

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).

   That sounds strange (Manifest *should* be able to determine DOS
version nuumber accurately), but I doubt that it has any reall effect.

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

   DOS 4.0x (and 5.0) use a different structure for disk buffers,
so the Quarterdeck program to increase buffers is incompatible.
You may wish to use the DOS 4.0x BUFFERS parameter that puts the
buffers into expanded (or was it extended?) memory.

   This *should* be documented in the QEMM386 or DV386 manual.

>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?)

   Geoff