------------------------------------------------------------------------
 ROBOCOMM SUPPORT BULLETIN                No. 1           July 12, 1992
------------------------------------------------------------------------

Hello everyone,

The Robocomm 4.2 upgrade kit has been out for about 2 weeks now, and
initial reports are that it is working well.  However, there are a few
items that need your attention and some that need some clarification.

    o   SETTING THE BBS TYPE -- A new "BBS Type" was added to the
        Robocomm 4.2 release.  It is "Wildcat 3.5."  When Robocomm logs
        on to a Wildcat system, take a close look at the text the sent
        by the BBS immediately after the connection is established.
        Make sure that the version indicated is correctly set on
        Robocomm's Directory-BBS screen for the BBS.

    o   ROBOCOMM'S WILDCAT 3.5 PROMPTS -- The prompts that you should be
        using with all standard Wildcat 3.5 systems were contained in
        the DEFAULT.WPF file.  After running the Robocomm 4.2 upgrade
        routine, you should have gone into your BBS Directory and used
        the DEFAULT menu option on the prompt screen for all of the
        Wildcat 3.5 systems that you have defined.

        THE WC35.WPF FILE THAT WAS DISTRIBUTED WITH ROBOCOMM 4.1 IS
        OUTDATED AND SHOULD BE DELETED!  Robocomm will not function
        properly if these prompts are loaded into a BBS definition.

    o   WILDCAT 3.5 PROMPT DISCREPANCIES -- It appears that, depending
        upon the Wildcat 3.5 upgrade method used by your sysop, there
        may be some small discrepancies in some crucial prompts used on
        Wildcat systems.  The most common discrepancies involve the
        prompts used during file uploading.  If you have set the BBS
        type to Wildcat 3.5 and have imported the correct default
        prompts for the BBS and are still having difficulties with
        uploading, then take a close look at the prompt that Robocomm is
        "Stuck" on and compare it to the text specified on the prompt
        screen for the BBS.  The most common discrepancy is that some
        Wildcat 3.5 systems apparently use:

         "KEYWORDS ?" and "DESCRIPTION ?"

        as prompts during the upload process while others use:

         "KEYWORDS?" and "DESCRIPTION?"

        The only difference is the placement of the question mark, but
        that's enough to throw Robocomm off.  So, depending upon the
        BBS, you may need to add or remove a space before the question
        mark to make some of the upload prompts work properly.

    o   PROBLEMS WITH WILDCAT 3.5 "!" LOGONS -- A couple of people have
        reported that Robocomm's new ability to request immediate access
        to the mail TomCat mail door during logon has caused Robo to
        appear "lost" when it arrives in the mail door.  The problem
        occurs when the BBS Type has been set to "Wildcat 3.5" and a
        "Get QWK" or "Send REP" agenda item is the first item on the
        agenda AND the "Mail Conference" for the BBS (indicated on the
        Directory-BBS screen) is not blank.  It seems that there is a
        small glitch in the code that causes problems if a mail
        conference has been specified.

        So, if you are attempting to get mail from a Wildcat 3.5 system,
        please make sure that your "mail door conference" setting on the
        directory-bbs screen is completely empty.  This will work around
        the problem in the code.

    o   GIFDOWN.BAT AUTO-EXECUTION -- By default, Robocomm 4.2 will look
        for the file GIFDOWN.BAT in your Robocomm directory whenever it
        attempts to download a file with a GIF extension during
        automated operations.  If GIFDOWN.BAT is found, Robocomm will
        shell out to DOS and execute the batch file to bring the file
        down.  This "hook" is designed for people who want to use a 3rd
        party utilities, such as SHOWGIF.EXE and DSZ.EXE to view GIF
        files as they are being downloaded.

        If you do not have both of these utilities the "sample"
        GIFDOWN.BAT that was distributed with the Robocomm 4.1 release
        will start up and then fail if you attempt to download a GIF
        file.  To remedy this situation, all you need to do is DELETE
        GIFDOWN.BAT from your Robocomm directory.

        If you would like to see GIF files while you download, then you
        will need to get the latest versions of DSZ and SHOWGIF (both
        are shareware programs) from your local BBS and place the files
        in your Robocomm directory or in your download path.  The sample
        batch file provided with Robocomm 4.1 should work without
        modification.

                                   # # #