#Arp & 1.3
2 messages in this thread
If anyone could help me figure out why the new PIPE: device doesn't work
with my setup I would be very thankfull. I am using ARP and WShell with 1.3,
and I complicate matters by using CSA hardware and a GVP 40 partitioned into 2
20meg sections. The PIP: device works fine from WShell, but the new pipe device
won't work when I 'dir > pipe:a' in one window (WShell or AmigaShell window)
and I 'type pipe:a' in the next window. The second window can't find the pipe:
device. To add to the problem I am still using VD0: and have newcon: mounted as
well. I will keep on digging here, and if I find the solution (or another
problem (:-) I will yell out. (I have the 1.2 ROM's as of now.) **************
* Turbo030 * ************** (Will install a '030 when I drop the 1.3 ROM's
in!)
The PIP: device doesn't support file locks, which are required by the ARP
commands which use wildcards. We'll be working on a way to allow use of PIP:
more easily with ARP V1.3. With V1.1 ARP TYPE you should be able to do what
you want with:
TYPE <PIP:A rather than:
TYPE PIP:A
( IE, use redirected input to the ARP Type command ).
…cheath