So. I kind of like BOMArchiverHelper.app, the default OS X unzipping utility. However, it has quite a number of limitations. Most other unarchivers on OS X have interfaces that I don't like, or just don't work very well. Also, thanks to Windows' idiotic idea of using the current system encoding for filenames, I have tons of archives from Japan with Shift_JIS filenames, which none of the unarchivers on OS X I've tried will handle properly.

And so I, because I obviously don't have enough to do already, get the idea that I need to write a better unarchiver. Features I think it needs include:

• Handle as many formats as possible. Not just Zip and Tar-Gzip, but RAR, 7-Zip, LhA, StuffIt, and anything else you can think of.
• Handle non-UTF8 filenames, perferrably automatically.
• Have a simple and straightforward interface like BOMArchiveHelper.app.
• Not leave .tar files lying around when unpacking .tar.gz files and the like.
• As a side benefit, produce some code that can be re-used to add archive support to Xee (so this whole project doesn't just steal time I could be working on Xee instead).

For actual information on the current state of this project, read on!

>>899

Ah, yes, that'd explain it. Basically, Archive Utility will mark all files executable if there's no information specifying otherwise.

>>900

It should be, but most programs produce invalid zip files for data larger than 4GB, so unarchiving programs have to try and compensate to get the data out. Which version are you using?

>>902

Like I said, it should work better in 2.7, and in the meanwhile, report it to Blizzard. The zip tool they are using is the actual problem.

(for your information only)

>>901

franck went ahead and published the new grafx2 version (and future ones, i hope) in a standard .tgz which keeps execution bit attributes preserved.

http://code.google.com/p/grafx2/downloads/detail?name=grafx2-svn1759-macosx.tgz&can=2&q=label%3AOpSys-OSX

>>902

even if we are lucky that !WAHa.06x36 fixes these issues for us, devs who distribute files for mac should use a mac compliant app to archive them, but i guess it's normal they don't know about the architecture of bundles and attributes on this platform.

I'm sorry, I don't understand what to do with the binaries to compile anything for Windows.
The Unarchiver is such an extraordinary tool for everyday use, it's one of the things I miss the most when I'm working on a PC.
Do you think it's possible to put a version out there for windows users ?

Thanks a lot for that incredible work !!

>>895
It doesn't seem well-documented at all - I can't find anything much on its technical specs, only that it is typically more efficient than .zip and .rar. It seems to have a niche following though, so it'll be up to you whether it is in use enough to merit support. Just a suggestion, and I managed to decompress my own files in any case. Thanks for The Unarchiver man, regardless of whether you take up my suggestion :).

Cheers,
Franklint

Have downloaded a file in two parts. When attempting to expand I get the attached message. How do I put the two parts together before expanding or hiow do I get past the error message???

I am trying to use The Unarchiver to read a ZIP file produced by 7-zip which is AES-256 encrypted. Unarchiver recognizes the file, opens it, and prompts me for the password. When I enter the correct password, it tells me each file in the archive is corrupted.

Suggestions?

>>908

File a bug on the bug tracker, including the file and correct password.

Well, I finally got it sorted out. There's a new version now, and it's available on the App Store.

http://itunes.apple.com/app/the-unarchiver/id425424353

If you can't or don't want to use the App Store, it's still available normally:

http://theunarchiver.googlecode.com/files/TheUnarchiver2.7.zip

The direct download version is still 32-bit x86 and PPC. The Mac App Store version is 32-bit and 64-bit x86. I'm going to put up the App Store version for direct download too later.

Other updates:

• Support for ISO and BIN disc images.
• Support for encrypted StuffIt archives, thanks to a friendly archivist.
• Workaround for broken Zip archives that make files non-executable.
• Fixed unpacking .pkg files.
• Better StuffIt X support.
• Other bugfixes.

The unar and lsar command-line utilities have been updated too:

http://theunarchiver.googlecode.com/files/unar0.4.zip
http://theunarchiver.googlecode.com/files/unar0.4_win.zip

The Windows version hopefully includes all the required DLLs this time.

Is there a reason the app is only available in the U.S. App Store?

Well, here's the 64-bit App Store version for anyone who wants it, but can't use the App Store:

http://theunarchiver.googlecode.com/files/TheUnarchiver2.7_64bit.zip

>>912

Is it? I can see it in Finland. Where can you not see it?

>>910
I have tried TheUnarchiver2.7 on PPC G3 and G4 running 10.4.11

Every time TheUnarchiver2.7 will start to unarchive a file, but it never finishes and I need to force quit it.
SHA1 is correct.

Console log:
2011-04-17 10:36:35.561 The Unarchiver[760] *** -[NSFileManager contentsOfDirectoryAtPath:error:]: selector not recognized [self = 0x507c00]
2011-04-17 10:36:35.562 The Unarchiver[760] *** NSThread: ignoring exception '*** -[NSFileManager contentsOfDirectoryAtPath:error:]: selector not recognized [self = 0x507c00]' that raised during delayed perform of target 0x596290 and selector 'extractFinished'

No problem with TheUnarchiver2.6

Any suggestions?

I have exactly the same proble as >>910. So far have attempted to unarchive two fairly large archives (over 300MB), and when it gets to the part where it has to make the tempfolder visible, set the permissions, whatever, it hangs, leaving the Unarchiver window open and permanently present (the X won't kill it). It does get far enough so the progress bar becomes steady Aqua (not pulsating), But I have to go to the Activity Monitor to kill it, and, of course, this leaves invisible and sometimes hard to find GIANT folders behind. It appears to do a good job of unpacking, but only an experienced user will be able to find the files and quit the program window.

I'm not certain if other file tasks are being completed, since the archives I used consisted of multi-thousands of small documents (txt, png, jpg, cvx, eps, ai, etc.). After moving the invisible folders to the desktop and making them visible, they look fine, and taking a random sampling, they all open without any sign of corruption... but with this many files, I have no idea if any were skipped, corrupted, or if naming and permissions were done correctly.

Another note, once it has been force quit, I cannot get it to relaunch properly until I reboot. If an attempt is made to open an archive that is supported, nothing happens. So force quitting IS NOT a valid method of terminating the program.

>>915-916

10.4 is accidentally not supported. Use 2.6 until it gets fixed.

>>916
If you use Unarchiver 2.6 on those files that failed with version 2.7
the invisible files will be "deleted". No need to find and delete.

2.7.1 is now available, and should hopefully fix compatibility with 10.4 and maybe even 10.3.9:

http://theunarchiver.googlecode.com/files/TheUnarchiver2.7.1.zip

That is the only change. Anybody on a newer version does not need to update, and there is no update for the Mac App Store version, as it does not work on 10.4 in the first place.

>>914

Not available in the Australian Mac App Store. :(

>>920

Complain to Apple. The App Store seems kind of buggy.

Hi,
Downloaded it from canadian app store. Say installed but can't find it anywhere???

/usr/bin/ld: libXADMaster.a(CSZlibHandle.o): undefined reference to symbol 'inflateInit2_'
/usr/bin/ld: note: 'inflateInit2_' is defined in DSO //usr/lib/libz.so.1 so try adding it to the linker command line
//usr/lib/libz.so.1: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make: *** [unar] Error 1

>>922

It should install just the same as any other App Store app. If it doesn't, complain to Apple.

>>923

What exactly are you doing? And is your libz installation really working right?

I followed the instructions, running make -f Makefile.linux. Debian doesn't have a libz package. It has a zlib1g-dev package that provides libz-dev.

>>923

Kete, you need to add "-lz" to the LIBS variable in XADMaster/Makefile.linux.

I'm in the process of creating a Debian package of The Unarchiver. You can find out more at http://bugs.debian.org/619602.

Matt, I don't know how to do that, tried LIBS=-lg
Godspeed (on the package)

>>927

Kete, you should be able to download a fixed XADMaster/Makefile.linux from https://theunarchiver.googlecode.com/hg/XADMaster/Makefile.linux.

>>915 >>919
Recently I was given an iBook G3 with 10.3.9

It seems Unarchiver version 2.x.x is NOT compatible with 10.3.9
They all fail the same way. Do you want the crash.log's?

The Unarchiver271.crash.log
The Unarchiver260.crash.log
The Unarchiver250.crash.log
The Unarchiver240.crash.log
The Unarchiver230.crash.log

Unarchiver161 works on a G3 with 10.3.9

Unarchiver271 works on a G3 with 10.4.11

-Bill

>>929

I guess it doesn't work on 10.3.9, then. I can't really do much about that, other than accept a patch if anyone figures out how to make it run.

>>928
Thanks, Matt, that worked without error, but I don't see where to go from here (sorry!).

I have recently encountered some weird behavior form this great app.
I will click on a .zip, .rar, ect file and it will do it's thing.
BUT I have to back out of that folder then go back into it in order for the items to reveal themselves?
I hope I'm explaining this well enough for some to understand me.
Might anyone have thoughts on how to correct this?
I did uninstall then reinstall....
no luck.
Thanks in advance

>>932

It has to do with the NFS (unix "nightmare file system") setup used on most LAMP webservers. It's none of your own fault. Trust me; I use a linux box for my home and business computings...

Have a nice day.

>>933

Shoot, just realized we weren't talking about LAMP software here! lol.

I just was reading an old post of mine on Kareha board installs, and then read this and my mind didn't immediately make the switch heh heh.

Sorry bout the screw up.

>> 932

the reason for your issue is the same, sans the LAMP webserver part. Macs are Unixes for no other reason than Jobs wanted to run the new NEXT/Mac on a Unix architecture, so he utilized the nightmare filesystem.

Besides Linux/BSD/Unix/Mac FS's being a load of cow crap, everything else in their makeup is far better than Windows, IMO. I could smash glass anyday, but give me a Linbox and I'd marry it on the spot (not being literal here).

Have fun. Hope this helps!

Won't help as a quick-fix for OS X native unarchiving. Why? This download can't unarchive itself!!!! You are not thinking! How can you put an unarchiving utility in an archive????? Duh!!!

>>931

Kete, you should now have lsar and unar executables. They should run correctly if built in wheezy (aka testing) instead of sid (aka unstable).

hi, when we have unarchiver on official debian packages?

>>937

I don't know; there are toolchain problems that prevent uploading to unstable yet.

In the meantime, you can download a Debian source package from http://anonscm.debian.org/gitweb/?p=collab-maint/theunarchiver.git;a=summary which you should be able to build in testing.

>>932

This is a Finder problem which I'm not aware of any workaround for. The answer given in >>934 is completely incorrect.

Any hope of being able to unarchive .kgb files

>>940

Depends. Apparently it is actually somewhat documented, so it would be possible, but I don't know if it is in wide enough use to be worth the effort.

>>940

Looking a bit closer into it, KGB is based on PAQ6, which is GPL licensed, and thus cannot be included in The Unarchiver, which is LGPL. Adding support would require the author of PAQ changing his license to LGPL.

Okay, thanks, Matt, I'm finally lsaring and uraring.

I'm a beginner here so I may be asking a dumb question, please bear with me as I've not been able to find an answer anywhere else.
I zipped a large folder of files to save space on a laptop (zipped, about 5GB) using the built-in function in Windows XP. I changed the name of the zip file - from something like xyz_123.zip to 1.zip. Now XP's inbuilt extract says that the archive is 'incomplete' or 'corrupted'. I've tried various other programs (7-zip, Winzip, etc) without success. I moved the archive over to my iMac (10.6.) and tried Stuffit Expander also without success. I then discovered The Unarchiver and tried it: It started to work and extracted about 10% of the files before failing with "Error during decrunching".
Any ideas?
The only thing I can think of: is it a bad move to change the name of a .zip archive? Is the name also internally-coded so that both must be the same?
cheers, and thanks in advance if you answer my questions.

When downloading from the Mac App Store, the application appears to install and then reverts back to the "Install" button and without the application appearing in the Applications folder. If you look under purchases, there is an "Install" button beside the application.

>>945

It is possible that XP's built-in archiver doesn't support archives more than 4 GB and actually broke the archive while making it.

>>946

That would be an App Store bug, so report it to Apple.

I clone the theunarchiver repository hosted at Google Code and I compiled on my GNU/Linux Fedora 15 box

$ make -f Makefile.linux
gcc -std=gnu99 -c -O2 -Wno-import -Wno-multichar -g -D_FILE_OFFSET_BITS=64 -isystem /usr/include/GNUstep -DGNUSTEP -DGNU_RUNTIME=1 -D_NATIVE_OBJC_EXCEPTIONS -fgnu-runtime -fexceptions -fobjc-exceptions -fconstant-string-class=NSConstantString unar.m -o unar.o
In file included from /usr/include/Foundation/NSClassDescription.h:30:0,

             from /usr/include/Foundation/Foundation.h:50,
             from XADUnarchiver.h:1,
             from unar.m:1:

/usr/include/Foundation/NSException.h:42:2: error: #error The current setting for native-objc-exceptions does not match that of gnustep-base ... please correct this.

Searching on the web, I found a workaround for this problem [1] by changing the line

#define BASE_NATIVE_OBJC_EXCEPTIONS 0

from /usr/include/GNUstepBase/GSConfig.h into

#define BASE_NATIVE_OBJC_EXCEPTIONS 1

The next message error was

gcc -Wl,--whole-archive -fexceptions -fgnu-runtime -o unar unar.o CSCommandLineParser.o CommandLineCommon.o NSStringPrinting.o libXADMaster.a ../UniversalDetector/libUniversalDetector.a -Wl,--no-whole-archive -lgnustep-base -lcrypto -lbz2 -licuuc -lobjc -lstdc++ -lm
/usr/bin/ld: libXADMaster.a(CSZlibHandle.o): undefined reference to symbol 'inflateInit2_'
/usr/bin/ld: note: 'inflateInit2_' is defined in DSO /lib/libz.so.1 so try adding it to the linker command line
/lib/libz.so.1: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make: *** [unar] Error 1

as stated [2] and [3] I fixed this by adding -lz ([3] comments that Fedora have a setting preventing gcc of
implicit linking.)

OK, after that I've got lsar and unar binaries. Great !

However, I've found there I've got this problem descompressing rar files (both with lsar and unar):

$ ./lsar ~/Desktop/example.rar
/home/jjmarin/Desktop/Evince/example.rar :
1.jpg
2.jpg
./lsar: Uncaught exception CSEndOfFileException, reason: Attempted to read past the end of file "/home/jjmarin/Desktop/Evince/example.rar" (XADFileHandle).

Any idea about this ? Has something to do with the BASE_NATIVE_OBJC_EXCEPTIONS change?

Links:
[1] http://www.mail-archive.com/[email protected]/msg12043.html
[2] http://wakaba.c3.cx/sup/kareha.pl/1151796773/l50
[3] http://groups.google.com/group/harbour-devel/browse_thread/thread/1d0c52b293f35c53?pli=1

>>949

You need a GNUStep built with native exceptions enabled, there is no way around this. You'll have to figure out how to get this on your distro. Either by building from source, or by pestering the maintainers until they fix this, most likely.

I'm trying to unarchive several archived files at once, but I want to extract them all to the same folder. It does look like this option is available in the preferences? It extracts each one to its own folder. I have" more than one top-level items" selected, but it still does it assuming they are all top level... any solution? Thanks!!

Hi, I use The Unarchiver 2.6 to join the split .rar files from this site:
http://doujin-games88.blogspot.com/2011/01/ps3-umineko-no-naku-koro-ni-majo-to.html
and then extract it.

There aren't any error messages during the process, but somehow the extracted files at the end got corrupted (doesn't work properly on PS3).

Then I use winrar to extract the joined .rar files. Winrar told me that the joined files got corrupted. So this time I join the split .rar files using winrar & then extract it using winrar. These extracted files work properly on PS3.

The strange thing is, the DATA.ROMs from both route (The Unarchiver vs. Winrar) end up with same md5 sum. Yet one works, one doesn't. Weird?

Any idea about this? Maybe something to do with >4GB file inside the archive?

The Unarchiver Hangs up often, and yet when it does...the finder does not see it, and therefore you cannot force quit the application. The start over, means you have to reboot your machine. I have had to do exactly that three times so far today alone...and it becomes a real pain. There has to be some way to shut down the application, without shutting down the entire machine constantly.

On the App store it say that the application is Free. There is however a comment from somebody stating that after a couple of weeks it asks you to purchase the full version. Is this true? or is it free forever.

@Dan

Open the Activity Monitor and just kill the Unarchiver process. No need to restart the computer.

I have also seen the problem with the AppStore installation. It looks like it's been installed but the app is not there.

First I used Cocktail to clean out my caches. I have had the Unarchiver installed before so I suspected that something old was in the way.

The next time I installed in the AppStore I went to the Dock and command clicked the installation icon as it was downloading. A command click on a Dock item = take me to this apps folder.

So I found where it was hiding. And very strange it had installed in a Dreamweaver folder way down in the Library.

/Library/Application\ Support/Adobe/Dreamweaver\ CS5.5/sv_SE/Configuration/Shared/Extend/The\ Unarchiver.app

Dragging it from there required my admin password. This is because the AppStore apps are not "owned" by me as an admin but by the system.

So the app now works and AppStore also thinks it is installed. Let's wait and see what happens when the next update arrives.

>>953

If it hangs, there is some kind of bug that needs to be fixed. Can you work out what exactly causes it to hang? And if you do, can you post an issue on the bug tracker about it?

>>956

It is completely free and open source. That person must be confusing it with some other program.

>>958

Very weird. You should possibly report this to Apple, as it is the App Store itself that handles the installation, and that is certainly the wrong place to install.

First of all, thank you for TheUnarchiver -- and ESPECIALLY for Mac OS 10.4 support. The folks who took over Stuffit removed support for Windows self-extracting .exe files and deny any knowledge that it used to work; I had command procedures which relied on it.

In any case, I plan to send you a small donation soon. But first, please consider the following:

#!/bin/bash
mkdir EO
curl -o EO/eo1.exe http://www.irs.gov/pub/irs-soi/eo1.exe
curl -o EO/eo2.exe http://www.irs.gov/pub/irs-soi/eo2.exe
curl -o EO/eo3.exe http://www.irs.gov/pub/irs-soi/eo3.exe
curl -o EO/eo4.exe http://www.irs.gov/pub/irs-soi/eo4.exe
open EO/eo1.exe
sleep 5
open EO/eo2.exe
sleep 5
open EO/eo3.exe
sleep 5
open EO/eo4.exe
sleep 5
cat EO/EO?.LST >eo.lst
rm EO/EO?.LST EO/eo?.exe
rmdir EO

is there a way I can invoke the expansion with a command which activates without the GUI, so that (1) I do not have focus stolen by the GUI and (2) I do not need the sleep commands?

Thanks/john

Found your command line utilites.

perfect.

expect a donation next week via PayPal.

Thanks.

Found The Unarchiver in MAS! Thank you!!!

I have just encountered a ZIP archive with file names encoded in the weirdest way I have ever seen; even The Unarchiver did not manage to decipher them. I did though, and here is my diagnosis:

1. the original file names were encoded in Shift JIS,
2. the resulting bytes were treated as Windows-1252 and decoded, with bytes which could not be decoded in Windows-1252 copied verbatim (or in other words, decoded in Latin-1) instead,
3. the resulting strings were encoded in UTF-8 and stored in the ZIP file as UTF-8 file names.

To add to the confusion, one file name in the same archive was simply encoded in Shift JIS but presented as CP437.

I honestly have no idea how widespread such archives are, but can The Unarchiver by any chance learn to decode this scheme?

I'm a very unsophisticated user. I downloaded unarchiver from the web and a window popped saying my winzip mac edition expired. ( I downloaded that about 3 months ago.) I tried looking around in my application folders to see if the unarchiver was hiding out
and couldnt find it

Firstly, thank You for the best OS X archive utility of all time. I've been using it since my very first day with a Mac and it was always just getting better since then.

Now, I wanted to ask - is there any chance „The Unarchiver” will get encrypted .7z and splited files (.001) support anytime soon? Like, 10.7-celebration update? Would be totally awesome :)
Also, since You've entered MAS with Your software, have You ever thought about making paid „The Archiver” (extended version with compress abilities)?

>>966

Well, encrypted 7z support should be added sooner or later. I don't have any specific plans right now. The main problem is that like every other part of 7z, it's horrible overengineered, and there are whole lot of different kinds of encryption, meaning it is a lot of annoying work.

Also, as for paid version, I do have some idea. Not exactly what you suggest, but something. We'll see.

(The Unarchiver itself will remain free forever, though, no need to worry about that one.)

hi !waha.

just fyi, the following zip hangs at the end, if you wanna test it. happens with older the unarchiver versions too. cheers.

http://photobatch.stani.be/download/package/phatch-0.2.7.1.zip

>>968

So it does, interesting. Will investigate further.

Should unar (beta 0.4 mac) be able to unpack multipart rars? When I use it it only parses the first .rar file and ignores the rest. Using GUI app opens the same multipart rar just fine.

>>970

There was a bug where finding multipart files didn't work unless for files in the current directory. I guess it didn't get fixed yet in 0.4. Add ./ in front of the filename to work around it, or wait for me to get the new versions done.

(Might take a while yet, writing lots of stuff.)

Unarchiver gets my official (but entirely imaginary) "cool tool" award... One question, though: What type of encryption is used if a password is set?

The app description mentions "support for AES encryption", but that is a little sparse...

Thx
DHH

>>973

It uses whatever the archive uses, if it's supported. What that is varies a lot. Zip files can use the encryption from APPNOTE.TXT, which is very weak, or AES if they use the WinZip extensions. If you want all the gory details, read either APPNOTE.TXT or the WinZip documentation at http://www.winzip.com/aes_info.htm.

Hi,
I'd like to report an issue with the tar.gz archive, downloadable here:
https://github.com/ryancramerdesign/ProcessWire/

Direct download link:
https://github.com/ryancramerdesign/ProcessWire/tarball/master

(the file is ryancramerdesign-ProcessWire-63c0381.tar.gz)

The Unarchiver performs extraction with no errors or warnings, but the directory wire/templates-admin/ is completely missing.
OS X Archive Utility instead extracts everything correctly.

Tried with The Unarchiver 2.7 on a 10.6.8 MacBookPro late 2008, and with 2.6 on a 10.6.3 hackintosh.

Thx
Riccardo

>>975

Confirmed.

>>975

Also, fixed, thanks to halcy.

I am using the MacOSX version of unar (cli) and I have a question: is there a way to uncompress an archive to stdout instead of a file? I need this to uncompress .7z files and pipe the output to another program.

Thanks!
Jay

>>979

No, but that is a good idea for a feature to add.

I'm not sure how to handle extracting multiple files, though. Maybe just allow extraction of a single file?

>>980

For my purpose allowing only one file will work for me. Thank you for the feature consideration!

Jay

>>977

whoa, that was fast =)

I'm not too great at computers, but I downloaded a .rar file from the internet and when I try and open it up The Unarchiver says the file can't be extracted with this program. Help??

x

xxx

Whether it is Lion or unarchiver, I don't know, but Unarchiver unpacked a zip file into invisible state, a remount did show the files.

I have heard that there are some issues with Lion, can anyone confirm/deny this for me while I decide when to upgrade?

So far it's working like a charm. Only thing I miss for the app is the gorgeous UI justlike one implemented in Entropy.

Great program thank you. But on Lion it's extremely annoying that Unarchiver clears the current selection of files in Finder just because it unarchived a file, because the focus shifts to the top file in Finder, even though the selection as empty when the unpacking of the file is done! Any way to fix that in the next version??

>>992

I'm not sure what you mean. The Unarchiver does nothing to the selection of files in the Finder on Lion here.

Great program thank you. But on Lion it's extremely annoying that Unarchiver clears the current selection of files in Finder just because it unarchived a file, because the focus shifts to the top file in Finder, even though the selection were empty when the unpacking of the completed! Any way to fix that in the next version??

Great program thank you. But on Lion it's extremely annoying that Unarchiver clears the current selection of files in Finder just because it unarchived a file, because the focus shifts to the top file in Finder, even though the selection were empty when the unpacking of the completed! Any way to fix that in the next version??

As this thread is just about to fill up, I have opened a new one for further discussion:

http://wakaba.c3.cx/sup/kareha.pl/1314820473/

I think XADMaster has a lot of potential as the definitive compressing/decompressing library. However, I think the fact it is written in Objective-C is a barrier for its general use.

Is there any plan to solve this (eg. providing a C bindings) ?

i've downloaded 2.7.1 twice and am unable to find the interface.

please help.

p.s. i'm a newbie so be gentle

>>997

C bindings is something I'd really like to have, but I haven't had any time to work on, and probably won't in the near future.

hi i just downloaded the the unarchiver and tried to unzip my file but it required a password. i don't know any password?? please help! thank you!