Search results for query: *

I am not sure the answers about everything changing are strictly correct. From the users point of view it can be a seamless transition. We went through the change from Netware 3.11 to Linux a couple of years ago. It isn't a hard process, you just need to be methodical although we did put a Linux...

If the Samba machine is also set as a WINS server it should sort this out itself as you would be using the Windows network names for pinging. At least thats how my network works ... It would also help if the DHCP server was on the linux box rather than the router, your timeout issues should then...

I run MS Works from inside Foxpro DOS on WIN98 using a .wps file on a network drive as follows: !c:\progra~1\msworks\msworks l:\quotes\&qworks..wps and have never had any memory issues. Works starts itself up as a completely separate job in a new window. This seems to work with all the windows...

For Win9x check out the following link. This is a method for setting user login/network variables into the environment. http://www.jsiinc.com/SUBD/tip1700/rh1786.htm You use putinenv to retrieve the data and set into the local environment, then use winset to set into the master windows...