Welcome, Guest. Please login or register.

Author Topic: LHA 2.15 stopping at 'unable to open file'  (Read 3715 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
LHA 2.15 stopping at 'unable to open file'
« on: January 17, 2018, 03:02:34 PM »
Hi.

I'm trying to archive a large folder (~200MB).
Using LHA it will always stop at some file, telling me that it cannot open it for reading. Depending on what's in the archive it is always a different file.
This is my lha cmdline: "lha -2 -a -e -r -x a ".
What could this be?

(Works fine with LZX.)


Manfred
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #1 on: January 19, 2018, 07:57:19 AM »
Hi.

Yeah, cmd line is the other way around.

The stack was a good pointer. Because there are a _lot_ of files and it seems LHA scans them all before compressing.
So I've increased the stack of the Shell from 4k to 128k. Unfortunately it didn't help.
What's the difference between CLI and Shell?
This is a 68080 (Vampire) CPU.


Manfred
« Last Edit: January 19, 2018, 08:00:08 AM by asrael22 »
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #2 on: January 19, 2018, 07:33:17 PM »
Hmm, that doesn't make a lot of sense.
Why would it eat up such a lot of fast ram?
If that really is the case then it's a bug.

I don't think it has something to do with the Vampire. Although I cannot be sure.
I'll try the same thing on a 68060.



Manfred
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #3 on: January 19, 2018, 09:20:19 PM »
Hmm, that seems to have worked.

What is that setting?



Manfred
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #4 on: January 20, 2018, 09:06:46 AM »
Hmm, that's interesting. Actually I've looked for some options and have seen -b option.
But I didn't try it because I thought that I/O buffer only sets the general read/write buffer for the files. The documentation does not mention that this setting helps with lots of input files to complete at all. So I'm a little surprised.

Anyway, this setting has helped.
Thanks a lot.


Manfred
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #5 on: January 20, 2018, 09:12:39 AM »
Quote from: awol2k;835185
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?....


256MB compressed to 99MB.
Didn't take the time. Will do again. Currently in operation...
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #6 on: January 20, 2018, 10:31:09 AM »
Quote from: asrael22;835195
256MB compressed to 99MB.
Didn't take the time. Will do again. Currently in operation...


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


Manfred
 

Offline asrael22Topic starter

  • Jr. Member
  • **
  • Join Date: Mar 2017
  • Posts: 77
    • Show all replies
Re: LHA 2.15 stopping at 'unable to open file'
« Reply #7 on: January 20, 2018, 10:32:10 AM »
Quote from: asrael22;835194
Hmm, that's interesting. Actually I've looked for some options and have seen -b option.
But I didn't try it because I thought that I/O buffer only sets the general read/write buffer for the files. The documentation does not mention that this setting helps with lots of input files to complete at all. So I'm a little surprised.

Anyway, this setting has helped.
Thanks a lot.


Manfred


Even more curiously, setting a 64k buffer (-b64) doesn't work either.