Subj : Files on LAN.
To   : Gerald Miller
From : Bj”rn Felten
Date : Sun Jul 18 2004 10:28 pm

 GM> Yes, in the SYSTEM.INI file, there is a "device=vshare.386" directive.

   Ah, yes, that's the bugger. Now I remember MS used to call all those new 
guys *.386. You may try loading it already in your config.sys and disable it in 
your system.ini, and see what happens.

 GM> copy all the directories / files from the Fidonet/DOS box to the XPP
 GM> machine (over the network, for backup to CD) _WITHOUT_ SHARE.EXE being
 GM> installed.

   Well, share/vshare were only there to prevent you from writing to a file 
that's already opened by another application, so just a simple copy should not 
require share to be installed -- moving the files probably would have caused 
some problems.

 GM> I suspect that I really don't require share to be installed, but I would
 GM> also be willing to listen to someone who can help me resolve the file
 GM> locking problems I receive with share when I'm not using WfW...

   If, as I said, two different applications are trying to access the same 
file, in write-enable mode, you are likely to end up in a dead-lock situation. 
Remember that the old operating system, you are using, was not originally 
intended to be used in a multi-user environment. Share/vshare was a rather 
pathetic attempt to solve the different conflicts in such a setup.

   Most network packages in those days, such as Lantastic, Novell and other, 
had to write their own variants of share, to get file sharing to work at least 
reasonably safe, but whenever MS came out with a new idea of their own, 
backward compatibility went down the drains and the rest of the companies had 
to start all over again. I bet the same goes for your 4dos...

---
 * Origin: news://felten.dyndns.org (2:203/2)

.