------------------------------------------------------------------------
      WHAT TO DO IN CASE OF PROBLEMS
  ------------------------------------------------------------------------



  ------------------------------------------------------------------------
    1. FIRST OF ALL
  ------------------------------------------------------------------------

    RELAX!



  ------------------------------------------------------------------------
    2. IF YOU CAN'T INSTALL OR START ZOC
  ------------------------------------------------------------------------

    * Please try installation into a fresh directory on your boot drive. 
      Do not convert files from an existing version.

    * Try to start ZOC from the command line instead of using the desktop
      icon, eg. CD ZOC
                ZOC

    * If you want to start ZOC from another working directory, you must
      add your ZOC directory to the LIBPATH statement in CONFIG.SYS (under
      OS/2) or add the ZOC directory to your PATH (under Windows).

    * It is possible to unpack the INSTALL.FIL file with a standard UNZIP.
      However, this is only an emergency method.

    * You can view the help file with the command VIEWHELP ZOC.HLP (OS/2)
      or WINHELP ZOC.HLP (Windows)



  ------------------------------------------------------------------------
    3. IF YOU HAVE TROUBLE USING ZOC
  ------------------------------------------------------------------------

    * Please check the common problems section in the help menu

    * Contact your dealer or EmTec (see ZOC-Help for addresses, email,
      phone numbers, etc.).



  ------------------------------------------------------------------------
    4. KNOWN PROBLEMS WHEN RUNNINGN ZOC FOR OS/2
  ------------------------------------------------------------------------

    * Lost characters with ET4000W32 video boards and Warp
      The Warp ET4000W32 drivers seem to cause lost characters in 
      the serial device. 
      Solutions:
       * Use the plain ET4000 drivers that come with Warp
       * There are updated drivers available from IBM's driver section at 
         http://ps.boulder.ibm.com

    * Lost characters with Matrox Millenium/Mystique
      With Matrox video boards, disabling the "Automatic PCI Bus Retry"
      option might help.

    * If the ZOC dialing or transfer windows are dragged while they are 
      about to be closed, they will stay open and lock the program.

    * Install program aborts with Trident 9440A video boards
      Cause unknown (so far).
      Please try to unpack INSTALL.FIL manually (unzip INSTALL.FIL).

    * Several problems were reported with ATI video drivers, especially
      with 16.7 Meg. colors
    
    * ZOC for OS/2 crashes with earlier versions of ATI MACH 32 drivers 
      when aborting a REXX script.  There are drivers available from IBM
      BBSs under the name MACH32.ZIP  The version number must be higher
      than 2.6
    
    * Sometimes strange things happen with Warp's COM.SYS. 
      There is a replacement COM.SYS driver from IBM.  It is available
      on CompuServe's OS2SUPPORT forum (lib 23, WFP_03.ZIP), on 
      ftp01.ny.us.ibm.net (/pub/warpcom/WRPCOM.ZIP) and on the ZOC 
      Support BBS.

    As far as we can tell, all these problems are due to OS/2 and not 
    due to ZOC.



  ------------------------------------------------------------------------
    5. KNOWN PROBLEMS WHEN RUNNINGN ZOC FOR WINDOWS
  ------------------------------------------------------------------------

    * ZOC does not work with Teles WinCOM (because WinCOM is a 16bit 
      application)

    * ZOC reports "Assert" errors with the modem sharing tool Stomper
      FIX: It is a bug in Stomper, please upgrade your stomper client

    * The TELES CAPI only supplies unit and time information, if
      the function "Device->Accept calls" is active.
    
    * The Teles ISDN CAPI V2.0 does not seem to work with PNP32 sound boards.
      The problem is very likely not caused by ZOC.
 
    * If you have other problems with ISDN drivers, please check ISDN.DOC
      and the common problems sections of the help menu (there are at least
      four items regarding ISDN).

    * Crash in Module GDI.EXE with Hercules Dynamite 128 video board
      (will probably happen with other ET6000 boards also).  Another user
      encountered screen corruptions with the same board.
      FIX: either use ET4000 drivers or decrease video acceleration in 
      the ET6000 drivers.

    * Crashes GDI.EXE with ATI MACH32 drivers when certain fonts (from 
      the Telix comm package, eg. Telix VT Font) are installed.

    * Lost characters on some machines when scrolling text in high 
      resolution and high color mode.  
      Workaround: Use a lower screen resolution or less colors or try 
      another driver.  (A user got this problem fixed by using a generic 
      S3 driver for his video board, insted of the manufacturer's). 
      With Matrox video boards, disabling the "Automatic PCI Bus Retry"
      option might help.
      Please contact EmTec if you encounter this behaviour!

    * Under certain circumstances the Terminal family of fonts is
      lost. They reappear after a system shutdown and reboot.  On some
      systems, they are only available when a DOS window or DOS Program
      is open.
      The cause of the problem has not yet been determined, but it 
      probably is a video driver problem.  Please contact EmTec if 
      you encounter this behaviour!