Hi Roy,

RM> A real gem, innit. Run the MSDos prompt icon, and get a dos box
RM> that inherits none of the parent Dos's environment, specifically no
RM> path. All of the nifty utes that are usually the reason for running
RM> the silly thing vanish in an instant.

Can't say that I have noticed that. I've been using WfW 3.11 for
about 6 or 9 months now and I haven't had a problem with it. Nor
have I noticed any problem with a DOS window inheriting the parents
DOS environment as you have. I've just had a quick look and I can't
see anything strange or custom about my setup in this regard either.

RM> And then there is its network support. Win 3.1 talks to our Novell
RM> network "captured" printers just fine. Win 3.11 freshly installed
RM> can't see network printers past lpt2, and doesn't recognize them as
RM> network printers anyway. Look into the network setup, and under
RM> Novell it asks for a diskful of drivers that we don't have, and
RM> will probably have to buy from Novell.

I will send you the latest Novell DOS/Win driver support disks
sometime next week. They should help. I've installed a few Novell
WfW networks over the last few months and the trick seems to be to
install WfW for NO network support, then install the Novell drivers.

You need to be using the diskset which is called "Client for DOS"
and you need the "Client for MS-Windows" diskette. If you have them,
then give it a whirl, otherwise, I'll send them up sometime this week.

BTW, you could check this with Alan Whiteman, if I remember correctly
he was attempting to become a Novell wizard.

Regards, Brenton
@EOT:

---