Xref: utzoo comp.os.msdos.misc:1932 comp.os.msdos.desqview:27
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!news.nd.edu!news.cs.indiana.edu!maytag!watstat.waterloo.edu!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.os.msdos.misc,comp.os.msdos.desqview
Subject: Re: FASTOPEN  (was Another QEMM problem.)
Message-ID: <1991May6.131604.16735@maytag.waterloo.edu>
Date: 6 May 91 13:16:04 GMT
Article-I.D.: maytag.1991May6.131604.16735
References: <9043@crash.cts.com> <1991May5.194030.2078@clmqt.marquette.Mi.US> <1991May6.080323.6898@msuinfo.cl.msu.edu>
Sender: news@maytag.waterloo.edu (News Owner)
Followup-To: comp.os.msdos.misc
Organization: University of Waterloo
Lines: 14

In article <1991May6.080323.6898@msuinfo.cl.msu.edu> draper@buster.cps.msu.edu (Patrick J Draper) writes:
>
>I'd say that the man was right on when he said to stay away from
>fastopen, but you are right about share. It causes problems as well, and
>if you don't use software that handles the disk using FCB's, you're OK
>without it.

Exactly what uses of share cause problems?  Command.com uses FCB's when it
deletes files; is this safe without share? 

Duncan Murdoch

P.S. I've set followups to comp.os.msdos.misc; this doesn't have anything to
do with DV any more.