=====================
|| ||
|| BOCALANcard ||
|| ||
|| BEN110/BEN120 ||
|| ||
|| RELEASE NOTES ||
|| ||
=====================
============================================================================
Contents of this file
============================================================================
Section I......Configuring the BEN110/120
Section II.....Programmable LED
Section III....PC-NFS Driver Installation
Section IV.....IBM LAN SERVER Driver Installation
Section V......Using Microsoft Networking (NetBEUI) with Windows for
Workgroups
Section VI.....Using NOVELL ODI and Microsoft Networks with Windows for
Workgroups
Section VII....Driver Error Messages & Troubleshooting
============================================================================
Section I. Configuring the BEN110/120
============================================================================
The BEN110/120 is configured by running a configuration utility,
BENCFG.EXE. This utility is installed when you run 'install' and select
'BEN110/120 Utilities and Documentation'.
BENCFG allows you to change Base Address I/O, IRQ, DMA Channel,
and programmable LED options.
IF YOU HAVE NETWORK DRIVERS LOADED INTO MEMORY, YOU WILL NOT BE ABLE
TO RUN BENCFG. In fact, running bencfg when network drivers are loaded
can cause your system to hang.
============================================================================
Section II. Programmable LED
============================================================================
The red LED on the back of your BEN110/120 card is programmable. You
can specify events that cause the LED to flash. Use the BENCFG
program to specify the events. Place a 'Y' next to any event
you want the LED to flash.
==========
LED EVENTS
==========
LED Transmit Activity: Your BEN110/120 is transmitting data
onto the network.
LED Receive Activity: Your BEN110/120 is receiving data on the network.
LED Normal Polarity: Turn on this indicator to view polarity status.
When lit, your BEN110/120 is cabled correctly. If not lit, the
Negative and Positive signals for both transmit and receive
have been swapped. The BEN110/120 automatically adjusts to this
condition. This is used for troubleshooting purposes only. Please
note that these conditions only apply to the BEN110/120 when the
normal polarity indicator is on ("Y").
LED Jabber Indicator: This indicates that the BEN110/120 is jabbering
on the network.
LED Collision Status: This event happens when more than one station
on the network is transmitting simultaneously.
=============
LED Operation
=============
Each time you power up your computer, the programmable LED reverts
back to its default configuration:
Normal Polarity Y
The easiest way to determine this number is by running BENCFG. When
you select 'Save & Exit', BENCFG tells you the command, including
the register number.
Refer to Appendix F in the Installation Guide for more detailed
information regarding the use of the programmable red LED.
============================================================================
Section III PC-NFS Driver Installation
============================================================================
PC-NFS Driver
1. Insert the PC-NFS QUIKNDIS disk into the system's floppy
drive. Change the drive letter containing the QUIKNDIS disk.
2. Type QUIKNDIS at the prompt and press Enter.
3. A message will appear asking for the current boot drive.
Enter the current boot drive and press Enter.
4. In the next dialog box, press "Y" to save the current
PROTOCOL.INI as PROTOCOL.OLD. Ignore this step if this dialog
box does not appear.
5. In the adapter card list box, select the Custom option to
install the NDIS driver for PC-NFS.
6. If necessary, remove the QUIKNDIS disk from the floppy drive.
Insert the BEN110/120 driver diskette into a floppy drive.
7. Now, follow the dialog boxes and enter the correct driver and
path on the BEN110/120 driver diskette to install the NDIS driver.
For example, A:\PCNFS.
8. Next, enter the BOCAND for the NIF file name and press Enter.
9. Installation of the BEN110/120 NDIS 2.0.1 driver for PC-NFS is
complete.
============================================================================
Section IV IBM LAN SERVER Driver Installation
============================================================================
1. Insert the BEN110/120 driver diskette.
2. In IBM LAN Server, select or run the LAPS (LAN Adapter and
Protocol Support) program. Please refer to the IBM LAN Adapter
and Protocol Support Configuration Guide to access this utility
and for more details on how to install additional adapters and
device drivers.
3. From the IBM LAPS dialog box, choose the INSTALL button to
install a Network adapter card for the IBM LAN Server
environment. If the BEN110/120 Adapter card has already been
INSTALLed, skip to step 6.
4. Then specify the drive and path (LANSRVR) to copy the
appropriate files from the driver diskette. For example,
please enter A:\LANSRVR.
5. After successfully installing or copying the appropriate NIF
files from the disk, the IBM LAPS dialog box will appear again.
6. Now from the IBM LAPS dialog box, select the Configure option
to complete the installation of the NDIS driver for the
adapter card.
7. In the Configuration dialog box, choose the "Configure LAN
transports" (default) option and select Continue.
8. When the Configure Workstation dialog box is displayed,
remove the current configurations from the Current Configuration
list box.
9. Choose the BOCALANcard Ethernet Adapter from the Network
Adapters list box, by highlighting the entry. Then choose Add to
add the BEN110/120 Adapter card to the Current Configuration list
box.
10. Highlight the appropriate protocols in the Protocols list
box. Then choose Add to add them to the Current Configuration
list box.
11. Choose the BOCALANcard Ethernet adapter at the Current Configuration
list box. Then choose Edit. The Parameters dialog box is
displayed.
12. View the default configuration. If the default configuration
is appropriate, choose OK.
For the BEN110/120 adapter cards, no settings need to be specified
since they are software configurable.
To install the driver for IBM Extended Services 1.0, follow
these steps:
1. Insert the BEN110/120 driver diskette into the floppy drive.
2. Display the Communication Manager main menu and choose
Advanced.
3. Choose Configuration.
4. Choose LAN Adapter and Protocol Support (LAPS).
5. At the Options dialog box, choose Copy additional network
adapter drivers. Then choose OK.
6. At the Copy Additional Network Adapter Drivers dialog box,
type the path (a:). Then choose OK.
7. When the Copy Diskette dialog box is displayed, choose OK.
8. When the Options dialog box is displayed, choose Configure
Workstation. Then choose OK.
9. When the Configure Workstation dialog box is displayed,
remove the current configurations from the Current Configuration
list box.
10. Choose the BOCALANcard Ethernet Adapter from the Network Adapters
list box, by highlighting the entry. Then choose Add to add the
BOCALANcard Ethernet adapter to Current Configuration list box.
11. Highlight the appropriate protocols in the Protocols list
box. Then choose Add to add them to the Current Configuration
list box.
12. Choose the BOCALANcard Ethernet Adapter at the Current
Configuration list box. Then choose Edit. The Parameters dialog
box is displayed.
13. View the default configuration. If the default configuration
is appropriate, choose OK.
For BEN110/120 adapter cards, no settings need to be specified
since they are software configurable.
==============================================================================
Section V. Using Microsoft Networking (NetBEUI) with Windows for
Workgroups:
==============================================================================
1.Install Windows for Workgroups.
2.Install the ethernet card.
3.Run BENCFG to select an I/O Address; and IRQ setting.
4.Start Windows.
5.In the 'Network Group', select 'Network Setup'.
6.Select 'Drivers'.
7.Remove any drivers currently installed by selecting the
'Remove' button.
8.Select 'Add Adapter'.
9.Highlight 'Unlisted or Updated Network Adapter'.
10.Select 'OK'.
11.Windows asks to insert the unlisted or updated driver
disk in...
12.Insert the driver disk you created.
13.Type in A:\WFW311 (or B:\WFW311).
14.Select 'OK'.
15.Windows displays 'Boca Ethernet Adapter' (if not, make
sure you made the disk correctly, and typed A:\WFW311 and not
something else.
17.Select OK.
18.Note (For BENPCI, set the following 3 options to
AUTO_SCAN.
19.Select The BASE I/O Port (Address) you selected in
BENCFG, then OK.
20.Select the Interrupt you selected in BENCFG, then OK.
21.Select the DMA you selected in BENCFG, then OK. (For the
BEN1VL, select AUTO_SCAN).
22.You should now be back at the 'Network Drivers' dialog
box, and the 'Boca Ethernet Adapter (NDIS2/NDIS3) -
Microsoft NetBEUI should be listed).
23.Select 'Close'.
24.You should now be back at the 'Network Setup' dialog box.
25.Select 'Sharing' and setup the type of sharing you desire.
26.Back at the 'Network Setup' dialog box, select 'OK'.
27.Windows may ask you for both your Windows diskettes and
the Boca Ethernet diskette.
28.If asked for the Boca Ethernet Diskette, always type in
A:\WFW311.
29.Windows makes modifications to your system files.
30.Then Windows tells you to restart your computer.
31.Select Continue, and exit Windows normally.
32.Shut off the power to your computer.
33.Remove the floppy disk.
34.Turn on the computer.
In step 29, Windows makes modifications to the following
files:
Protocol.ini
Net.cfg
Autoexec.bat.
If you experience any difficulty, use any text editor to
view these files, and compare them with the examples below:
PROTOCOL.INI (in your windows subdirectory)
-------------------------------------------
[network.setup]
version=0x3110
netcard=ms$bocan3,1,MS$BOCAN3,3
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,NETBEUI
lana0=ms$bocan3,1,ms$netbeui
lana1=ms$bocan3,1,ms$ndishlp
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP
[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=MS$BOCAN3
[NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=MS$BOCAN3
LANABASE=0
[MS$BOCAN3]
DriverName=BOCAND$
IOADDRESS=0x300
INTERRUPT=12
DMACHANNEL=0
[BOCAN3]
Adapters=MS$BOCAN3
AUTOEXEC.BAT
------------
C:\WINDOWS\net start
PROMPT $p$g
SET TEMP=C:\DOS
NET.CFG (note, your INT, PORT and DMA may differ!
-------------------------------------------------
; *** SAMPLE NET.CFG FILE ***
LINK DRIVER BOCANW
Frame Ethernet_802.3
INT 12
Port 300
Frame Ethernet_II
Frame Ethernet_802.2
Frame Ethernet_SNAP
Link Driver
Frame Ethernet_802.3
Frame Ethernet_II
Frame Ethernet_802.2
Frame Ethernet_SNAP
Link Driver NE2100
Frame Ethernet_802.3
Frame Ethernet_II
Frame Ethernet_802.2
Frame Ethernet_SNAP
==============================================================================
Section VI.Using NOVELL ODI and Microsoft Networks with Windows for Workgroups
==============================================================================
BEFORE RUNNING THIS PROCEDURE, SETUP MICROSOFT
WINDOWS AS DESCRIBED IN SECTION V.
1.Install the Novell DOS ODI drivers as described in your
users manual.
2.Copy the files from the directory A:\NOVELL\WKSTN\DOSODI to
your Network Driver Directory.
3.Run BENCFG to select an I/O Address; and IRQ setting.
4.Insert the commands into your Autoexec.bat file to load
the Novell ODI Drivers. For Example:
C:\BEN110\LSL
C:\BEN110\BOCANW
C:\BEN110\IPXODI
C:\BEN110\NETX
5.Restart your computer and make sure you can log into your
fileserver.
6.Start Windows.
7.In the network group, select 'Network Setup'.
8.Go to 'Network Setup'.
9.Select 'Networks'.
10.Select 'Other'.
11.Select 'Novell Netware (Workstation Shell 3.x) (or 4.0 and
above)'.
12.Select 'OK'.
13.The 'Novell Netware' dialog box appears.
14.Select the IPXODI.COM and LSL.COM.
15.Select 'OK'.
16.Back at the 'Network Setup' dialog box, select OK.
17.Windows may ask you for both your Windows diskettes and
the Boca Ethernet diskette. If you run into trouble with the
Windows diskette, refer to the Microsoft Windows manual on
how to expand the necessary files and try the procedure again.
18.Windows may ask you for the directory of your net.cfg
file. Select the directory where you installed the DOS ODI
drivers.
19.Windows makes modifications to your system files.
20.Then Windows tells you to restart your computer.
21.Select 'Continue', and exit Windows normally.
22.Verify that your AUTOEXEC.BAT File has your Novell ODI
drivers loading BEFORE the NET START command. (See Example
Below).
22.Shut off the power to your computer.
23.Remove the floppy disk.
24.Turn on the computer.
Protocol.ini
------------
This file resides in you Windows subdirectory.
Windows for Workgroups setup may incorrectly remove the BINDINGS statements.
Your Protocol.ini file should look something like this:
[network.setup]
version=0x3110
netcard=ms$bocan3,1,MS$BOCAN3,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$bocan3,1,ms$netbeui
lana1=ms$bocan3,1,ms$nwlinknb
[net.cfg]
PATH=C:\BEN110\NET.CFG
[MS$BOCAN3]
[Link Driver BOCANW]
data=Frame Ethernet_SNAP
data=Frame Ethernet_802.2
data=Frame Ethernet_II
data=Frame Ethernet_802.3
[NWLINK]
BINDINGS=BOCANW
[NETBEUI]
BINDINGS=BOCANW
LANABASE=0
SESSIONS=10
NCBS=12
Net.cfg
-------
This file resides where your Novell ODI drivers are installed.
The file should look something like this, but remember that your
INT and PORT statements may differ, depending on how the board is
configured:
; *** SAMPLE NET.CFG FILE ***
LINK DRIVER BOCANW
Frame Ethernet_802.3
Int 12
Port 300
Frame Ethernet_II
Frame Ethernet_802.2
Frame Ethernet_SNAP
Link Driver
Frame Ethernet_802.3
Frame Ethernet_II
Frame Ethernet_802.2
Frame Ethernet_SNAP
Autoexec.bat
------------
Loading the Novell ODI drivers before NET START is Very Important!
REM SAMPLE AUTOEXEC.BAT FILE
c:\ben110\lsl
c:\ben110\bocanw
C:\ben110\ipxodi
C:\ben110\netx
C:\WINDOWS\net start
C:\WINDOWS\odihlp.exe
C:\WINDOWS\SMARTDRV.EXE /X
PROMPT $p$g
PATH=C:\WINDOWS;C:\SE1440;C:\DOS
============================================================================
Section VII. Driver Error Messages & Troubleshooting
============================================================================
Driver error messages are provided for the following drivers:
Packet Driver Error Messages
Artisoft LANtastic 4.x/5.x Driver Error Messages
Novell DOS - ODI Driver Error Messages
Custom DOS - ODI Driver Counters
Novell OS/2 - ODI Driver Error Messages
Novell Server - ODI Driver Error Messages
Netware Server Driver Custom Counters
NDIS 3.0 Driver Error Messages
============================================================================
Packet Driver Error Messages
============================================================================
Message: BOCAPK-DOS-1: BOCAPK [-n] [-d] [-w] <INT=packet_int_no>
[IRQ=int_no] [IOADDR=io_addr] [DMA=dma_no]
[BUSTYPE=bus] [DMAROTATE] [TP] [LED0=xx]
[LED1=xx] [LED2=xx]
[LED3=xx]
Meaning: The command line entered with associated parameters is incorrect.
Action: Refer to the board user manual and make sure that the command line
and its associated parameters are correct.
Message: BOCAPK-DOS-2: Unable to reset the Ethernet device
Meaning: The software could not reset the board
Action: Verify that a Ethernet board is physically installed properly or
replace the Ethernet board.
Message: BOCAPK-DOS-3: Unable to initialize the Ethernet device
Meaning: The software could not initialize the board
Action: Check the I/O address, Interrupt and DMA settings of the board.
Make sure that the driver settings of these three parameters
match the hardware setting. If the settings are correct, and
you still get this message, then replace the board.
Message: BOCAPK-DOS-4: VDS memory allocation failed
Meaning: The driver could not allocate memory for the virtual board.
Action: Check the system configuration.
Message: BOCAPK-DOS-5: There is already a packet driver at xxxx
Meaning: The driver is already loaded at this memory location
Action: Do not load the driver again.
Message: BOCAPK-DOS-6: <IRQ=int_no> should be between 0 and 15 inclusive
Meaning: The specified IRQ is out of range for the Ethernet board.
Action: Use valid IRQ values. Refer to the Software Keyword section of
this manual for valid ranges.
Message: BOCAPK-DOS-7: Packet driver failed to initialize the board
Meaning: The board initialization failed.
Action: Replace the board.
Message: BOCAPK-DOS-8: <INT=packet_int_no> should be in the range
0x60 to 0x80
Meaning: The specified software interrupt is out of the allowable range.
Action: Modify the INT value.
Message: BOCAPK-DOS-9: DMA number is not necessary for PCI device
Meaning: The Ethernet-PCI board does not require a DMA setting.
Action: Remove the DMA setting.
Message: BOCAPK-DOS-11: PnP device DMA number mismatch
Meaning: The specified DMA number mismatches with the DMA number
assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action: Remove the DMA setting.
Message: BOCAPK-DOS-12: PCI device IRQ number mismatch
Meaning: The specified IRQ number mismatches with the IRQ number assigned
by the PCI BIOS.
Action: Remove the IRQ setting.
Message: BOCAPK-DOS-13: VESA device IRQ number mismatch
Meaning: The specified IRQ number mismatches with the IRQ setting
designated by the on-board EEPROM.
Action: Remove the IRQ setting.
Message: BOCAPK-DOS-14: PnP device IRQ number mismatch
Meaning: The specified IRQ number mismatches with the DMA number assigned
by the PnP Configuration Manager or by the on-board EEPROM if PnP
is disabled.
Action: Remove the IRQ setting.
Message: BOCAPK-DOS-15: Device not found
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
Ethernet board.
Message: BOCAPK-DOS-16: Device not found at IOADDRESS
Meaning: The Ethernet device cannot be found at the IO Address specified.
Action: Verify that the specified IO Address matches with the board.
Otherwise, remove IOADDR keyword during installation.
Message: BOCAPK-DOS-17: PCI scan can only execute on a 386 and higher
processor
Meaning: The PCI bus is not available on your current system. The PCI
bus is only supported on systems with a 386 or higher processor.
Action: Do not specify PCI for BUSTYPE during installation.
Message: BOCAPK-DOS-18: PCI scan specified, device not found
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Otherwise, replace the board.
Message: BOCAPK-DOS-20: PnP scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the Ethernet-ISA+ board is physically installed properly.
Otherwise, replace the board.
Message: BOCAPK-DOS-21: ISA scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the Ethernet-ISA board is physically installed properly.
Otherwise, replace the board.
Message: BOCAPK-DOS-22: ISA DMA number out of range
Meaning: The Ethernet-ISA only supports four DMA channels.
Action: Specify a valid DMA number to match the jumper setting on the
ISA board. Refer to the Software Keyword section of this manual
for the available range of values.
Message: BOCAPK-DOS-23: ISA IRQ number out of range
Meaning: The Ethernet-ISA only supports eight IRQ channels.
Action: Specify a valid IRQ number to match the jumper setting on the
ISA board. Refer to the Software Keyword section of this manual
for the available range of values.
Message: Packet driver is at segment xxxx
Meaning: The memory address where Packet Driver is loaded is xxxx.
Action: None.
Message: Packet interrupt number xxxx
Meaning: The interrupt number used by the Packet Driver is xxxx.
Action: None.
Message: My Ethernet address is xxxx.
Meaning: The Ethernet address of this station is xxxx.
Action: None.
Message: My ARCnet address is xxxx
Meaning: The ARCnet address of this station is xxxx.
Action: None.
============================================================================
Artisoft LANtastic 4.x/5.x Driver Error Messages
============================================================================
Message: BOCALC-DOS-1: MPX number is already in use - Try another number
Meaning: The multiplex (MPX) interrupt number hh is being used by another
application or low-level driver.
Action: Try another MPX number.
Message: BOCALC-DOS-2: BOCALC AI-LANBIOS Compatible driver NOT installed
Meaning: The Artisoft LANtastic driver could not be installed.
Action: This message is displayed if BOCALC.EXE driver is invoked
with /help option. This message will also be displayed if
an error occurs during the installation. If an error occurs
during installation, then an error message is displayed before
this message. Try to correct the error which has occurred by
following specific instructions for that error.
Message: BOCALC-DOS-3: No network hardware found at I/O base address
Meaning: The Ethernet device cannot be found at the IO Address specified.
Action: Verify that the IO Address matches with the board. Otherwise,
remove the IOBASE keyword from the STARTNET.BAT file.
Message: BOCALC-DOS-4: BOCALC AI-LANBIOS Compatible Driver is not loaded
Meaning: The Artisoft LANtastic driver is not loaded.
Action: This message is in response to "BOCALC /remove" command when the
driver was not loaded previously. Only issue the remove option
Message: BOCALC-DOS-5: Installed AI-LANBIOS Compatible Driver is different
version
Meaning: You have loaded a version of the BOCALC.EXE program and attempted
to remove it from memory with the /REMOVE switch. The version with
which you are attempting to remove BOCALC.EXE is not the same
version that was loaded.
Action: Remove BOCALC.EXE with the same version of the program that was
loaded.
Message: BOCALC-DOS-6: Can't REMOVE -- interrupts re-hooked
Meaning: You have attempted to remove BOCALC.EXE and the interrupts are
in use by another TSR, or BOCALC.EXE was not the last TSR loaded.
Action: Remove any TSRs loaded after BOCALC.EXE. For example, if you
load BOCALC.EXE and then AILANBIO.EXE, you must first remove
AILANBIO.EXE, then you can remove BOCALC.EXE.
Message: BOCALC-DOS-7: Can't REMOVE -- AI-LANBIOS(R) still installed
Meaning: AI-LANBIOS is still installed. The remove sequence of the TSR
has been violated.
Action: REMOVE the AI-LANBIOS before using REMOVE for the Ethernet driver.
Message: BOCALC-DOS-9: Insufficient memory to load driver
Meaning: Not enough free DOS memory existed to load the driver.
Action: Remove other resident programs to free conventional memory.
NOTE: On some machines the BOCALC.EXE driver cannot be loaded
high since the bus master mode of the adapter cannot access the
upper memory blocks.
Message: BOCALC-DOS-10: Incorrect DMA jumper setting
Meaning: The DMA jumper setting mismatches with the DMA setting in
STARTNET.BAT.
Action: Change the DMA setting on the hardware to match the DMA setting
in STARTNET.BAT.
Message: BOCALC-DOS-11: Incorrect IRQ jumper setting
Meaning: The IRQ jumper setting mismatches with the IRQ setting in
STARTNET.BAT.
Action: Change the IRQ setting on the hardware to match the IRQ setting
in STARTNET.BAT.
Message: BOCALC-DOS-12: Adapter self test failed --
Initialization timeout
Loopback timeout
Network error
Transmit error
Receive error
Message compare error
Meaning: The BOCALC performs a self test when the driver is loaded and
has failed.
Action: Replace the adapter or if a Ethernet-ISA type card is being
installed, set the XBUS command line switch
Message: BOCALC-DOS-13: VDS memory allocation failed
Meaning: The driver could not allocate memory for the virtual board.
Action: Check the system configuration.
Message: BOCALC-DOS-14: DMA number is not necessary for PCI device
Meaning: The Ethernet-PCI board does not require a DMA setting.
Action: Remove the DMA setting in STARTNET.NET.
Message: BOCALC-DOS-16: PnP device DMA number mismatch
Meaning: The DMA number specified in STARTNET.BAT mismatches with the DMA
number assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action: Remove the DMA number in STARTNET.BAT.
Message: BOCALC-DOS-17: PCI device IRQ number mismatch
Meaning: The IRQ number in STARTNET.BAT in STARTNET.BAT mismatches with the
IRQ number assigned by the PCI BIOS.
Action: Remove the IRQ number in STARTNET.BAT.
Message: BOCALC-DOS-18: VESA device IRQ number mismatch
Meaning: The DMA number specified in STARTNET.BAT mismatches with the
DMA number assigned by the on-board EEPROM.
Action: Remove the IRQ number in STARTNET.BAT.
Message: BOCALC-DOS-19: PnP device IRQ number mismatch
Meaning: The IRQ number specified in STARTNET.BAT mismatches with the
IRQ number assigned by the PnP Configuration Manager or by the
on-board EEPROM if PnP is disabled.
Action: Remove the IRQ number in STARTNET.BAT.
Message: BOCALC-DOS-20: Device not found
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
Ethernet board.
Message: BOCALC-DOS-21: Device not found at IOADDRESS
Meaning: BOCALC.EXE did not find an adapter at the I/O port address
specified on the command line.
Action: Make sure the adapter is correctly installed and that the IOBASE
command line switch corresponds to the I/O base setting on the
board.
Message: BOCALC-DOS-22: PCI scan can only execute on a 386 and higher
processor
Meaning: The PCI bus is not available on your system. The PCI bus is
only supported on systems with a 386 or higher processor.
Action: Do not specify PCI for BUSTYPE with your current system.
Message: BOCALC-DOS-23: PCI scan specified, device not found
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Otherwise, replace the board.
Message: BOCALC-DOS-25: PnP scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the Ethernet-ISA+ board is physically installed properly.
Otherwise, replace the board.
Message: BOCALC-DOS-26: ISA scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the Ethernet-ISA board is physically installed properly.
Otherwise, replace the board.
Message: BOCALC-DOS-27: ISA DMA number out of range
Meaning: The Ethernet-ISA only supports four DMA channels.
Action: Specify a valid DMA number at the command line or in STARTNET.BAT
to match the jumper setting on the ISA board. Refer to the
Software Keyword section of this manual for the available range of
Message: BOCALC-DOS-28: ISA IRQ number out of range
Meaning: The Ethernet-ISA only supports eight IRQ channels.
Action: Specify a valid IRQ number at the command line or in STARTNET.BAT
to match the jumper setting on the ISA board. Refer to the
Software Keyword section of this manual for the available range of
values.
Message: BOCALC-DOS-29: MPX channels CO - FF not available
Meaning: The driver could not find an available MPX channel to register.
Action: Remove unused MPX channel designations from other TSRs to make
MPX channels available.
Message: BOCALC-DOS-30: IO address conflict with the existing devices
Meaning: The specified IO Address conflicts with other devices in the
system.
Action: Change the IO Address hardware setting and the IO Address setting
at the command line or in the STARTNET.BAT file to match the
jumper setting.
Message: BOCALC-DOS-31: IRQ number conflict with the existing devices
Meaning: The specified IRQ conflicts with other devices in the system.
Action: Change the IRQ hardware setting and the IRQ setting at the
command line or in the STARTNET.BAT file to match the jumper
Message: BOCALC-DOS-VL: DMA number conflict with the existing devices
Meaning: The specified DMA conflicts with other devices in the system.
Action: Change the DMA hardware setting and the DMA setting at the
command line or in the STARTNET.BAT file to match the jumper
setting.
Message: BOCALC-DOS-33: Can't REMOVE, INT 2Fh used by other TSR
Meaning: Another TSR is sharing INT 2Fh and the same MPX channel.
Action: Remove the other TSR that shares the same MPX channel
before removing the Ethernet driver.
Message: BOCALC AI-LANBIOS Compatible Driver Installed
Meaning: The Artisoft LANtastic driver is installed.
Action: None.
Message: BOCALC AI-LANBIOS Compatible driver REMOVED.
Meaning: The driver is removed from memory.
Action: None.
Message: Cannot open indirect file - @file
Meaning: The file "file" cannot be opened as an indirect file.
Action: The file must exist before it can be used as an indirect file.
Message: Illegal character after switch name - ?????nnnn
Meaning: The switch ?????? is followed by a character other than
"=" or ":" or the switch does not take a value.
Action: Only use the characters "=" or ":" to specify switch values
and do not place characters after switches that do not take values.
Message: Illegal digit in switch value - ??????=nnnn
Meaning: An illegal digit (character) was encountered in the numeric switch
value.
Action: You must restrict numeric decimal values to the numbers 0-9.
You must restrict hexadecimal values to the numbers 0-9 and
Message: Illegal switch - ??????=nnnn
Meaning: The switch ??????=nnnn is not a recognized switch.
Action: You may only specify legal switches on the command line.
============================================================================
Novell DOS - ODI Driver Error Messages
============================================================================
Message: BOCANW-DOS-1: The LSL is not loaded
Meaning: The Link Support Module program (LSL.COM) is not loaded.
Action: Load the LSL.COM before loading the driver.
Message: BOCANW-DOS-2: The LSL has no more room for a board using
Frame <string>
Meaning: The maximum number of board, whether virtual or physical, has
been registered with the Link support layer. The DOS ODI LSL
can support up to eight boards.
Action: Reduce the number of active boards in the systems by unloading
a board or by decreasing the number of frame types activated by MLID.
Message: BOCANW-DOS-3: Could not find BOCANW MLID to unload
Meaning: A request was made to unload BOCANW MLID, but the MLID is not loaded.
Action: None
Message: BOCANW-DOS-4: A TSR is loaded above the BOCANW MLID.
Meaning: You tried to unload the BOCANW MLID from memory, but the
BOCANW MLID detected another Terminate-and Stay-Resident
program loaded above the MLID. For the BOCANW MLID to safely
unload, TSRs that were loaded after it must be unloaded first.
Action: Either load the other TSR before loading the BOCANW MLID or
unload the TSR before trying this operation.
Message: BOCANW-DOS-5: BOCANW MLID could not be unloaded; the operation
was aborted
Meaning: The BOCANW MLID was attempting to remove the resident BOCANW MLID
from memory. The BOCANW MLID was unable to successfully shut down
the resident BOCANW MLID. A hardware failure has probably occurred.
Action: Check the hardware. If hardware is faulty, replace the faulty
hardware.
Message: BOCANW-DOS-6: The adapter did not initialize. BOCANW did not load.
Meaning: The hardware did not initialize correctly. The BOCANW did not load.
Action: Check the hardware. Make sure that the hardware setting of the
board matches the card settings in the NET.CFG file.
Message: BOCANW-DOS-7: You need another BOCANW MLID Section Heading in the
NET.CFG file in order the load the MLID again.
Meaning: You tried to load the BOCANW MLID a second time. Normally, you
would do this so that you could use two or more boards in the
workstation. When two or more of the same type of network boards
are installed in the workstation, an associated BOCANW MLID section
heading must be specified in the NET.CFG file.
Action: Create a NET.CFG file and add the commands for both BOCANW MLID
boards to the file. Then reboot the workstation.
Message: BOCANW-DOS-8: A NET.CFG is required to load the MLID again.
Meaning: You tried to load the BOCANW MLID a second time. Normally, you
would do this so that you could use two or more boards in the
workstation. When two or more of the same type of network boards
are installed in the workstation, an associated BOCANW MLID section
heading must be specified in the NET.CFG file.
Action: Create a NET.CFG file and add the commands for both BOCANW MLID
boards to the file. Then reboot the workstation.
Message: BOCANW-DOS-9: The NET.CFG entry has been ignored
Meaning: The BOCANW ignored the NET.CFG entry.
Action: You may want to modify the NET.CFG file to delete or change the
entry in question.
Message: The BOCANW MLID has been successfully removed
Meaning: A request was made to unload an BOCANW MLID, and the BOCANW MLID
was removed from memory.
Action: None
Message: BOCANW-DOS-11: The MLID does not support frame <string>.
The protocol keyword has been ignored.
Meaning: The "PROTOCOL" option was specified in the NET.CFG for an
BOCANW MLID. The specified frame type is not supported by
the BOCANW MLID.
Action: Check the "PROTOCOL" line in the NET.CFG file for possible
omissions of required dashes and underscores or any misspellings.
Check the board documentation for supported frame types.
Message: BOCANW-DOS-12: The protocol keyword must have a frame type.
Entry ignored.
Meaning: The "PROTOCOL" option was specified in the NET.CFG for an
BOCANW MLID. The entry failed to specify the associated frame
type for the protocol ID addition. AN entry in the NET.CFG file
for the "PROTOCOL" option should look similar to the following:
LINK DRIVER BOCANW
PROTOCOL IPX 8137 ETHERNET_II
Action: Specify a frame with the "PROTOCOL" option.
Message: BOCANW-DOS-13: The MLID could not register Protocol ID <string>
for protocol stack <string> for frame type.
Meaning: The BOCANW MLID could not register the specified Protocol ID.
Action: Verify the protocol information in the NET.CFG file.
Message: BOCANW-DOS-14: This version of LSL is not supported
Meaning: The BOCANW MLID cannot run correctly using this version of the LSL.
Action: Update your LSL.COM to a newer version.
Message: BOCANW-DOS-15: The frame type is already activated for
frame <string>. The NET.CFG entry has been ignored.
Meaning: Two "Frame" keywords under the same main section heading specified
the same frame type. A specified frame type may be specified only
once per driver.
Action: Remove the duplicate "Frame" keyword entry.
Message: BOCANW-DOS-16: The node address was incorrectly specified
in NET.CFG.
Meaning: You used the "NODE ADDRESS" option in the NET.CFG file to override
the node address on the network board. The number specified was not
a valid Ethernet node address. An Ethernet address is 6 bytes in
length. This error occurs if Bit 0 of the first address byte is a 1.
This bit must always be 0. For example, if the first byte has the
following address, an invalid Ethernet address is generated.
FIRST BYTE
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 1
This byte will produce node addresses in the 0100 0000 0000 to
01FF FFFF FFFF range, all of which will be invalid.
Action: Change the NET.CFG file so that a valid node address is specified.
Message: BOCANW-DOS-17: An invalid keyword was specified in NET.CFG on
line xx.
Meaning: The keyword specified in NET.CFG file is incorrect.
Action: Check the keyword in question. Make sure that the keyword
is correctly spelled.
Message: BOCANW-DOS-18: The frame type specified in NET.CFG is not
supported.
Meaning: The "PROTOCOL" option was specified in the NET.CFG for an
BOCANW MLID. The specified frame type is not supported by
the BOCANW MLID.
Action: Check the "PROTOCOL" line in the NET.CFG file for possible
omissions of required dashes and underscores or any misspellings.
Check the BOCANW MLID documentation for supported frame types.
Message: BOCANW-DOS-19: An invalid Ethernet node address is specified
in NET.CFG. The MLID modified the incorrect address bits.
Meaning: The NET.CFG has an invalid node address. The BOCANW MLID
modified and corrected the address.
Action: You may want to correct the node address line in the NET.CFG file.
Message: BOCANW-DOS-50: The board cannot be found.
Meaning: The board is either not physically present or not configured
correctly.
Action: Make sure that the board is physically present in the system.
Also check the hardware setting of the board (I/O, IRQ, DMA)
against the NET.CFG settings. If this message still appears,
replace the board.
Message: BOCANW-DOS-54: The board did not respond to the initialization
command.
Meaning: The board initialization failed.
Action: Replace the board.
Message: BOCANW-DOS-58: The board did not respond to the initialization
command.
Meaning: The DMA and IRQ settings may be incorrect with the hardware
settings. Otherwise, the EEPROM may be corrupted.
Action: Verify the DMA & IRQ settings in NET.CFG match the hardware
jumper settings or verify that the EEPROM on-board is programmed
correctly.
Message: BOCANW-DOS-59: Buffers could not be locked
Meaning: An attempt was made to lock buffers for direct access. The
attempt failed.
Action: Check the memory manager documentation and make sure that it
supports a memory manager VDS (Virtual DMA Server). If in doubt,
either use another memory manager or do not use it.
Message: BOCANW-DOS-60: PnP device DMA number mismatch.
Meaning: The DMA number specified in NET.CFG mismatches with the DMA
number assigned by the PnP Configuration Manager or by the
on-board EEPROM if PnP is disabled.
Action: Remove the DMA number in NET.CFG.
Message: BOCANW-DOS-61: PCI device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the
IRQ number assigned by the PCI BIOS.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-DOS-62: VESA device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the
IRQ number assigned by the on-board EEPROM.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-DOS-63: PnP device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the
IRQ number assigned by the PnP Configuration Manager or
by the on-board EEPROM if PnP is disabled.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-DOS-64: Device not found.
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
the Ethernet board.
Message: BOCANW-DOS-65: Device not found at IOADDRESS.
Meaning: The Ethernet device cannot be found at the IO Address specified
in NET.CFG.
Action: Verify that the IO Address in NET.CFG matches with the board.
Otherwise, remove the PORT keyword from NET.CFG.
Message: BOCANW-DOS-66: PCI scan can only execute on a 386 and higher
processor.
Meaning: The PCI bus is not available on your system. The PCI bus is
only supported on a 386 or higher processor.
Action: Do not specify PCI for BUSTYPE with your current system setup.
Message: BOCANW-DOS-67: PCI scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Use the BUSTYPE keyword to specify PCI1 or PCI2 values if
the PCI mechanism is known for your system. Otherwise, replace
Message: BOCANW-DOS-69: PnP scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the ISA board is physically installed properly.
Otherwise, replace the Ethernet-ISA+ board.
Message: BOCANW-DOS-70: ISA scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the ISA board is physically installed properly.
Message: BOCANW-DOS-71: ISA DMA number out of range.
Meaning: The Ethernet-ISA board only supports four DMA channels.
Action: Specify a valid DMA number in NET.CFG to match the jumper
setting on the Ethernet-ISA board. Please refer to the Software
Keyword section of this manual for the available range of values.
Message: BOCANW-DOS-72: ISA IRQ number out of range.
Meaning: The Ethernet-ISA board only supports eight IRQ channels.
Action: Specify a valid IRQ number in NET.CFG to match the jumper setting
on the Ethernet-ISA board. Please refer to the Software Keyword
section of this manual for the available range of values.
Message: BOCANW-DOS-80: DMA number is not necessary for PCI device.
Meaning: The Ethernet-PCI board does not require a DMA setting.
Action: Remove DMA from NET.CFG.
============================================================================
Custom DOS-ODI Driver Counters
============================================================================
1) Babbling Transmitter:
This counter indicates that the transmitter has been
transmitting longer than required to send the maximum has been transmitting longer than the time
size frame. This counter is incremented if 1519 bytes or
greater are transmitted.
2) Fatal Rx Int.:
This counter is incremented if the driver receives a frame
> 1518 bytes. Ethernet networks should not contain frames
> 1518 bytes.
3) Ethernet Reset:
This counter is incremented when the board goes through a reset.
4) Max Collision:
This counter is incremented when there is a collision on the
Ethernet Network.
5) Memory Error:
This counter is incremented when the board does not get bus master
resource in the system.
6) Missed Packet:
This counter is incremented when the board misses an incoming
packet from the network due to low resources.
7) Rx Frame Error:
This counter is incremented when the board receives a frame with
CRC error.
8) Tx Late Collision:
This counter is incremented when a late collision (after 51.2 micro
seconds) occurs on the Ethernet network.
9) Tx Retry:
This counter is incremented when the board transmitter fails to
transmit a frame after attempting to transmit for 16 times due to
repeated collisions.
10) Tx Time Out:
This counter is incremented when the transmitter in the board
could not transmit a packet, within an allowed time, on the network
due to very heavy traffic conditions.
============================================================================
Novell OS/2 - ODI Driver Error Messages
=========================================================================
Message: BOCANW-OS2-1: The LSL is not loaded.
Meaning: The Link Support Module program (LSL.SYS) is not loaded.
Action: Load the LSL.SYS before loading the driver.
Message: BOCANW-OS2-21: Could not add MLID Protocol ID.
Meaning: The BOCANW MLID could not register the specified Protocol ID.
Action: Verify the protocol information in the NET.CFG file.
Message: BOCANW-OS2-22: Could not allocate memory. Virtual board did not
load.
Meaning: The driver could not allocate memory for the virtual board.
Action: Check the system configuration.
Message: BOCANW-OS2-54: The board did not respond to the initialization
command.
Meaning: The board initialization failed.
Action: Replace the board.
Message: BOCANW-OS2-56: This interrupt is already used and cannot be shared.
Meaning: This interrupt is already used and cannot be shared.
Action: Change the IRQ in NET.CFG. For Ethernet-ISA, verify the jumper
setting matches with IRQ in NET.CFG.
Message: BOCANW-OS2-58: The board did not respond to the initialization
command.
Meaning: The DMA and IRQ settings may be incorrect with the hardware
settings. Otherwise, the EEPROM may be corrupted.
Action: Verify the DMA & IRQ settings in NET.CFG match the hardware
jumper settings or verify that the EEPROM on-board is programmed
correctly.
Message: BOCANW-OS2-59: Buffers could not be locked
Meaning: An attempt was made to lock buffers for direct access.
The attempt failed.
Action: Check the memory manager documentation and make sure that it
supports a memory manager VDS (Virtual DMA Server). If in doubt,
either use another memory manager or do not use it.
Message: BOCANW-OS2-60: PnP device DMA number mismatch.
Meaning: The DMA number specified in NET.CFG mismatches with the DMA number
assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action: Remove the DMA number in NET.CFG.
Message: BOCANW-OS2-61: PCI device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the IRQ number
assigned by the PCI BIOS.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-OS2-62: VESA device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the IRQ number
assigned by the on-board EEPROM.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-OS2-63: PnP device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the IRQ number
assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-OS2-64: Device not found.
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
the Ethernet board.
Message: BOCANW-OS2-65: Device not found at IOADDRESS.
Meaning: The Ethernet device cannot be found at the IO Address specified
in NET.CFG.
Action: Verify that the IO Address in NET.CFG matches with the board.
Otherwise, remove the PORT keyword from NET.CFG.
Message: BOCANW-OS2-66: PCI scan can only execute on a 386 and higher
processor.
Meaning: The PCI bus is not available on your system. The PCI bus is
only supported on a 386 or higher processor.
Action: Do not specify PCI for BUSTYPE with your current system setup.
Message: BOCANW-OS2-67: PCI scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Use the BUSTYPE keyword to specify PCI1 or PCI2 values if the
PCI mechanism is known for your system. Otherwise, replace the
PCI board.
Message: BOCANW-OS2-69: PnP scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the ISA board is physically installed properly.
Otherwise, replace the Ethernet-ISA+ board.
Message: BOCANW-OS2-70: ISA scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the ISA board is physically installed properly.
Otherwise, replace the Ethernet-ISA board.
Message: BOCANW-OS2-71: ISA DMA number out of range.
Meaning: The Ethernet-ISA board only supports four DMA channels.
Action: Specify a valid DMA number in NET.CFG to match the jumper
setting on the Ethernet-ISA board. Please refer to the
Software Keyword section of this manual for the available
range of values.
Message: BOCANW-OS2-72: ISA IRQ number out of range.
Meaning: The Ethernet-ISA board only supports eight IRQ channels.
Action: Specify a valid IRQ number in NET.CFG to match the jumper
setting on the Ethernet-ISA board. Please refer to the Software
Keyword section of this manual for the available range of values.
Message: BOCANW-OS2-73: Unable to allocate memory.
Meaning: The driver could not allocate memory for the virtual board.
Action: Check the system configuration.
Message: BOCANW-OS2-80: DMA number is not necessary for PCI device.
Meaning: The Ethernet-PCI board does not require a DMA setting.
Action: Remove DMA from NET.CFG.
============================================================================
Novell Server - ODI Driver Error Messages
============================================================================
Message: BOCANW-NW-054: The board did not respond to the initialization
command.
Meaning: The board did not respond when the software tried to initialize it.
Action: Make sure that the board is physically present in the system.
Check the I/O address and other settings and make sure that these
jumper values match the software driver settings.
Message: BOCANW-NW-58: The board did not respond to the initialization
command.
Meaning: The DMA and IRQ settings may be incorrect with the hardware
settings. Otherwise, the EEPROM may be corrupted.
Action: Verify the DMA & IRQ settings in NET.CFG match the hardware jumper
settings or verify that the EEPROM on-board is programmed correctly.
Message: BOCANW-NW-59: Buffers could not be locked
Meaning: An attempt was made to lock buffers for direct access.
The attempt failed.
Action: Check the memory manager documentation and make sure that it
supports a memory manager VDS (Virtual DMA Server). If in doubt,
either use another memory manager or do not use it.
Message: BOCANW-NW-66: The cable might be disconnected on the board
Meaning: The BNC cable may not be connected to the BNC connector on the
board.
Action: Connect the BNC cable to the board.
Message: BOCANW-NW-071: The matching virtual adapter could not be found.
Meaning: You tried to load another instance of the driver with a different
I/O address. This new board could not be found.
Action: Make sure that the board is physically present. Also check the
I/O settings of the board with the settings supplied to the driver.
Message: BOCANW-NW-072: A resource tag in unavailable.
Meaning: The driver tried to allocate some resources. These resources
were unavailable.
Action: Try to add and/or free some memory in the system. Reboot and
restart the system.
Message: BOCANW-NW-073: Unable to allocate memory.
Meaning: The driver failed to allocate the memory needed for normal
operation.
Action: Add more memory in the system or else free some memory resources
in the system and reboot the machine.
Message: BOCANW-NW-074: The hardware interrupt cannot be set.
Meaning: An attempt was made to initialize a given hardware interrupt.
The attempt was not successful.
Action: Check the hardware system. Make sure the board jumpers are set
to correct interrupt numbers. Also make sure that no other device
is using this interrupt in the system.
Message: BOCANW-NW-075: The MLID cannot be registered with the LSL.
Meaning: An error occurred while the driver was trying to register
with Link Support Layer.
Action: Check the version of Netware Operating System. Make sure that
this driver is for the version of Netware you are running.
Restart the complete system.
Message: BOCANW-NW-076: The polling procedure cannot be added.
Meaning: An error occurred while the driver was adding polling procedure
to the Netware Operating System. polling routines.
Action: Check the version of Netware Operating System. Make sure that
this driver is for the version of Netware you are running.
Restart the complete system.
Message: BOCANW-NW-077: The event notification cannot be registered.
Meaning: The driver failed to register its event notification routines
with the Netware operating system.
Action: Check the version of Netware Operating System. Make sure that
this driver is for the version of Netware you are running.
Restart the complete system.
Message: BOCANW-NW-078: The firmware file cannot be read.
Meaning: The driver tried to read a firmware file. The read process failed.
Action: Make sure that the support files accompanying the driver are
present. Reboot and restart the complete system.
Message: BOCANW-NW-079: The MLID did not initialize MSMTx Free Count.
Meaning: The MSMTx Free Count is not initialized correctly.
Action: Restart the system. If error is still present report it to the
Card Manufacturers.
Message: BOCANW-NW-084: Unable to allocate memory below the 16 megabyte
boundary.
Meaning: A request was made to allocate memory below 16 megabyte. The
request failed to complete successfully.
Action: Free some memory below 16 megabyte or add some more memory below
16 megabyte boundary.
Message: BOCANW-NW-086: The driver parameter block is too small.
Meaning: The driver parameter block is too small.
Action: Restart the system. If the error is still present, report it
to the Card Manufacturer.
Message: BOCANW-NW-087: The media parameter block is too small.
Meaning: The driver media parameter block is too small.
Action: Restart the system. If error is still present, report it to
the Card Manufacturer.
Message: BOCANW-NW-091: The hardware configuration conflicts.
Meaning: You tried to load a new frame type for the existing adapter.
The hardware assumption made in doing so are incorrect.
Action: Check the manual of your card and also check the physical hardware.
Make sure that your hardware configuration matches the software
settings.
Message: BOCANW-NW-092: Cannot schedule AES without an HSM routine.
Meaning: The Netware Operating System needs a Hardware Support Module
routine before it can schedule an AES event.
Action: Restart the system. If the error is still present, report it
to the Card Manufacturer.
Message: BOCANW-NW-093: Cannot schedule interrupt time call back without
an HSM routine.
Meaning: The driver needs a Hardware Support Module routine before it can
schedule an interrupt time call back.
Action: Restart the system. If the error is still present, report it to
the Card Manufacturer.
Message: BOCANW-NW-094: Cannot set hardware interrupt without an HSM
routine.
Meaning: The driver needs a hardware interrupt call back routine before
it sets the interrupt.
Action: Restart the system. If the error is still present, report it
to the Card Manufacturer.
Message: BOCANW-NW-095: Cannot add polling without an HSM routine.
Meaning: The driver needs an HSM polling routine before it can start the
polling process.
Action: Restart the system. If the error is still present, report it to
the Card Manufacturer.
Message: BOCANW-NW-026: The MSM in unable to parse a required custom keyword.
Meaning: An incorrect parameter keyword was entered by the user.
Action: Check the manual and make sure the keyword entered is correctly
spelled. Reload the driver.
Message: BOCANW-NW-126: The group bit in the node address override was
cleared.
Meaning: The IEEE address has a group bit indicating that an address belongs
to a group of station. This bit is only used for destination
address and not source address. You tried to enter a source address
with this bit set. The driver cleared the group bit of the source
address.
Action: None.
Message: BOCANW-NW-127: The local bit in the node address override was set.
Meaning: The local bit in the IEEE address format indicates that the
addresses are being managed locally. If you use the node address
override capabilities of this driver to enter a new address then
the local bit should be set. You entered an address without the
local bit set. The driver has set the local bit.
Action: None.
Message: BOCANW-NW-160: PnP device DMA number mismatch.
Meaning: The DMA number specified in NET.CFG mismatches with the DMA number
assigned by the PnP Configuration Manager or by the on-board EEPROM
if PnP is disabled.
Action: Remove the DMA number in NET.CFG.
Message: BOCANW-NW-161: PCI device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the IRQ number
assigned by the PCI BIOS.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-NW-162: VESA device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the IRQ
number assigned by the on-board EEPROM.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-NW-163: PnP device IRQ number mismatch.
Meaning: The IRQ number specified in NET.CFG mismatches with the IRQ number
assigned by the PnP Configuration Manager or by the on-board EEPROM
if PnP is disabled.
Action: Remove the IRQ number in NET.CFG.
Message: BOCANW-NW-164: Device not found.
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
the Ethernet board.
Message: BOCANW-NW-165: Device not found at IOADDRESS.
Meaning: The Ethernet device cannot be found at the IO Address specified
in NET.CFG.
Action: Verify that the IO Address in NET.CFG matches with the board.
Otherwise, remove the PORT keyword from NET.CFG.
Message: BOCANW-NW-166: PCI scan can only execute on a 386 and higher
processor.
Meaning: The PCI bus is not available on your system. The PCI bus is
only supported on a 386 or higher processor.
Action: Do not specify PCI for BUSTYPE with your current system setup.
Message: BOCANW-NW-167: PCI scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Use the BUSTYPE keyword to specify PCI1 or PCI2 values if the
PCI mechanism is known for your system. Otherwise, replace
the PCI board.
Message: BOCANW-NW-168: VESA scan specified, device not found.
Meaning: The driver cannot locate the BEN110/120 board on the VL bus.
Action: The BEN110 is not a VL board so this error should not occur.
Verify that the board is physically installed properly.
Otherwise, replace the board.
Message: BOCANW-NW-169: PnP scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the ISA board is physically installed properly.
Otherwise, replace the Ethernet-ISA+ board.
Message: BOCANW-NW-170: ISA scan specified, device not found.
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the ISA board is physically installed properly.
Otherwise, replace the Ethernet-ISA board.
Message: BOCANW-NW-171: ISA DMA number out of range.
Meaning: The Ethernet-ISA board only supports four DMA channels.
Action: Specify a valid DMA number in NET.CFG to match the jumper
setting on the Ethernet-ISA board. Please refer to the Software
Keyword section of this manual for the available range of values.
Message: BOCANW-NW-172: ISA IRQ number out of range.
Meaning: The Ethernet-ISA board only supports eight IRQ channels.
Action: Specify a valid IRQ number in NET.CFG to match the jumper setting
on the Ethernet-ISA board. Please refer to the Software Keyword
section of this manual for the available range of values.
Message: BOCANW-NW-180: DMA number is not necessary for PCI device.
Meaning: The Ethernet-PCI board does not require a DMA setting.
Action: Remove DMA from NET.CFG.
============================================================================
Netware Server Driver Custom Counters
============================================================================
1) Heart Beat Error:
This error indicates that a collision input on the AUI failed
to activate within 20 network bit times after terminating
transmission. This indicates a transmitter problem.
2) Memory Time Out:
This counter is incremented when the board does not get bus master
resource to read or write to memory in the systems
3) Tx Babbling Error:
This counter indicates that the transmitter has been
transmitting longer than the time required to send the
maximum size frame. This counter is incremented if 1519 bytes
or greater are transmitted.
4) Tx Under Flow Error:
This error indicates that a frame transmission was aborted
because the board could not get the data from memory in time.
5) Tx Buffer Error:
This error indicates that the frame buffers which were queued for
transmission were not set up correctly by the software.
6) Rx ECBs Over 16 Meg Count:
This is a standard statistics counter counting receive Event Control
Blocks which are located above 16 Megabytes.
7) Tx ECBs Over 16 Meg Count:
This is a standard statistics counter counting transmit Event
Control blocks which are located above 16 Megabytes.
8) Packet Used 2ECBs:
This is a statistic counter indicating that a packet used 2 Event
Control Blocks. NDIS 2.0.1 Driver Error Messages
Message: BOCAND-DOS-1: Unable to open Protocol Manager
Meaning: The NDIS stack is not configured correctly
Action: Check and correct your configuration.
Message: BOCAND-DOS-6: Out of memory while allocating buffers
Meaning: The driver failed to allocate buffers.
Action: Check your system configuration, including TX/RX Buffers in
PROTOCOL.INI.
Message: BOCAND-DOS-7: Protocol Manager device error
Meaning: The NDIS stack is not configured correctly
Action: Check and correct your configuration.
Message: BOCAND-DOS-8: Bad status for Protocol Manager
Meaning: The NDIS stack is not configured correctly.
Action: Check and correct your configuration.
Message: BOCAND-DOS-9: Can't find PROTOCOL.INI entry
Meaning: The NDIS stack is not configured correctly.
Action: Check and correct your configuration.
Message: BOCAND-DOS-10: Protocol Manager ioctl failed
Meaning: The NDIS stack is not configured correctly.
Action: Check and correct your configuration.
Message: BOCAND-DOS-11: Protocol Manager registration failed
Meaning: The NDIS stack is not configured correctly.
Action: Check and correct your configuration.
Message: BOCAND-DOS-13: Physical address from VDS is above 16M,
can't handle it.
Meaning: The Ethernet-ISA cannot handle buffers above 16M. (16 bit addressing)
Action: Modify your system configuration to load the driver below 16 Meg.
Message: BOCAND-DOS-15: Device not found
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
Ethernet board.
Message: BOCAND-DOS-16: PCI scan specified, device not found
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Otherwise, replace the board.
Message: BOCAND-DOS-17: PCI scan can only execute on a 386 and higher
processor
Meaning: The PCI bus is not available on your system. The PCI bus is
only supported on systems with a 386 or higher processor.
Action: Do not specify PCI for BUSTYPE with your current system.
Message: BOCAND-DOS-18: PnP scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the Ethernet-ISA+ board is physically installed properly.
Otherwise, replace the board.
Message: BOCAND-DOS-19: VESA scan specified, device not found
Meaning: The driver cannot locate the BEN110/120 board on the VL bus.
Action: The BEN110/120 is not a VL board so this error should not occur.
Verify that the board is physically installed properly.
Otherwise, replace the board.
Message: BOCAND-DOS-20: ISA scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the Ethernet-ISA board is physically installed properly.
Otherwise, replace the board.
Message: BOCAND-DOS-21: Board failed checksum test. Please run configuration
utility
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
board.
Message: BOCAND-DOS-22: Ethernet DMA doesn't match protocol.ini
Meaning: The specified DMA setting does not match the hardware setting for
the Ethernet device.
Action: Remove the DMA setting from PROTOCOL.INI or match the DMA setting
in PROTOCOL.INI with the hardware jumper setting.
Message: BOCAND-DOS-23: WARNING: Ethernet IRQ found =
Meaning: The IRQ setting in PROTOCOL.INI does not match the hardware IRQ
setting.
Action: Remove the IRQ setting from PROTOCOL.INI or match the IRQ setting
in PROTOCOL.INI with the hardware jumper setting.
Message: BOCAND-DOS-24: Ethernet IRQ doesn't match protocol.ini
Meaning: The IRQ setting in PROTOCOL.INI does not match the hardware IRQ
setting.
Action: Remove the IRQ setting from PROTOCOL.INI or match the IRQ setting
in PROTOCOL.INI with the hardware jumper setting.
Message: BOCAND-DOS-25: PCI scan specified, PCI bus not found!
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Otherwise, replace the board.
Message: BOCAND-DOS-26: Interrupt handler is not working, please check
your protocol.ini
Meaning: IRQ handler is not working. It is possible that PROTOCOL.INI
does not match the hardware (Ethernet-ISA only).
Action: Check your hardware jumper settings.
Message: BOCAND-DOS-27: ISA IRQ number out of range
Meaning: The Ethernet-ISA only supports eight IRQ channels.
Action: Specify a valid IRQ number in PROTOCOL.INI to match the jumper
setting on the ISA board. Refer to the Software Keyword section
of this manual for the available range of values.
Message: BOCAND-DOS-28: ISA DMA number out of range
Meaning: The Ethernet-ISA only supports four DMA channels.
Action: Specify a valid DMA number in PROTOCOL.INI to match the jumper
setting on the ISA board. Refer to the Software Keyword section
of this manual for the available range of values.
Message: BOCAND-DOS-29: WARNING: DMA number is not necessary for PCI device
Meaning: The Ethernet-PCI board does not require a DMA setting.
Action: Remove the DMA setting in PROTOCOL.INI.
Message: BOCAND-DOS-30: WARNING: DMA number is not necessary for VESA
device
Meaning: The BEN110/120 board does not require a DMA setting.
Action: Remove the DMA setting in PROTOCOL.INI.
Message: BOCAND-DOS-31: DMA number is already in use by another Ethernet
device
Meaning: The specified DMA number is already in use by another Ethernet device.
Action: Modify the DMA setting on the hardware and/or modify the DMA
setting in PROTOCOL.INI.
Message: BOCAND-DOS-32: IRQ number is already in use by another Ethernet device
Meaning: The specified IRQ number is already in use by another Ethernet device.
Action: Modify the IRQ setting on the hardware and/or modify the IRQ setting
in PROTOCOL.INI.
Message: BOCAND-DOS-33: Ethernet device with specified IOBASE is already in use
Meaning: The specified IO Address number is already in use by another Ethernet
device.
Action: Modify the IO Address setting on the hardware and/or modify the
IO Address setting in PROTOCOL.INI.
============================================================================
NDIS 3.0 Driver Error Messages
============================================================================
Windows NT
Windows NT error messages are logged into a log file. The user may view
the file with the Event Viewer. Error messages from the driver appear
with "BOCAN3" prefix followed by "Missing Configuration Parameter" message
and several hex numbers. The hex numbers must be converted to decimal to
correspond to the error numbers in this manual.
Message: BOCAN3-9: IO base address is already in use by another Ethernet device
Meaning: The specified IO Address number is already in use by another Ethernet
device.
Action: Modify the IO Address setting on the hardware and/or modify the IO
Address setting in the setup dialog box.
Message: BOCAN3-13: IRQ and/or DMA number is already in use by another Ethernet
device
Meaning: The specified IRQ and/or DMA is already specified by another Ethernet
device.
Action: Modify the IRQ and/or DMA settings in the setup dialog box.
Message: BOCAN3-17: PCI scan specified, PCI bus not found
Meaning: PCI scan specified on a non-PCI system..
Action: Modify the bus to scan in setup dialog box to the correct bus to
scan.
Message: BOCAN3-18: PCI scan specified, device not found
Meaning: The driver cannot locate the Ethernet-PCI board on the PCI bus.
Action: Verify that the PCI board is physically installed properly.
Otherwise, replace the board.
Message: BOCAN3-19: LanceOpenAdapter failed
Meaning: The configuration is setup incorrectly.
Action: Re-run the setup program.
Message: BOCAN3-20: Device at specified IO base address not found
Meaning: The Ethernet device cannot be found at the specified IO Address.
Action: Verify that the IO Address matches with the board. Otherwise,
remove the IO Address specification from the setup.
Message: BOCAN3-21: Device not found
Meaning: The driver cannot find any Ethernet device.
Action: Verify that a Ethernet board is installed or replace the resident
Ethernet board.
Message: BOCAN3-22: PnP scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA+ board on the ISA bus.
Action: Verify that the Ethernet-ISA+ board is physically installed properly.
Otherwise, replace the board.
Message: BOCAN3-23: VESA scan specified, device not found
Meaning: The driver cannot locate the BEN110/120 board on the VL bus.
Action: The BEN110 is not a VL board so this error should not occur.
Verify that the board is physically installed properly.
Otherwise, replace the board.
Message: BOCAN3-24: ISA scan specified, device not found
Meaning: The driver cannot locate the Ethernet-ISA board on the ISA bus.
Action: Verify that the Ethernet-ISA board is physically installed properly.
Otherwise, replace the board.
----*----
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.