 |
|
|
|
Installing Novell NetWare ODI Drivers
Table of Contents
Open Datalink Interface (ODI) is a driver specification developed by Novell to offer a standard driver interface for Novell NetWare. AMD provides driver support for the following environments:
Novell NetWare 3.1x Novell NetWare 4.x
and AMD provides the following drivers:
NetWare DOS ODI Client NetWare OS/2 ODI Client NetWare Server ODI 3.11 NetWare Server ODI 3.12 NetWare Server ODI 4.x
Installation procedures for each of the above drivers are described in the following sections.
AMD's NetWare DOS ODI client driver may be installed using the automated AMINSTAL utility or manually from the command line prompt. Both methods are explained below.
Note: The user may need to make modifications to Autoexec.bat, using the AMD-supplied sample
autoexec.net file as reference.
Follow the steps listed below:
1. Run the AMINSTAL utility to configure your PCnet adapter card's I/O base address, IRQ channel, and DMA channel.
See the AMINSTAL Utility section for more information
on configuring your PCnet adapter card.
After you have completed the configuration of your PCnet adapter card using the AMINSTAL utility, go to step 2 below to continue.
2. Select the "Continue" button in the "Configuration" dialog box. The "Installation" dialog box will appear.
3. Select the desired PCnet adapter card by highlighting it in the top of the dialog box.
4. Highlight the "Novell ODI DOS Client driver" for the NetWare environment. Change the default path if necessary.
5. Press the "Continue" button to install the driver. The AMINSTAL utility will then copy the driver into the specified directory, create a NET.CFG file in the specified directory, and copy a sample AUTOEXEC.NET file into the specified directory. The AUTOEXEC.NET file contains the following command lines:
LSL PCNTNW IPXODI NETX
The user must copy the following files into the specified directory above:
LSL.COM (Link Support Layer) PCNTNW.COM (AMD NetWare DOS ODI Client driver) IPXODI.COM (An IPX protocol stack file) NETX.EXE (NetWare Shell, used with conventional memory workstations)
The LSL.COM, IPXODI.COM, and NETX.EXE files can be obtained from the Workstation Driver Diskette in the Novell Client Software Package or from
CompuServe. The AMD-supplied client driver file PCNTNW.COM can be
obtained from the DOS ODI directory of the AMD NetWare driver diskette (i.e., a:\novell\wkstn\dosodi).
6. Exit from the AMINSTAL utility when the installation has completed.
The installation of the NetWare DOS ODI client driver is now complete.
Follow the steps listed below:
1. Insert the AMD DOS ODI driver diskette into the floppy drive.
2. Create a subdirectory in your client's main boot drive with the following files:
LSL.COM (Link Support Layer) PCNTNW.COM (AMD Netware DOS ODI Client Driver) IPXODI.COM (An IPX protocol stack file) NETX.EXE (Netware Shell, used with conventional memory workstations)
NET.CFG (Optional (used for configuring options different from the default settings). See Appendix A or the Novell Netware Operating
System Keywords section.)
The NETX.EXE, LSL.COM, and IPXODI.COM files can be obtained from the Workstation Driver Diskette in the Novell Client Software Package or from CompuServe. Copy the AMD-supplied client driver file (PCNTNW.COM) from the DOS ODI directory of the AMD NetWare driver diskette to the appropriate subdirectory. To do this, copy the file using the following path:
A:\NOVELL\WKSTN\DOSODI
3. To manually load these files from the DOS prompt, type the following commands in the given order to initialize DOS ODI driver support and the IPX protocol stack:
LSL.COM Followed by <Enter> PCNTNW.COM Followed by <Enter> IPXODI.COM Followed by <Enter> NETX.EXE Followed by <Enter>
Note: NETX.EXE is compatible with DOS Versions 3.x, 4.x, 5.x, and 6.x.
4. To automatically load these files, use a DOS text editor to create and/or modify an AUTOEXEC.BAT file. Load the files in the
following order:
(1) link support layer, (2) LAN driver, (3) protocol stacks, and (4) the shell. Your AUTOEXEC.BAT file should look similar to the following:
\<subdirectory>\LSL \<subdirectory>\PCNTNW \<subdirectory>\IPXODI \<subdirectory>\NETX
5. When the commands have been added to the AUTOEXEC.BAT file, reboot the workstation. After the commands execute and if a server is present, the workstation will attach to the server and display the server's name.
6. Log onto the network.
The installation of the NetWare DOS ODI client driver is now complete.
Follow the steps listed below:
1. Insert the AMD DOS LAPP driver diskette into the floppy drive.
2. Create a subdirectory in your client's main boot drive with the following files:
LSL.COM (Link Support Layer) PCLAPP.COM (AMD Netware DOS ODI LAPP Driver) IPXODI.COM (An IPX protocol stack file) NETX.EXE (Netware Shell, used with conventional memory workstations)
NET.CFG (Optional (used for configuring options different from the default settings). See Appendix A or the Novell Netware Operating
System Keywords section.)
The NETX.EXE, LSL.COM, and IPXODI.COM files can be obtained
from the Workstation Driver Diskette in the Novell Client Software Package
or from CompuServe. Copy the AMD-supplied client driver file (PCLAPP.COM) from the DOS ODI directory of the AMD NetWare driver diskette to the appropriate subdirectory. To do this, copy the file using the following path:
A:\LAPP\DOSODI
3. To manually load these files from the DOS prompt, type the following commands in the given order to initialize DOS ODI driver support and the IPX protocol stack:
LSL.COM Followed by <Enter> PCLAPP.COM Followed by <Enter> IPXODI.COM Followed by <Enter> NETX.EXE Followed by <Enter>
Note: NETX.EXE is compatible with DOS Versions 3.x, 4.x, 5.x, and 6.x.
4. To automatically load these files, use a DOS text editor to create and/or modify an AUTOEXEC.BAT file. Load the files in the following order: (1)link support layer, (2) LAN driver, (3) protocol stacks, and (4) the shell. Your AUTOEXEC.BAT file should look similar to the following:
\<subdirectory>\LSL \<subdirectory>>\PCLAPP \<subdirectory>\IPXODI \<subdirectory>\NETX
5. When the commands have been added to the AUTOEXEC.BAT file, reboot the workstation. After the commands execute and if a server is present, the workstation will attach to the server and display the server's name.
6. Log onto the network.
The installation of the NetWare DOS ODI LAPP driver is now complete.
Note: The LAPP driver cannot work on a PCnet-ISA board.
To change any default settings after the driver is loaded, the user must create a NET.CFG file on the workstation diskette. See Section 5.6, Novell NetWare Operating System Keywords for more information on valid keywords. See Appendix A for sample NET.CFG files using various keywords.
Note: The Novell Netware ODI DOS installation documentation will provide additional information on installing the DOS ODI driver and using keywords during installation.
To install AMD's OS/2 ODI client driver, the Novell OS/2 Requester should be used.
Load the NetWare OS/2 ODI client driver from the OS/2 CONFIG.SYS file in the sequence given below. See the Novell NetWare Requester OS/2 Installation documentation for more information.
After installing the OS/2 Requester, follow the steps listed below:
1. Using the Netware OS/2 disks provided by Novell, install the Netware OS/2 Requester files on the client. Follow the instructions displayed to configure the Netware OS/2 Requester for a Netware-supported
LAN adapter card.
If the Netware-supported LAN adapter card contains the PCnet adapter
option, select it; otherwise, select any other LAN adapter.
2. Insert the AMD NetWare driver diskette into the floppy drive.
3. Copy the OS/2 ODI driver (PCNTNW.OS2) from the AMD NetWare driver diskette to the C:\NETWARE directory of the boot drive using the following path:
A:\NOVELLl\WKSTN\OS2ODI\PCNTNW.OS2
4. Edit the CONFIG.SYS file and replace the Netware-supported LAN
adapter driver with the name of the AMD OS/2 ODI driver (PCNTNW.OS2). For example:
DEVICE=C:\NETWARE\PCNTNW.OS2
If the Novell OS/2 Requester is used to install the driver, the Requester will automatically make modifications to the CONFIG.SYS
file.
The following is an example of the CONFIG.SYS load sequence for
NetWare 3.12 OS/2 ODI driver support using the IPX protocol stack:
REM --- Netware Requester Statements BEGIN --- SET NWLANGUAGE=ENGLISH DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE REM -- ODI-Driver Files BEGIN -- DEVICE=C:\NETWARE\PCNTNW.OS2 REM DEVICE=C:\NETWARE\ROUTE.SYS REM -- ODI-Driver Files END -- DEVICE=C:\NETWARE\IPX.SYS DEVICE=C:\NETWARE\SPX.SYS RUN=C:\NETWARE\SPDAEMON.EXE DEVICE=C:\NETWARE\NWREQ.SYS IFS=C:\NETWARE\NWIFS.IFS RUN=C:\NETWARE\NWDAEMON.EXE DEVICE=C:\NETWARE\VIPX.SYS DEVICE=C:\NETWARE\VSHELL.SYS GLOBAL REM --- Netware Requester Statements END ---
The default settings may be modified when the driver loads by creating the NET.CFG file. The AMD OS/2 ODI client driver may also be installed to support multiple protocol stacks and Ethernet frame types. Refer to Appendix A for sample NET.CFG files using the optional keywords. Also, refer to the Novell Netware Requester OS/2 Installation
documentation for more information on configuring the NET.CFG file.
5. Reboot the system.
The installation of the NetWare OS/2 ODI client driver is now complete.
To change any default settings when the driver is loaded, the user must create a NET.CFG file on the workstation diskette. The Novell NetWare Operating System Keywords section provides a list of the available keywords. See Appendix A for sample NET.CFG files using common keywords used when installing the OS/2 ODI client driver.
For a NetWare Server 3.11 configuration, AMD provides a NetWare 3.11 Server ODI driver on the AMD NetWare driver diskette. Use the LOAD and BIND commands to load the NetWare 3.11 ODI server driver as described below. For more information on these commands, refer to the Novell NetWare 3.11 LAN Driver Installation documentation.
There are two methods for loading the NetWare Server 3.11 driver: (1) use the server command line prompt (":") or (2) edit the AUTOEXEC.NCF file.
Note: If you use the server command line, you will need to load the driver each time the system is booted. If you edit the AUTOEXEC.NCF file, it will automatically load the driver each time your system is booted.
WARNING: Be sure to use the Monitor Program which is included on the AMD NetWare driver diskette. Do not use the original Monitor Program shipped with NetWare 3.11 because it will cause the system to crash (known software bug).
Follow the steps listed below:
1. Install Novell NetWare Server 3.11 on your system.
2. Copy all the files from the 3.11 server directory of the AMD NetWare driver diskette to the hard disk directory where NetWare 3.11 system files are located. The following path should be used to access
the files from the AMD NetWare driver diskette:
A:\NOVELL\SERVER\3.1x\PCNTNW.LAN
3. Boot NetWare by executing SERVER.EXE. Refer to the appropriate
Novell NetWare documentation on loading disk drivers and mounting
volumes for more information.
4. To load the driver manually, follow either step 4.1 (for a PCnet-ISA Adapter Card) or step 4.2 (for PCnet-ISA+, PCnet-ISA II, PCnet-32, and PCnet-PCI Adapter Cards). If you want to load the driver using the AUTOEXEC.NCF file, go to step 5.
Note:You will need to specify the DOS path if the driver is located in a DOS partition.
__4.1 To manually load the driver for a PCnet-ISA adapter card:
a. Type the following command at the file server console (which also changes the default settings for PCnet-ISA adapter cards):
LOAD LSLENH.NLM LOAD MSM31X.NLM LOAD ETHERTSM.NLM LOAD PCNTNW PORT=320 INT=5 DMA=7 FASTISA
Notes: 1) All of the files listed above are needed. You must use the versions of these files included on the AMD driver diskettes.
2) Make sure the LSLENH, MSM31X, PATCHMAN, and ETHERTSM files are present in the same directory as the PCNTNW.LAN file. These files should be copied from the AMD NetWare support files driver diskette from the 3.11 subdirectory under the Novell directory. You must use the latest versions of these files provided in the AMD diskette.
b. Then press <Enter>. The PORT, INT, and DMA values used above must correspond to the PCnet-ISA adapter card's jumper settings.
Note: IOP, IRQ, and DRQ are older keywords previously used in place of PORT, INT, and DMA, respectively. However, they are still supported in order to maintain backward compatibility.
c. Next, bind the driver to the IPX protocol stack by typing:
BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
d. Then press <Enter>.
The installation of the NetWare Server 3.11 driver is now complete.
__4.2 To manually load a driver for PCnet-ISA+, PCnet-ISA II, PCnet-32, and PCnet-PCI adapter cards:
a. Type the following commands at the file server console:
LOAD LSLENH.NLM LOAD MSM31X.NLM LOAD ETHERTSM.NLM LOAD PCNTNW
Note: All of the files listed above are needed. You must use the versions of these files included on the AMD driver diskettes.
b. Then press <Enter>.
The adapter card configuration information is automatically determined by the PCNTNW driver.
c. Next, bind the driver to the IPX protocol stack by typing:
BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
d. Then press <Enter>.
The installation of the NetWare Server 3.11 driver is now complete.
5. To load the driver using the AUTOEXEC.NCF file, you must first edit the AUTOEXEC.NCF file.
Note: You will need to specify the DOS path if the driver is located in a DOS partition.
a. Type "LOAD INSTALL" at the server prompt (":") to access the Install Utility.
b. Open the SYSTEM OPTIONS menu to access "EDIT AUTOEXEC."
c. Then add the following command lines to the AUTOEXEC.NCF file.
The following is a PCnet-ISA adapter card example:
LOAD C:\PCNTNW DMA=5 INT=3 PORT=320 FRAME=Ethernet_802.2 BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
Note: IOP, IRQ, and DRQ are older keywords previously used in place of PORT, INT, and DMA, respectively. However, they are still supported in order to be backwards compatible.
The installation of the NetWare Server 3.11 driver is now complete.
See Keyword Examples under Section 5.5, Novell NetWare Server 4.x , to use keywords for NetWare Server 3.11.
For a Novell NetWare Server 3.12 configuration, AMD provides a NetWare 3.1.2 Server ODI driver, which is included on the AMD NetWare driver diskette.
Note: The directory structure provided on the AMD NetWare driver diskette has been set up for automatic OEM installation. Also, more information can be found in the Novell NetWare 3.12 documentation.
Use the LOAD and BIND commands to load the NetWare 3.12 ODI server driver as described below. For more information on these commands, refer to the Novell NetWare 3.12 LAN Driver Installation documentation.
There are two methods for loading the NetWare Server 3.12 driver: (1) use the server command line prompt (":") or (2) edit the AUTOEXEC.NCF file.
Note: If you use the server command line, you will need to load the driver each time the system is booted. If you edit the AUTOEXEC.NCF file, it will automatically load the driver each time your system is booted.
Follow the steps listed below:
1. Install NetWare 3.12 on your system.
2. Copy the AMD ODI Server driver (PCNTNW.LAN) from the AMD NetWare driver diskette to the hard disk directory where the NetWare 3.12 system files are located. The following path should be used to access the files from the AMD NetWare driver diskette:
A:\NOVELL\SERVER\3.1x\PCNTNW.LAN
3. Boot NetWare by executing SERVER.EXE. Refer to the appropriate
Novell NetWare documentation on loading disk drivers and mounting
volumes for more information.
4. To load the driver manually, follow either step 4.1 (for a PCnet-ISA Adapter Card) or step 4.2 (for PCnet-ISA+, PCnet-ISA II, PCnet-32, and PCnet-PCI Adapter Cards). If you want to load the driver using the AUTOEXEC.NCF file, go to step 5.
Notes: 1) You will need to specify the DOS path if the driver is located in a DOS partition.
2) Make sure the MSM31X.NLM and ETHERTSM.NLM files are present in the same directory as the PCNTNW.LAN file. These files should be copied from the AMD NetWare support files driver diskette from the 3.12 subdirectory under the Novell directory. You must use the latest versions of these files provided in the AMD diskette.
. 4.1 To manually load the driver for a PCnet-ISA adapter card:
a. Type the following command at the file server console (which also
changes the default settings for PCnet-ISA adapter cards):
LOAD C:\PCNTNW PORT=320 INT=5 DMA=7 FASTISA
b. Then press <Enter>.
The PORT, INT, and DMA values used above must correspond to the PCnet-ISA adapter card's jumper settings.
Note: IOP, IRQ, and DRQ are older keywords previously used in place of PORT, INT, and DMA, respectively. However, they are still supported in order to maintain backward compatibility.
c. Next, bind the driver to the IPX protocol stack by typing:
BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
d. Then press <Enter>.
The installation of the NetWare Server 3.12 driver is now complete.
__4.2 To manually load a driver for a PCnet-ISA+, PCnet-ISA II, PCnet-32, or PCnet-PCI adapter card:
a. Type the following command at the file server console:
LOAD C:\PCNTNW
b. Then press <Enter>.
c. Next, bind the driver to the IPX protocol stack by typing:
BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
d. Then press <Enter>.
The installation of the NetWare Server 3.12 driver is now complete.
5. To load the driver using AUTOEXEC, you must first edit the
AUTOEXEC.NCF file.
a. Type "LOAD INSTALL" at the server prompt (":") to access the Install Utility.
Note: You will need to specify the DOS path if the driver is located in a DOS partition.
b. Open the SYSTEM OPTIONS menu to access "EDIT AUTOEXEC."
c. Then add the following command lines to the AUTOEXEC.NCF file.
The following is a PCnet-ISA adapter card example:
LOAD C:\PCNTNW DMA=5 INT=3 PORT=320 FRAME=Ethernet_802.2 BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
Note: IOP, IRQ, and DRQ are older keywords previously used in place of PORT, INT, and DMA, respectively. However, they are still supported in order to be backwards compatible.
The installation of the NetWare Server 3.12 driver is now complete.
See Keyword Examples under Section 5.5, Novell NetWare Server 4.x , to use keywords for NetWare Server 3.12.
For a NetWare 4.x server configuration, AMD provides a NetWare 4.x Server ODI driver which is included on the AMD NetWare driver diskette.
Note: The directory structure provided on the AMD NetWare driver diskette has been set up for automatic OEM installation. Also, more information can be found in the Novell NetWare 4.x documentation.
Use the LOAD and BIND commands to load the NetWare 4.x ODI server driver as described below. For more information on these commands, refer to the Novell NetWare 4.x LAN Driver Installation documentation.
There are two methods for loading the NetWare Server 4.x driver: (1) use the server command line prompt (":") or (2) edit the AUTOEXEC.NCF file.
Note: If you use the server command line, you will need to load the driver each time the system is booted. If you edit the AUTOEXEC.NCF file, it will automatically load the driver each time your system is booted.
Follow the steps listed below:
1. Install Novell NetWare Server 4.x on your system.
2. Copy the AMD ODI Server driver (PCNTNW.LAN) from the AMD
NetWare driver diskette to the hard disk directory where the NetWare 4.x
system files are located. The following path should be used to access the
files from the AMD NetWare driver diskette:
A:\NOVELL\SERVER\4.x\PCNTNW.LAN
3. Boot NetWare by executing SERVER.EXE. Refer to the appropriate
Novell NetWare documentation on loading disk drivers and mounting
volumes for more information.
4. To load the driver manually, follow either step 4.1 (for a PCnet-ISA Adapter Card) or step 4.2 (for PCnet-ISA+, PCnet-ISA II, PCnet-32, and PCnet-PCI Adapter Cards). If you want to load the driver using the AUTOEXEC.NCF file, go to step 5.
Notes: 1) You will need to specify the DOS path if the driver is located in a DOS partition.
2) Make sure the MSM.NLM and ETHERTSM.NLM files are present in the same >directory as the PCNTNW.LAN file. These files should be copied from the AMD NetWare support files driver diskette from the 4.x subdirectory under the Novell directory. You must use the latest versions of these files provided in the AMD diskette.
__4.1 To manually load the driver for a PCnet-ISA adapter card:
a. Type the following command at the file server console (which also
changes the default settings for PCnet-ISA adapter cards):
LOAD C:\PCNTNW PORT=320 INT=5 DMA=7 FASTISA
The PORT, INT, and DMA values used above must correspond to the PCnet-ISA adapter card's jumper settings.
Note: IOP, IRQ, and DRQ are older keywords previously used in place of PORT, INT, and DMA, respectively. They are still supported in order to be backwards compatible.
b. Next, bind the driver to the IPX protocol stack by typing:
BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
c. Then press <Enter>.
The installation of the NetWare Server 4.x driver is now complete.
__4.2 To manually load the driver for PCnet-ISA+, PCnet-ISA II, PCnet-32, and PCnet-PCI adapter cards:
a. Type the following command at the file server console:
LOAD C:\PCNTNW
b. Then press <Enter>.
c. Next, bind the driver to the IPX protocol stack by typing:
BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
d. Then press <Enter>.
The installation of the NetWare Server 4.x driver is now complete.
5. To load the driver using the AUTOEXEC.NCF file, you must first edit the AUTOEXEC.NCF file.
Note: You will need to specify the DOS path if the driver is located in a DOS partition.
a. Type "LOAD INSTALL" at the server prompt (":") to access the AMINSTAL utility.
b. Open the MAINTENANCE/SELECTIVE INSTALL menu and select the "NCF File Options" from the menu to access "EDIT AUTOEXEC."
c. Then add the following command lines to the AUTOEXEC.NCF file.
The following is a PCnet-ISA adapter card example:
LOAD C:\PCNTNW DMA=5 INT=3 PORT=320 FRAME=Ethernet_802.2 BIND IPX TO PCNTNW NET=xxxx
(Bind to IPX or any other protocol stack; where e.g., xxxx=1234)
Note: IOP, IRQ, and DRQ are older keywords previously used in place of PORT, INT, and DMA, respectively. They are still supported in order to be backwards compatible.
The installation of the NetWare Server 4.x driver is now complete.
If the bus type is known for the PCnet adapter card installed in the system, the BUSTYPE keyword may be used with the LOAD command. If the BUSTYPE keyword is specified, then the driver will not scan other buses. The available bus types are:
Bus Type PCnet Adapter Card Keyword ISA PCnet-ISA ISA Plug and Play (PnP) PCnet-ISA+, PCnet-ISA II PNP VESA Local Bus (VL) PCnet-32 VESA PCI Local Bus PCnet-PCI PCI/PCI1/PCI2
Examples:
For PCnet-ISA: LOAD PCNTNW BUSTYPE=ISA For PCnet-ISA+/PCnet-ISA II: LOAD PCNTNW BUSTYPE=PNP For PCnet-32: LOAD PCNTNW BUSTYPE=VESA For PCnet-PCI: LOAD PCNTNW BUSTYPE=PCI For PCnet-PCI: LOAD PCNTNW BUSTYPE=PCI1 For PCnet-PCI: LOAD PCNTNW BUSTYPE=PCI2
Note: If the PCI Configuration Access mechanism is known for the PCI system, the user may use PCI1 or PCI2 with the BUSTYPE keyword. However, using PCI with the BUSTYPE keyword will cause the driver to attempt to determine the proper mechanism in the PCI system.
The FRAME keyword should be used with the LOAD command to designate the desired frame type. In addition, to supporting multiple FRAME types, the BOARD keyword must be used in conjunction with the FRAME keyword if no IO Address is specified. The available FRAME values are the following:
Ethernet_802.2 Ethernet_802.3 Ethernet_SNAP Ethernet_II
Refer to the appropriate Novell NetWare documentation for details regarding each frame type. The BOARD keyword value is designated by the user. The range available for BOARD is 0-254.
LOAD PCNTNW FRAME=Ethernet_802.2 BOARD=1 LOAD PCNTNW FRAME=Ethernet_802.3 BOARD=1 LOAD PCNTNW FRAME=Ethernet_II BOARD=1 LOAD PCNTNW FRAME=Ethernet_SNAP BOARD=1
Then press <Enter>.
Finally, the driver must be "binded" to the IPX protocol for each frame type based on the procedure provided in the Novell NetWare documentation. Note that if memory is low to support multiple frames, the buffer size must be increased in the STARTUP.NCF file in NetWare. For example, the SET RESERVED BUFFERS below 16 MBytes should be set to 32 from the default setting of 16. For example:
Set Reserved Buffers below 16 Meg=32
The FRAME keyword should be used with the LOAD command to designate the desired frame type. For single FRAME support, no BOARD keyword is needed to designate one frame type. The available values and description to load FRAME types is explained above in the Multiple Frame Type Support section.
The driver must be loaded again for each new PCnet adapter board installed in the system. For example, to load three PCnet-ISA+, PCnet-32, or PCnet-PCI adapter cards in the system for the Novell NetWare environment, the following must be entered.
First PCnet Adapter Card: LOAD PCNTNW Second PCnet Adapter Card: LOAD PCNTNW Third PCnet Adapter Card: LOAD PCNTNW
Then press <Enter>.
If more than one PCnet-ISA adapter card will be installed, the user must specify the IRQ and DMA channel for each card. For example, to load two PCnet-ISA adapter cards:
PCnet-ISA Adapter Card 1: LOAD PCNTNW DMA=5 INT=3 PCnet-ISA Adapter Card 2: LOAD PCNTNW DMA=6 INT=5
Then press <Enter>.
The BOARD keyword may be used with the LOAD command to specify the board number to the selected physical adapter board. This keyword is used to load a different frame type to the same board. See the Multiple Frame Type Support section above for examples using the BOARD keyword.
Note: If PORT and IO Port Address are specified, then the BOARD keyword should not be used. In this case, the same PORT should be used to load a different frame type.
The PCnet-ISA II adapter card provides full duplex operation. For example:
Enable full duplex on 10BaseT port: Load PCNTNW FDUP = UTP Enable full duplex on AUI port: Load PCNTNW FDUP = AUI Disable full duplex: Load PCNTNW FDUP = OFF
Note: If FDUP = AUI then the TP (Twisted Pair) keyword is void.
The CDCOFF keyword will disable the write buffers on the Intel CDC chip. For example:
BUSTYPE=PCI CDCOFF
Keywords for Novell NetWare DOS and OS/2 ODI client drivers and Server drivers are shown in Tables 1 and 2, respectively.
Table 1. Novell NetWare DOS and OS/2 ODI Client Keywords
| ||||
| I/O Address | PORT
| See Common Keywords. | ||
| Interrupt | INT
| See Common Keywords. | ||
| DMA | DMA
| See Common Keywords. | ||
| FASTISA | FASTISA
| FASTISA is a mode that increases the performance of the PCnet-ISA, PCnet-ISA+, and PCnet-ISA II by reducing the memory write cycle time from 450 ns to 350 ns. Some older machines with slower memory may not be compatible, if they do not have an EISA mode. Refer to Appendix A for more details on NET.CFG options. | Present or
| Not Present |
| Ethernet Frame type | FRAME | See Ethernet Frame type from the IEEE Specification. | Ethernet_802.2
| Ethernet_802.2 (NetWare 3.12, 4.x)
|
| Bus Timer Off | BTO
| BTO will reset bit 13 in CSR4 of the PCnet device to enable the Bus Timer register (CSR82). By default the timer is always on. | Present or
| Not Present |
|
| |||
| Full Duplex | FDUP
| FDUP keyword is used to enable or disable full duplex on the 10BaseT and AUI ports. See Common Keywords. | UTP
| Not Present (What is in EEPROM) |
| Disable write buffers
| CDCOFF
| CDCOFF keyword is used to disable the write buffers on the Intel CDC chip. | Present or
| Not Present |
Note: All of the keywords available to the Novell ODI
client drivers may be automatically activated by creating or modifying
the NET.CFG file. See Appendix A for sample NET.CFG files.
Table 2. Novell NetWare Server Keywords
| I/O Address | PORT
|
See Common Keywords. | ||
| Interrupt | INT
| See Common Keywords. | ||
| DMA | DMA
| See Common Keywords. | ||
| FASTISA | FASTISA | FASTISA is a mode that increases the performance of the PCnet-ISA, PCnet-ISA+, and PCnet-ISA II by reducing the memory write cycle time from 450 ns to 350 ns. Some older machines with slower memory may not be compatible if they do not have an EISA mode. Refer to Appendix A for more details on NET.CFG options. | Present or
| Not Present |
| Ethernet Frame type | FRAME | See Ethernet Frame type from the IEEE Specification. | Ethernet_802.2
| Ethernet_802.2
|
| Physical Board Number | BOARD | Specifies the physical board number. | 0-254 | 255
|
| Name of Logical Board Number | NAME | Used to identify the logical board for different FRAME types | Any ASCII characters | None |
| Bus Timer Off | BTO | BTO will reset bit 13 in CSR4 of the PCnet device to disable the Bus Timer register (CSR82). By default the timer is always on. | Present or
| Not Present |
| Full Duplex | FDUP
| FDUP keyword is used to enable or disable full duplex on the 10BaseT and AUI ports. See Common Keywords. | UTP
| Not Present (What is in EEPROM) |
| Disable write buffers
| CDCOFF
| CDCOFF keyword is used to disable the write buffers on the Intel CDC chip. | Present or
| Not Present |
