Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!mcsun!corton!chorus!opera.chorus.fr!mir From: mir@opera.chorus.fr (Adam Mirowski) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: an lharc problem Keywords: lharc Message-ID: <8038@chorus.fr> Date: 28 Feb 91 17:49:06 GMT References: <2108@cluster.cs.su.oz.au> <3280@sixhub.UUCP> Sender: mir@chorus.fr Reply-To: mir@opera.chorus.fr (Adam Mirowski) Organization: Chorus systemes, Saint Quentin en Yvelines, France Lines: 25 In article , valley@uchicago (Doug Dougherty) writes: %% davidsen@sixhub.UUCP (Wm E. Davidsen Jr) writes: %% >In article <2108@cluster.cs.su.oz.au> lim@cluster.cs.su.oz.au (Hong Lip %% >Lim) writes: %% >| One way of course is to ensure that the UNIX files do not contain %% >| multiple dots in their names. But if that is not possible, %% >| is there an improved version of the lharc program on the PC %% >| that does not have this problem? %% > There is no problem with lharc, the problem is that DOS can't accept %% > reasonable filenames. The solution is to extract to stdout and redirect %% > to a file with a restricted DOS name. %% Actually, ZOO does a pretty good job with this. Admittedly, information %% can be lost, but all in all, ZOO is the way to go. What I usually do is to edit the file with a binary/hex editor and substitute another characters in place of the dots. Because the header is under a checksum, it is necessary to change one of the letters to keep it constant. Anyway, maybe the new 2.05 version of lharc manages the name problem? As for the extracting to standard output, if lharc doesn't setmode(1,O_BINARY) then maybe it could be run from a program that does it before doing a system() call. -- Adam Mirowski, mir@chorus.fr (FRANCE), tel. +33 (1) 30-64-82-00 or 74 Chorus systemes, 6, av.Gustave Eiffel, 78182 Saint-Quentin-en-Yvelines CEDEX