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.

In addition, version 0.99 of the command-line utilities has been released. The 0.99 version number signifies that the interface for them should now be the one that will go into 1.0, and which will be stable from 1.0 onwards, but there might still be some tweaks before that. Hopefully nothing will change, though.

Mac OS X version: http://theunarchiver.googlecode.com/files/unar0.99.zip
Windows version: http://theunarchiver.googlecode.com/files/unar0.99_win.zip
Source code: http://theunarchiver.googlecode.com/files/unar0.99_src.zip

• All the file-format-related improvements from post >>34 also apply to this version of unar and lsar.
• The command-line interface has changed drastically. Things have been renamed, moved around and lots of stuff has been added.
• The JSON code output by lsar in JSON mode has also changed.
• unar now has interactive prompts to deal with file collisions and similar things. There are also options to override the prompts.
• unar can now enclose extracted files in subdirectories, much like The Unarchiver. There are various command-line options to control the behavior.
• lsar now has a long format (-l) which displays more information about files.
• The programs now exit with error codes on errors.
• The Windows version no longer needs the OpenSSL dll file, and now only relies on Foundation1.0.dll.
• There is now a separate source code archive for unar and lsar. It contains mostly the same as the The Unarchiver source archive, except for the GUI-specific parts.

Grabbin' it.

Any chance this could open Nero .NRG files?

>>37

Some proprietary ISO formats work. I think .CDI works, but I forget if I tested .NRG. Try dropping one on the icon and seeing if it works. I haven't yet added icons for them, though. I'll try to get that done for the final release.

The simple listing of lsar 0.4.0 (only file path, no filesize, etc.) would be nice to have again. Maybe a --short -s option?

>>39

I guess I could possibly also just revert the standard view to the old format. I added the more elaborate one before implementing -l, so it's a bit redundant now.

hi the unarchiver seems to require a password before it unzips my file but i don't know of any password. please help! thank you!

>>41

Ask whoever made the file.

Here is another alpha release of 3.0:

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

Just a few changes: Support for broken RAR files created by some unidentified archiver, and Japanese, German, Russian and Italian translations.

What I'd really need now are some more translations! I can't seem to get a hold of a lot of the people who did the previous translations, and so I'll need to find some new volunteers. If you'd feel like translating The Unarchiver into your language, please grab the source archive, and then go through the .nib and .strings files in the English.lproj folder, and translate them all, then send me the results.

The source is here: http://theunarchiver.googlecode.com/files/TheUnarchiver3.0alpha2_src.zip

>>35
IMO making xadmaster in a DLL or merging lsar as an option/switch of unar can make the binary size smaller.

I'm trying to create Bash completion specifications for lsar and unar. When it tries to complete an archive name, I'd like it to only offer the names of archive files. Is there a list of extensions that I could use to filter the list of filenames?

>>45

Not really. The Unarchiver doesn't look at extensions much.

You could try to dig out all the extensions listed in the Info.plist file that that the Mac OS X version uses to register for filetypes, maybe.

lsar says this file is corrupted xttp://pastebin.com/VvYp3ir6

>>47
agh, lsar directly from mercurial source.

>>47

Looks like a really new issue, I'll look into it later. For now, try hopping back a few revisions and see if it goes away.

http://apps.bandisoft.com/bandizipx/
doesn't it look like The Unarchiver?

bug report

OSX Lion 10.7.2,The Unarchiver 2.7
Unarchivering x,-,+
and Minimize.
Don't exist to app.

>>50

Hahahah, it sure does. And they're not supplying any source, which is a license violation.

>>52
Sue them for $100,000/day.

I have downloaded the unarchiver for my Mac, however, I can't seem to open the file. It shows this screen and nothing more.

Any suggestions?

Hi. Sorry for the delay.

>>40
Please do. That'd help a lot.

>>49
If I update to the revision 660:db09ff7312a9, just before the tip 661:7006e72e3a01 "Apply Zip64 fix from Greg Seitz", the error disappears.

try to put all of them on or try to up date your computer

The attached file will expand with version 1.6.1 but not 2.7.1

Version 2.7.1 gives error "Could not write to the destination directory."

-Bill

God, BandiZipX even sells in App Store for $1.99 USD!
http://apps.bandisoft.com/bandizipx/

Cyrillic is totally not supported. Every zip and rar has broken filename.

>>59

Please file a bug, with example files and information about what the correct output should be.

Hi,

http://bjfrj.blogspot.com/2012/01/john-talabot-fin-2012.html

the pwd protected rar archive above can not be opened with The Unarchiver. It extracts without problems with Alexander Roshal's unrar 3.60 on the cmd line.

Regards,
Klaus

>>61

It works fine here. What version are you using?

>>55

Should be fixed now, I think.

Time for another alpha version. It's mostly done now, though:

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

However, I am still lacking translations! The Danish, Spanish, French, Korean, Portugese, Swedish and traditional and simplified Chinese translations have not been updated for 3.0. I'd really like to find someone to translate these before the final release, and also any other language which is not supported yet.

(I guess I should just do the Swedish one myself, but I'm not sure I even know Computer Swedish...)

Changes from alpha 2 include:

• Enabled sandboxing. Hopefully this doesn't break anything. This could use some testing!
• Support for old High Sierra CD images.
• Support for LZMA2 in 7z.
• Support for multi-volume StuffIt files.
• Cleaned up the filetypes and added some ISO image formats, like CDI, NRG and MDF.
• Fixed some self-extracting LZH files. (That means Touhou 7.5.)
• Filename encoding handling bugfixes.
• Zip64 fixes.
• Symlinks in zip files were broken.
• Less crashing on supported and unsupported sitx files.
• Fixed junk added to the ends of uncompressed encrypted files in RAR.
• Bugfixes for DiskDoubler, tar and MacBinary.

Well, 3.0 is finally released.

http://itunes.apple.com/app/the-unarchiver/id425424353?mt=12&ls=1
http://theunarchiver.googlecode.com/files/TheUnarchiver3.0.zip

It also has a new site:

http://unarchiver.c3.cx/

A summary of the changes, as listed in the earlier posts:

• Support for WinZip Zipx.
• Support for extracting images and sounds from Flash SWF files.
• Support for various Unix formats, such as ar and deb.
• Support for more CD and DVD image formats, such as MDF, NRG and CDI.
• Better support for Zip64 (large zip files) and extended attributes.
• Better support for 7z (self-extracting files, and LZMA2).
• Better support for some old formats, like LBR, StuffIt and DiskDoubler.
• There is now an option to never create an enclosing folder when extracting an archive.
• The icon is now always shown, even when extracting.
• The Unarchiver is now sandboxed.
• Lots of bugfixes.

Also, it is still lacking translations! It is most definitely time for people to step up and contribute some!

Also, the version of The Unarchiver linked in the last post is the one built for the Mac App Store. It has no support for PPC or older versions of OS X. I hope to get a version built that does have this support, but it's getting a bit complicated, so it will be delayed a little bit.

Similarly, there is no WIndows build for unar.exe and lsar.exe yet. These will also follow shortly.

Oh, also, one change that went unlisted: unar and lsar now have less a less terrible Makefile.

Does it means that if i have already bought the Archive Browser, it is no use for me to install the Unarchiver simultaneously?

Hi!

As a French user, I've seen that unfortunately you no longer support French (among others) on the last version of unarchiver, and you were looking for some volunteers :)

I might try to do it and help you to translate it in French (and maybe in Spanish, but let's deal with the French first), but I was wondering.... how ? How could I "submit" a translation, what is the best way to do it according to your needs, ... ?

Sincerely,
Elendil.

Hi,

I could help too for the French translation. Feel free to contact me !

Hi,

I could help too for the French translation. Feel free to contact me !

>>68

It depends on which interface you prefer. The Unarchiver is simpler.

>>69

Download the the source code from http://theunarchiver.googlecode.com/files/TheUnarchiver3.0_src.zip, then use Xcode to translate all the files in English.lproj, and save them in a fr.lproj directory. You can try copying this into the The Unarchiver along with the others to see if it works.

If you get something working, post it on http://code.google.com/p/theunarchiver/issues/list

Ok, there aren't a lot of strings to translate. I'll do it as I need to relax a little, and post it tonight ;-).

Hi again,

I've opened an issue as you asked, with the French translation file attached (http://code.google.com/p/theunarchiver/issues/detail?id=445&q=french)

hey !WAHa.06x36 & guys. can you help me test this? i'm on lion 10.7.3 and i've read sandboxing is causing problems for some developers and users already.

download isoul from macupdate and decrunch it with v2.7.1. launch isoul and after accepting the quarantine warning (this application was downloaded from safari, blah, blah) it should launch ok.

now try to decrunch it with v3. after accepting the quarantine warning, isoul will just stay bouncing on the dock. clicking on its icon will make it exit without warning. if you try to launch it a second time it will launch ok.

this behavior is happening on other apps and i think that it's caused by sandboxing and a quarantine bug in lion. not sure if it's caused by the unarchiver alone or a combination of lion, safari and the unarchiver (i haven' tested trying to download with another browser). can someone try to reproduce it? thanks.

isoul (direct link from macupdate)
http://www.macupdate.com/download/33320/iSoul%200.5.0.b1.zip

sources about sandboxing and qurantine issues:
http://reviews.cnet.com/8301-13727_7-57374676-263/workarounds-for-quarantine-bug-in-os-x-lion/
http://stackoverflow.com/questions/9544874/how-can-i-stop-my-app-from-setting-the-quarantine-bit

The extract from SWF feature is great, I'd love to have the same for PDF files:

• extract the text into a single txt file
• extract the vectors into a raw post script file per page
• extract the images into png or jpeg files depending on the type

>>75

I've noticed similar problems with other apps, and if you extract shell scripts they will not run at all from the Terminal.

I don't think this is technically a bug in The Unarchiver, more an unintended consequence of some OS X features. It should perhaps be reported to Apple.

Also, does Archive Utility do the same thing or not?

you're right it's apple's fault but caused by sandboxing. many people complaining about the shell scripts (also editing with textedit will screw them up but textwrangler and bbedit won't).

both the unarchiver 2.7.1 and archive utility (sandboxed?) work fine.
i guess it's a matter of waiting for the next major os x update (10.7.3 didn't fix it) or mountain lion.

thanks man and best to you.

If you or anybody else find any information about how to work around this, or if anything else needs to be done to fix it, do post an issue about it on the bug tracker.

according to my link above (stackoverflow.com) the LSFileQuarantineEnabled should be set to FALSE in the application's Info.plist (the unarchiver, in this case) but even so, the bug always sets the quarantine flag on items processed by it. another guy suggested removing the quarantine flag programmatically (in this case, to remove it from the decompressed file) but it can't be done since the app is sandboxed. he also confirms that outside the sandbox, this bug doesn't occur. he filed a bug (i guess with apple) so it's a matter of waiting. i'll post if i have more news on this. keep up.

I had the unarchiver installed via mac app store, there was an update today, which i installed. Now when I try to unzip anything I get the error that the dir has no write permission. Other unzippers work just fine. How can I go back to the older version which had no problems? I checked chown and chmod on the ls -hal of the dirs and files, and they are all in order.

>>81

Due to sandboxing, only some paths are allowed. Currently, this is /Users/ and /Volumes/. What is the full path to the places you are trying to extract files from? I can try to add more in the next version.

In the meanwhile, you can get the old version from the Google Code downloads page.

I look forward to seeing the PPC version. I hope the Archive Browser will be PPC-compatible too.

There is no mention anywhere on the new Unarchiver homepage, the old Unarchiver page, or CNET that this latest version is Intel-only. I had to download to find out it wouldn't work.

>>82

re: your sandboxing...

i get the write permission dialog when I try to unzip to /unShared/incoming/

if I choose [extract elsewhere...] and navigate to /unShared/incoming/ the archive is extracted without issue.

i want the old behavior back, please.

i'll be very pleased to do some translation work for The Unarchiver if i have such a chance. i think i'm qualified to do that interpretation from English to Chinese(Simplified Chinese for Chinese Mainland). Just let me know it how to do it?

>>84

Unfortunately, Apple mandates sandboxing, and it is not possible to tell the sandbox that you want to access all files everywhere, at least not that I have found. So you are unfortunately stuck with it.

If you are really desperate, you can build your own version with the sandbox disabled. Maybe I will try to make the build for older version also not use the sandbox, we'll see what is possible.

>>83

The Archive Browser uses lots of 10.6-only functionality, so it will unfortunately never run on PPC.

>>85

I already had one offer for translation into Chinese, but I haven't received anything back yet for that. So I am not sure how to coordinate things so that you do not do the same work.