#help with LHARC
20 messages in this thread
Hi! I'm having trouble extracting .LZH files. I've downloaded LHARC.EXE
and changed the name to LHARC, and placed it in my C: directory, but I keep
getting the message "Cannot create directory ''" Any ideas? I am really
stumped, because I've gotten it to work once (too bad I didn't use it on
UNDOX.LZH, huh?). Comments or suggestions welcome (begged for…)
Thanks,
Jay Gallagher
70402,156
What is the exact line you're typing to extract files? It should be
something like: LHARC x filename.lzh
Steve
That's exactly what I'm typing. I've also tried LHARC -m -x x <file.LZH>.
That worked the first time, but not since. I thought that in the shuffle,
something necessary had been deleted, so I downloaded it a second time with
tthe same results.
Jay Gallagher
Jay,
Is it possible that you have a FILE in that directory that has the
same name as a directory that LHarc is trying to create? For example, if
you had a file called "doc" in that directory, and lharc tried to extract a
file called "doc/read.me" there'd be a conflict between the name of the
directory and an existing filename.
Try doing the extraction in RAM: and see what happens.
Don
Hi Jay!
Sounds like you may have a problem with disk space, or, rather, the lack
of it. Make sure you've either CD'ed to a volume with lotsa room on it, or
use the path option in LHARC: e.g.
lharc a LZHFILE.LZH BIGDISK:directory/
Note that the path MUST end with a volume (:) or a directory (/)
The other option is to CD to a different volume/directory and then path
to the archive, providing it's not already _in_ that directory…
cd otherplace:downloads
lharc a overhere:whereitwuz/lzhfile
The easiset method is to just have a copy of the .lzh file in some
directory, CD to it, then invoke LHARC a lzhfile.
The last helpful hint: While the .lzh is not needed when invoking LHARC,
it MUST be the file's suffix
File is named things.lzh, "lharc a things" will work.
File is named "things.arc" "lharc a things.arc" will NOT work
Hope this helps,
Doug
Jay,
Suppose that youhad UNDOX.LZH in RAM: Here is how you would unpack it,
also in RAM:
MAKEDIR RAM:UNDOX
CD RAM:UNDOX
LHARC -m -x x RAM:UNDOX.LZH (the .lzh is not really necessary. I just
put it here to distinguish the new directory from the original file.)
Betty
Betty, It's interesting that Jay is having this problem. Wherever I put
LHarc and whatever I type I always get "Unable to load LHarc – file is not
an object module". As you will remember, I've been banging on about this
for some time now. I got a copy of LZ from AUI magazine and that works
fine. OK, next thing – I download PKAX.LZH and unpack it. Guess what
happens – "Unable to load PKAX – file is not an object module". This is
error code 121. Anybody, please, please,please – what is happening here??
Bill Hardman
– via Whap!
Are you trying to RUN the programs? You cannot just run them – though the
rest of your message indicates that you already know that! You have to
give them something to work on – such as LHARC -m -x x filename.lzh.
Betty
I'm making gradual progress with the beast now. I've got a working copy of
LZ which copes with most .LZH's etc and have now got PKAZIP working as
well. This has the intuition interface and can handle the .ZIPs. With PKAX
and LHARC I still get this peculiar error message 121 – "file is not an
object module". Now if the computer cannot load the file at all it cannot
do anything with it. LISTING them shows —-rwed no problems but it still
won't load them.
– via Whap!
With LHARC, are you trying to load it, or are you commanding it to work on
a file? LHARC itself will not load, but if you command it, such as:
LHARC -m -x x path:filename.lzh
then LHARC ought to load and go to work on the file. If it does not, I
suspect you have a bad copy of LHARC.
Betty
Bill,
Note the "LZH" extension on PKAX.LZH. That means it's a packed
file, you first need to extract the runnable files from the archive before
they can be used.
Don
Don, I have done but I still get this error code 121 "unable to load PKAX –
file is not an object module". If not an object module what the h… is it?
– via Whap!
Bill:
If you downloaded LZH.ARC it needs to be decompressed with ARC. If you
downloaded LZH.EXE you need to rename the file to: Lharc (with no
extension).
Good luck.
Michael
….from the north coast
Michael,
Please…it's not necessary, although it makes it easier, to rename
files with .EXE extensions in order to get them to run. It's simply a
convenience.
Don
Don:
To someone unfamiliar with AmigaDos, coming from an MSDOS background, it
could appear that a program with a filename extension of EXE could be
executed by entering the filename without the extension. In other words, a
PC'er might try to run the program LHARC.EXE by entering:
LHARC
which would return an error: "file not found". On a PC, it would work, on
an Amiga, it would not.
The person posting the message asking for help originally stated that they
were familiar with PC's and not the Amiga. Renaming LHARC.EXE to LHARC is
most appropriate in this situation, in lieu of a discussion of AmigaDos
command syntax, no?
Michael
….from the north coast
Michael,
No, since the specific error he saw was 121 (Not an object module)
which means he "located" the file, just couldn't get it to execute.
Don
Bill,
Oh dear…you're going to hate this. PKAX.ARC is an ARCHIVE file
and needs to be extracted using ARC.EXE which is in LIB 16, and will run as
downloaded.
Unfortunately, there has been a proliferation of archivers,
crunchers and so forth and each needs a different extraction program get
the executables out.
We used to require all our files be in ARC format, but along came
ZOO files which provided better compression. Then ARC lost it's support
and ZOO got even better. Then along came ZIP and LHARC and WHARP and
LHWARP'ed files and so forth.
There was no way we could force a single archive standard any more,
so there are several available.
We do have the file ARCHLP.EXE (also executable after download)
that explains what the various archive programs are, where to get them and
how to use them. It explains what the various filename extensions means.
I'm sorry it seems like we keep telling you you've got to get
another extraction utility, but believe it or not…I *think* you've got
them all by now…and once you've got them you'll not need to go thru this
garbage again.
Don
Don, I extracted PKAX.ARC with LZ and I think it extracted OK. Still won't
work. I've been trying to download ARCHLP.EXE but in common with several
other people (see Amigavendor) Whap! now seems unable to download anything
at all. Is there no end to it? It's going to be back to Tapcis at this
rate!
– via Whap!
Bill,
Two thoughts come to mind. The first is that the telecom service you're
using is chopping the high-bit of each byte. That's happened to a lot of
people in the past, and was common for a while for many 'overseas' CIS
users. If _none_ of your binary downloads arrive properly you may want to
contact them as to what might be done to remedy that.
The only other is that you're the culprit, using 7-N-1 for your
communications. The instructions are wrong on this, for most terminals
don't set the parity when downloads begin, just using what they've been
told to use for the entire session.
If you've found out that this is the case and you can't change your
settings due to restrcitions beyond your control, and you still want those
downloads, you might try using Kermit for your protocol while downloading.
Kermit is slow, but doesn't use the high-bit. It was originally designed
for allowing binary transfers over hardware that only allowed 7-bit 'bytes'
over the transmission lines and may be worth a shot.
Hope this helps,
Doug
Doug, I'm using Whap! on to the CIS London node which doesn't use any other
PSS type service. Some downloads work OK – it's just these 2 which are
giving me the problems. Bill
– via Whap!