>>>>We've had problems in the past with Client32 (Novell), but using the "Microsoft Client for Netware" everything works great (over three years now). Having used both NT and Netware 4.x, I prefer Netware (very stable).
>>>
>>>That's what I'm using. However, the company I work for is rather large and not having a single standard really makes support difficult for our network people.
>>>
>>>BTW, I find Netware 4.x/Client 32 too "aggressive". It wants things setup a certain way. For example, until I got rid of it, it insisted on attaching to a server for my G: drive. Very annoying.
>>
>>I haven't used Client32 in about 3 years, but I understand it's much improved. Frankly, it would have to be! 8^)
>
>Oh yes. If he hasn't yet replied to this thread, wait'll Ed Rauh tells you what he thinks.

I hadn't, but it boils down to:

(1) The combination of NW 4.x and the Novell Client32 software has been the most problematic of the NOS combinations for database applications I've worked on where file server services were involved. I can't count the number of times Novell has 'fixed' problems involving Client32 and NW 4.x...NOT!

(2) Uninstalling the Client32 stuff doesn't work reliably - it's usually easier to reinstall the operating system from scratch if you want to remove it. I don't have this problem adding/removing Microsoft's client software.

(3) If you code to the NetWare API using Novell's tools, you're stuck with Client32. Three guesses why I don't use Novell's API...