🚀 go-pugleaf

> Is it true that use of this client
> under Win95 will eliminate the need to load the typical drivers
> currently loaded either in Autoexec.bat or with Startnet.bat.  

The client entirely replaces the VLM or NETX client in autoexec.bat or 
startnet.bat.
This only gives you access to the network while in windows 95 however, or 
in DOS boxes within the '95 session.
Using DOS mode bypasses the client as far as I'm aware, so that's the 
only compatibility prob I can see..
Client 32 may give you a few quirky times with '95 at the latest versions 
if you're unlucky, however, it's a MUCH better client...

Rich James

musicman wrote:
> 
> I've been digging around in the Novell site, looking for information
> about the Client 32 for Windows 95.  Is it true that use of this client
> under Win95 will eliminate the need to load the typical drivers
> currently loaded either in Autoexec.bat or with Startnet.bat.  I'm
> specifically referring to lsl, NIC driver, ipxodi and vlm.
> 
> Ken
> 
> --
> **********************************************
> *  Ken Roberts                               *
> *  musicman@netpath.net                      *
> *  http://www.netpath.net/~musicman/ken.htm  *
> **********************************************Generally when using win95 you want to use 32 bit protected mode drivers 
if possible. That means you wouldn't want to use real mode drivers like 
lsl, ipxodi, and vlm along with your nic driver. The win95 disk provides 
the basic novell client stuff to get the basic connection but you would 
want to change to protected mode stuff right away. the microsoft client 
for netware networks works well if you include ms service for nds. I 
found novell's client 32 unstable with some of our programs and a 
really slow proformer. Client 32 does provide an nprinter utility that 
sort of works though.

Jim

mhs@centuryinter.net

musicman wrote:
> 
> I've been digging around in the Novell site, looking for information
> about the Client 32 for Windows 95.  Is it true that use of this client
> under Win95 will eliminate the need to load the typical drivers
> currently loaded either in Autoexec.bat or with Startnet.bat.  I'm
> specifically referring to lsl, NIC driver, ipxodi and vlm.

Yes it's true. Use of Client32 for DOS/Win3.x will also eliminate those
in the DOS environment. Ain't it amazin' what they can do
nowadays...;)-- 

Thomas E. Boismier, MPH <boismier@umich.edu>
Assistant Director, Vestibular Testing Center
Department of Otorhinolaryngology
University of Michigan Hospitals

That's right.  It is completely different.

Once you go and install it, don't play with your Autoexec.bat or
Config.sys.  Those files are there for compatability reasons ONLY, to
support legacy applications (Same thing for the WIN.INI and SYSTEM.INI).

Client32 integrates directly with Windows 95.

My opinion thus far, although I am not an expert on Client 32 (have not
installed or played with it that much so far).  I know that several people
on this newsgroup will have more in-depth opinions on this matter.

musicman <musicman@netpath.net> wrote in article
<32F867D7.66AD@netpath.net>...
> I've been digging around in the Novell site, looking for information
> about the Client 32 for Windows 95.  Is it true that use of this client
> under Win95 will eliminate the need to load the typical drivers
> currently loaded either in Autoexec.bat or with Startnet.bat.  I'm
> specifically referring to lsl, NIC driver, ipxodi and vlm.
> 
> Ken
> 
> -- 
> **********************************************
> *  Ken Roberts                               *
> *  musicman@netpath.net                      *
> *  http://www.netpath.net/~musicman/ken.htm  *
> **********************************************
> 

>if you're unlucky, however, it's a MUCH better client...
>
>Rich James
Why?

Jeroen.