How do I get rid of the ODI driver default so I can use NDIS drivers?
Articles and Tips: qna
01 Apr 1998
Q.
Dear Ab-end: I'm having some problems trying to remove support for ODI drivers with NetWare Client 32 and ODINSUP. I tried deleting the network adapter from the Windows Device Manager, but the ODI drivers keep coming back again when I reinstall Client 32. How do I get rid of the ODI driver default so I can use NDIS drivers?
Struggling in Stockholm
A.
Dear Struggling: There have been problems with earlier versions of the Client 32 Uninstall program (UNC32.EXE) leaving old settings in the registry, particularly ODI as the default setting. The version of UNC32.EXE that comes with IntranetWare Client 32 version 2.2 does a good job of cleaning out the registry of any Client 32 settings. Download this Client 32 version from http://support.novell.com. Then run UNC32.EXE before rebooting the workstation.
There is an alternative manual method that is rather long, but it is effective. First, Alt+click on the Network Neighborhood icon on your desktop. Highlight and remove Novell ODINSUP and the ODI network adapter driver, then click OK and answer No to the question "Do you want to restart your computer now?" Next, go into the Windows Explorer and delete the .INF files from NE100.INF up through NE3200.INF (up to but excluding the NET.INF file). Then find the OCE2XODI..INF file and delete all of the files that have ODI in them, up to the OEM*.INF file.
Next, run REGEDIT (Run | regedit | OK) and search (Ctrl+F) for ODINSUP. You should find the value ODINSUP.INF, and next to it there should be two other values: ODILOAD.VXD and ODINSUP.SYS. Delete all three value listings from the registry. Then press F3 to ensure there are no other listings of ODINSUP in the registry. When you press F3, you should see the message "Finished searching through the registry." If you find other ODINSUP values, it means you didn't remove both Novell ODINSUP and the ODI network adapter driver from the Network Properties page.
Now reboot your workstation (sometimes it's better to turn off the workstation and turn it back on to ensure that all the new settings take hold). As the workstation reboots, you should see a message that Windows 95 has found a new device and will add an NDIS driver to the network adapter. Or you can select all devices and ensure that an NDIS driver gets installed. At this point you may have to use the Windows 95 CAB files to install the proper NDIS driver for the discovered network adapter. As a word of warning, make sure you have local access to the Windows 95 CABs and the Client 32 installation files. Otherwise you will be stuck when you reboot.
As the rebooting workstation redetects the network adapter, it will automatically load the Client 32 install program--you shouldn't have to run the Client 32 setup manually at this point. But if you do have to reinstall Client 32, be sure to uncheck the "Update NDIS drivers with ODI drivers automatically if available" option. As you start the Client 32 installation, you can also put a "/n" parameter after SETUP command, such as Run | d:\products\win95\setup.exe /n. The "/n" parameter ensures that the NDIS drivers are used as the default instead of ODI drivers.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.