README.TXT Driver File Contents (3c319x.exe)

                        3Com (R) Corporation
                     TokenDisk (R) Diskette for
  The 3C319 TokenLink Velocity ISA Token Ring Network Interface Card
                           Release Notes


This TokenDisk diskette supports 3Com's TokenLink Velocity ISA 16/4 
Token Ring NIC.  Key product features include:

-   Parallel Tasking (R) architecture for highest performance
-   DynamicAccess (TM) Class of Service feature prioritizes 
    data transmissions for critical applications
-   Auto ring speed detect for Windows 95 & Windows NT driver
-   Promiscuous mode support for Windows 95 & Windows NT driver 
-   Guaranteed compatibility with IBM legacy drivers             
-   Ease of installation with AutoLink and Plug and Play support
-   Broad driver support, including NetWare, NDIS 2.01, NDIS 3.0, 
    NDIS 4.0 and others 
-   SNMP manageability
-   Lifetime warranty
-   Dedicated Token Ring support with full duplex capability for switched 
    token ring environments
-   CISPR B and FCC B certification for reduced electromagnetic emmissions 
    when using either STP or UTP cabling
  
  3Com Configuration and Diagnostic Program Runs in DOS Mode Only
  ---------------------------------------------------------------
  If you are running Windows 95, please exit to DOS mode before 
  running the 3Com Configuration and Diagnostic program.  If you
  are running Windows NT, boot from the DOS partition or boot
  from a DOS diskette.
        
  Installation Tips
  -----------------

o   Because the 3C319 is 100% IBM compatible, it uses shared
    RAM to transfer data.  If you are using a DOS memory 
    manager such as EMM386 on your PC, you must reserve 
    upper memory for the NIC.  The 3C319 NIC's default 
    configuration requires 16K of shared RAM at address
    D8000-DBFFF and 8K for the BIOS/MMIO area at address
    CC000-CDFFF.  You must edit the memory manager device
    statement in the CONFIG.SYS file to exclude the memory
    range.  For example:

    DEVICE=C:\WINDOWS\EMM386.EXE X=D800-DBFF X=CC00-CDFF

o   The 3C319 supports Plug and Play configuration which makes it easy
    to install in many systems.  Windows 95 is the only network 
    operating system that supports Plug and Play configuration of the 
    NIC.  PnP configuration may or may not work in other environments.
    Also, older systems with an older BIOS may not recognize the NIC 
    upon install. If you have problems installing the NIC, make sure you 
    have the latest BIOS from your PC vendor. If you still have problems 
    installing the NIC, you should disable PnP and configure the NIC using 
    the Configuration and Diagnostic Program (3TRDIAG.EXE).  At the DOS
    command prompt, type:

    a:3trdiag co /PnP:disable

    PnP configuration will NOT work with the following drivers:
    
    - NetWare Server driver: 3CTOKEN.LAN
    - NDIS 2.01 DOS and OS/2 drivers: TLNK3.DOS and TLNK3.OS2 
    - IBM drivers: TOKEN.COM, TOKEN.SYS, TOKEN.LAN,     
                   IBMTOK.DOS, IBMTOK.OS2, DXMA0MOD.SYS,
                   DXMC0MOD.SYS

    You must disable PnP when using the above drivers.  
      
o   With new installations of Windows 95, Windows 95 detects the 3Com 
    NIC as an IBM adapter.  This occurs because the 3C319 is 100% IBM
    compatible.  You can remove the IBM driver and then install the 
    3Com driver from the 3Com TokenDisk diskette.

o   When installing the OS/2 driver (TLNK3.OS2) on an IBM PC 360, OS/2
    will hang if the 3C319 NIC is not physically installed in the PC.
    Be sure to install the card in the PC and run diagnostics 
    (3TRDIAG.EXE) to verify there are no configuration conflicts before 
    installing the OS/2 driver.  

o   The PnP BIOS of some PCs, configures the card in 8-bit mode.  OS/2 
    clients cannot connect to a server if the card is in 8-bit mode.  
    Run diagnostics (3TRDIAG.EXE) and reconfigure the card to 16-bit 
    mode.

o   The Diagnostic program (3TRDIAG.EXE) will fail to identify the 3C319 
    in an HP NetServer LF 486/66 unless the card is first configured in 
    EISA mode.

o   When installing the 3C319 in a NetWare 3.12 Server, use the files 
    contained in the /NW312 subdirectory on TokenDisk diskette #2.

o   When installing Novell Client32, use the files contained in the
    /CLIENT32 subdirectory on TokenDisk diskette #2.

o   When using the NetWare DOS Client driver (3CTOKEN.COM) with the 
    Novell ODINSUP driver, the 3C319 is unable to access an IBM host.  
    To connect to both a NetWare Server and IBM host, use the IBM
    LAN Support drivers (DXMA0MOD.SYS and DXMC0MOD.SYS) with the 
    Novell LANSUP driver. 

o   3Com does not support the use of the 3C319 OS/2 driver in a 
    Microsoft OS/2 1.3 and LANManager 2.2 environment.

o   If you are re-installing the 3C319 under Windows 95 to 
    install the new Class of Service enabled driver, Windows 95
    may not properly detect the memory resources the first time
    you reboot the system.  Simply reboot the system again - 
    Windows 95 will correctly detect the resources.  

o	If you are installing the 3C319 under Windows NT with the new 
	Class of Service enabled driver in EISA mode from Disk 2, you 
	will need to enter the path A:\NT95\EISA when prompted for the 
	disk and path.

o	After enabling and configuring DynamicAccess Class of Service
	support for Windows 95 and Windows NT, the system has to be 
	re-booted for any changes to take effect.

o	Under Windows NT, there are two ways to configure the Class of 
	Service applications. The first way is by double-clicking the 
	Class of Service icon in the Control Panel. The second way is 
	by double-clicking on the priority button on the adapter 
	properties screen. (refer to figure 7-5 in the User Guide).

	In the latter case, the Locally Administered network Address(LAA) 
	should be set after exiting the Class of Service setup application.


o   Make sure you have the latest BIOS version for your 
    computer.  Contact your computer's manufacturer to make 
    sure you are using the latest BIOS.  Here are the phone
    numbers for some PC system manufacturers:

    Company     Phone
                
    ALR*        (800) 257-1230   
    Ambra*      (800) 465-2227   
    AST*        (800) 727-1278
    AT&T*       (800) 543-9935   
                (800) 531-2222
    Compaq*     (800) 652-6672  
                (800) 345-1518       
                            
    Dell*       (800) 626-4308   
                (800) 624-9896
    Digital     (800) 354-9000   
    Equipment*
    Gateway*    (800) 846-2070   
                (800) 846-2301
    Hewlett-    (800) 322-HPPC    
    Packard*    (800) 752-0900
    IBM*        (800) IBM-3333   
    Micron*     (800) 438-3343   
    Packard     (800) 733-4411   
    Bell*
    Unisys*     (800) 328-0440   
    Zenith*     (800) 227-3360   
    ZEOS*       (800) 554-7172   
                (800) 228-5390

    In addition, here are the phone numbers and on-line 
    addresses of several popular OEM motherboard manufacturers:
                
    Company     Phone             ON-line address
     
    Intel*      (503) 264-7999    ftp://ftp.intel.com\pub\bios
    Micronics   (510) 651-6837
    ASUS        (408) 956-9084    http://asustek.asus.com.tw
                
* Third-party trademarks and copyrights are the property of
  their respective owners.

  3Com Technical Support
  ----------------------
  Please refer to your user guide for technical support information.
  In addition, this information is also available in the
  \HELP\SUPPORT.TXT file on the TokenDisk diskette.

 

3Com, TokenLink, TokenDisk, Parallel Tasking and DynamicAccess are 
registered trademarks of 3Com Corporation.


                  (%VER README.TXT - Release Notes v1.0d)






Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web5, load: 0.45