🚀 go-pugleaf

*Theoretically* it should work, meaning the client merely loads the app
into ram from the server instead of its own hd.

However, if that app opens or accesses a file of some kind, and that is
stored on the server as well, say via a mapped drive, old apps don't have
any kind of error to display, they just stop if they can't support more
than a single access and one occurs.

What you have then is basically an app trying to be a client/server app
that doesn't support being one.

If that is your prob, good luck; hacking those dos apps can be a mess, and
seems to be a case-by-case solution when any.

Some don't really support running off a server; they work some because the
redirector tricks them into thinking they're operating locally, net use
lptx \\<printer> being a good illustration of that.

What I recommend is to hate and curse the vendor a whole lot. 
Won't make it work, but can sometimes cleanse the spirit if delivered in a
purging, virulent-enough rant-tone. 

Share.exe is not recommended for use with win95 btw, in case you're
thinking of that.
You'll note it isn't in dos 7.x, and setup rems it out if it finds it,
along with deleting certain other dos apps right out of the c:\dos dir and
remming others.


-- 
All this and no job
Leave nospam in Reply To. Yes, works.

: This is serving about 15 clients all running either Windows95\98 or
: basic dos. I have to run a dos based program from the server on all the
: machines. This works fine until two users use the same program at the
: same time, if this is done the program simpley hangs in dos. I think it
: is that two or more cant share or operate the program at the same time.
: I have tried installing "share.exe" on all the dos systems but with no
: success.