=================================================================
AirAccess V2.03          RELEASE NOTES          February 16, 1995
=================================================================

  Table of Contents :

  1) AirAccess User Interface Changes
  2) Command Line Syntax for AutoStart Local Server
  3) Non-Standard Windows Communications Drivers
  4) Disabling Warning Message for Non-Standard Windows Drivers
  5) Cancel an AirAccess action
  6) LANMAN10.386 Driver
  7) Using a 14,400 baud modem (or other baud rate)
  8) Fail to activate an Air drive, but AirPing without problem
  9) Using QEMM Memory Manager with AirAccess
 10) Using AirAccess in Multple Paths

=================================================================

The following information details changes to AirAccess since
V2.02, which are not reflected in the AirAccess User's Guide.
This document should be reviewed prior to running AirAccess
V2.03.

---------------------------------------------------------------
1) AirAccess User Interface Changes
---------------------------------------------------------------

  a) "Connect" and "Disconnect" AirDrive terminology has been
     changed to "Activate" and "Deactivate" respectively.  This
     change was implemented to avoid confusion between
     connecting/disconnecting an AirDrive and connecting/
     disconnecting a phone connection.  The terminology change
     is  reflected in all areas of the AirAccess User
     Interface, including Quick Icon bar, menus, and message
     boxes.

  b) The "File Browser" has been renamed to "Cache Status" to
     clarify its function.  Also, the Cache Status utility is
     no longer displayed by default (it must be activated via
     the Options Menu) and is now displayed as a separate,
     sizable child window.



-----------------------------------------------------------------
2) Command Line Syntax for AutoStart Local Server
-----------------------------------------------------------------

  Through AirAccess V2.02, it was necessary to manually start the
  AirAccess Server after running AirAccess. It is now possible
  to automatically start your Local Server every time Windows
  starts.  Syntax is as follows:


  AIR_WIN.EXE /S


  You can easily take advantage of the AutoStart Server
  capability by simply creating a new icon in your Windows
  StartUp Group which uses the above command line syntax. For
  example:


  C:\AIR\AIR_WIN.EXE /S



-----------------------------------------------------------------
3) Non-Standard Windows Communications Drivers
-----------------------------------------------------------------

  AirAccess requires the standard Windows communications drivers
  for reliable communications. Many 3rd party communications
  programs disable, modify or overwrite these drivers, which may
  cause unpredictable AirAccess data transfer results.


  AirAccess V2.03 addresses this problem by warning the user in
  the event the communications drivers on the system are not the
  Windows standards.  AirAccess accomplishes this warning by
  checking the Windows\System.ini file for the proper devices
  and by verifying the file size of the actual communications
  driver.


  Should the user receive an AirAccess warning message regarding
  non-standard communications drivers, it is advised to perform
  the following procedure:

  a) Check the WINDOWS\SYSTEM.INI file as follows:

     1. Using the SEARCH Menu, use the FIND Option to search
        for "comm"

        The desired, standard comm driver statement should read:

        comm.drv=comm.drv

        If your COMM.DRV statement is identical to the one
        above, then your system.ini file contains the proper
        comm.drv statement and you can proceed to step #3.

        If you find any other statement which starts with
        "comm.drv=" in the "[BOOT]" section, or if the above
        comm.drv statement has a semicolon (";") at the
        beginning of the line, then you have a 3rd party, non-
        standard comm driver loaded, and must perform step #2.

     2. Place a semicolon at beginning of line before any
        COMM.DRV statement other than the above standard.  The
        semicolon will remark the non-standard statement out of
        the system.ini file.

        Remove semicolon if present at the beginning of the
        standard comm.drv statement.

        If the standard comm.drv is not present, create new line
        in "[BOOT]" section to read:

        comm.drv=comm.drv


     3. Using the SEARCH Menu, use the FIND Option to search for

        "vcd"

        The desired, standard vcd driver statement should read:

        device=*vcd

        If your VCD statement is identical to the one above,
        then your system.ini file contains the proper VCD
        statement and you can proceed to step #5.

        If you do not find the device=vcd statement in the
        "[386enh]" section, or if the above VCD statement has a
        semicolon (";") at the beginning of the line, then you
        have a 3rd party, non-standard VCD driver loaded, and
        must perform step #4.

     4. Remove semicolon if present at the beginning of the
        standard VCD statement.

        If the standard VCD statement is not present, create
        new line in "[386Enh]" section to read:

        device=*vcd


  b) Check the COMM.DRV file size as follows:

     1. In File Manager, use the File Menu option, SEARCH, to
        search for the file C:\WINDOWS\SYSTEM\COMM.DRV.


        The COMM.DRV file size should be one of the following:

        Windows V3.1 file size = 9,280 bytes

        Windows for Workgroups V3.11 file size = 5,968 bytes


        If the file size of your COMM.DRV is the proper size
        for your Windows version, then your communications
        driver is standard and is OK to work with AirAccess.

        If the file size of your COMM.DRV is other than the
        proper size for your Windows version, then your
        communications driver is non-standard and must be
        reinstalled; please proceed to step #2.


     2. Delete the non-standard COMM.DRV file from your
        WINDOWS\SYSTEM directory.  Then reinstall the standard
        comm.drv file from your Windows or Windows for
        Workgroups diskettes. At this point, your communications
        driver is standard and is OK to work with AirAccess.


-----------------------------------------------------------------
4) Disabling Warning Message for Non-Standard Windows Drivers
-----------------------------------------------------------------

  AirAccess requires the standard Windows communications drivers
  for reliable communications. Many 3rd party communications
  programs disable, modify or overwrite these drivers, which may
  cause unpredictable AirAccess data transfer results.

  AirAccess V2.03 addresses this problem by warning the user in
  the event the communications drivers on the system are not the
  Windows standards.  AirAccess accomplishes this warning by
  checking the Windows\System.ini file for the proper devices
  and by verifying the file size of the actual communications
  driver. AirAccess checks for the following items in your
  SYSTEM.INI

     1. a standard COMM.DRV in the [boot] section

     2. a DEVICE=*VCD line in the [386enh] section

     3. avoid DEVICE=LANMAN10.386 in the [386enh] section

  Should the user receive an AirAccess warning message regarding
  non-standard communications drivers, it is advised to perform
  the procedures in section 3 above.

  If you would like to disable the warning message, perform the
  following steps:

     1. Using a text editor, open the AIR.INI file located in
        the Windows directory.

     2. Under the [CONFIGURATION] section, change the comm
        warning setting from 1 to 0.

        example:

        EnableCommWarning=0

     3. To re-enable the warning, change the above line to

        EnableCommWarning=1


-----------------------------------------------------------------
5) LANMAN10.386 Driver
-----------------------------------------------------------------

  AirAccess will display progress in the AirStatus window
  whenever you access un-cached information on your AirDrive.
  If you experience a long delay every time prior to AirSoft's
  status window appearing and/or the same delay each time a file
  is opened on your AirDrive this is probably because the
  LANMAN10.386 driver is installed on your system.  The
  LANMAN10.386 driver interferes with any programs which  use a
  windows function called "Switch VMs and Callback" (you do not
  need to know about this function) of which AirAccess is one.
  The LANMAN10.386 driver is required only if you use a CD-ROM
  and are using a copy of MSCDEX (Microsoft's CD-ROM driver)
  earlier than version 2.2.  To remedy this problem you will
  need to do the following:

    a)  Find and comment-out the line containing
        "device=lanman10.386" from your SYSTEM.INI file
        (you can comment-out lines by adding a semi-colon (";")
        at the beginning of the line)

    b)  Obtain an updated version of the MSCDEX driver from
        Microsoft Corp. Or upgrade to Windows 3.11 or Windows
        for Workgroups (these versions of Windows come with
        MSCDEX version 2.2 or higher.)

  NOTE: b) ABOVE IS UNNECESSARY FOR WINDOWS 3.11 AND WINDOWS FOR
           WORKGROUPS SINCE THEY ARE SHIPPED WITH MSCDEX VERSION
           2.2 OR HIGHER.

  CAUTION: IF YOU INSTALL EITHER WINDOWS 3.11 OR WINDOWS FOR
           WORKGROUPS ON TOP OF AN EXISTING COPY OF WINDOWS 3.1
           THE LANMAN10.386 DRIVER DOES NOT AUTOMATICALLY GET
           REMOVED FROM YOUR SYSTEM.INI FILE. THIS WILL STILL
           HAVE TO BE REMOVED MANUALLY.


-----------------------------------------------------------------
6) Cancel an AirAccess action
-----------------------------------------------------------------

  When AirAccess is reading large un-cached files from your Air
  drive, a progress indicator appears.  You can either press the
  Cancel button (in Windows) or press ESC (in DOS).  Sometimes
  you may have to cancel more than once.  The number of times
  you have to cancel depends on how your application handles
  critical errors.  When you cancel, AirAccess generates a
  critical error (same as the error you receive when you try to
  read data from an empty floppy drive.)  File Manager for
  example, requires 2 cancels when you cancel a listing of an
  un-cached directory.


-----------------------------------------------------------------
7) Using a 14,400 baud modem (or other baud rate)
-----------------------------------------------------------------

  To set up the correct baud rate in Mobile Setup, you pick the
  baud rate that is close to the highest capable rate.  For
  example, pick 9,600 or 19,200 baud rate for your 14,400 modem.


-----------------------------------------------------------------
8) Fail to activate an Air drive, but AirPing without problem
-----------------------------------------------------------------

   If you can AirPing your server, but can not activate your
   AirDrive, you should check to see if the Local Server Security
   is enabled on the server.  If it is, then most likely, you did
   not enter the proper login information.  Use Change Password
   under the AirDrive menu to change your login information.


-----------------------------------------------------------------
9) Using QEMM Memory Manager with AirAccess
-----------------------------------------------------------------

   When using the QEMM Memory Manager with AirAccess, please 
   follow these instructions for reliable AirAccess functionality: 
   
   a) Do not load AIRSYS.EXE high using QEMM.

      Using a text editor, search your AUTOEXEC.BAT for a QEMM 
      loadhi statement similar to the following:


      C:\QEMM\LOADHI\R:2 AIRSYS.EXE 
      

      If you find such a statement, comment it out by adding "rem"
      as follows:

      
      REM C:\QEMM\LOADHI\R:2 AIRSYS.EXE


      Then add the following line immediately following your "PATH" 
      line:

      AIRSYS.EXE
      

   b) Do not use QEMM to load DOS-UP.SYS and DOSDATA.SYS

      Using a text editor, search your CONFIG.SYS for QEMM 
      statements similar to the following:
      
      DEVICE=C:\QEMM\DOSDATA.SYS 
      
      DEVICE=C:\QEMM\DOS-UP.SYS
      
      If you find such statements, comment them out by adding "rem"
      as follows:
      
      REM DEVICE=C:\QEMM\DOSDATA.SYS

      REM DEVICE=C:\QEMM\DOS-UP.SYS


-----------------------------------------------------------------
10) Using AirAccess in Multple Paths
-----------------------------------------------------------------

      Some programs, including MS-DOS 6.0 and above, support the 
      ability to have multiple "PATH" statements in your 
      AUTOEXEC.BAT file. Please be advised that the AirAccess 
      installation will only add the AirAccess directory to a
      single PATH statement.  If you desire AirAccess to be 
      included in multiple PATHs, please manually add the proper 
      AirAccess drive\directory to the additional PATH statements 
      in your AUTOEXEC.BAT.
      
      
      
