INT 6
in the Link Driver section of the NET.CFG file. Failure to do this results in the following error message:
"ERROR: "First Mac ODI MLID does not conform to the latest ODI MLID
specification. Call adapter manufacturer and request a newer MLID that
preserves the PIC mask bit."
For a complete discussion of ODINSUP.COM and configuration information for it, please contact Novell.
Windows for Workgroups 3.11
If Windows for Workgroups 3.11 is to be installed, it is recommended that you become familiar with the protocol.ini file, which Windows for Workgroups 3.11 uses for setting up the networking environment. Without the proper entries in this file, Windows for Workgroups 3.11 networking will not function properly. The installer for Windows for Workgroups 3.11 does NOT modify the PROTOCOL.INI or NET.CFG file correctly, which means they must be manually edited. A suggested resource is the Windows for Workgroups 3.1 Resource Kit, available from Microsoft.
MACODI
MACODI.COM is located on the DOS Compatibility Card Installer Disk for DOS Environment.
It is important to note that the Power Macintosh 6100 DOS Compatible does not require any special settings where networking is concerned. The DOS side functions as would any DOS machine using ODI drivers. The only special consideration is to be sure the same protocols are not running in both environments unless tunneling is used.
Binding TCP/IP protocols in NET.CFG
For any TCP/IP setup, you MUST bind IP and ARP in the NET.CFG file. The only notable exception to this that we know of is FTP Software's PC/TCP. If the IP protocol stack you use requires RARP, you MUST bind this also. The entries that bind IP, ARP, and RARP will ALWAYS be the same, unless you are binding to a frame type other than Ethernet_II, which is unlikely. This is the standard IP, ARP, and RARP listing that MUST be in the NET.CFG file for IP support:
Link Driver MACODI
Frame Ethernet_II
Protocol IP 800 Ethernet_II
Protocol ARP 806 Ethernet_II
Protocol RARP 8035 Ethernet_II
As a general rule, do not add PORT or INT statements to the NET.CFG file. ODI drivers do not necessarily require them, and MACODI does not use interrupts. If using odinsup.com for NDIS compatibility, set the INT value to 6.
Example Installation and Settings Files
The following are some examples of networking configurations on the Power Macintosh 6100 DOS Compatible. Note that for all of these installations, Novell Netware was loaded. Also note that defaults were selected in all of these scenarios, which may not be valid for your environment. These are included as examples only. In some situations, the installer may not respond as outlined due to differences in files loaded into memory at the time of the installation. If that occurs, proceed per the software's documentation for using the software with ODI drivers. For the sake of brevity, only portions of files specific to the discussion will be listed. For further help in setting up the various networking environments, please contact the vendor of your network operating system.
InterCon TCP/Connect II for Windows
You must have successfully installed the NetWare client software and Windows before performing this step. "Successfully" means you are able to connect to a NetWare server and you are able to run Windows. Windows comes preinstalled on the Power Macintosh 6100 DOS Compatible. If you are not able to connect to a NetWare server, check your files against those listed above. Make sure all of the programs needed (called) are in the proper location. Also, make sure you don't have networking software loaded on the Macintosh that would cause a conflict, such as MacIPX. Once you have successfully connected to a server, follow these steps to load InterCon's TCP/Connect II for Windows. Again, only the steps that deviate from standard installations will be thoroughly outlined. Please note that for this installation, Windows for Workgroups 3.11 was installed.
Before beginning the installation, you will need to have the following information:
IP ADDRESS:
SUB-NET MASK:
DEFAULT ROUTER IP ADDRESS:
DOMAIN NAME:
DOMAIN NAME SERVER IP ADDRESS:
(If DNS services will be used)
2. Listed below is the NET.CFG file for TCP/Connect support. Notice that IPX is also loaded, set for 802.2 frame type. Only networking specific entries are listed in the AUTOEXEC.BAT. Note the Windows for Workgroups 3.11 entries in the AUTOEXEC.BAT are not listed, as they aren't modified by the InterCon installer.
Link Driver MACODI
Frame Ethernet_802.2
Frame Ethernet_802.3
Frame Ethernet_SNAP
Frame Ethernet_II
PROTOCOL IPX E0 ETHERNET_802.2
PROTOCOL IP 800 ETHERNET_II
PROTOCOL ARP 806 ETHERNET_II
PROTOCOL RARP 8035 ETHERNET_II
LINK SUPPORT
Buffers 8 1600
MemPool 4095
AUTOEXEC.BAT
C:\\NWCLIENT\\LSL.COM
C:\\NWCLIENT\\MACODI.COM
C:\\NWCLIENT\\IPXODI.COM
C:\\TCPCONN\\ODIPKT.COM 3 107
For further help with installing InterCon TCP/Connect II for Windows, please call InterCon.
Description of Files
C:\\NWCLIENT\\LSL.COM
-------------------
Link support layer driver. Supplied by Novell client software
C:\\NWCLIENT\\MACODI.COM
----------------------
Network interface card driver. Supplied by Apple.
C:\\NWCLIENT\\IPXODI.COM
----------------------
IPX Protocol stack layer. Supplied by Novell client software
C:\\TCPCONN\\ODIPKT.COM 3 107
---------------------------
ODI Packet driver. The first number selects the frame type from the entries in the net.cfg file. The first frame listed in the net.cfg is considered 0. Since we are using Ethernet_II, and it is the last of 4 frame types specified in the net.cfg file, this number is 3 in this example. The second number is the "line number" and should always be set to 107 for Ethernet. Supplied by InterCon software.