Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange nested double extraction of this LZH #395

Closed
gingerbeardman opened this issue Apr 8, 2019 · 8 comments
Closed

Strange nested double extraction of this LZH #395

gingerbeardman opened this issue Apr 8, 2019 · 8 comments
Assignees
Milestone

Comments

@gingerbeardman
Copy link
Contributor

@gingerbeardman gingerbeardman commented Apr 8, 2019

Similar to #390?

font_all.lzh.zip

from: http://rutosa.com/pp/font_all.lzh

I get an error

Screen Shot 2019-04-08 at 12 59 06

and this output

Screen Shot 2019-04-08 at 13 04 31

...seems to go into recursive/infinite loop?


Archiver.app extracts it without error.

Screen Shot 2019-04-08 at 13 04 52

@gingerbeardman gingerbeardman changed the title Unable to extract this LZH Strange nested double extraction of this LZH Apr 8, 2019
@aonez aonez self-assigned this Apr 8, 2019
@aonez aonez added the wont fix label Apr 8, 2019
@aonez aonez added this to the 1.1.15 milestone Apr 8, 2019
@aonez
Copy link
Owner

@aonez aonez commented Apr 8, 2019

Hi @gingerbeardman!

The duplication most probably was because you run the operation twice, and one of the times inside the previous extraction? I did not got that result.

As for the error, the file seems to be corrupt. The file s8.bdf is only partially extracted. The original file was 878293 bytes but only 786432 can be extracted. I'm not sure why the Archiver.app does not show the error, but it also only partially extracts that file.

This is the output generated with lha-1.14i-ac20040929:

PAWFF.LOG	- Melted   :  o
s8/s8hn.bdf	- Melted   :  oooo
s8/S8.FNT	- Melted   :  oooooooo
s8/s8.ttf	- Melted   :  ooooooooooooooooooooooooooooooooooooo
s8/s8.txt	- Melted   :  o
s8/s8_jos4.prc	- Melted   :  ooooooo
s8/s8.bdf	- Melting  :  ooooooooooooooooooooooooooooooooooooLHa: Error: Bad table (case a)
LHa: Removing: s8/s8.bdf

Maybe you can try downloading that file again, in case it was downloaded.

@gingerbeardman
Copy link
Contributor Author

@gingerbeardman gingerbeardman commented Apr 8, 2019

No, I do not run it twice.

Using Keka 1.1.14

Video: https://0x0.st/zZ4V.mov

@gingerbeardman
Copy link
Contributor Author

@gingerbeardman gingerbeardman commented Apr 8, 2019

Also get bad table with this one, which results in two files from Keka.

Screen Shot 2019-04-08 at 20 32 05

dasaji_w-1.lzh.zip

If they are truly bad, that is a shame. I will investigate.

Yes: this one was incomplete download. https://www.vector.co.jp/download/file/data/writing/fh085161.html

File in OP is complete download so must be bad file.

Sorry!

@aonez
Copy link
Owner

@aonez aonez commented Apr 10, 2019

Just reproduced the double compression, reopening this one. Thanks @gingerbeardman!

@aonez aonez reopened this Apr 10, 2019
@aonez aonez added the fixed label Apr 10, 2019
@gingerbeardman
Copy link
Contributor Author

@gingerbeardman gingerbeardman commented Apr 10, 2019

What was the problem?

@aonez
Copy link
Owner

@aonez aonez commented Apr 10, 2019

What was the problem?

Since 1.1.14 if UNAR fails P7ZIP is used instead. In this case UNAR fails but extracts some files then P7ZIP is used, hence the duplication. Just removing that first failed extraction.

@aonez
Copy link
Owner

@aonez aonez commented Apr 10, 2019

It's curious how some apps I've tried with this fonts file just ignore the existence of the damaged s8.bdf file.

@gingerbeardman
Copy link
Contributor Author

@gingerbeardman gingerbeardman commented Apr 10, 2019

It's curious how some apps I've tried with this fonts file just ignore the existence of the damaged s8.bdf file.

@aonez indeed it is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants