-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Another odd LZH from Atari ST #1257
Comments
@gingerbeardman just was taking a look at this file. It has some kind of Germanish wording before an unusual LZH signature. I'm not sure if this is a variant of the format or just a corrupt one. Do you have any other example from the same site/provider? |
If you browse using DiscMaster you'll see that it was able to parse the whole archive and it's all navigable and human readable, so it seems to be complete. Here's a link to a different copy of the same LZH (hash matches): DicMaster powered by Dexvert: Also, this is very low priority... I just mentioned it as a point of interest! |
I don't have a working Atari ST setup with LHA/LZH decompressors... but: After research: this file uses using
using
MacLHA on Macintosh System 7.5 complained but was able to extract it all. |
Other fails from this folder: http://discmaster.textfiles.com/file/11869/www.umich.edu.archive.2014.03.zip/www.umich.edu/~archive/atari/Games/Puzzle/ |
Ok my bad, I was overlooking the extra header info. It actually is a comment, starting with
Just removing the comment helps: I'll check all the comment specifications (if I found them) to fix it properly. |
Cool! Thanks. Interestingly, the other fails are all -lh1- with no comment that I can see. |
Will check those, probably are older since the compression method 1 was used instead of the 5. |
I was using |
Also implemented the detection and proper parsing of the commented file in the build above. |
http://discmaster.textfiles.com/file/11869/www.umich.edu.archive.2014.03.zip/www.umich.edu/~archive/atari/Games/Puzzle/nanjin11.lzh
Originally posted by @gingerbeardman in #84 (comment)
The text was updated successfully, but these errors were encountered: