Problem:  Telix and the modem do not seem to be able to detect busy signals.

Solution: Some modems (especially older 1200 bps units) do not have the
          capability to detect busy signals. Assuming yours does, you'll still
          probably have to edit the default modem Init String. The X1 that
          Telix uses in the string to be compatible with all modems does not
          enable busy detection in most modems. Try a value like X3, X4, or
          higher.












Problem:  When the Host Mode script is run Telix always thinks that a caller
          is online and immediately asks for the caller's name; or Telix
          always says that a Hang-up operation failed even when it did in fact
          successfully hang-up the modem.

Solution: Your modem is almost certainly overriding the true state of the
          Carrier Detect signal. This is the factory default on most modems,
          but should be disabled. For proper operation, Telix needs to see
          this signal on when connected to another computer, and off when not.
          If your modem has dip switches, as do most 1200 bps units and all US
          Robotics external Couriers, switch number 6 usually controls this
          and must be in the up position. If your modem does not seem to have
          any dip switches (look carefully, sometimes the front needs to be
          popped off), it is probably controlled solely by software commands,
          as are most 2400 bps units. Just a few examples of these are the
          Hayes 2400, ATI 2400, GVC 2400, and many others. For these modems,
          adding &C1&D2 in the modem Init String (before the final ^M (Car-
          riage Return is a good spot)) will configure the modem properly.







Problem:  When redialing Telix does not seem to know when a connection has
          been reached.

Solution: Telix knows when a connection has been reached in one of two ways:
          when it receives a Connect string from your modem, or when the
          Carrier Detect signal turns on (if it was off). Make sure that the
          Connect string is properly defined in the Configuration Menu, or
          that your modem does turn on the Carrier Detect signal regardless of
          whether or not there is a connection.

Problem:  Telix doesn't work with a certain modem.

Solution: Telix is set by default to use the Hayes 'AT' modem command stan-
          dard. There are modems that are not Hayes compatible however, and
          use other commands to dial, hang up, and perform other tasks. Make
          sure that if your modem is not Hayes compatible Telix has been
          properly configured to its commands.



Problem:  When trying to use the DOS Shell, or another function that uses DOS,
          Telix warns that it can not find a file called COMMAND.COM, and
          aborts the function.

Solution: The file COMMAND.COM is the DOS command interpreter. Telix must be
          able to find it to use many DOS functions. The location of COM-
          MAND.COM is stored in an environment variable (explained in your DOS
          manual) called COMSPEC. COMSPEC is set at boot-up, but if you boot
          of a floppy and then change to another floppy or a hard disk, it
          will not point to the right place anymore. In short, make sure that
          COMSPEC always points to the location of COMMAND.COM, or that
          COMMAND.COM is in the current directory.

Problem:  When calling some systems, especially large ones such as Compuserve
          or the Source, all incoming characters look like garbage.

Solution: The communications parameters are probably wrong. Most of these
          systems need a setting of Even parity, 7 data bits, and 1 stop bit.
          This is different from the normal standard of N81 used for most
          bulletin boards.