Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!caen!uwm.edu!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!news.iastate.edu!skank
From: skank@iastate.edu (Skank George L)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: HandShake 2.20c DOES work with xprzmodem
Message-ID: <1991Mar19.232850.24534@news.iastate.edu>
Date: 19 Mar 91 23:28:50 GMT
References: <101@haberfel.uucp> <339@tardis.dbaccess.com>
Sender: news@news.iastate.edu (USENET News System)
Organization: Iowa State University, Ames, IA
Lines: 41

In article <339@tardis.dbaccess.com> peter@dbaccess.com (Peter A. Castro) writes:
>in article <101@haberfel.uucp>, eric@haberfel.uucp (Eric Haberfellner) says:
>> 
>> Hi,
>> 
>> Sorry, I missed the beginning of this thread. Could someone please give me
>> a quick summary of the HandShake problem under discussion.
>> 
>> I am the author and would like to kiil any bugs in the new release as 
>> soon as possible.
>> 
>> Eric :{)
>
>  If you have read the previous posts concerning XPR and the Zmodem library
>  (zprzmodem.library, v2.10).  Then you already know that typically when
>  invoking the "receive" option, the zmodem window appears, and the machine
>  Gurus, with a 00000003 code.  I have found that when I run through the
>  "Init Ext. Params" option first, say when I just started up, it works
>  without trouble.  Here are some data points about the environment:
>
>     Handshake V2.20c
>     xprzmodem.library V2.10
>     Kickstart (v1.3) 34.5, Workbench (v1.3) 34.28
>     ARexx V1.10
>     Stock A1000 w/2MB Ram (1.5Mb Ext)
>     Modem used is a Telebit T2500 (at speeds up to 19.2K)

Eric,
     I'd like to throw in my 2 cents here also.  I've been using Handshake
2.20c on my A3000 and it seems to work flawlessly.  My environment is:

      Handshake V2.20c
      xprzmodem.library V2.10
      Kickstart 2.02
      ARexx (included with A3000)
      Stock A3000
      Modem used is an Applied Engineering 2400 baud modem.

Maybe that will help you debug the problem.
				--George