Apple PC Compatibility Card 7-inch card - Manual (Page 152)

Using ODI drivers with NDIS compatible protocols
If you will be using ODI drivers with NDIS compatible protocols, you need a
translator file. Microsoft’s NDIS to ODI translator, ODIHLP.EXE, is
automatically installed with Windows for Workgroups 3.11 if you indicate you
will be using ODI drivers.
If you will be using both Novell NetWare and Windows for Workgroups 3.11,
you should use ODIHLP.EXE instead of Novell’s equivalent file,
ODINSUP.COM (included with NetWare).
If you use ODINSUP.COM, you must change the NET.CFG file to specify an
interrupt. Add the statement
INT 6 to the Link Driver section of the
NET.CFG file.
Conserving memory
The line CALL C:\NWCLIENT\STARTNET.BAT in the AUTOEXEC.BAT
file loads four programs into DOS memory—LSL.COM, MACODI.COM,
IPXODI.COM, and VLM.EXE (in this order). To conserve memory in the
lower DOS region, you may wish to edit the STARTNET.BAT file to load
those four programs with the LOADHIGH (LH) command. See your DOS
documentation for more details on manually optimizing DOS memory.
Installing NetBEUI and IPX/SPX in Windows 95
This section describes how to install the NetBEUI and IPX/SPX protocols for
use with an ODI driver in Windows 95. If you are using NDIS 2.0, refer to this
topic in “Installing Protocols for Use With NDIS 2.0” later in this appendix.
1 Install the NetWare client software.
For more information, see “Installing NetWare Client Software” earlier in
this appendix.
2 In Windows 95, click Start, choose Settings, and then choose Control Panel from the
menu that appears.
3 Double-click the Network Icon in the Control Panel.
4 Click Add in the Network Configuration dialog box.
5 Select Adapter Component from the Network Component list, and then click Add.
144 Appendix B