README.TXT Driver File Contents (6100.zip)

AMICard Manager Pro(tm) 2.1
July 15, 1997
Version 2.1.0 with Windows Installation

*****************************************************************
This README file contains important information that supplements
the AMICard Manager's Help File. 

For more information, run the AMICARD.HLP file using the Windows 
Program Manager.
*****************************************************************

README FILE CONTENTS

1.    WHAT'S NEW IN AMICard MANAGER PRO 2.1
      1.1  CardBus Support
      1.2  Zoom Video Support
      1.3  Reduced Memory Footprint for Card Services

2.    WHAT CHANGES HAVE BEEN MADE IN THIS VERSION
      2.1  AMICard Manager Pro 2.1 Version 2.1.0I
      2.2  AMICard Manager Pro 2.1 Version 2.1.0H
      2.3  AMICard Manager Pro 2.1 Version 2.1.0G
      2.4  AMICard Manager Pro 2.1 Version 2.1.0F
      2.5  AMICard Manager Pro 2.1 Version 2.1.0E
      2.6  AMICard Manager Pro 2.1 Version 2.1.0D

3.    INSTALLATION NOTES
      3.1  Minimum System Requirements including a note about 
           Windows 95.
      3.2  Installing on a System Without Any Card or Socket 
           Services Already Installed.
      3.3  Installing on a System With a Previous Version of 
           AMICARDZ Release 1.xx Already Installed.
      3.4  Installing on a System With a Previous Version of 
           AMICard Manager Pro 2.x Already Installed.
      3.5  Installing on a System With Another Vendor's Card and 
           Socket Services Already Installed.
      3.6  Installing Third Party Flash File System Drivers

4.    DESCRIPTION OF AMICard MANAGER PRO 2.1 FILES
      4.1  Description of Installed Files

5.    KNOWN PROBLEMS
      5.1   DOS Card Viewer (AMIINFO) Not Updating Screen When 
            a PC Card is Inserted or Removed 
      5.2   Miscellaneous AMICard Manager Problems

6.    RESTRICTIONS
      
      6.1   SETUP always overwrites files in the destination 
            Directory
      6.2   Only EMM386 exclude ranges are modified by SETUP
      6.3   Only the first EMM386 line in CONFIG.SYS is modified 
            with the Exclude ranges by SETUP
      6.4   Must disable Windows 95 PCMCIA support if using 
            AMICard Manager Pro 2.1 under Windows 95
      6.5   AMIDRIVE forces MS-DOS Compatibility Mode under 
            Windows 95
      6.6   Miscellaneous AMICard Manager Restrictions With This 
            Release
      6.7   Using Third Party Drivers from older PC Cards
      6.8   Using Fax/Modems with Windows 95

7.    CUSTOMIZING AMICARD MANAGER PRO 2.1
      7.1   Command Line Options for Card Services
      7.2   Using CSDEBUG.EXE
      7.3   Command Line Option for the Resource Manager (AMIRM.SYS)

8.    TROUBLESHOOTING
      8.1   When Using a CardBus Controller
      8.2   Problems with the Resource Manager (AMIRM.SYS)
      8.3   Problems with Third Party Client Drivers
      8.4   Problems with Card Detection

9.    TECHNICAL SUPPORT
      9.1   Getting the Latest Version of AMICard Manager Pro 2.1
      9.2   If You Have a Problem 
      9.3   American Megatrends' Bulletin Board
      9.4   Technical Support Fax
      9.5   Technical Support Internet Address
      9.6   Calling Technical Support

-----------------------------------------------------------------
1.    WHAT'S NEW IN AMICard MANAGER PRO 2.1

1.1   CardBus Support

      Card and Socket Services have been updated to include 
      support for CardBus Cards.  This allows for the use of CardBus
      Cards that provide 32-bits of address and data, 33MHz operation,
      and Busmaster operation.  Card and Socket Services provide the 
      necessary interfaces for DOS/Windows 3.1x Client drivers that 
      come with CardBus cards.  

1.2   Zoom Video Support

      Card and Socket Services have been updated to include support
      for Zoom Video.  This allows for the use of MPEG, Video Capture,
      and other cards that use the Zoom Video technology.  The system
      must also have a Zoom Video capable socket. Card and Socket
      Services provide the necessary interfaces for DOS/Windows 3.1x
      Client drivers that come with the Zoom Video PC Cards.

1.3   Reduced Memory Footprint for Card Services

      Card Services has been reduced by 67% compared to the AMICard 
      Manager Pro 2.0 product.  The 2.0 product size was around 55KB. 
      The new size is around 18KB.

-----------------------------------------------------------------
2.    WHAT CHANGES HAVE BEEN MADE IN THIS VERSION

2.1   AMICard Manager Pro 2.1 Version 2.1.0I

      AMICBSS.EXE    Additional fixes for older PC Cards that don't
                     return Voltage Sense pins correctly.

2.2   AMICard Manager Pro 2.1 Version 2.1.0H

      AMICBSS.EXE 1. Setting Auto-size bit in controller to fix 
                     problems seen with Multifunction PC Cards.
                  2. Add support for Serialized IRQS.
                  3. Fixed problem setting Speaker and RI bits
                     for Fax/Modem PC Cards.
                  4. Fixed problems for older PC Cards that don't
                     return Voltage Sense pins correctly.

      AMICL.SYS      Added support for VIA Socket Controllers.

2.3   AMICard Manager Pro 2.1 Version 2.1.0G
      
      SETUP.INS      Make setup program can be run from CD-ROM.

2.4   AMICard Manager Pro 2.1 Version 2.1.0F

      AMICBSS.EXE    The video and audio was real slow on some
                     systems when playing MPEG files with Zoom
                     Video Cards. This is now fixed.
                     
2.5   AMICard Manager Pro 2.1 Version 2.1.0E

      AMICBSS.EXE    Corrected another problem related to writing to
                     flash PC Cards

2.6   AMICard Manager Pro 2.1 Version 2.1.0D

      AMICS.EXE      1) Fixed problems where fax/modems were configured
                        but could not perform AT Command
                     2) Fixed problems with some Multifunction Cards
                     3) Fixed problem where flash cards could not be
                        written to

      AMICL.SYS      Fixed problems where fax/modems were configured
                     but could not perform AT Command
                     
-----------------------------------------------------------------
3.    INSTALLATION NOTES

      Installation must be performed by running SETUP from the 
      Windows Program Manager.  A DOS only installation can 
      be provided upon request.

      SETUP prompts you for some information and then loads all
      the software required for AMICard Manager Pro 2.1.
      SETUP saves a previous copy of all of your  system files it 
      modifies.
      
3.1   Minimum System Requirements

      DOS 5.0 and Greater
      Windows 3.1, 3.11, or Windows 95*
      80386SX Processor or Greater
      PC Card Socket Controller (Call for supported list)
      Mouse

  *NOTE: AMICard Manager Pro 2.1 will work with Windows 95 if the PCMCIA
  support provided with Windows 95 is disabled. For Windows
  95, American Megatrends recommends using the PCMCIA support within 
  Windows 95 instead of using the Real Mode drivers provided in AMICard 
  Manager Pro 2.1.  AMICard Manager Pro 2.1 should only be used as a last
  resort to get some PC Card to work that isn't working with the support
  provided by Windows 95.

3.2   Installing on a System Without Any Card or Socket Services 
      Already Installed.

      If there are no other Card Services loaded in your system,
      SETUP loads AMICard Manager Pro 2.1 and prompts you to 
      reboot your system.  

3.3   Installing on a System With AMICARDZ Release 1.xx Already 
      Installed.

      If you run SETUP and it detects the presence of American 
      Megatrend's Release 1.0 PCMCIA product known as AMICARDZ, 
      you will be asked if you want to uninstall it.  If you 
      select yes, the SETUP program will Uninstall AMICARDZ and 
      prompt you to reboot your system.  Then you need to rerun
      the SETUP program agsin. 
      
3.4   Installing on a System With a Previous Version of AMICard 
      Manager Pro 2.x Already Installed.

      If you run SETUP and it detects the presence of another 
      version of AMICard Manager Pro 2.x, you will be asked if 
      you want to uninstall it.  If you select yes,  the SETUP
      program will Uninstall the currently installed version  and 
      prompt you to reboot your system.  Then you need to rerun
      the SETUP program again.

3.5   Installing on a System With Another Vendor's Card and 
      Socket Services Already Installed.

      If you run SETUP and it detects the presence of some 
      other vendor's Card Services, you will be prompted to 
      remove it from all of the system files before you can 
      Install AMICard Manager Pro.  Look at the documentation
      that accompanies the other vendor's software for more 
      information.  Once removed, rerun SETUP.

3.6   Installing Third Party Flash File System Drivers

      AMICard Manager Pro 2.1 does not come with a Flash File
      System that is required to access Flash Memory PC Cards. 
      The flash file system software must be obtained from a 
      third party.

-----------------------------------------------------------------
4.    DESCRIPTION OF AMICard MANAGER PRO 2.1 FILES

4.1   Description of Installed Files

      AMICARD.DLL   DLL for AMICard Manager
      AMICARD.HLP   AMICard Manger's Help File 
      AMICARD.INI   INI File for AMICard Manager Pro 2.1
      AMICARD.LNG   Language file for AMICard Manager
      AMICARD.ORG   Copy of the originally installed INI File
      AMICBSS.EXE   CardBus Socket Services for TI113X and CL6832
      AMICL.SYS     Cirrus Logic PD67xx Socket Services
      AMICS.SYS     Card Services
      AMIDB.SYS     Databook TCIC-2/N Socket Services
      AMIDRIVE.EXE  ATA and Memory PC Card Client Driver
      AMIFIND.EXE   Used during installation to detect system resources
      AMIFMT.EXE    ATA PC Card Format Utility
      AMIGE.SYS     Generic Enabler
      AMIINFO.EXE   DOS Card Viewer
      AMIMGR.DAT    Windows AMICard Manager's data file
      AMIMGR.EXE    Windows AMICard Manager
      AMIMGRD.EXE   DOS AMICard Manager
      AMIOMEGA.SYS  Omega 82C094 Socket Services
      AMIOPTI.SYS   OPTI Socket Services
      AMIPPEC.SYS   Intel PPEC Socket Services
      AMIRICOH.SYS  Ricoh Socket Services
      AMIRM.BIN     Used by AMIRM.SYS to detect system resources
      AMIRM.SYS     Resource Manager
      AMISL.SYS     Intel 82365SL Socket Services
      AMITI.SYS     TI 1031/113x Socket Services (16-bit mode only)
      AMIVADEM.SYS  Vadem 365/46x Socket Services
      AMIVCD.386    Windows VxD Driver for Hot Insertions
      AMIVLSI.SYS   VLSI VL82C146 Socket Services
      CSDEBUG.EXE   Card Services Debug Aid
      DPMS.EXE      Novell's DOS Protected Mode Services 
      FVIEW.EXE     Program used to view readme file 
      FVIEW.DOC     Document describing FVIEW.EXE
      P_DIRECT.ZNC  File Required by AMICard Manager
      P_SERVIC.ZNC  File Required by AMICard Manager
      README.BAT    Batch file for viewing README.TXT
      README.TXT    This File That You Are Viewing

-----------------------------------------------------------------
5.    KNOWN PROBLEMS

5.1   DOS Card Viewer (AMIINFO.EXE) Not Updating Screen When a PC 
      Card is Inserted or Removed

      When POWER.EXE is loaded in CONFIG.SYS, AMIINFO will 
      sometimes not automatically update the screen when cards 
      are inserted or removed.  Press "Enter"  to force a screen 
      update.

5.2   Miscellaneous AMICard Manager Problems

5.2.1 Some Radio Buttons and Check Boxes don't look right with 
      Windows 95

-----------------------------------------------------------------
6.    RESTRICTIONS

6.1   SETUP always overwrites files in the destination Directory

6.2   Only EMM386 exclude ranges are modified by SETUP

      If you have any other memory manager, e.g. QEMM, 386MAX,
      etc., then the exclude ranges must be manually removed.

6.3   Only the first EMM386 line in CONFIG.SYS is modified with
      the Exclude ranges by SETUP
      
      If you have menu items and each menu item contains separate 
      EMM386 lines, only the first EMM386 line is modified.

6.4   Must disable Windows 95 PCMCIA support if using AMICard
      Manager Pro 2.1 under Windows 95

      1. In Device Manager, click your PCMCIA socket, and then 
      click the Properties button.
      2. Click the General tab, and in the Device Usage box, click 
      to clear the check beside the hardware profile.

6.5   AMIDRIVE forces MS-DOS Compatibility Mode under Windows
      95 for the drives it supports

6.6   Miscellaneous AMICard Manager Restrictions With This
      Release

6.6.1 Cannot associate an application to with a Fax/Modem PC Card 
      that looses its Card Information when configured

      When some fax/modems are configured, the vendor information
      for the PC Card can no longer be read.  This prevents the 
      AMICard Manager from associating an application.

6.6.2 ATA Utility, and Advanced Menu Items and SmartIcons are 
      not available in this release

6.6.3 Application Association Files specified in the Application 
      Association Window must not be in upper case

6.6.4 Avoid loading Card Services high when EMM386 excludes memory between
      CC00-CFFF range. This combination may result in a memory conflict
      with AMICard Manager and some Windows drivers (mouse drivers).
      
6.7   Using Third Party Drivers from older PC Cards

      Many PC Cards come with drivers that need to be installed
      in order to get the PC Card to be functional.  These drivers
      should be Client Drivers that use the Card Services
      interface.  Many early PCMCIA drivers were Point Enablers
      that interface directly with the socket controller hardware
      instead of using the Card Services interface.  If you have
      such an Enabler, you should request a later driver from 
      the PC Card Manufacturer.  Using a Point Enabler when Card
      Services is loaded may cause your system to hang when 
      inserting and removing PC Cards.

      Card Services provides services to Client Drivers.  Most
      Client Drivers determine what release of Card Services is 
      present before attempting to use its services.  The 1995
      PC Card Standard indicates that Card Services
      should return release 5.01 when asked what release is
      implemented.  AMICard Manager Pro's Release 5.01 Card Services
      is backward compatible with Release 2.01 and 2.10.  Some 
      Client Drivers were written exclusively for release 2.01
      or 2.10.  If your Client Driver does not work with 
      this release of Card Services, contact your PC 
      Card Manufacturer for an updated Client Driver.  Below is
      a list of drivers that we know of that have this problem:

         ACCTON Ethernet PCMCIA Client Driver Ver. 1.08

6.8   Using Fax/Modems with Windows 95

      When using AMICard Manager Pro 2.1 under Windows 95, the 
      following must be performed for Windows 95 to detect and
      configure a Fax/Modem PC Card:

      1. Run the Add New Hardware wizard to detect and configure the 
      card as a COM port.
      2. Run the Install New Modem wizard to detect and configure
      the card as a modem.
      
-----------------------------------------------------------------
7.0   CUSTOMIZING AMICARD MANAGER PRO 2.1

7.1   Command Line Options for Card Services

/v
   /v
   Causes Card Services to return that it is compliant to the 2.10
   PC Card Standard.  Without this option, Card Services returns
   that it is compliant to the 5.01 PC Card Standard (default).

/f
   /f=filename
   Specify configuration filename. Default is AMICARD.INI in the directory
   from which Card Services is loaded.

/p
   /p=xxx
   Power on stabilzation delay. 'xxx' is the number of timer ticks (55ms)
   to delay to allow power to stabilize when card is inserted or reset.
   Default is 1.

/c
   /c=xxx
   Configuration "wait for ready" maximum timeout. 'xxx' is the maximum 
   number of timer ticks (55ms) to wait for an IO card to become ready
   after writing to its options register. IO card without a Pin Replacement
   Register will always reach this timeout.
   Default is 10.

/w
   /w=xxx
   Card Reset "wait for ready" maximum timeout. 'xxx' is the maximum number
   of timer ticks (55ms) to wait for a card to become ready after a reset.
   A card reset is performed before applying power to the card during
   insertion. Debug displays 'EE' if this timeout occurs.
   Default is 128.

/n
   /n=x
   Maximum functions per card. 'x' is the maximum number of functions 
   to support per card (1-8).
   Default is 1.

/s
   /s=x
   Sound notifications. 'x' = '0' to turn Card Services tones off.
                        'x' = '1' to turn Card Services tones on.
   Default is 1.

/z
   /z
   Use Status Change IRQ. This causes Card Services to read and use the
   SCIRQ value in the configuration file.

/d
   /d or
   /d=x
   Debug mode. 'x' is a hexidecimal value based on the following
   bit definitions:

   Bit 0 = Show events (if Status Change IRQ used shows additional display)
   Bit 1 = Show Socket Services calls made by Card Services
   Bit 2 = Show Card Services API calls
   Bit 3 = Show callbacks to clients


Card Services Debug:

   Bit 0 = Show events (if Status Change IRQ used shows additional display)

   Display: EVxx where 'xx' is the hexidecimal event value detected.

            EV40 - Card Insertion
            EV05 - Card Removal
            
            If Status Change IRQ used: SCxx yy where 'xx' is the latch
            value and 'yy' is the instantaneous value returned by 
            Socket Services GetStatus call.

            SSxx yy EV40 - Card Insertion
            SSxx yy EV05 - Card Removal


   Bit 1 = Show Socket Services calls made by Card Services
   
   Display: SSxx [yy] where 'xx' is the hexidecimal Socket Service request
            and 'yy' is the nonzero hexidecimal return code.

            SS89    - Successful Socket Services SetWindow
            SS89 08 - BAD_PAGE error returned by Socket Services SetWindow


   Bit 2 = Show Card Services API calls

   Display: CSxx [yy] where 'xx' is the hexidecimal Card Service request
            and 'yy' is the nonzero hexidecimal return code.

            CS30    - Successful Card Services RequestConfiguration
            CS1F 02 - BAD_ATTRIBUTE error returned by Card Services RequestIO

   Bit 3 = Show Card Services callbacks to clients

   Dislpay: CBxx [yy] where 'xx' is the hexidecimal callback event and
            'yy' is the nonzero hexidecimal value returned by the client.

            CB40    - CARD_INSERTION callback.
            CB0E FF - EXCLUSIVE_REQUEST with client returning value of FF

7.2   Using CSDEBUG.EXE

     CSDEBUG.EXE can be used to turn on/off Card Services debug.
     
     It takes one agrument which is a hex value representing the debug 
     level bit mask (you know just like the /d=x AMICS.SYS switch).
     
     To turn off debug:
        CSDEBUG 0.
     
     To set various debug levels:
     
        CSDEBUG 1   /* Display Status Change and/or event notifications */ 
        CSDEBUG 2   /* Display Socket Services calls */
        CSDEBUG 4   /* Display Card Services calls */ 
        CSDEBUG 8   /* Display Callbacks */
     
     To set various combinations of debug:   
        CSDEBUG 3  /* Status Change and Socket Services */ 
        CSDEBUG 5  /* Status Change and Card Services */ 
        CSDEBUG 6  /* Socket Services and Card Services */
        CSDEBUG 7  /* Status Change, Socket Services, and Card Services */ 
        CSDEBUG 9  /* Status Change and Callbacks */ 
        CSDEBUG a  /* Socket Services and Callbacks */
        CSDEBUG b  /* Status Change, Socket Services, and Callbacks */ 
        CSDEBUG c  /* Card Services and Callbacks */
        CSDEBUG d  /* Status Change, Card Services, and Callbacks */ 
        CSDEBUG e  /* Socket Services, Card Services, and Callbacks */ 
        CSDEBUG f  /* Status Change, Socket Services, CardServices and      
                      Callbacks */

7.3   Command Line Option for the Resource Manager (AMIRM.SYS)

/RL
   Causes the resource manager to use the resources as defined in the
   AMICARD.INI file rather than scanning the system resources at boot
   time.  This option is useful if the resource manager is not 
   correctly detecting system resources.

-----------------------------------------------------------------
8.    TROUBLESHOOTING

      Here are some suggestions to try when you are having problems 
      getting your system to work properly.  These problems could be
      related to software or hardware.


8.1   When Using a CardBus Controller
      
      If you are using a Texas Instruments or Cirrus Logic CardBus
      controller and your PC Cards are not working, try replacing
      the CardBus Socket Services (AMICBSS.EXE) with the non-CardBus
      Socket Services (AMITI.SYS for Texas Instruments and AMICL.SYS
      for Cirrus Logic).  See if this takes care of your problem, but
      be aware that you can no longer use CardBus cards.  Please 
      provide the results of this change to American Megatrends' 
      Technical Support.  
                                                          
8.2   Problems with the Resource Manager (AMIRM.SYS)

      If the Resource Manager hangs up your system during startup, 
      try putting the /RL option on the AMIRM.SYS line of your 
      CONFIG.SYS file (see section 7.3).  Please provide the results
      of this change to American Meagetrends' Technical Support.

8.3   Problems with Third Party Client Drivers

      If a Card Services aware client driver is provided with your
      PC Card is not working correctly, you can get some additional
      information about the interaction between the client driver and
      Card Services by enabling a debug display as seen in section 7.2.
      This information would be helpful for American Megatrends'
      Technical Support.

8.4   Problems with Card Detection

      The default method for detecting card insertion and removal is
      to periodically poll the hardware for a change in status.  If this
      does not appear to be working, put the /Z option on the AMICS.EXE
      line (as mentioned in section 7.1) and reboot your system.  This 
      will enable an interrupt to be generated whenever a card is 
      inserted or removed.  Please provide the results of this change
      to American Megatrends' Technical Support.

-----------------------------------------------------------------
9.    TECHNICAL SUPPORT

9.1   Getting the Latest Version of AMICard Manager Pro 2.1

      To get the latest release of AMICard Manager Pro 2.1, call 
      the American Megatrends' BBS.  

      If you would like a list of the supported PC Cards or 
      socket controllers supported by AMICard Manager Pro 2.1, 
      contact American Megatrends' Technical Support.  

9.2   If You Have a Problem 

      If you are experiencing problems, please provide the 
      following information to Technical Support:

      1.  Description of the problem.

      2.  Copy of your CONFIG.SYS, AUTOEXEC.BAT, SYSTEM.INI and 
          AMICARD.INI.

      3.  What PC Cards you are using.

      4.  What system you are running on and what type of socket 
          controller(s) (indicated during installation).

9.3   American Megatrends' Bulletin Board

      24 Hour online services
      Two 28.8 Kbps and Two 14.4 Kbps lines
      Retrieve AMICard Manager Pro 2.1 Evaluation updates
      Leave messages

      (770) 246-8780

9.4   Technical Support Fax

      To ask questions, report problems, etc., send a fax to 
      Technical Support at:

      (770) 246-8772

9.5   Technical Support Internet Address

      To ask questions, report problems, etc., send a message to 
      Technical Support at:

      support@american.megatrends.com

9.6   Calling Technical Support
      
      To ask questions, report problems, etc., call Technical 
      Support at:

      (770) 246-8645
-----------------------------------------------------------------
                   *** END OF README FILE ***


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: web2, load: 1.21