lim@cluster.cs.su.oz.au (Hong Lip Lim) (02/21/91)
I have found out that if the name of a UNIX file contains more than one dot character (say TEST.1.2), then if I compress them using the lharc program on UNIX and then try to decompress it on the PC (using lharc x lzhname) , I get the following message: LHarc 1.13c (c) Yoshi, 1988-1989 Can't write file : 'TEST.1.2' 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? +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Hong Lip Lim Email: lim@cs.su.oz.au Department of Computer Science Phone: 61 2 692 4276 University of Sydney, Australia, NSW2006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (02/23/91)
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. No version of lharc can solve this, because information must be lost, and it's up to you to decide on a name mapping. Lharc and zip alos seem to lose the file permissions and turn readonly files into regular files. How very nice for them. -- bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) sysop *IX BBS and Public Access UNIX moderator of comp.binaries.ibm.pc and 80386 mailing list "Stupidity, like virtue, is its own reward" -me