Installing Client32 over the top of LAN Workplace 5.0 for DOS/Windows
LAN WorkPlace 5 only includes the old VLM client. The newer Client32 has some nice features like using less conventional memory and the ability to login to the network under windows. This page shows the process of installing Client32 over the top of LAN WorkPlace 5.
If you're using a later version of Client32 like v2.71 there isn't really much in this - just make sure you select the TCP/IP stack when installing and the installer will mostly do the right thing.
Screenshots
Freshly booted with LAN WorkPlace 5 stuff running! I've pretty thoroughly tested that LAN WorkPlace stuff works fine so if something is broken when this is over we'll know it was installing Client32 that broke it.
I've got the Client32 installer sitting on my NetWare server. So I'll just login to that and run it from there.
Step 1: Run the Client32 installer!
Hit enter.
Step 2: Ensure at least Novell Client for DOS and TCP/IP protocol stack are selected. If you've got windows 3.1x installed you'll also want to install Novell Client Windows Support. The other stuff is all optional. When done making selections, hit F10.
Step 3: Hit F10 unless you need to change any of this stuff .
Step 4: You probably want DHCP. Hit F10 when done.
Step 5: Select a LAN Driver.
I'm using an AMD PCnet II PCI
Step 6: Selections made - press F10 to continue.
Installation happens!
Step 7: Reboot (Ctrl+Alt+Del)
If, during startup, you get asked if you would like to Load the LAN Support Software [y/n]? choose no.
As is pretty common, the driver complains about the SLOT number not being supplied. If you get this just hit enter.
Note the "The hardware configuration conflicts" in the background.
Booted and the client seems to be working! Now edit C:\novell\client32\startnet.bat.
For some reason the installer has duplicated the network driver. Delete the second copy if this happens.
Then specify the SLOT number to slience those annoying errors (the correct slot number is visible in the background of the error messages). Save the file.
Next open up autoexec.bat and check the LAN WorkPlace BIN directory is on the path. Also check that any references to C:\NET\BIN\STARTNET.BAT are gone. Early versions of Client32 would leave it behind but later versions will do the right thing and replace it with a call to the Client32 version of this batch file. Once autoexec.bat is fixed up and saved (if necessary), reboot.
Booted without errors!
Window integration is working!
And TCP/IP applications from LAN WorkPlace still work too! All done.
Disclaimer & Comments
I'm not a netware expert, don't have any of those fancy novell certifications and have never administred a netware network; I've just played with it at home occasionally since 2004 or so. Email me if you've got any suggestsions or corrections for this page or any extra information you think is worth including here. My address is david at this websites domain name (without the www bit of course).