1. IEE_10.ZIP Driver
2. RELNOTES.TXT File Contents

RELNOTES.TXT Driver File Contents (IEE_10.ZIP)

   Latest news about your EtherExpress PRO/10+ adapter
                                                                    v3.10


NetWare* server and OS/2* users
-------------------------------

If you have a Plug and Play BIOS and are running OS/2 or a NetWare
server, make sure you disable Plug and Play on your adapter using
SoftSet2. Having Plug and Play enabled on your adapter may cause
configuration problems because these environments don't support Plug and
Play.


Make sure you're using the latest SoftSet2
------------------------------------------

Make sure you're using the latest version of SoftSet2 (version 4.10 or
later, available on SW Release disk 3.0) that came with your adapter. If
you need the latest version, you can download it from one of Intel's
online services. For connection information, see the Technical Support
readme file or the inside back cover of your Installation Guide.


Windows* 95 users
-----------------


Enabling Plug and Play

If using Windows 95, leave Plug and Play enabled on your adapter. This is
the default setting. If Windows 95 doesn't automatically recognize your
adapter, run SoftSet2 and make sure Plug and Play is enabled. For more
information, see the readme file called Plug and Play Computers.


Running SoftSet2

If you're running Windows 95 and want to use SoftSet2, run it in Windows
95's MS-DOS* mode. To enter MS-DOS mode, choose Shut Down from the Start
menu, select Restart the computer in MS-DOS mode, and click Yes.


Using FlashVirusProtect

FlashVirusProtect must be disabled when upgrading your system to Windows
95.

To disable FlashVirusProtect features, change your FVP configuration
using either FVPCFG (if you have FVP software locally) or FLUPDATE on the
NetWare server.

After Windows 95 installation is complete, you can re-enable the pre-boot
file and sector scanner options, but not the anti-virus TSR.

After you've rebooted with scanners active, messages appear indicating
changes to your boot sector and system files. Save these changes to the
Flash ROM.

For more information, download document #6280 from one of Intel's online
services.


Using FlashStart

FlashStart does not support Windows 95.


Using FlashUpdate

Be sure to enable processing of your NetWare login script to allow
FLDRVCHK to run.

Any file update that alters the adapter's flash, such as flash images and
anti-virus pattern files, won't work.


AUI cabling
-----------

If you're using AUI cabling, you must change the board connector type
from the default Auto-detect to AUI connector. Here's how:


DOS or Windows
1  Run SoftSet2.
2  Select Change Adapter Configuration.
3  Set the Board connector type to AUI connector.

Windows NT* or Windows for Workgroups
1  Select the Network icon in the Control Panel.
2  Highlight "EtherExpress(TM) PRO/10 adapter" and select Configure.
3  Set the Connector type to AUI.


Windows 95
1  Double-click the Network icon.
2  Click the Configuration tab.
3  Click "Intel EtherExpress(TM) PRO/10+," then click Properties.
4  Click the Advanced tab.
5  Click Tranceiver Type, then it to AUI Connector.

If you need to use both AUI and BNC cables, connect only one cable at a
time. EtherExpress PRO/10+ adapters don't support simultaneously active
AUI and BNC network connections.


PCI/ISA computers
-----------------

If you install the adapter in a PCI/ISA computer, you should keep the
adapter configured for 16-bit mode; it may not work properly if set to 8-
bit mode.

Also, if you have a PCI/ISA computer without a Plug and Play BIOS, your
adapter's flash program may be disabled during installation due to ROM
shadowing problems. To fix this problem, use your computer's BIOS setup
program to disable ROM shadowing for the flash memory address.


XT computers
------------

Intel PRO/10+ adapters don't support XT computers (8086's and 8088's).
Try contacting your computer vendor or reseller for a network adapter
that supports XT computers.


Undetectable IRQs
-----------------

SoftSet2 and FlashSet can reliably detect most IRQs used in a computer.
However, some devices use IRQs in a way these programs can't detect. If
you have problems with the computer after installing the adapter, make
sure no other device uses the same IRQ as the adapter.


NE2000 adapters
---------------

You can't run SoftSet2 when NE2000 drivers are loaded. If you're
installing the adapter in a computer with an NE2000 adapter, restart the
computer without loading the drivers before you run SoftSet2.


The following information concerns flash adapters

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


FlashWorks and VLM's
--------------------

If you use VLM's, make sure this line is in the CONFIG.SYS file:

   LASTDRIVE=Z

Without this line, the FIRST NETWORK DRIVE=F command in the NET.CFG file
won't work.


FlashVirusProtect
-----------------

If you don't want to install FlashWorks or don't have a NetWare* server,
you can still use FlashVirusProtect. To install FlashVirusProtect, run
its setup program (SETUPFVP) and follow the onscreen directions.


Updating FlashVirusProtect

If an update of FlashVirusProtect fails, and FLUPDATE's View status
option displays

      Failed: Insufficient flash memory

make sure you've turned off FlashStart on the adapter. Then run FLUPDATE
to reschedule the event.


Using FlashVirusProtect without a floppy drive

If you're running FlashVirusProtect and don't have a floppy drive, make
sure you configure FlashVirusProtect to scan only your hard drive. (The
default is to scan all drives.)


Changing the scan frequency

If you download a FlashVirusProtect configuration, and scans don't occur
when expected, delete the SLOCKFL.CFG file from the workstation and
reboot. FlashVirusProtect then scans at the proper frequency.


Using DoubleSpace*
------------------

FlashStart won't work properly on computers using DoubleSpace with the
/move parameter.


FlashStart and "Can't create directory" error
---------------------------------------------

FlashStart won't work properly on computers that use Dynamic Driver
Overlay (a special driver that supports drives larger than 540MB in
systems whose BIOS supports only smaller drives). When FlashStart runs,
the Dynamic Driver Overlay is not loaded, and FlashStart cannot find the
hard disk. Check with the system vendor for an updated BIOS that supports
large drives.


Using FlashStart or RPL
-----------------------

With NetWare 4.x

If you're using NetWare 4.x and experience problems running FlashStart or
remote boot, replace the server's RPL files as follows:

1  If RPL is already loaded, unload it from the server console.

2  From a workstation, log in as ADMIN and flag \LOGIN\RBOOT.RPL and
   \SYSTEM\RPL.NLM as read-write.

3  Insert the driver disk and copy \NWRPL\RBOOT.RPL to the server's
   \LOGIN directory and \NWRPL\RPL.NLM to the server's \SYSTEM directory.

4  Flag both files as read only.

5  From the server console, load RPL and bind it to the Ethernet 802.2
   frame type.


With Windows for Workgroups

If you have a Windows for Workgroups client set up for NDIS drivers,
don't use FlashStart to add ODI with VLM support. FlashStart doesn't
modify your WIN.INI and SYSTEM.INI files correctly. Use the Windows for
Workgroups network setup instead. FlashStart works only with Windows
3.1x.

If you need to recover the previous versions of these files, check your
Windows directory for versions with a .OLD extension. When FlashStart
modifies a file, it saves the previous version with this extension.


With Advanced Configurations

If you have a complex boot configuration, FlashStart may not correctly
modify your AUTOEXEC.BAT file. If FlashStart modifies a file, it saves
the previous version with an .OLD extension.


Memory overlap problems
-----------------------

The default flash chip address is D000-D3FFh. If you install the adapter,
turn on the computer, and see a blank screen or an error message, the
flash address probably conflicts with something else in the computer. To
resolve the conflict:

-  Determine which device is using the D000-D3FFh range and reconfigure
   that device to use a different memory address.

-  Check your system setup and disable ROM shadowing at D000h.

-  As a last resort, remove the adapter from this computer, install it in
   another computer that doesn't have a conflict at D000-D3FFh, and use
   SoftSet2 to configure it to use a different flash chip address. Then,
   reinstall the adapter in the first computer.


Changing the flash chip address when a memory manager is running
----------------------------------------------------------------

When a memory manager is running, SoftSet2 indicates that all memory
addresses (except D000) are used, even if they're free. To change the
flash chip address, follow these steps:

1  Temporarily disable the memory manager. For example, add a REM
   statement to the start of the memory manager command in your
   CONFIG.SYS file. Then reboot.

2  Run SoftSet2 and select a flash chip address. Note the address.

3  Exclude the memory range the flash chip uses and re-enable the memory
   manager.

4  In CONFIG.SYS, exclude the memory range the flash chip uses and re-
   enable the memory manager.

For example, to exclude the D000 range in EMM386, use this line in
CONFIG.SYS:
   
   device=c:\dos\emm386.exe x=D000-D3FF


Updating flash memory
---------------------

If a flash update fails, and FLUPDATE's View status option displays
   
   Failed: Flash memory erase error

run FLRESTOR /ERASE at the computer (make sure the flash image file with
a .FLS extension is in the same directory), then run FLUPDATE at the
server and reschedule the update. If you still have problems, download
the most recent image file (FLSIMG.EXE) from one of Intel's online
services. See the online help file called "Using Intel's Automated
Customer Support" for more information.


Installing multiple flash adapters
----------------------------------

If you're installing multiple EtherExpress PRO/10+ flash adapters in one
computer, install and configure the adapters one at a time. For each
adapter (except the last), change the IRQ and I/O address from the
defaults and disable the flash chip before installing the next adapter.

If you plan to use FlashVirusProtect on the computer, enable the flash
chip on the last adapter you install.



*  Third-party trademarks are the property of their respective owners.