******************************************************************************
**                                                                          **
**  Part:  SF0005-10                    Znyx Corporation                    **
**                                      48501 Warm Springs Blvd.            **
**  EPIX Driver Diskette for ZX312      Suite 107                           **
**  Release 10                          Fremont, California 94539           **
**  (960122)                            USA                                 **
**                                                                          **
**  Copyright (c) 1994, 1995            510 249 0800 voice                  **
**  All Rights Reserved                 510 656 2460 fax                    **
**                                      510 656 7969 BBS                    **
**                                      ftp.znyx.com anonymous ftp          **
**                                      info@znyx.com Internet email        **
**                                                                          **
******************************************************************************

This driver release includes new and enhanced software to support the
ZNYX ZX312 PCI EtherAction LAN Adapter.

Following are release notes for individual components:



ZVERSION Utility
================

The ZVERSION utility displays version information found in device
driver files or other system files. ZVERSION can be used to display
version information for specific files, for all files in a specific
directory, or to scan an entire driver disk or even hard disk drive.

If used with the '-p' option, ZVERSION will also display operating
system platform information for files found.

Usage examples:

    ZVERSION A:\ZX312.SYS     Get version of file A:\ZX312.SYS
    ZVERSION A:\*.IMG         Get version of all .IMG files in A:\ 
    ZVERSION C:\NWSERVER\*.*  All files in C:\NWSERVER
    ZVERSION -p A:            All files on A: including platform ID



DIAG312.EXE
===========

The DIAG312.EXE program performs a confidence check on ZX312 boards.
If run without any parameters it will operate on the first ZX312
adapter it finds in the system.

DIAG312.EXE does NOT test the analog output stages of the board, so it
is possible for DIAG312.EXE to pass a board which does not work with
one or more of the media types supported.

A specific ZX312 adapter may be tested by entering the command

      DIAG312 <bus> <device>

where <bus> is the PCI bus number of the device, and <device> is the
PCI device number.

To list all PCI devices in the system, run the command

	DIAG312 LIST

A ZX312 adapter does not need to be installed to run this option.



Microsoft Windows 95
====================

ZX312 driver support is included in the Windows 95 operating system.
Be sure to only configure network adapter cards using the automated
'Add Hardware' procedure. Manual installation of plug-and-play LAN
adapters does not work properly in all cases.

Driver Update for DC21X4.SYS Shipping With Windows 95
-----------------------------------------------------

Windows 95 will hang during startup if the network adapter is not
connected to a life network. Windows 95 ships with version 2.2 of the
DC21X4.SYS driver. This driver can be found in the Windows 95 SYSTEM
directory. Run the PATCH95 program that comes on this disk to upgrade
the DC21X4 driver to version 2.3. Use the ZVERSION utility found on
this disk to determine the version of the DC21X4 driver in your Windows
95 system.



Netware DOS Client HSM
======================

Version 2.54 of the ZX312 DOS HSM supports the HSM Specification 4.0
and is compatible with all versions of Netware.

The configuration information for the DOS HSM is contained in
a configuration file, typically named NET.CFG. The NET.CFG
file on the driver disk contains examples for tayloring your
configuration. Some changes made to NET.CFG (e.g. frame types
used by the DOS client HSM) require unloading and reloading of
the LSL.COM Link Support Layer module to be activated.

Depending on your Netware installation you might have to change
the frame type used. Edit your NET.CFG file and restart the
system to begin using the frame types supported by your Netware
servers.


Netware Server Driver HSM
=========================

The included ZX312.LAN 32bit Netware Server HSM (Hardware Specific
Module) allows operation of the ZX312 adapter under various versions
of the Netware Server Operating System and other 32bit
applications.

Version 2.35 of the ZX312.LAN HSM incorporates changes to enhance
performance in newer PCI systems. Certification of this driver version 
is pending.


Buffer Configuration
--------------------

Depending on the specific configuration, each ZX312 adapter requires
approximately 50 Packet Receive Buffers. The default and maximum number
of Packet Receive Buffers can be configured using the Netware Settable
Parameters 'Minimum Packet Receive Buffers' and 'Maximum Packet Receive
Buffers'. The 'Minimum Packet Receive Buffers' parameter can only be set
in the STARTUP.NCF configuration file, whereas the maximum value can be
modified any time from the server console prompt.


Additional Driver Parameter Keywords
------------------------------------

In addition to the driver load line keywords listed in the Quick Start
Reference and the User Reference this driver supports the following
options:

INSTANCE=<instance>

        The INSTANCE keyword will load the driver for a specific adapter
        without requiring knowledge of the specific adapter's PCI bus and
        device address. Adapters are enumerated by ascending bus and
        device numbers. Moving an adapter to a different PCI slot might
        change the INSTANCE number for all of the ZX312 adapters
        in the system.

SILENT

        The SILENT keyword will inhibit generation of an alert message
        when the adapter is operated without a proper network cable
        connection.

Shared interrupts are fully supported in this version of the driver and
have been tested with various SCSI adapters, including Mylex, NCR,
Adaptec, BusLogic, QLogic.


NetWare 4
---------

The HSM can be installed on a Netware 4 file server using the INSTALL.NLM
program supplied with the Netware operating system.


NetWare 3
---------

Version 2.35 of the ZX312 HSM fully supports operation under NetWare 3.11
and NetWare 3.12.

Installation for NetWare 3.11:

    - Load PATCHMAN.NLM and LSLENH.NLM. These modules are required to
      update NetWare 3.11 LAN driver interface functionality to the
      NetWare 3.12 level.
    - Replace the MONITOR.NLM found on your NetWare 3.11 server with the
      one found on the driver disk. The NetWare 3.11 MONITOR.NLM will
      not function properly with the new HSM statistics tables and
      will ABEND the server.
    - Load MSM31X.NLM. Make sure you load version 2.20 of the Media
      Support Module or later. The server software will inform you of
      that the module name is in fact MSM.NLM. This is normal.
    - Load ETHERTSM.NLM. Make sure you load version 2.20 of the Ethernet
      Topology Support Module or later.
    - Load the ZX312.LAN HSM.

Installation for NetWare 3.12:

    - Load MSM31X.NLM. Make sure you load version 2.20 of the Media
      Support Module or later. The server software will inform you of
      that the module name is in fact MSM.NLM. This is normal.
    - Load ETHERTSM.NLM. Make sure you load version 2.20 of the Ethernet
      Topology Support Module or later.
    - Load the ZX312.LAN HSM.

Support for the monolithic NetWare 3.1X driver has been dropped in favor
of the modular LAN driver configuration using the Hardware Support Module
(HSM), as explicitly recommended by Novell, Inc.


Netware Requester for Windows/NT
--------------------------------

The driver files are arranged to eliminate installation conflicts
when the driver is installed under Windows/NT.  To install the
driver on Windows/NT, copy the contents of the \4.XX directory on
the diskette to an empty directory on the hard disk.  When installing
the driver from the installation dialog box, specify the hard disk
directory.

IMPORTANT NOTE:  When using the HSM driver with Windows NT (NetWare
Requester) and the system is shut down, the user MUST engage a hard
reset to shut down the adapter.  The current version of the NetWare
Requester does not inform the HSM (driver) that the system is being
shut down, which leaves the hardware active after a warm boot.
Failure to provide a hard reset will result in a crash or data
corruption of the system after it is re-started.

NOTE: Windows NT 3.5 and later comes with Client Support for Netware
Networks, which allows Windows NT workstations to participate in
Novell Netware networks. This software will not run over the HSM,
but use the Windows NT NDIS driver instead.



DOS and OS/2 NDIS 2.01
======================

The NDIS 2 driver is used for systems running IBM LAN Server,
Microsoft LAN Manager, Windows-for-Workgroups, Banyan Vines, Digital
Pathworks, and other software developed to Microsoft's Network Driver
Interface Specification (NDIS) 2.01.

The current OS/2 version of this driver (2.10) may hang and prevent
the system from starting if the network adapter card is not found or
otherwise not properly configured. This problem does not affect
normal operation of the driver if configured correctly. This problem
also does not affect the DOS version of the driver used for MS-DOS
and Windows-for-Workgroups, among other environments.



Netware Client HSM for OS/2
===========================

The OS/2 ODI driver is used in connection with Netware Requester For
OS/2, Lanworkplace For OS/2, and other network software using Novell's
ODI interface for OS/2.

Version 2.10 of the ZX312 DOS HSM supports the OS/2 HSM
Specification 2.1.



Windows NT NDIS Miniport
========================

The included ZX312.SYS Miniport driver supports all versions
of the Windows NT operating system. Automatic adapter detection is
supported on most hardware platforms by specifying PCI bus and PCI
device to be zero. Systems with multiple peer-to-peer or hierarchical
bus systems might require specific adapter configuration. The PCI
bus and device number address of a specific adapter can be obtained
through the DIAG312 device list option.

To run this driver on Windows NT Version 3.1, you need to obtain a
replacement NDIS.SYS system file.


Error messages under Windows NT
-------------------------------

Launch the 'Event Viewer' application found in the 'Administrative Tools'
program group.  Events generated by the ZX312 driver are marked
by the 'ZX312' name in the 'Source' column in the event listing.

Double-clicking an event line will pop-up a more detailed description of
the event.  In the case of the ZX312 network adapter, select the
'Words' option in the Data portion of the Event Detail window.  The last
word in the data window is the ZNYX-specific error code, which is
required by ZNYX personnel for problem diagnosis.



Windows NT NDIS Miniport For Alpha Systems
==========================================

The Miniport driver in the \ALPHA sub directory supports Windows
NT 3.5 and later for Alpha PCI systems. To install, run the
Network Control Panel Applet and select 'Other' when installing
a new adapter. When prompted for the driver location, respond
with A:\ALPHA if you are installing from the A: drive. The PCI
bus and device numbers may be obtained through the ARC loader
diagnostics listing.



NDIS 3.0 for Windows-for-Workgroups
===================================

This driver supports Windows for Workgroups (WfW) 3.11.

IMPORTANT NOTE:  When halting a WfW 3.11 system, a hard reset must be
performed.  Failure to do so will leave the adapter(s) active, causing
data corruption and crashes on future operations.  A CTRL-ALT-DEL
sequence will NOT deactivate the ZX312.

EXTREMELY IMPORTANT:  When re-configuring the Windows network
software or other system settings, Windows will prompt you to
reboot the system to activate any changes made. Restarting your
computer this way will NOT deactivate the ZX312 adapter.
When the system re-boots, data corruption and/or crashes may
occur.  The reset button must be pressed during a warm boot.

Driver error messages under Windows-for-Workgroups
--------------------------------------------------

Windows-for-Workgroups does not display error messages generated by the
NDIS device driver.  Instead, error messages are written to the NDIS
error log file NDISLOG.TXT. This file can be found in the Windows
directory (e.g. C:\WINDOWS).

Errors are logged into this file, one line at a time. In the case of the
ZX312 network adapter, the number at the very end of a line is the
ZNYX-specific error code, which should be noted before contacting
ZNYX Technical Support. The NDISLOG.TXT file is erased every time
Windows starts or restarts, so be sure to retain a copy for later study.


Unix Driver Installation and Configuration
==========================================


MAKEDISK.EXE
------------

In order to install the Unix drivers, you will need to prepare a floppy
disk with the driver and support files in the format appropriate for
your OS.  The MAKEDISK program is supplied to prepare device driver
installation floppy disks from files found on the floppy disk shipping
with the ZX312 adapter.

Under DOS, change to the drive that contains the ZX312 driver
disk and run the MAKEDISK utility.  Follow the directions given by the
MAKEDISK utility to generate the Unix driver disk. You can run MAKEDISK
on a computer system other than the one you're planning to install the
driver on.

Before booting the Unix system to install the driver, boot DOS and run
DIAG312 to examine your system configuration. Make a note of the PCI
bus and device numbers as well as the interrupt configured for the
adapter. With most PCI systems, the interrupt assignment is configurable
in the ROM BIOS setup.

When configuring the Unix driver under either OS, select PCI bus 0,
device 0 for automatic board detection. Automatic detection works for more
than one adapter, but is only recommended when using a single adapter.


Streams Buffer Configuration under System V Release 3:
------------------------------------------------------

For frame reception, the drivers use 2K Streams buffers.  Buffer
pools in System V Release 3 (SVR3)-style systems are configured at
kernel link time and do not dynamically adjust to load requirements.
Increasing the number of Streams buffers of the required size
(NBLK2048) will help increase your system performance.

ZX312 drivers for SVR3 automatically increase the configured
number of buffers. You will be prompted to accept the change.

Removing the ZX312 driver will not decrease the number of
buffers configured. Frequently installing and removing the ZX312
driver will result in a unnecessary large number of buffers configured.


SCO Unix Driver
---------------

Tested with SCO Unix 3.2.4, SCO ODT 3.0, and SCO Open Server 5.0.
Use the 'custom' command to install the driver.  The 'mkdev' and
'netconfig' configuration methods are both supported.

Use the 'configure' command located in /etc/conf/cf.d to configure
Streams buffer allocation for SCO Unix and SCO ODT. SCO Open Server
5.0 employs a dynamic buffer managament system and Streams buffers
need not be configured.


Sunsoft Interactive Unix Driver
-------------------------------

Tested with Interactive Unix versions 2.2, 3.0, and 4.0. Use the
'sysadm' command to install the driver. If you are running version
3.0 or newer of Interactive Unix, the driver will become part of
the network device driver subset. When configuring TCP/IP, select
picking a driver from the subset rather than specifying '3rd party
driver'. Use the 'kconfig' command to configure Streams buffer
allocation.


Novell UnixWare DLPI Driver
===========================

Installation of the Novell UnixWare Driver is fully menu-driven.

Installing the UnixWare driver requires creating a secondary driver
disk. See the description of the MAKEDISK utility in this file for
details.

During installation you will be prompted for the PCI bus and device
numbers, the interrupt configuration, and the desired media type.
Automatic adapter detection is supported for a single adapter by
configuring both PCI bus and device as zero. Use the DOS-based
diagnostic tool to obtain the bus and device numbers to configure
specific adapters.

Note that UnixWare is based on SVR4 and does not require configuration
of individual Streams buffer counts.

Unixware 1.x
------------

From the UnixWare desktop, open the System_Setup folder and launch
the Application Install utility ('Appl-n_Setup'). Within the
Application Install program select 'Uninstalled Applications' from
the 'View' pulldown menu. Choose the floppy disk drive you are
installing from.

You will then be presented with a series of menu screens. In the
first menu, select the number of ZX312 adapters you want to
install. A parameters configuration menu will come up for each adapter
being installed.

Unixware 2.x
------------

From the UnixWare desktop, open the Admin_Tools folder and launch
the App_Installer utility. From the 'Install From:' pull-down,
select the appropriate installation media (usually Disk_A). Start
the installation process after selecting the driver package in the
upper window portion by clicking on the 'Install' button.

You will then be presented with a series of menu screens. In the
first menu, select the number of ZX312 adapters you want to
install. A parameters configuration menu will come up for each adapter
being installed.


