Path: utzoo!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!yale!eagle.wesleyan.edu!jtreworgy From: jtreworgy@eagle.wesleyan.edu Newsgroups: comp.sys.amiga.programmer Subject: Re: Does ARP have problems? Message-ID: <1991Mar18.143445.40379@eagle.wesleyan.edu> Date: 18 Mar 91 19:34:45 GMT References: <1991Mar7.201652.27356@javelin.es.com> <2147@public.BTR.COM> Organization: Wesleyan University Lines: 20 In article <2147@public.BTR.COM>, thad@public.BTR.COM (Thaddeus P. Floryan) writes: > Hmmm, wondering about all the recent flak over HandShake 2.20c, I recovered > it from floppy (after doing "CLI> delete hand#?" earlier), and noticed that > 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. Handshake only brings in the library if you select ARP file requester (and use it). You don't "need" arp library to use handshake. Believe me, though, Handshake 2.20c crashes all by itself... doesn't need any help from arp. By the way, in the wake of all this flak about arp, I should comment that I have used it exclusively since the most recent version was released, and it makes life in CLI a lot easier than the original commands... whatall with pipes and redirection and stuff. I believe incompatibilities exist but I have never personally experienced one.. I'll take a chance for the added convenience. -- James A. Treworgy -- No quote here for insurance reasons -- jtreworgy@eagle.wesleyan.edu jtreworgy@WESLEYAN.BITNET