Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!gatech!prism!russ
From: russ@prism.gatech.EDU (Russell Shackelford)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DesqView 386 vs VM/386 comparisson
Summary: hi res bus mouse
Message-ID: <1318@hydra.gatech.EDU>
Date: 1 Aug 89 21:07:31 GMT
References: <3425@titan.camcon.co.uk>
Organization: Georgia Institute of Technology
Lines: 33


>In article <3425@titan.camcon.co.uk>, mrh@camcon.co.uk (Mark Hughes) writes:

[stuff deleted about the responses to query about Desqview386 & VM/386]
 
> The dissatisfied (ex) DV user had a lot of installation problems, failed to
> get DV to work with his Logitech hi-res bus mouse, and got no help from

I have no experience with Desqview support people, mainly because I found
that for me it worked just fine as soon as I fiddled with it as per
instructions in the manual.  The manual's ok, not great, but ok. I imagine
that some people (maybe NOT the one who reported problems) are just 
acclimated to software that just loads and works with no fiddling. I thought
that the required fiddling was relatively straighforward and not too
complicated.

As for the problem with the Logitech hi-res bus mouse, I've got one and
have had no difficulty of any kind using it with DV.  I used one of
the QEMM programs to load mouse.com in hi memory, and I find myself
with MORE of the 640 RAM available than the manual sez I should! (575K).

I like it just fine. Just wish they could squeeze MORE of their stuff 
up high to leave MORE of the 640 available.  Actually, the only place
I need it is with Ventura, so I suppose that I should wish for better
memory management from THOSE folks.


 
-- 
Russell Shackelford
School of Information and Computer Science
Georgia Institute of Technology, Atlanta, GA, 30332
russ@prism.gatech.edu         (404) 834-4759