As the previous thread filled up, here is part 2 of the The Unarchiver thread.

• The old thread is here: http://wakaba.c3.cx/sup/kareha.pl/1151796773/
• The homepage is here: http://wakaba.c3.cx/s/apps/unarchiver
• The Google Code page is here: http://code.google.com/p/theunarchiver/

It is much better to post bugs on the bug tracker, rather than in this thread! Anything posted on the bug tracker has much less chance of being forgotten by me!

So, post bugs here: http://code.google.com/p/theunarchiver/issues/list

Also, remember that if you post a bug about a file that is not work, you must also post the file itself, or else there is nothing I can do about it!

It would be great if the tool recognized CP/M .lbr archives with lzh "crunched" members, e.g. a file originally named SRC.Z80 would be contained as SRC.ZZ0. Currently, it extracts the crunched file and leaves it compressed. I have not been able to find a Linux based tool that can subsequently handle it.

>>2

Post an issue and provide test cases.

Also, did you try just running unar on the extracted file?

>>2

Actually, I notice I have at least one testcase already with that kind of files. It seems they unpack just fine if I run unar on them for a second time.

However, you are right that it would be a lot more useful to unpack them automatically. Feel free to file an issue about that, at least, so I don't forget.

The Unarchiver 2.7.1 could not open a ZIP archive which is larger than 4GB.
Could you fix this problem?

I am using Intel Mac OS X 10.6.8.

The ZIP archive is too large to send to you.

I have created another ZIP archive using Mac OS X Finder.
(1) Select '/Developer' folder on my Mac.
(2) Choose 'Compress "Developer"' in the File menu of Finder.
The ZIP file is about 6GB. The Unarchiver could not open the ZIP archive.

>>7

I managed to recreate the problem, and will look into it. Thanks!

>>7

Ok, I found the problem. The Finder does not create valid Zip64 files when it makes files that are bigger than 4GB. I added a workaround to try and read them anyway.

So I've just downloaded the unarchiver and it's asking me for a password before it unzips my files. I have no idea what this might be. Could you help me out?

>>10

Not really. You'll have to ask whoever made the files.

First off,

I just want to say what a great app The Unarchiver is and am so happy to discover's maker to be one and the same of one of my favorite sites, wakaba. I am thoroughly impressed with all your coding endeavors and sing your praise.

I stumbled here actually looking for information about command line functions. I noticed Transmission in its preference with the option to Call script when download completes and was wondering if I could plug in a few lines into Automator and maybe make an .rar detection and .rar extraction type thing with Automator.

>> 9

Thank you!

How is your RAR implementation free? Did you implement the virtual machine from scratch? This confuses me.

>>18

Every part is implemented from scratch, including the virtual machine.

Just downloaded on my iMac running Leopard. Is there an option to JUST "view" the archive files WITHOUT unarchiving it into a folder?? I was hoping your utility had that since the default Mac utility also did the same & I do not always want t a new folder created. Thx in advance.

mine constantly gets to about 99.9% done with unarchiving it and just freezes up completely with everything i download.

Hi there - I had posted this 2 weeks ago but have not seen a response yet. Any help will be appreciated -- << Just downloaded on my iMac running Leopard. Is there an option to JUST "view" the archive files WITHOUT unarchiving it into a folder?? I was hoping your utility had that since the default Mac utility also did the same & I do not always want t a new folder created. Thx in advance. >>

Youre app is awesome. Had nearly ten app or command line tries but always problems with the special characters of a zip file I got from a customer. Took me 3 hours to try and fail again and again. Now it was done in 30 seconds.
Thank you, my friend!

Your doc page mentions command-line versions of the tool (lsar and unar). It would be great to include them, along with man pages, on the App Store download. Even if those are just under the .app wrapper and one needs to find them and link to them, it'd be a good addition.

>>25

I might once they are out of beta (which should be next release), if I can figure out a decent way to do it.

I plan to use The Unarchiver in an application. The lsar program does its work great, it just lists the archive files.

One suggestion: please make both lsar and unar exit with an error code when errors occur during the list/extract operation.

>>27

They should do that already, I think?

>>28
$ unar arch.rar ; echo $?
Extracting arch.rar... Couldn't open archive.
0

They exit with an error message, not an error code.

>>29

What version?

>>30
$ unar -h
unar v0.4 (Oct 19 2011), a tool for extracting the contents of archive files.

>>31

Try the current version in the hg repository.

>>32
The hg repository version does exit with an error code. Thanks.

So, I have been working on a new version for some time now. There aren't all that many visible changes, but as I've made lots of changes to the internals of the code, I've probably introduced some fresh new bugs. Therefore, the version has been bumped to 3.0, so that people can see the scary ".0" and know that there might be a few problems.

To avoid the worst problems, I've made an alpha version available, and would very much like for as many brave people as possible to grab it and try to use it, and report any problems. It should work fine most of the time - I am not aware of any outstanding bugs at the moment - but obviously I alone can not test it under all circumstances. Therefore, please grab it and try it.

http://theunarchiver.googlecode.com/files/TheUnarchiver3.0alpha1_64bit.zip

Please don't post it on any software listing sites until it reaches the official release status, though, it is somewhat mean to expose unsuspecting people to unfinished software.

Also, the uploaded version is Intel and 10.5 or greater only, the same that would go on the App Store. The final version will be available for older OSes and PPC, though.

Now, for the change list:

• As mentioned, lots of internal rewrites. The Unarchiver and the command-line tools now use mostly the same code to unpack, unlike earlier when The Unarchiver was stuck with old code. This has probably introduced bugs, so watch out.
• Some UI changes: The icon is now always visible to make it easier to deal with crashes, the file list now shows multi-part archives better, and the password view actually shows the filename of the file.
• It is now possible to explicitly set the encoding for passwords.
• Experimentally added support for never creating an enclosing directory, as has been requested. I am not entirely sure this won't cause problems, though, so it might get removed if it does and can not be easily fixed. Please report experiences with it, good or bad.
• Fixed strange UI lockup that would happen sometimes with password-protected files.
• Full support for WinZip Zipx, including Wavpack and JPEG modes.
• Support for Mac OS X extended attributes in Zip, Tar, and Xar. Also supports setting Spotlight comments from archive comment fields.
• Support for extracting resources from Flash SWF files. Embedded images and sounds can be extracted into separate files.
• Support for Ar and Deb archives.
• Support for self-extracting 7z.
• Support for LBR with embedded crunched and squeezed files.
• Better support for huge Zip files.
• Better support for old StuffIt (thanks to Friendly Archivist),
• Bugfixes for Zip, RAR, Tar, Cpio, HQX, CAB, Zoo, PackIt,

For programmers:

• There is now a XADSimpleUnarchiver class that does a lot of work that XADArchive used to do.
• XADArchive will now use XADSimpleUnarchiver internally. XADArchive is also (still) deprecated, so I am not going to guarantee it will work flawlessly. Feel free to report bugs in XADArchive, but if they are very complicated I might not fix them. New features will not be added to XADArchive either, except those it gets for free through XADSimpleUnarchiver.
• The XADPath interface has changed in various ways, some of them backwards incompatible. Hopefully nobody is relying very much on specific features of this class, but if you do, your code might break with the new version. If you need help fixing it, feel free to ask me.
• Archive entries now have a XADIndex field for easy ordering. There are also new fields giving the index of the next and first solid entry.