Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!clarkson!news.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: RVD (was: PD PC-NFS) Message-ID: Date: 17 Oct 90 20:34:50 GMT References: <9010161443.AA19891@asylum.sf.ca.us> Sender: news@news.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 18 In-Reply-To: romkey@asylum.sf.ca.us's message of 16 Oct 90 21:43:48 GMT Nntp-Posting-Host: image.soe.clarkson.edu In article <9010161443.AA19891@asylum.sf.ca.us> romkey@asylum.sf.ca.us (John Romkey) writes: By the way, RVD is not available for distibrution. It hasn't been in use at MIT for years, so by now it would've suffered a lot of bitrot. I wouldn't be surprised if the sources for it didn't exist anymore. I don't recall it ever being released publically, and it's probably not what you should really be running... What's wrong with RVD? I've got two PCs, one at work, and one at home. I'd to run a little TSR program that acts as a RVD server on each machine, and also a RVD client, so that my D: drive would be my "other" machine. I don't mind at all if I only get read access to the other machine. It seems like RVD would be the perfect protocol to use. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) Russ.Nelson@$315.268.6667 It's better to get mugged than to live a life of fear -- Freeman Dyson