Newsgroups: comp.sys.amiga.datacomm
Path: utzoo!utgpu!watserv1!watdragon!rose!sbmueller
From: sbmueller@rose.uwaterloo.ca (stephan();)
Subject: Re: HandShake 2.20c DOES work with xprzmodem
Message-ID: <1991Mar5.192516.19358@watdragon.waterloo.edu>
Keywords: handshake guru
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <1718@public.BTR.COM>
Date: Tue, 5 Mar 1991 19:25:16 GMT
Lines: 49

In article <1718@public.BTR.COM> thad@btr.btr.com writes:

>Having read "HandShake gurus my machine" the past several days, I really
>didn't believe it, so I ftp'd HandShake-2.20c.lzh from ab20.larc.nasa.gov
>and tried for myself using the xprzmodem.library "2.0 (28 Oct 1989)" and
>it works just fine ... in fact, VERY impressively.

Sometimes.  When it works, it works extremely well!  When it doesn't,
the lockup is immediate, and the guru persistent.

Handshake 2.20c locks up for me at two specific times:
- when attempting to dial (using the dialer menu, not by manually
typing ATDT etc.)
- when attempting to download (this has happened with external
protocols as well as the builtin Kermit text, for instance)

The lockup happens as soon as the appropriate window appears and
text is spewed to it.  If I get the first 256 bytes of a download,
it will finish.  If dialing starts it will finish.

Whether or not it works is independent of anything I've noticed.
Some days it does, some days it doesn't.

I'm running Handshake 2.20c, on an A1000, with 2.5Megs, Comspec
HD controller, KS/WB1.3.2, ARP, Conman/WShell/ARexx, and other things
too numerous to mention but whose removal has no effect on the problem.

I'm curious: do those of you who've had no problem by chance all own
A3000s?  Eric Haberfellner does, and a friend who also has had no
problems does...  

(-: Hmm.  Maybe, Eric sends the fully functional version only to those
who register (so where's my copy Eric? :-)

>I trust all those having problems DID, in fact, select "Init Ext. Protocol"
>from the [TRANSFER] menu and answer the eleventy-seven questions prior to
>attempting any zmodem transfers.

Definitely.

>You DID read the xpr specs and docs, didn't you?  :-)

A while ago.  I didn't act much on them though :-)  In particular,
I do not have any xpr[zmodem] env: variables set.

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

stephan("A cop is a walking zoo, with a gun");

