BootWare Configuration Supplement

BootWare/3C5X9
Tri-Protocol/McAfee RomShield/Built-in Configuration Facility

Version Information The information contained in this document applies to
BootWare/3C5X9 version 2.00. Note: This version features McAfee RomShield
boot sector anti-virus firmware, and a ROM-based adapter configuration
facility, which is also used to select BootWare's boot protocol and
configure other operating parameters.

Adapters Supported BootWare/3C5X9 supports all 3Com EtherLink III (3C509,
3C529, 3C579, and 3C509B),Ethernet adapters for the ISA, Micro Channel and
EISA, Bus & the Farallon EtherWave ISA adapter. This release of BootWare
features updatable ROM technology which is supported by the 3C509B adapter
series. A software update utility is provided for future code updates.

Environments Supported
BootWare/3C5X9 features six selectable boot protocols; Native NetWare
802.2, Native NetWare 802.3, Native NetWare Ethernet_II, RPL, BOOTP,
and DHCP.

NetWare Modes
Three Ethernet frame types are supported in NetWare mode; NetWare 802.2,
NetWare 802.3, and NetWare  Ethernet_II. Choose a frame type that is
supported by your file server(s). Note that NetWare v3.12 and v4.x support
NetWare 802.2 as the default frame type; all older versions support 802.3
as the default.

NetWare mode supports the remote booting of all currently available
versions of PC-DOS, MS-DOS,  DR-DOS, and Windows 95.

In NetWare mode, BootWare supports either ODI drivers, or older IPX
drivers. When using ODI drivers, please note that the Novell RPLODI utility
must be loaded after LSL, and before the ODI driver itself is loaded. Do
NOT run RPLFIX on the boot image. BootWare/3C5X9 supports DOS 5 and higher
without any patch. 

RPL Mode
RPL mode supports NT Server 3.0/4.0, LAN Manager 2.0C and newer, and IBM
LAN Server 3.0/4.0. Remote boot of various versions of DOS and Windows 95
are supported, depending on the network operating system.

Sample installation files  can be found on the BootWare Utility Disk by
running the program BWVIEW. Users are strongly encouraged to examine the
examples found on BootWare Utility Disk.

TCP/IP Modes
TCP/IP modes require a TFTP service (daemon) and a  DHCP or  BOOTP service
(daemon) to be loaded at the host. Windows 95 and  most versions of DOS
can be booted. Both BOOTP and DHCP modes perform implicit ARPs, allowing
the boot image file to reside on alternate servers.


INSTALLING THE BootWare ROM
BootWare is installed in the 28-pin socket on the adapters; pay special
attention to the position of the notch on the ROM socket, making sure that
it aligns correctly with the notch on the ROM. Consult the 3Com EtherLink
III Adapter Guide on the location of the 28-pin ROM socket. Run the adapter
configuration software provided by 3Com to enable the Boot ROM. When
selecting ROM Size, follow the guidelines below:

Plug and Play
This version of BootWare/3C5X9 does not yet support the Plug and Play
specification. The following steps should be followed when the 3C509B is
installed in workstations with a Plug and Play BIOS:


1.  Insert the adapter with BootWare/3C5X9 into one of the workstation's
empty slots.
2.  Run 3Com's Configuration/Diagnostic program.
3.   Disable the Plug and Play feature by changing the Plug and Play
software option setting.
4.   Select a ROMSize of 32K and a non-conflicting ROM Base Address.
Save the settings.

BootWare/3C5X9 version 2.00 features updatable ROM technology; when the
Plug and Play specification is extended to support boot ROMs, Lanworks
will provide the necessary software to update the boot ROM on a 3C509B
at no extra cost.

ADAPTER CONFIGURATIONS SUPPORTED BY BootWare/3C5X9

Accessing the built-in configuration facility BootWare/3C5X9 features a
built-in setup facility which may be used to view or change the
configuration of your EtherLink III adapter. The setup utility may be
accessed by pressing <Ctrl><ALT><B> within 3 seconds when the message
"Initializing EtherLink III Adapter" is displayed.

3C529 and 3C579 Note: Use the Micro Channel Reference Disk or the EISA
Setup Program to configure I/O base, interrupt level, ROM size/base, and
media type.

Configuring BootWare with BWUPDATE
The BWUPDATE utility may be used to configure BootWare/3C5X9's
operating parameters, or to update to newer versions of BootWare firmware
(firmware updates supported on the 3C509B adapter only). The following
parameters and values are supported:

Option		   Option Values		   Option Function

Boot Protocol	ETHERNET_802.2, ETHERNET_802.3,      Change Boot Protocol
		ETHERNET_8137, RPL, BOOTP, DHCP      used by BootWare

Config Menu	ENABLE , DISABLE		     Enable or Disable
						     ROM-based configuration
						     facility

Menu Key	ENABLE , DISABLE		     Enable or Disable menu
						     key display
RomShield	ENABLE , DISABLE		     Enable or Disable McAfee
						     RomShield anti-virus
						     functions
Default Boot	LOCAL , NETWORK 		     Default Boot from local
						     disk or network

BWUPDATE supports menu, command line, and configuration file parameters;
please refer to the BootWare User Guide for complete details.


ERROR MESSAGES The error messages described below are specific to
BootWare/3C5X9. Please refer to the "BootWare User Guide" for information
on generic error messages.

Unable to expand BootWare to 32K. Press <F1> to continue.
BootWare is unable to perform virtual paging; try to change the ROM Size to
32K & select a ROM Base address that is conflict free. If problem is not
solved, disable the ROM-based configuration facility by running BW5X9.EXE.

32K BootWare checksum is invalid. Press <F1> to continue.
Virtual Paging requires that the 32K region surrounding BootWare is not
occupied. As an example, a ROM Size/Base of 8K,D600 will need a
conflict-free region of D000-D7FFh.

Could not find 3C5X9
Run the configuration software and make sure that it is appropriate
for your workstation.

3C5X9 IO conflict
Caused by either an I/O Address conflict between 3C5X9 & some other
device, or 3C5X9 installed in an 8-bit slot.

3C5X9 cannot run on 86/88/186 machines
The 3C5X9 must be installed in a 16-bit slot on at least a
286-based workstation.

IRQ7 not supported with NetWare
Choose another interrupt level.

Unable to find 3C529 ID
The Micro Channel Adapter ID assigned to the 3C529 (627C, 627D,
62F7 & 62F6) was not found in any slots.

Rx2 Rx2 Rx2...
Timeout waiting for reply from file server. Could be caused by:
- 3C5X9 Transceiver/Media Type incorrectly configured
- incompatible Ethernet standard (802.3 vs 802.2 vs Standard 
Ethernet 8137)
- not connected to an active file server

ERROR: Ethernet card is improperly installed or not connected to the
network. Adapter is not connected to an active Ethernet segment or the
media type is incorrectly configured.

ROMShield requires 32K ROMSize or 3C5X9B requires 32K ROMSize
Both ROMShield & 3C5X9B requires 32K ROM Size. Use 3Com's Config/Diag
program to set ROMSize to 32K.


ROM-BASED CONFIGURATION FACILITY

Invalid Adapter Configuration. Use 3Com Config/Diag program to reconfigure
card Before entering the configuration menu, BootWare will verify the
integrity of the configuration data by checking the checksum. The
configuration facility will be disabled when a invalid checksum is
detected. Use 3Com's EtherLink III Configuration and Diagnostic Program
(3C509.EXE) to reconfigure and diagnose the adapter.

Detected potential I/O Base conflict. OR Detected potential ROM Base
conflict. BootWare detected a potential conflict at new I/O or ROM Base
location; please use a different selection.

Value Out of Range. Use Default value (0,0000)
EtherLink III adapter contains a setting that is not recognized by
BootWare. Avoid using BootWare's ROM-based configuration facility to
configure the adapter.

Newer BootWare version is available for this adapter.
Newer BootWare version is available which may offer additional features
/ improved performance with this adapter.

New EtherLink III found. Need new BootWare version.
BootWare version being used is incompatible for this adapter; please
upgrade BootWare version.

Problems and Solutions Boot ROM test failed under 3Com's
Configuration/Diagnostic Program The test result might indicates that the
ROM Base region is occupied by a memory manager. The solution is to exit
the Config/Diag Program without saving any settings, reboot the machine
without any memory manager and re-run the Config/Diag Program. If the Boot
ROM test still fails, choose another ROM Base Address.

ELNK3.SYS as Default Image filename and Wildcard support in BOOTCONF.SYS
Under Novell NetWare, default image file ELNK3.SYS is added in addition
to NET$DOS.SYS. Wildcard character (?) for network number and node number
in BOOTCONF.SYS is also supported. For example, BOOTCONF.SYS
can have the following line:

     0x????????, 00??3??432?? = WILDCARD.SYS



