|03RE: |11Qmodem TD, error rese
|03BY: |11DALE SHIPP |03to |11DAVE MIDDLETON |03on |11Thu Sep 04 1997 02:34 
pm|07
 >  -=> On 09-02-97  11:43, Dave Middleton <=-
 >  -=> spoke to Dale Shipp about Qmodem TD, error reset <=-
 >
 >  DM> I too have used Qmodem T.D.4.52 for several years and for the BBS'ing
 > >
 >  DM> Have you tried calling other BBS's to see if the same problems occur?
 >  DM> Maybe the trouble is with the BBS; have any other users experienced
 >  DM> problems since the changes?
 >
 >  There is a problem with the lines or software on that BBS that is
 >  causing the CRC errors to happen too frequently.   I don't tend to get
 >  them on other BBS.
 >
 >  I had thought that Qmodem was supposed to be able to recover from a CRC
 >  error.  It certainly goes through some actions that would look like it
 >  is trying, but almost always gets hung up with the statement "Sending
 >  ZRPOS".   At that point, I have no option other than to hit ESC, and
 >  disconnect from the BBS using ALT-X.  Even CTRL-K does not stop things
 >  as advertised.
 >
 >  DM> Incidentally, I have tried RTS When Writing both OFF and ON And I
 >  DM> can't really see any difference in performance.
 >
 >  Based on another suggestion here I have put it to ON (and also set EMS
 >  to ON) but am still having the problems.
 >
 >  Thanks for your response.  Hope someone comes up with how to make
 >  Qmodem successfully restart after a CRC error and not get hung on
 >  Sending ZRPOS.
 >
Try installing DSZ.COM as an external Zmodem protocol and use that, at least 
on the troublesome board.  It's a bit more robust than other Zmodem 
implementations and I've been able to force data, with patience, down bad 
lines that other Zmodem drivers gave up on.  I've used it exclusively, 
assigning it the Z letter, thus disabling and replacing the internal Zmodem, 
for years.  My version dates back to 6/7/95 and was widely distributed as 
DSZ0607.ZIP; if there have been later updates, they've escaped my attention.  
Cheers ... - Dan  (P.S.  Should you reply and appear to be ignored, it's 
because this echo is not available at my regular ports of call and I rarely 
get to it more than a couple times a year.)
--- InterEcho 1.12
---------------