Hi Brenton



 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.



 BV> Can't say that I have noticed that. I've been using WfW 3.11 for

 BV> about 6 or 9 months now and I haven't had a problem with it. Nor

 BV> have I noticed any problem with a DOS window inheriting the parents

 BV> DOS environment as you have. I've just had a quick look and I can't

 BV> see anything strange or custom about my setup in this regard either.



We have two machines doing it, and a third that doesn't, but I

haven't had time to play with them yet. Gotta be something silly.



 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.



 BV> I will send you the latest Novell DOS/Win driver support disks

 BV> sometime next week. They should help. I've installed a few Novell

 BV> WfW networks over the last few months and the trick seems to be to

 BV> install WfW for NO network support, then install the Novell drivers.



Sounds right.



 BV> You need to be using the diskset which is called "Client for DOS"

 BV> and you need the "Client for MS-Windows" diskette. If you
have them,

 BV> then give it a whirl, otherwise, I'll send them up sometime this week.



Never seen a "Client for Win" disk. That would be appreciated; ta.



 BV> BTW, you could check this with Alan Whiteman, if I remember correctly

 BV> he was attempting to become a Novell wizard.



Haven't seen him in the last few months. That's probably why 



Cheers





--- PPoint 1.88