Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!UMCVMB.MISSOURI.EDU!C506634
From: C506634@UMCVMB.MISSOURI.EDU (Eric Edwards)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Does ARP have problems?
Message-ID: <910316.180915.CST.C506634@umcvmb.missouri.edu>
Date: 17 Mar 91 00:09:15 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Hackers Without Hard Drives
Lines: 23

In Message-ID: <2147@public.BTR.COM>
          thad@public.BTR.COM (Thaddeus P. Floryan) said:
>Hmmm, wondering about all the recent flak over HandShake 2.20c, I recovered
>it from floppy (after doing "CLI> delete hand
>it (using the ARTM monitor ... great program, by the way) was the ONLY thing
>on my system bringing in the ARP library.  And HandShake 2.20c is the ONLY
>thing on my system(s) that causes a guru without undue provocation.
>
>Are we "on" to something here?  Just curious.
Doubtfull.  The only part of ARP that Handshake uses is the file requester.
The major problems that people have been having with Handshake is with XPR's
especially Zmodem.

For the record, here's another handshake bug that's been there since at least
1.60b..   Under very low memory conditions or heavy fragmentation, try to open
the phonebook.  LOCKUP.  No messages, no guru.  No problems with the rest of
the system but now you have a large application dead in the water, eating
memory. For those of us with only 1 meg, the only real option is a three finger
salute.

Eric Edwards: c506634 @    "The 3090.  Proof that by applying state of the
Inet: umcvmb.missouri.edu   art technology to an obsolete architecture,
Bitnet: umcvmb.bitnet       one can achieve mediocre performance."