Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!beta!hc!ames!oliveb!sun!dbercel From: dbercel@sun.uucp (Danielle Bercel, MIS Systems Programming) Newsgroups: comp.sys.ibm.pc Subject: Re: PK ARC, Another View Message-ID: <23065@sun.uucp> Date: Thu, 9-Jul-87 15:54:23 EDT Article-I.D.: sun.23065 Posted: Thu Jul 9 15:54:23 1987 Date-Received: Sun, 12-Jul-87 07:06:04 EDT References: <287@cpsc6b.cpsc6a.att.com> Reply-To: dbercel@sun.UUCP (Danielle Bercel, MIS Systems Programming) Organization: Sun Microsystems, Mountain View Lines: 50 Keywords: arc, pkarc In article <287@cpsc6b.cpsc6a.att.com> crs@cpsc6b.cpsc6a.att.com (C. R. Seaman) writes: > >Interesting, that a ~30K COM file should determine that my 640K PC didn't >have enough memory. I started poking around, and found that the problem >was not really a lack of memory on my PC's part, but some confused >interaction on the part of the software with my environment (I have it >expanded to about 450 bytes). I discovered that, in order to run >the PK ARC family, I must *completely* wipe out my environment! (I >am using an AT&T PC6300, if that has any bearing). > >After getting the software to work, I then discovered that it apparently >(correct me if I am wrong) can't deal with acrhive files outside the >current directory. And, as if that weren't enough, PKXARC *requires* that >you preface switches with a "/", and doesn't even check the value of >SWITCHAR. > >I have gotten PKARC sort of limping along, but I find these inconveniences >almost outweigh the speed and improved compression provided. > >I would be grateful for any information on how to overcome the problems >I am having, as I have seen just how fast PKARC is (38 seconds to create >an archive that took over 3 minutes with arc). > You have described an environment that is *NOT* anywhere close to my experience with PKARC and PKXARC. I run Phil's programs on my XT and everything is fine. The environment doesn't have to be changed and everything I've set for other programs remains unchanged. Paths are no problem and I have never encountered a situation when I could not use a path name. For example, I have a directory called \tmp. This is the directory where all my downlods go. However, I usually extract files into other directories. The following command works perfectly using PKXARC: pkxarc arcname \dirname\dirname From the various system I access, and the people I've spoken to, nobody has been reporting the problems with PKARC and PKXARC that you are having. Perhaps the environment problem is related to your AT&T PC6300. danielle -- UUCP: {hplabs,decvax,}!sun!toto!{danielle,dbercel} /-------------------------------------\ | Toto, I don't think this is Kansas. | -- Danielle Bercel \-------------------------------------/ Sun Microsystems, Inc.