Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!STERNLIGHT@USC-ECL.ARPA
From: STERNLIGHT@USC-ECL.ARPA (STERNLIGHT)
Newsgroups: net.micro
Subject: Re: Crosstalk woes
Message-ID: <1334@brl-tgr.ARPA>
Date: Sat, 7-Sep-85 15:56:53 EDT
Article-I.D.: brl-tgr.1334
Posted: Sat Sep  7 15:56:53 1985
Date-Received: Mon, 9-Sep-85 03:21:28 EDT
Sender: news@brl-tgr.ARPA
Lines: 19

I, too, have had experience with Microstuf that suggests that they are
less than customer-aware when anomalies occur in Crosstalk XVI.  For the
longest time there has been a bug in their XMODEM protocol for receiving
files, which causes the system to hang in the middle of a transfer under some
(unknown) circumstances.  Several phone calls to them, and several versions
have not cured the bug, which is notorious enough for someone to have
posted an XMODEM program to some bulletin boards for the specific purpose
of leaving Crosstalk, downloading, and returning to Crosstalk.  Since I
find this unacceptable, I have abandoned my investment and use ACSII PRO,
an outstanding communications program written by Bill Blue for United
Software.  I am particularly dissatisfied with the conversations with
Microstuf, in which they tried to blame their problems on everyone but
their inadequate code.  ("Well, there's no standard XMODEM protocol."  
ME:"Why do the following six communications programs have no problem?"
"Well we can't get information about the protocol."  ME:"Try calling
..... (I supplied a list of several experts who have written various
programs like MEX, MODEM, etc.)"
--david--
-------