1. DE55001to3.zip Driver
2. RELEASE.TXT File Contents

RELEASE.TXT Driver File Contents (DE55001to3.zip)

*****************************************************************************
		Microdyne NE2500/NE5500 Software Release 3.01 May 16, 1996
*****************************************************************************
This release does not update any device drivers.  The JumpStart program has been
upgraded with new features, including built-in adapter diagnostics.

Special note for McAfee RomShield (TM) users:
----------------------------------------------
There is a known bug related to using McAfee RomShield with the Microdyne NE2500 
series of adapters. This bug will cause JumpStart to lock up if the RomShield
ROM is active when JumpStart is used.  To work around the problem, follow these
steps:

1. Remove the RomShield rom from its' socket.
2. Run the JumpStart adapter configuration program by typing "a:\jmpstart".
3. Configure your adapter as desired.
4  Exit the JumpStart program.
5. Replace the RomShield chip in its' socket.

------------------------------------------------------------------------------
                  
		Microdyne Software Release 3.0 July 21, 1995
                  
The elements of this release are:

ODI Driver (DOS, OS/2, Server)
NDIS 2.0.1 Driver (DOS, OS/2)
NDIS 3.X Driver (for WFW 3.11; NT versions 3.1, 3.5 and 3.51; Win95)
Packet Driver
DMInstall (DMI Installation utility)

Shipped on request:
	SCO UNIX Driver (SCO ODT 3.0, SCO Open Server 5.0)
	Sun Solaris Driver (for v2.4)
	Novell UNIXWARE Driver (for v1.1 and 2.0)



NEW FEATURES
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. DMI support has been added to the ODI (DOS/OS2), NDIS2 
(DOS/OS2), and WFW NDIS 3 Drivers. The following procedure can
be used to manually install the required DMI files (see item #2
below for a description of the automated DMI installation
utility):

- Install your NE2500/NE5500 Series network driver for DOS, OS/2
or Windows using conventional installation procedures.

- Install the DMI package (SL, browser, etc) for the OS you plan
to use. If you do not have a specific DMI package for your
system, one can be obtained from the Desktop Management Task
Force (DMTF). They can be contacted at:

          Desktop Management Task Force
          M/S JF2-51
          2111 N.E. 25th Avenue
          Hillsboro, OR  97124
          PHONE:(503) 696-9300
          FAX:  (503) 696-9027

- From the disk, copy the files required for the operating
system you are using to the corresponding DMI directory.

      for OS/2:

        copy a:\dmi\pcnet.mif c:\dmi\os2\bin\mifs
        copy a:\dmi\pcnet.dll c:\dmi\os2\bin

for DOS and Windows with real mode (ND2/ODI) Pcnet driver 
installed:

        copy a:\dmi\pcnet.mif c:\dmi\dos\mifs
        copy a:\dmi\pcnet.ovl c:\dmi\dos\bin

for Windows for Workgroups 3.11 with NDIS 3 driver installed:

        copy a:\dmi\pcnet.mif c:\dmi\dos\mifs
        copy a:\dmi\pcnet.exe c:\dmi\win16\bin

- Edit the pcnet.mif file's 'Serial Number', 'Installation' and
'Connector Type' fields.

- Install the pcnet.mif file into the SL's database. In the
simplest case, this can be done using the DMTF's browser.

- To verify that the installation was successfull, use your DMI
management application to explore the information.

2. The manual procedure above can be effected using the
DMINSTL.EXE program provided on the disk in the A:\DMI
subdirectory. It copies the necessary files. To invoke the
program, place a copy of the disk into drive A:. Make sure the
disk is not write protected. Enter the following commands:

- C:>A:           <Enter>
- A:\>CD \DMI     <Enter>
- A:\DMI>DMINSTL  <Enter>

When the main panel is displayed, enter the serial number of
distribution package you received (if none is provided, the field
can be left blank). Press the Enter key or the Tab key to advance
to the next field.
    
The Installation Date field displays the current system time by 
default. If you wish to change the value of this field, use the 
left and right arrow keys to move about the text and type over 
the old values. Note that DMINSTL uses the TZ environment
variable to determine the offset from GMT. If this variable
is not set, DMINSTL assumes PDT (offset +480).

Advancing to the Connector Type field, you can change its value
by pressing the Alt-F4 key combination and selecting the
connector type in use on your system. To highlight different
values, use the up and down arrow keys. To select one of the
values, press the Enter key. To hide the pull-down list and
leave the selection unchanged, use the Esc key. 

Finally, advancing to the Target Driver field, you can inform the
installation utility regarding which drivers you intend to run on 
the system. The choices are NDIS 3 for native operation under 
Windows for Workgroups v3.11. Or, you can select NDIS 2 / ODI for 
operation in DOS or in WFW 3.11 using real mode DOS drivers.
Once the information has been entered, press the F10 key to 
initiate the installation. Pressing Alt-F4 anytime prior to 
pressing F10 will cancel the installation and return to DOS.

The DMI installation utility will invoke the DMI SL if found to 
assist with the installation. If the SL cannot be invoked, 
DMINSTL will copy the necessary files into the DMI directory 
structure -- which it will create if not already present on drive
C:. The next time the SL is loaded, it will complete the 
installation on behalf of DMINSTL.

Note that DMINSTL expects to be executed out of the same
directory that contains the files:

      PCNET.MIF
      PCNET.EXE
      PCNET.OVL

    *IMPORTANT*

To avoid conflicts with certain TSRs, it is best to run DMINSTL
in a minimally configured system. In other words, booting to a
plain vanilla DOS system (e.g. no CONFIG.SYS and AUTOEXEC.BAT
files) is preferred.
    
3. Two new directories with the NDIS2 DOS driver have been added
on the Supplemental driver disk to support DOS client packages
for IBM Lan Server 4.0. The first -- \IBMLSP -- should be used
as a path for the "Advanced Lan Support Program". The second --
\IBMADOS -- is for the "Advanced Lan DOS Services" package.

4. Two new directories with the NDIS3 drivers have been included
on the Supplemental Driver disk to support Windows 95 and Windows
NT v3.51. Note that the NT 3.51 driver is not backwards
compatible with Windows NT v3.1 or v3.5.

NOTES
~~~~~
1. When invoking the DMI Service Layer (SL.EXE), set the overlay
buffer size to 10k as follows:

      C:\DMI\DOS\BIN> SL o=10 <Enter>


2. Certain system/floppy diskette drive combinations do not
tolerate the default dma mode which limits bus master DMA cycles
by the number of transfers performed. To address the problem, the
default mode for ISA systems has been changed. Although the DMABR
register retains the default values used in v2.0 of the drivers,
the DMABAT register is now enabled and is programmed to a value
of 6 microseconds by default. This mode and value is ONLY used on
ISA systems.

Since the exact value for the DMABAT register is system
dependent, a new keyword - BUSTIMER - has been introduced
to allow different values to be selected. Generally speaking,
a larger value improves performance while a smaller value
improves compatibility with sensitive devices that use DMA
(e.g. FDD). The valid range for the BUSTIMER keyword is 5 to
13 inclusive.

At present, there is a known problem with systems designed around
a particular PCI/ISA bridge. In particular, the default value of
6 microseconds in the DMABAT may cause the adapter to experience 
difficulty when exchanging packets with other network nodes. This 
problem can be resolved by increasing the DMABAT value to 7 
microseconds. However, it is possible that programs that use
system DMA heavily or that reprogram the DMA controller for added
performance may encounter difficulty when DMABAT is set to 7
microseconds.

    DMABR=Chip Default (16 transfers)
    DMABAT=6 micro sec (for ISA systems - not used on PCI or VL).

    If BUSTIMER=n given either by command line or system
    configuration utility, DMABAT is set to n micro secs.