home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
NBR11.ZIP
/
README.DOC
< prev
next >
Wrap
Text File
|
1993-02-16
|
28KB
|
760 lines
Readme.Doc for NIC Bridge/Async Version 1.1j
Feb 15 1993
Copyright (c) Eighth Layer Systems 1990-1993.
All rights reserved.
The <PageUp>, <PageDown>, <Home> and <End> keys may be used to
view this document from within the NicDoc utility.
This documentation is formatted with 23 line pages. It contains
IBM PC type block graphics characters.
┌──────────────────────┐
│ Update: Version 1.1j │
└──────────────────────┘
Version 1.1j of NIC Bridge/Async contains no functional enhancements
over version 1.1i. This release contains only bug fixes for problems
known as of February 15, 1993. These fixes are limited to the NAsync and
NBridge device drivers as detailed below.
FIXED BUGS:
NAsync.Os2/O86
- Direct Port Mode on OS/2 MCA PCs would not work,
causing a system trap. This has been rectified,
but the drivers do NOT support shared interrupts.
Alternate fix: use OS/2 Filesystem Mode.
NAsync.Os2/O86/Dos/D86
- Some protocols, particularly IBM protocols such as the
LANDD.SYS component of IBM Communications Manager,
would not work and/or cause a system trap.
NBridge.Os2/O86/Dos/D86
- In Token Ring Source Routing Mode, communications through
another Source Routing Bridge would not work if that other
bridge had a non zero Bridge Number.
- In Ethernet Transparent Bridge Mode, broadcast filtering
would not work on networks with more than a moderate level
of traffic.
UNFIXED BUGS:
NBridge.Os2/O86/Dos/D86
- In Ethernet Transparent Bridge Mode, NBridge may not be
able to peacefully coexist with some network protocols
on a shared ethernet adapter. This is most likely to be
true with NICs which do not support Multiple Data Transfers
and which use the NDIS ReceiveAhead receive method.
Workaround: use a dedicated PC or a dedicated Ethernet
adapter for Ethernet bridging.
- The Protocol.Ini FILTERBC_MAC parameter has been reported
to cause error messages on occasion. Workaround: disable
the parameter with a semicolon (;) or modify Protocol.Ini.
FURTHER RECOMMENDATIONS:
It has been observed that most reasonably sized networks generate
a great deal of broadcast traffic. This virtually requires that
broadcast filtering be used for any remote connections. Note that
broadcast filtering may not work with TCP/IP on Ethernet, however.
A Token Ring bridge may use the [SRTOK_NIF] SRBC parameter.
Remember to enable broadcast filtering ONLY for local Ethernet or
Token Ring adapter ports. For example:
; Protocol.Ini fragment:
; Note: example only. NBridge can't bridge Ethernet
; and Token Ring simultaneously.
[NBRIDGE_NIF]
BINDINGS = "SRTOK_NIF", "ELNKII_NIF, "NASYNC_NIF", "NASYNC_NIF2"
FILTERBC_MAC = YES, YES, NO, NO, NO, NO, NO, NO, NO
DOCUMENTATION CHANGES:
Only this document file, Readme.Doc, has been updated. The
updates are limited to this section: "Update: Version 1.1j".
PLANNED ENHANCEMENTS:
Version 1.1j of NIC Bridge/Async has been released to fix some
known problems, but has not been extensively tested.
It will be followed with a more extensively tested version 1.1k.
This upcoming version 1.1k will support some mechanism to allow
ethernet broadcast filtering with TCP/IP. This will involve either
allowing certain broadcast ARP requests to pass the broadcast
filter or allowing the bridge to generate ARP replies locally.
REPORTED COMPATABILITY:
With the fixes contained in version 1.1j of NIC Bridge/Async,
the following configurations have been reported to work:
- IBM NetBEUI on OS/2.
- IBM Lan Support Program on DOS.
- IBM Communications Manager on OS/2.
- IBM TCP/IP on OS/2.
- Microsoft NetBEUI on OS/2 and DOS.
- Microsoft TCP/IP on OS/2 and DOS.
- Banyan Vines on OS/2.
SOFTWARE AVAILABILITY:
The NIC Bridge/Async software was previously available as
Nbr11i.Zip. For version 1.1k and subsequent releases it will
be available as Nbr11.Zip. Currently the file size is
approximately 380 KBytes.
NIC Bridge/Async is available on Compuserve in the MSNETWORKS
forum library 7 (LM/Remote Access) as well as in the OS2DF2 forum
library 3 (LAN Server).
NIC Bridge/Async is reportedly available via FTP at:
comlab.gatech.edu as /pub/lanman/ndis/NAME
lanman.gatech.edu as /pub/lanman/ndis/NAME
ftp-os2.nmsu.edu as pub/os2/new/NAME
hobbes.nmsu.edu as pub/os2/new/NAME
comp.binaries.os2 as UNKNOWN
Where NAME is nbr11i.zip or nbr11.zip.
NIC Bridge/Async is also available on BIX in the LANS section.
┌────────────────┐
│ NICDOC UTILITY │
└────────────────┘
The NicDoc utility can be used to read the documentation provided
with NIC Bridge/Async. Like all NIC Bridge/Async utilities it is a "bound"
application and will run under either DOS or OS/2. It requires less than
200 KBytes of free memory to run. The error message "SYS2090: The system is
unable to load the program." indicates insufficient free memory.
When NicDoc is run it will attempt to load and display the file
Readme.Doc. This file will first be searched for in the directory specified
by the environment variable NICDIR. If this environment variable is not set,
the search defaults to the directory C:\NIC11. If the Readme.Doc file is
not found the current directory is searched and if this fails NicDoc will
terminate with the error message "Error opening README.DOC".
Once the file has been loaded and displayed the <PageUp>, <PageDown>,
<Home> and <End> keys may be used to view the document.
Functions displayed at the bottom of the screen may be selected with
the left and right cursor keys. Pressing <Enter> will select a function.
To advance one page press <PageDown> or select [Next]. To go back one
page press <PageUp> or select [Prev]. Pressing <Home> or <End> sets the view
to the first or last page.
Selecting the [Index] function allows other NIC Bridge/Async document
files to be selected and viewed.
NicDoc may be exited by pressing the <Esc> key or selecting [Exit].
┌──────────────────────┐
│ EIGHTH LAYER SYSTEMS │
└──────────────────────┘
NIC Bridge/Async is brought to you by Eighth Layer Systems in Ottawa,
Ontario, Canada. Eighth Layer Systems is solely owned by Michael A. Reid.
Version 1.1j of NIC Bridge/Async is free of charge subject to the
terms of a license detailed in the LICENSING section below. As no fee is
charged, no support should be expected. I will attempt, however, to respond
to simple questions or bug reports directed to my Compuserve mail address as
time permits.
I may be reached at:
Compuserve: 76236,1403
Internet: 76236.1403@CompuServe.COM
┌───────────┐
│ LICENSING │
└───────────┘
This software, known as NIC Async, NIC Bridge, NIC Bridge/Async, the
related drivers, utilities and documentation are copyrighted by Eighth Layer
Systems. This software is licensed and not sold or given away. All rights are
reserved.
You are granted a cost free perpetual license to use version 1.1j of
this software at your own risk. Eighth Layer Systems assumes no liability for
any damages whatsoever that may arise from the use of this software or any
information contained within.
Version 1.1j of this software may be copied or otherwise distributed
with the following restrictions:
(1) No fee may be charged for the copying or distribution of this
software in excess of 20 U.S. dollars.
(2) Any fee charged for the copying or distribution of this software
must be disclosed to the customer specifically as a fee for
copying or distribution only.
(3) All files provided with this software must remain intact and
unmodified in any copy or distribution.
(4) This software may not be included with any commercial product
without the express written permission of Eighth Layer Systems.
Failure to comply with any of these restrictions terminates this license.
Compliance with export controls on encryption or other technologies
are the responsibility of the exporter.
The 3Com NDIS Protocol Manager version 2.0E and related utilities
are bundled with NIC Bridge/Async for use on standalone PCs. The 3Com NDIS
Protocol Manager and related utilities are Copyright 1988 Through 1991
3Com Corporation.
The 3Com NDIS Protocol Manager and related utilities may be found in
the PROTMAN directory of the install disk and are copied to the PROTMAN
subdirectory of the target directory when NIC Bridge is installed.
Use of the 3Com software is subject to a license granted by 3Com to
Eighth Layer Systems as reproduced below.
DEVELOPER'S OBJECT CODE LICENSE
Copyright 1988 Through 1991 3Com Corporation
All Rights Reserved
By using this object code and related documentation as defined below,
you are agreeing to the terms and conditions contained in this Developer's
Object Code License ("License").
1. 3Com Adapters Description. 3Com Adapters are the Etherlink and
TokenLink adapters which are identified by the following 3Com product numbers:
3C501, 3C503, 3C503-16, 3C505, 3C507, 3C523, 3C527, 3C603, 3C605, 3C503-TP,
3C503-16-TP, 3C507-TP, 3C523-TP and 3C527-TPX, (collectively referred to as
"3Com Adapters").
2. Licensed Software Description. The object code and related
documentation to be used exclusively with 3Com adapters is defined as follows:
(i) 3Com Driver and Diagnostic program; (ii) DOS NDIS Utilities which includes
NETBIND.EXE, PROTMAN.EXE, PROTMAN.DOS, PRO.MSG, PROH.MSG, READPRO.EXE and
UNBIND.EXE; and (iii) OS/2 NDIS Utilities which includes NETBIND.EXE,
PROTMAN.OS2, PROTCHK.EXE, READPRO.EXE, UNBIND.EXE and RELOAD.EXE; ("Licensed
Software").
3. License Grant. This Licensed Software is being licensed to you to be
used exclusively in conjunction with 3Com Adapters. 3Com and Microsoft
Corporation co-developed the NDIS Utilities, which are incorporated into the
Licensed Software, and therefore, in order to use or distribute the Licensed
Software with any other type of adapters other than the 3Com Adapters, you
must contact Microsoft Corporation directly.
This license grant is a non-exclusive, royalty-free, perpetual license
to use and distribute the unmodified version of the Licensed Software. You may
copy and distribute the unmodified copies of the Licensed Software as you
receive it, in any medium, so long as the Licensed Software is used only with
3Com Adapters and provided that you: (i) distribute only the latest or most
current version of the Licensed Software; (ii) provide technical support to
the end user or installer of the Licensed Software; (iii) conspicuously and
appropriately publish on each copy a valid copyright notice; (iv) keep intact
the notices on all files that refer to this License and to the absence of any
warranty on the Licensed Software; and (v) give any other recipients of the
Licensed Software a copy of this License along with the Licensed Software.
3Com shall have no obligation to you or any third party to provide any
support or maintenance for, or new releases or updates to, the Licensed
Software. Modification, reverse engineering, reverse compiling or disassembly
of the Licensed Software are expressly prohibited. The Licensed Software may
be downloaded from 3Com's Cardboard BBS or Ask3Com Forum on CompuServe.
4. Limited Warranty and Limitation of Liability. BECAUSE THIS LICENSED
SOFTWARE IS PROVIDED TO YOU FOR FREE OF CHARGE, 3COM MAKES NO WARRANTIES,
EXPRESS OR IMPLIED IN FACT OR BY OPERATIONS OF LAW, STATUTORY OR OTHERWISE, AS
TO ANY MATTER WHATSOEVER. IN PARTICULAR, 3COM SPECIFICALLY DISCLAIMS ANY AND
ALL WARRANTIES OF MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD-PARTY RIGHTS.
IN NO EVENT SHALL 3COM BE LIABLE TO YOU OR TO ANY THIRD PARTY FOR ANY
DAMAGES, INCLUDING WITHOUT LIMITATIONS, DIRECT, SPECIAL, INDIRECT,
CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES, LOSS OF PROFITS OR REVENUE OR
INTERRUPTION OF BUSINESS IN ANY WAY ARISING OUT OR RELATED TO THIS LICENSE OR
THE LICENSED SOFTWARE (INCLUDING BUT NOT LIMITED TO, ERRORS, OMISSIONS, OR
OTHER PROBLEMS WITH THE LICENSED SOFTWARE) REGARDLESS OF THE FORM OF ACTION,
WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT PRODUCT LIABILITY OR
OTHERWISE, EVEN IF ANY REPRESENTATIVE OF 3COM HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
5. General. You agree not to assign any rights under this License;
any attempted assignment shall be null and void and shall result in the
termination of this License. This License shall be governed by the laws of the
state of California, except for California's conflict of law rules.
This License represents the entire agreement between the parties
regarding the subject matter hereof and supercedes any and all prior or
contemporaneous agreements or understandings, whether written or oral, between
them relating to the subject matter hereof. This License may only be amended
or modified by a writing signed by both parties.
END OF 3COM LICENSE AGREEMENT
┌────────────────────────────────────┐
│ INSTALLATION/GENERAL CONFIGURATION │
└────────────────────────────────────┘
There are two main steps required to make use of this software: the
Installation/General Configuration step and the Setup/Main Configuration step.
Any network software needed, such as MS Lan Manager or IBM Lan Server, should
be installed prior to NIC Bridge/Async installation. This allows the automatic
determination of General Configuration parameters.
Installation/General Configuration is performed with the Install.Exe
utility. It creates a general configuration file NIC.CFG, makes modifications
to Config.Sys or Autoexec.bat to add a directory to the system command search
path and set the NICDIR environment variable, and copies files from an install
disk to a target disk. It makes no changes to the network configuration.
Setup/Main Configuration is performed with the MS Lan Manager
Setup.Exe, IBM Lan Server LanInst.Exe, NicSetup.Exe, and/or NicCfg.Exe
utilities. This will create or modify the network configuration after
Installation/General Configuration has been done.
If NIC Bridge/Async was received in a ZIP file format it must first be
decompressed to create an install disk. The command "Pkunzip -d xxx.Zip A:\"
will create an install disk on a floppy in drive A:. This requires a floppy
disk with a capacity of at least 1.2 megabytes.
To initiate Installation and General Configuration insert the install
disk into the A: drive and enter the command "A:\Install". Reboot the PC when
this completes. The command "NicDoc" can be used to read the NIC Bridge/Async
documentation files.
┌──────────┐
│ PLANNING │
└──────────┘
The main component of NIC Async is an NDIS adapter driver for serial
ports. It can be used virtually anywhere that an NDIS driver for Ethernet or
Token-Ring adapters can be used. It may be used alone or with NIC Bridge.
A diagram illustrating the use of NIC Async alone is shown below.
This configuration allows a workstation to remotely access a single server.
┌─────────────┐ ┌─────────────┐
│ Workstation │ │ Server │
└─────────────┘ └─────────────┘
│ │
┌─────────────┐ ┌─────────────┐
│ NIC Async │ │ NIC Async │
│ NDIS Driver │ │ NDIS Driver │
└─────────────┘ └─────────────┘
│ │
┌───────────┐ Fixed or Dialup Link ┌───────────┐
│ Modem │───────────/ /──────────│ Modem │
└───────────┘ └───────────┘
The main component of NIC Bridge is an NDIS protocol driver. It can
be bound to multiple NDIS adapter drivers and provide bridging between the
adapters. It may be used alone or with NIC Async.
A diagram illustrating the use of NIC Bridge alone is shown below.
This configuration provides local ethernet bridging between two segments.
NIC Bridge can also be used to provide Source Routing Bridging with IBM
Token Ring Adapters.
┌───────────────────────────────┐
│ NIC Bridge NDIS Protocol │
└───────────────────────────────┘
│ │
┌────────────┐ ┌────────────┐
│ Ethernet │ │ Ethernet │
│ NDIS Driver│ │ NDIS Driver│
└────────────┘ └────────────┘
│ │
┌────────────┐ ┌────────────┐
Ethernet Segment A │ Ethernet │ │ Ethernet │ Ethernet Segment B
────────//─────────│ Adapter │ │ Adapter │────────//─────────
└────────────┘ └────────────┘
A diagram illustrating the use of NIC Async and NIC Bridge together
is shown below. This configuration provides remote access to all network
resources. This remote access can be provided to a single user or to multiple
users on another network with the same configuration.
NIC Bridge can also be used to provide remote Source Routing Bridging
with IBM Token Ring Adapters.
┌───────────────────────────────┐
│ NIC Bridge NDIS Protocol │
└───────────────────────────────┘
│ │
┌────────────┐ ┌────────────┐
│ NIC Async │ │ Ethernet │
│ NDIS Driver│ │ NDIS Driver│
└────────────┘ └────────────┘
│ │
To Remote User or │ ┌────────────┐
Remote Network ┌───────────┐ │ Ethernet │ Local Ethernet Network
────────//──────────│ Modem │ │ Adapter │────────//─────────────
└───────────┘ └────────────┘
The configuration possibilities shown in the preceding pages are just
three of those possible. Multiple NIC Async drivers may be loaded on a single
PC to allow multiple simultaneous remote connections. NIC Bridge, a multiple
port bridge, can be used to tie together local networks, remote networks and
remote standalone PCs all at the same time.
For remote access to a single server by a remote PC the NIC Async only
configuration should be considered first. This configuration is relatively
easy to setup and has low resource requirements. It provides remote users
with access to the server on which NIC Async is installed. Other servers and
network resources will not be accessible to remote users, however.
Remote access to multiple network servers requires the use of NIC
Bridge together with NIC Async. This is shown in the configuration on the
preceding page. The Bridge PC may run under DOS or OS/2 and be a standalone
dedicated Bridge PC, a network workstation or a network server. A dedicated
Bridge PC is however, recommended for reasons of performance and simplicity.
NIC Bridge can provide Token Ring Source Routing Bridging with IBM
Token Ring adapters. This requires the use of special NDIS drivers provided
with NIC Bridge. In this release these drivers will work only with NIC Bridge
and cannot be shared by other NDIS protocols. Thus, the installation of NIC
Bridge on a PC which already makes use of an IBM Token Ring adapter will
require the addition of another adapter.
It should also be noted that the use of more than two serial ports
with NIC Async will ususally require the use of a multi-port serial card
under OS/2. The multi-port serial card used must provide OS/2 drivers.
Further information on NIC Async may be found in NAsync.Doc or by
selecting "NIC Async" from the NicDoc Index.
Further information on NIC Bridge may be found in NBridge.Doc or by
selecting "NIC Bridge" from the NicDoc Index.
The following pages contain information on NDIS concepts and is
recommended reading for those who are unfamiliar with NDIS.
┌───────────────┐
│ NDIS CONCEPTS │
└───────────────┘
NDIS is an acronym for the Network Driver Interface Specification.
It was jointly developed by 3Com and Microsoft and is supported by many
network software vendors and network adapter manufacturers. NDIS is currently
specified for both DOS and OS/2 and will soon include Windows NT.
NDIS provides a published software interface between network protocol
software and network adapter drivers, also known as MAC drivers. The interface
is largely equivalent to the interface between the Data Link and Network
layers of the OSI reference model. The position of the NDIS interface relative
to the OSI reference model is illustrated on the following page.
The introduction of published network adapter interface specifications
such as NDIS is a major advance over prior proprietary interfaces. It allows
the development of network protocol software which runs on a wide range of
hardware and the development of network adapter drivers which work with a wide
variety of network protocols. It also makes feasible the development of
independent network software such as NIC Bridge and NIC Async.
OSI Reference Model
┌──────────────┐ ────────────────────────────
│ Application │
├──────────────┤
│ Presentation │ NETWORK SOFTWARE
├──────────────┤
│ Session │ ────────────────────────────
├──────────────┤
│ Transport │
├──────────────┤
│ Network │ NDIS PROTOCOLS
├──────────────┤ ──────────────────────────── <- NDIS INTERFACE
│ Data Link │ NDIS MAC DRIVERS
├──────────────┤ ────────────────────────────
│ Physical │ ADAPTERS & CABLING
└──────────────┘ ────────────────────────────
The main component of NDIS is the Protocol Manager. The Protocol
Manager is implemented as a device driver, usually named Protman.Dos or
Protman.Os2. This device driver must be loaded before any NDIS protocols
or MAC drivers.
When the Protocol Manager loads it will read and process protocol and
MAC driver configuration data from a Protocol.Ini file. This configuration
data is made available to NDIS protocols and MAC drivers when they load and
register with the Protocol Manager.
The Config.Sys fragment shown below is typical for IBM Lan Server. The
Protocol Manager is loaded first, followed by the NDIS protocol NetBEUI and
the NDIS MAC driver IBMTOK for an IBM Token Ring adapter. The "/I:C:\IBMCOM"
parameter to the Protocol Manager specifies that the Protocol.Ini file can be
found in the directory C:\IBMCOM.
Config.Sys fragment:
DEVICE = C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE = C:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE = C:\IBMCOM\MACS\IBMTOK.OS2
The Protocol.Ini file is an ASCII text file consisting of a number of
named sections. The section names are enclosed in square brackets. The example
Protocol.Ini fragment shown below is typical for IBM Lan Server. Note the
BINDINGS parameter for NetBEUI. This specifies that NetBEUI will control or
"Bind" to one MAC driver, the IBM Token Ring adapter driver.
Protocol.Ini fragment:
[PROT_MAN]
DRIVERNAME = PROTMAN$
[NETBEUI_NIF]
DRIVERNAME = NETBEUI$
BINDINGS = IBMTOK_NIF
;.... Other parameters
[IBMTOK_NIF]
DRIVERNAME = IBMTOK$
;.... Other parameters
NDIS protocols must be bound to their MAC drivers in order to transmit
and receive network packets. This binding can be initiated with the NDIS
NetBind.Exe utility. IBM OS/2 Lan Server includes the following line in
Config.Sys to initiate this binding.
RUN = C:\IBMCOM\PROTOCOL\NETBIND.EXE
This binding can also take place when the OS/2 Netwksta IFS loads. MS
OS/2 Lan Manager includes the following line in Config.Sys.
IFS = C:\LANMAN\NETPROG\NETWKSTA.SYS /I:C:\LANMAN
IBM OS/2 Lan Server includes the following IFS line in Config.Sys. The
/N parameter disables the binding action of Netwksta.
IFS = C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
The examples above show one protocol, NetBEUI, binding to one MAC
driver, the IBM Token Ring adapter driver. This is the simplest case and is
illustrated in the diagram below.
NetBEUI Protocol driver
┌──────────┐
│ NetBEUI │
└──────────┘
| <- NDIS Interface
┌──────────┐
│ IBMTOK │
└──────────┘
IBM Token Ring driver
NDIS allows more complex configurations where multiple protocols may
share and bind to multiple MAC drivers. Shown below is an illustration of a
complex configuration. NetBEUI is bound to both an IBM Token Ring adapter
driver and a 3Com Etherlink II adapter driver. NetBEUI and TCP/IP share the
Etherlink II driver. This sharing is facilitated by the Protocol Manager and
is transparent to all drivers.
NetBEUI Protocol driver TCP/IP Protocol driver
┌──────────┐ ┌──────────┐
│ NetBEUI │ │ TCP/IP │
└──────────┘ └──────────┘
| \ |
| \ |
| \ |
┌──────────┐ ┌──────────┐
│ IBMTOK │ │ ELNKII │
└──────────┘ └──────────┘
IBM Token Ring driver 3Com Etherlink II driver
A Protocol.Ini fragment for the complex configuration above is shown
below. Note the BINDINGS parameter for NetBEUI. This specifies that NetBEUI
will control or "Bind" to two MAC drivers: the IBM Token Ring adapter driver
and the 3Com Etherlink II adapter driver. The TCP/IP protocol is bound to just
one MAC driver: the 3Com Etherlink II adapter driver.
Protocol.Ini fragment:
[NETBEUI_NIF]
DRIVERNAME = NETBEUI$
BINDINGS = IBMTOK_NIF, ELNKII_NIF
[TCPIP_NIF]
DRIVERNAME = TCPIP$
BINDINGS = ELNKII_NIF
[IBMTOK_NIF]
DRIVERNAME = IBMTOK$
[ELNKII_NIF]
DRIVERNAME = ELNKII$
┌──────────────────┐
│ ACKNOWLEDGEMENTS │
└──────────────────┘
All trademarks are the property of their owners.
This includes, but is not limited to, the trademarks
of 3Com, IBM, Microsoft, and Hayes.
;