   Latest news about your EtherExpress PRO/10 adapter
   ==================================================

   NetWare* server, Windows NT*, and OS/2* users
   ---------------------------------------------
 
      If you have a Plug and Play BIOS and are running OS/2, Windows NT, 
      or a NetWare server, make sure you disable Plug and Play on your 
      adapter using SOFTSET.EXE. 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 
      3.1x or higher) that came with your adapter. If you need the latest 
      version, you can download it from Intel's BBS.


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

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

	 1.  Run SoftSet2.

	 2.  Select Change Adapter Configuration.

	 3.  Set the board connector type 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 
      it configured for 16-bit mode. The adapter 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, use your computer's 
      BIOS setup program to disable ROM shadowing for the flash memory 
      address.


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

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


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

      SoftSet2 can reliably detect most IRQs used in a computer. 
      However, some devices use IRQs in a way that SoftSet2 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.


   LANDesk(TM) Manager users
   -------------------------

      If you're using LANDesk Manager to perform a Ping Test on a 
      workstation with an EtherExpress PRO/10 adapter, download the 
      most recent DOSODI network driver (EPROODI.COM v2.33 or later) 
      from the Intel BBS and install it in the workstation. See your 
      User's Guide for BBS phone numbers.


   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. Here's how:

      Installing from the FlashWorks disk   
      
	 1.  Put a copy of the FlashWorks disk into a drive, switch to that 
	     drive, and at the DOS prompt, type: 

	     SETUPFVP

	     The batch file decompresses files from the diskette and copies
	     them to C:\VPROTECT.PC. It then starts the FlashVirusProtect 
	     configuration program.

	 2.  Specify the configuration you want (see the FlashWorks 
	     Installation and User's Guide for details) and press F10.

	 3.  Choose Yes to download the configuration to the flash 
	     adapter.   

      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.)


   Using Doublespace*
   ------------------

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


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

      With NetWare 4.x

	 If you're using NetWare 4.x and are experiencing 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, login as ADMIIN 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're using FlashStart on a WfW client and installing 
	 VLM's, FlashStart may not correctly modify your WIN.INI and 
	 SYSTEM.INI files. If FlashStart modifies a file, it saves 
	 the previous version with an .OLD 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 what 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 that the flash chip uses and re-enable
	  the memory manager.


   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. The flash 
      image file is available from the Intel BBS (in FLSIMG.EXE).


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

      If you're installing multiple Intel flash adapters in one computer,
      install and configure the adapters one at a time.
      
      Also, if you plan to use FlashVirusProtect on the computer or have 
      a computer with a Plug and Play BIOS, disable the flash chip on all 
      but the last adapter you install. Otherwise, disable the flash chip 
      on all of the adapters.



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




