Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!rutgers!rochester!kodak!sisd!jeh
From: jeh@sisd.kodak.com (Ed Hanway)
Newsgroups: comp.sys.amiga.tech
Subject: Re: ASyncRun() doesn't work with pipe:xxx!
Message-ID: <1990Sep6.201155.22739@sisd.kodak.com>
Date: 6 Sep 90 20:11:55 GMT
References: <6516@sugar.hackercorp.com> <57200@microsoft.UUCP> <6528@sugar.hackercorp.com>
Sender: news@sisd.kodak.com
Organization: Printer Products Division Eastman Kodak
Lines: 22

peter@sugar.hackercorp.com (Peter da Silva) writes:
>Every time I've switched to ARP I've run into problems, either because of
>limitations in ARP or incompatibilities. What I'd do is install ARP, then
>swap back to AmigaDOS whenever I ran into a problem. After a while I found
>that a good deal of my C: directory was back to DOS.

Is it really necessary to "switch" to ARP to run programs like sksh?  All
that they really require is the 17100 byte arp.library, not all of the
replacement commands in C:.

Like sksh, I needed to push data through pipes in the background in HamLab,
and like Steve, I settled on PIPE: and AsyncRun().  I would have preferred
to avoid arp.library completely, but it offers about the only reliable
method of running processes asynchronously short of 2.0.  I was pleasantly
surprised to find that ARP 1.3 AsyncRun() apparently works under 2.0, so I
don't regret the decision.

Fortunately, I only use AsyncRun() for the pipe: writer, so I haven't
run into the problems that Steve has.

Ed Hanway
uunet!sisd!jeh