Scott Parks wrote in a message to Mike Bilow:
 MB> As for that error message from Novell Client 32, I would
 MB> guess that either you did not install it correctly or your
 MB> registry is munged.  You must have Windows 95 Service Pack 1
 MB> installed if you are not using OSR2.  If prompted during the
 MB> installation of Novell Client 32 to replace NDIS with ODI
 MB> drivers, then you should elect to do so.
 SP> They are all OSR2 and I'll take a closer look when
 SP> reinstalling Client 32 today.  Your suggestion that the
 SP> registry might be  corrupted may be the answer for 2 labs of
 SP> computers.  Thats the drawback to using a program like Ghost
 SP> to clone workstations. If you get one bad one ... you
 SP> suddenly have a room full of them. 
I've used Novell Client 32 on OSR2 very widely.  I have noticed that, on 
OSR2, sometimes the installation will fail out with a bizarre error message.  
However, restarting the installation from that point has always succeeded, so 
we have never really bothered to investigate this further.
It may be worth mentioning that we usually do our Novell Client 32 
installations over the wire, using the Microsoft Client for NetWare as a kind 
of boot loader.  Our preferred workstation at the moment is the IBM PC300PL, 
which comes with a built-in 10/100 Ethernet connector.  We simply install 
Windows 95 on the defaults -- the machines have a self-installing copy of 
OSR2 when they arrive from IBM -- and allow the Microsoft Client for NetWare 
to be installed.  We then log onto the network where the Novell Client 32 has 
been lodged, and run its SETUP program across the wire.
 
-- Mike
--- 
---------------