ID Number: Q63239
2.00
OS/2
Summary:
If an error message is received indicating that a driver failed to
bind following initialization of the network adapter card, check the
following in the PROTOCOL.INI file:
1. Is the driver name correct for the adapter card?
2. Does the section definition match the _NIF specified in the
bindings line? (The example used below is the UB MAC driver).
3. Is the memory mapped correctly to match the adapter board's
settings?
4. Is the I/O port mapped correctly to match the adapter board's
settings?
5. Does the interrupt setting match what the board is jumpered to?
The following is a sample PROTOCOL.INI file. The numbers in the left
margin refer to the questions listed above.
[PROTOCOL MANAGER]
DRIVERNAME = PROTMAN$
[NETBEUI_XIF]
(1) Drivername = netbeui$
(2) BINDINGS = UBMAC_NIF
(2) [UBMAC_NIF]
DriverName = UBMAC$
AdapterType = NIUpc
(3) MemoryWindow = 0xD8000
(4) IO_Port = 0x368
(5) IRQ_Level = 3
The following is a list of other possible problems:
- Adapter card could be bad.
- Cable could be bad.
- PS/2: For the NIUps, "IRQ_Level," "MemoryWindow," and "IO_Port" are
not needed and will be ignored. If the PS/2 does not bind, boot off
the PS/2 reference disk to configure the card correctly.
- IRQ conflict: No two options (mouse, net card, etc.) should use the
same interrupt (IRQ).
Hardware Interrupts Used by IBM PC/XT/AT
----------------------------------------
No two options (mouse, net card, etc.) should ever use the same
interrupt (IRQ).
IRQ Number Potential Use
---------- -------------
0 System board timer
1 Keyboard
2 AT Hard Disk*, bus mouse, some clock calendars,
UBNET (on PC), AppleTalk, Tops card.
3 Serial port 2, bus mouse, Tangent, AppleTalk,
Tops cards
4 Serial port 1, bus mouse, AppleTalk card
5 XT hard disk, parallel port 2, bus mouse, UBNET
card
6 Disk controller
7 Parallel port 1
IBM AT ONLY
8 Real time clock
9 Software redirect to IRQ 2
10-12 Reserved
13 Coprocessor
14 Hard disk controller
15 Reserved
The IBM AT uses IRQ2 to access interrupts 8-15, by activating
a separate interrupt controller.
- Memory conflict: It is very common to find situations where the
memory addresses on a network card and an expanded memory manager
overlap. This is primarily because of the differences in how
network cards and memory boards address locations in the computer's
memory.
The expanded memory manager is generally loaded through the
CONFIG.SYS file and takes over an area of memory (64K minimum)
between C000H:0000 and E000H:FFFF. This address range is also
reserved for network cards, IBM XT hard disk controllers, and ROM
memory expansion. Because network cards do not access the memory
window until the network software is activated, memory conflicts
may not appear in an application using expanded memory until the
network is activated.