Xref: utzoo comp.sys.laptops:2748 comp.os.msdos.desqview:57
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!jarthur!euler.claremont.edu!dhosek
From: dhosek@euler.claremont.edu (Don Hosek)
Newsgroups: comp.sys.laptops,comp.os.msdos.desqview
Subject: Re: DV/QEMM versions 2.31 vs 2.32?
Message-ID: <1991May7.111706.1@euler.claremont.edu>
Date: 7 May 91 18:17:06 GMT
References: <1991May7.123515.12974@news.cs.indiana.edu>
Sender: news@jarthur.Claremont.EDU
Followup-To: comp.sys.laptops
Distribution: na
Organization: Harvey Mudd College
Lines: 32

In article <1991May7.123515.12974@news.cs.indiana.edu>, bobmon@iuvax.cs.indiana.edu (RAMontante) writes:
> Can someone tell me what differences exist betweeen DV386 versions 2.31
> and 2.32, and between QEMM versions 5.11 and 5.12?

It was windows-related patches; viz, if you don't use windows,
don't worry. 
 
> A couple of months ago I asked the net about getting Quarterdeck to
> upgrade my brand-new copy of v2.31 of DV386 (and 5.11 of QEMM) to the
> just-released versions 2.32/5.12, with no response other than "ask
> Quarterdeck".  After *finally* getting through to their BBS and finding
> no information there, I thought I'd find out whether the difference is
> worth the effort of getting through to Quarterdeck --- they aren't
> looking real accessible to an individual without any commercial accounts
> (e.g. Compu$erve).

Actually, the main support conference is releayed through BBSs
all over the place. If you have the Quarterdeck White Papers
(available from simtel20 as qwhite.arc or somesuch) there is a
tech note on what BBSs carry the conference. They're quite
accessible in that way.

-dh

-- 
Don Hosek                  | To retrieve files from ymir via the mailserver,
dhosek@ymir.claremont.edu  | send a message to mailserv@ymir.claremont.edu 
Quixote Digital Typography | with a line saying send [DIRECTORY]FILENAME
714-625-0147               | where DIRECTORY is the FTP directory (sans 
---------------------------+ "anonymous") and FILENAME is the filename, e.g. 
"send [tex]00readme.txt". There is a list of files in each directory under the 
name 00files.txt. Binary files are not available by this technique.