Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!mips!btr!thad
From: thad@btr.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: HandShake 2.20c DOES work with xprzmodem
Message-ID: <1774@public.BTR.COM>
Date: 15 Feb 91 13:44:50 GMT
References: <1718@public.BTR.COM> <1991Feb12.134052.27100@sarah.albany.edu> <2598.27ba56d7@incstar.uucp>
Organization: BTR Public Access UNIX, MtnView CA, Contact: cs@btr.com 415-966-1429
Lines: 41

In article <2598.27ba56d7@incstar.uucp> lhotka@incstar.uucp writes:
>...
>However, Handshake 2.20c does tend to be a bit flaky with the xpr
>calling...  I find that about 80% of my transfers work great and then I
>guru.  I have been trying to figure out exactly what I am doing different
>in the cases where it crashes, but there does not appear to be a pattern...

As part of my testing HandShake 2.20c, I've transferred over 2,000 files both
ways during the past several days, over direct connections and over modems, in
multiple sessions (i.e. restarted HandShake from scratch each day).

I'm assuming you DID read the xprzmodem docs, and have a "xprzmodem" file
with the correct params in your ENV: directory, you've INIT'd the external
protocol, etc etc

Having done all the above, it works fine for me.

I do dispute Willy's assertion the one-pixel-wide artifacts are an OS bug
since they do NOT occur using the Meshugena program.  Without source I can
only conjecture, but my guess as to the nature of the problem is that the
character cell size used to "clear" an inverse-bolded character is one pixel
"off" from the cell-size that originally placed the char on the screen.

My only other "gripe" about HandShake 2.20c is that it doesn't handle xpr
directory paths as nicely for zmodem as does the "old" AZcomm program with
which I can start a transfer and have it transfer (and create) subdirectories
offset from a specified "root-point" at the receiving end; with HandShake 2.20
you EITHER ignore directory paths on receipt OR you must accept the sender's
directory paths.  Not very nice, so for zmodem transfers I'm still using
AZcomm.

As far as "development requests" for HandShake, my needs are modest and
comprise only:

1) 38400 baud (as does AZcomm), and

2) paced ASCII transfers (with specifiable char and line delays) along the
   lines of A-Talk (this pacing is needed to input chars into some brain-
   damaged BBS systems which assume human typing speed).

Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]