Path: utzoo!mnetor!uunet!husc6!cmcl2!phri!dasys1!tneff From: tneff@dasys1.UUCP (Tom Neff) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: ZOO/ARC Discussion Message-ID: <4336@dasys1.UUCP> Date: 9 May 88 17:54:49 GMT References: <827@uvm-gen.UUCP> <21371@amdcad.AMD.COM> <1424@iscuva.ISCS.COM> <8405@iuvax.cs.indiana.edu> <4281@dasys1.UUCP> <165@falkor.UUCP> Reply-To: tneff@dasys1.UUCP (Tom Neff) Lines: 27 Summary: not really In article <165@falkor.UUCP> heiby@mcdchg.UUCP (Ron Heiby) writes: >Tom Neff (tneff@dasys1.UUCP) writes: >> or just as good, port the uuencoded text >> stream over to the PC. A perfectly good PC port of uudecode exists. > >What Tom fails to consider with this statement is how *extremely* nice >it was to be able to read through the (almost) non-existent documentation >for a recently posted demonstration ... >... It is VERY important to be able to pull documentation files >out of the archive on the host system (which is usually a UNIX derivative). Tom didn't fail to consider that; Tom is on your side 100%. It's just that, as has already been pointed out at some length in this newsgroup, ARC and ZOO are both running on UNIX and VMS at this time. If you read my posting you must also have read several testimonials to this effect. So get the programs and use them. My point about squirting the uuencodes without trying to extract them was only that if you KNOW you want the file, but just don't have a VAX hosted copy of ARC or ZOO at hand, it's not strictly necessary -- you can do everything on the PC, including uudecoding. If you want to exercise selectivity at the mainframe stage, though, it obviously helps to be able to manipulate the archives right there. Which I believe you can do. TMN -- Tom Neff UUCP: ...!cmcl2!phri!dasys1!tneff "None of your toys CIS: 76556,2536 MCI: TNEFF will function..." GEnie: TOMNEFF BIX: are you kidding?