LHA 2.15 stopping at 'unable to open file'

[awol2k]

Are you trying this from CLI, SHELL or have tried both?
What have you got your stack set to?
Is this running under a 68060?

Also, shouldn't the command be this way around?:
"lha -2 -a -e -r -x a "

[awol2k]

To be honest, I forget the difference between CLI and shell, it's been a while since I knew!

EDIT:
AmigaOS.net says this:
"For historical reasons, you will still find references to the CLI in AmigaOS but this is really a shell that is used everywhere in the system. "

I did try and reproduce the problem using WinUAE with A1200 config +8MB fast, with the 68020 version of LhA, and a 231 MB directory of files last night
- it wasn't able to complete either.
I ran out of RAM disk about the time the LhA file got to 84MB
- which was about 3 or 4 hours after I started it!

If you haven't tried already I would try archiving it again but using the 68k version of LHA 2.1.5, and see if that makes a difference - as I appreciate the Vampire is not a true 060, but I have heard that some 060's were better at running 68000 code than they were at running 020, 030, or 040 versions of code.

I'm re-running the test but this time with WinUAE configured for 256MB z3 FAST....
This may take a while!

[awol2k]

Turns out my laptop paused WinUAE when I opened VirtualBox, and wouldn't come out of it, so I had to restart WinUAE and the LhA!

I will get back to you...

[awol2k]

Amiga file systems used a bitmap (for where files are located) that is updated regularly, which I guess could cause a performance hit so I guess the developer of LhA tried to mitigate this using RAM:
- I only had 8MB of RAM: configured when i ran out btw.

LhA still going.. 51 MB so far...

[awol2k]

I'd love to know the answer to that too!

Meanwhile, my LhA is using 16,777,216 bytes of RAM:

[awol2k]

Well Manfred,
my LhA job just finished, 231 MB archived to 194MB in a super quick 4 hours and 59 minutes.
How long did yours take again?....

[awol2k]

I wasn't at the computer when it finished, but it was well under an hour.
Manfred

Before I went to sleep, I decided to run a comparison againts 7zip on the i5-3320m Windows 7 laptop I was running that WinUAE on.

To compress the same 231MB of data I did using LhA, i used 7z archive format with ultra compression, 64MB dictionary size and 2 out of 4 available CPUs*

It took 2 minutes and 9 seconds.
While it was running, it used 699 MB of RAM - this amount of ram did not fluctuate - and despite the settings in effect it used all 4 cpu cores to perform the archive process.

Now, the way LhA archives appears to be different.
This archives 1 file at a time into temp and THEN appends the data for that one file only to the LhA file it has created. If the data it is reading from is store on disk, this typically has a big overhead on an amiga. If the LhA file it is writing to is tored on disk, this has a massive overhead on an amiga.

So for a comparison i'm going to repeat the process in RAM: alone.

Edit @ 14:59, 15:01:
WinUAE is reading from DH0: (a windows folder) at approx 500 KBps. This is one heck of a bottleneck.