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!

Well, after some work, I've finally got this into a state where it is actually just about presentable. It's still an alpha version, and is released mostly because I could really use some large-scale testing, but it should actually be useful.

http://wakaba.c3.cx/releases/mac/TheUnarchiver_alpha_1.zip

Features include:

• Built around libxad (http://sourceforge.net/projects/libxad/). This is an old Amiga library for handling unpacking of archives. It supports a whole lot of formats, and I added a couple more, and bugfixed old code. I also wrote a higher-level Objective-C wrapper around it, which might be useful for other projects too (including Xee).
• Supports more formats than I can remember. Zip, Tar, Gzip, Bzip2, 7-Zip, Rar, LhA, StuffIt, several old Amiga file and disk archives, CAB, LZX, stuff I don't even know what it is.
• Supports split archives for certain formats, like RAR.
• I copied the Finder file-copying/moving/deleting interface for its interface.
• Uses the character set autodetection code from Mozilla to auto-detect the encoding of the filenames in the archives.
• I haven't bothered packaging them yet, but at some point I'll release the source for all this, and also frameworks for linking against the archive and character set autodetection parts, which might be useful in other projects.

Issues:

• The format support is not complete for many formats. Given the complexity and unplanned evolution of most popular archive formats, support will probably never be complete. However, most files should work. Notable exceptions include:

  • No support for encryption in any formats. Libxad supports encryption, but the GUI does not. The RAR and 7-Zip modules do not support encryption at all.
  • No support for fancy RAR features like recovery records.
  • Very basic 7-Zip support (based on the 7zC code). It can open all of the (very few) 7-Zip archives I have, but there are probably archives out there it doesn't support.
  • No support for .sitx files. This format seems completely undocumented and un-reverse-engineered.
• No icons yet. If anyone wants to contribute, I would be very grateful. It needs a program icon, and a set of icons for the huge set of archive formats it supports.
• The error messages should probably be re-written to be more friendly.
• It opens an icon in the dock, unlike BOMArchiveHelper.app. This is very easy to fix, but for the alpha versions, it's easier to keep track of what's happening if the icon is there.

What's needed now is:

• Testing! Try it out on all kinds of archives, see what it handles, and what it chokes on. Send me archives it doesn't handle, and I'll see what I can do about fixing support for them.
• Icons! Are you a Mac icon artists? I want your help!
• Code contribution! Libxad is an awesome library. However, it could always use support for more formats. Is your favourite format not supported, or broken? If you contribute code for it to libxad, it will be supported by The Unarchiver, too!
• Suggestions! Is it missing features not already mentioned here? Suggest them, and I'll give them consideration!

Oh yeah, one more missing feature:

• A preference page, including at least some way to easily make archives open with The Unarchiver, like the format list in Xee.

Is this universal if not then you need to DIE.

It's universal, but I have no idea if it works right on Intel. There might very well be endianness issues in the various pieces of code. I'd especially like to know if the RAR and 7-Zip code works right on Intel, so get testing.

Ok, first obvious bug: Xcode has somehow messed up the framework linking, and this won't launch at all on most machines! Stay tuned for alpha 2!

http://wakaba.c3.cx/releases/mac/TheUnarchiver_alpha_2.zip

All right, fixed! Big thanks to Rich Siegel for untangling my linking issues.

Alpha 3 is done. It is pretty much feature-complete for 1.0. However, it still has no icons. I have some help for that lined up, though, but I don't know how long that will take. In the meantime, for testing purposes, the archive icons are replaced by a picture of Aruruw sitting in a box.

http://wakaba.c3.cx/releases/mac/TheUnarchiver_alpha_3.zip

Changes since the last version include:

• Bugfixed file type declarations.
• Interface for easily associating (and un-associating) archives with The Unarchiver, making it easy to install and remove.
• Working password interface.
• Bugfixes for bzip2 archives.
• Various other bugfixes.

I could really use some testing results from this, successful or not. I'd really like to know if it is working at all for whatever archives you have lying around!

It runs on my Power Mac G4. I am trying to unpack some splitted ace archives that unace on GNU/Linux didn't manage to fix, and it seemed to work in The Unarchiver! I'd like if it had an option to select where to unpack the files to, though.

Oh no, it didn't extract after all. But those archives could be rotten. I'm going to make it my default unarchiver anyway.

>>13

It doesn't support Ace 2, sadly, just Ace 1. Ace 2 is propriatary and undocumented, as far as I know. It really would be nice if somebody would add support for it to libxad, but I think it's beyond my abilities to do.

http://wakaba.c3.cx/releases/mac/TheUnarchiver_alpha_4.zip

An enough-coding-for-tonight release. Features better control over filename encodings, and better fallbacks when the autodetection isn't sure about the encoding.

http://wakaba.c3.cx/releases/mac/TheUnarchiver_alpha_5.zip

Some GUI bugfixes and optimizations, and support for OS X-specific features in .tar and .cpio files (as created by OS X's version of tar, and ditto, respectively).

Repost for great justice.

Uh, the thumbnail doesn't look very good, probably because of something about the way the graphics program exported the PNG, or the way the thumbnail was made. But, uh, if you click on it it the original looks a lot better. At least, it does for me. Sorry about the double post.

When I think of something to open up boxes with, a box cutter comes to mind. Perhaps it could be seen in bad taste, but it seems pretty natural.
I expect that the thumbnail will look bad again, due to the transparent PNG.
Third version adds the background.

adding "-background white -flatten" to the convert command line in wakaba and kareha would probably fix that problem...

The Unarchiver unpacked some of my SHIFT_JIS encoded archives with no problems! I love this application. If it'd only been ported to GTK+-2 as well···

It messes up the filenames on the sit here.

http://micono.hp.infoseek.co.jp/decodingqr/index.html

>>24

Oh yeah, SIT filenames aren't necessarily correct. I should look into that.

Ok, let's call this feature-complete and thus, beta.

http://wakaba.c3.cx/releases/mac/TheUnarchiver_beta_1.zip

Now with icons! Made by Adam Betts, infamous creator of the Adium duck. There's no proper main program icon yet, though, just a placeholder for now. That will come with the final release version, probably. Funnily enough, he also decided on a boxcutter theme for it. Sorry to >>21 for not using his icon, but I'd already talked to Adam at that point about it.

Also, >>24 should be fixed.

I suppose it's my own fault for making them. I could certainly make the cutter look a little bit shinier and aqua-esque... but then, I only spent a day on it. Even if nobody uses it, I kinda like how it turned out, and if Betts uses a cutter, too, then it must have been a pretty good idea.

Me, I never liked the duck. Memorable though it may be. That's right! I'm a-callin' you out, Betts! Dreeeaaw! No, but seriously, I'll be interested to see what a real artist can do with it. And I hope you end up using his icon because it's better, too.

And I hope you come up with a catchier name, by the way. I always kind of assumed that it was a working title, frankly.

I always end up using dumbass titles for programs. I kind of like this one though because of the implication that it's just the unarchiver, as opposed to one out of several. Also "Open With -> The Unarchiver" is pretty clear and descriptive.

It's a bit ungooglable unless you include the "The", though.

If anyone has a catchier name for it, I will definitely consider it, though.

"rip it open"?

Speaking of box cutters, there's a multipurpose box- and blister-pack opener tool call "OpenX", which also happens to be a great potential name for The Unarchiver. Maybe it'd be possible to get a permanent license from those guys to use both the name and a picture of the tool. Free publicity for them, catchy name and nice icon for the product. ;-)

http://www.myopenx.com/

I wouldn't do it for anything less than permanent licensing, or for more than the cost of a simple reciprocal link to their homepage. But it's a thought.

That tool would be a little too complex for 128x128 icon, people will have a hard time figuring it out. What I'm going to do is make a very basic box cutter so it will scale very well. 32x32 is around the size everyone will see a lot. I don't have time to do them right now but soon I will.

By the way, here's a mockup of The Unarchiver window in black HUD. I know author said he doesn't want to do it since it's not easy to do but my friend Jan Van Boghout is willing to do it if he have the source code.

Beautiful window like this will definitely get a lot more people to download The Unarchiver :)

A random thought popped into my head: Since the theme for the icons is packages and opening them, would "The Unpacker" be a better name, or not? More or less recognizable? More or less Googlable? More or less cheesy?

When I read that, I only saw: "The Fudgepacker"

I've been spending too much time on /b/.

Unarchiver is at least one syllable too long. I've actually been calling it Unpacker every time I saw it...

Also, black is kinda neat, but frankly I'm against it until you at least have the standard set of buttons on that window, sir. Which would be easy enough to fix, I guess.

But there are ways to change how OS X looks, and it seems like somebody who wants black windows might already have done that to their system... at which point, the Unpacker is just going to stand out as different, right? I know I'm just a fuddy-duddy, but I like my user interfaces standard. Apple has been doing a very bad job with that recently, but that doesn't mean we all have to jump off the bridge.

That black HUD window is actually the newest standard. You can find it in Apple's iPhoto, Aperture, Motion, etc.

More and more developers are using it for palettes/window that doesn't need full white space.

It's not about me wanting a black window just for the sake of it, it's excellent for usability since it's light weight with transparency and has flat look which look much more professional and stay out of your face.

Hopefully Apple will add a public API to use that style. That'd make it an easy change.

But I fear that might not be until 10.5, if at all.

do you distibute source of?

I was meaning to release the source at the same time as the final version, since development is not in a very stable state until then, but if you really want it, I can upload a copy of it before that, too.

New version with some bugfixes:

http://wakaba.c3.cx/releases/mac/TheUnarchiver_beta_2.zip

• Fixes problems with directory structures in Japanese archives.
• Fixes problems with data forks in some StuffIt files.

Thank you SO GODDAMN MUCH

> That black HUD window is actually the newest standard.

Brushed Metal is gonna be so pissed

> Brushed Metal is gonna be so pissed

Brushed Metal is so ugly!

Any updates?

I hope WAHa doesn't mind me pasting this:

< WAHa_06x36> onii-chan: I've had The Unarchiver in beta 
for MONTHS now, and I haven't gotten a single bug report 
except from MrVacBob, and that one has a much larger 
possible user base.

If you want updates, maybe submitting a bug report or two would make him happy?

At this point I am mainly waiting for a final icon (I should probably kick Adam's ass a bit), and in the meanwhile any final theoretical bug reports.

Well, since there haven't been any bug reports, I guess I'll just call this done and release v1.0.

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.0.zip
http://wakaba.c3.cx/releases/mac/TheUnarchiver1.0_src.zip
http://wakaba.c3.cx/s/apps/unarchiver.html

Hi.

Nice idea. I'm going to try it as an alternative to allume's bloatware!

I'll post as I find issues, but here's one right away. It doesn't play well with .sitx files.

Cheers

Calvin

Ooops! Found it.

Sorry, I was reading the latest posts only, not the full thread.

I tried beta version, everthing seemed fine except that "File name encoding" didn't work. I couldn't read it in the advanced menu of the preferences. Just lines of the strange characters in the menu...

As for the version 1.0, I couldn't even start it.
I tried to throw away the old preference file, but I couldn't find it.
No way.

My enviroment is OS 10.4.7.
I use my Mac in Japanese, English and French.

Anyway, I appreciate your work.
Thanks

>>49

Can you open Console.app and see if it lists any error message from The Unarchiver?

Yes, I tried.
But there is nothing in the log.
I erased the log before I opened the unarchiver.

This time, the preference window is opened.
But the application menu didn't appear. No application icon in the Doc.
I had to open the activity monitor to quit it.

I've never seen things like that!

>>51

It is set up to not use an icon when it opens archives, just like BOMArchiveHelper.app. However, this means it also doesn't show an icon when you open the preferences window. However, you can quit it by just closing the window.

Normally, you don't open the program directly, you just let the operating system open archives using it. (Again, like BOMArchiveHelper does.)

OK, so it's a normal behaviour.
For the file name encoding, I choose "Ditect automatically".
But other choices are unreadable.
Is it normal, or do you know a solution?

>>53

It's probably a bug in the program. The way the program has to get this list is kind of strange, and I probably got the code wrong somewhere along the line. You usually do not need the list, so it's not a big problem. I'll try to fix it for the next version.

How can I choose not to "mkdir" when it unarchieves?
Sometimes it get many unnecessary folders.

It crashes on start up. Does it require Tiger?

I tried it on the tbz file for my plus and minus icons, and it didn't do anything: it simply showed me the “Preparing to extract “plusminus-1.0.tbz”” dialog. Clicking Cancel does nothing but disable the cancel button. I must force-quit the app to get it to stop its barber pole. Nothing is written to console.log.

Regarding the icon: I love it. ☺

>>55

There's no option for it, but it should not create a new diretory if there is only a single base directory in the archive. If you are getting several single directories inside each other, it's probably because that's how the archive is stored.

>>56

I haven't checked, but it probably does.

>>57

I can't find the .tbz file on that site. If you have it, mail it to me.

Thanks, another really needed app like Xee :).
Seems to work fine until now here on OS 10.4.7 PPC, but it didn't associate itself to archive file types although I selected all file types in its preferences. I suppose I should associate them manually, but I'll wait because it lacks one feature important to me: choosing a default unarchive destination.
As far as I can see, it currently unarchives files in the same folder where the archive resides, while I prefer unarchiving them on my desktop. Is it a planned feature for the future?

>>59

The OS X API for associating with filetypes is still kind of broken. Also, if you're using a Mozilla-based browser, the browser has this super-annoying behaviour where it will set a filetype and creator on the files it downloads, but will NOT get the right one. It's a reported bug, I've tried voting for it and mentioning it needs to be fixed, but nobody cares.

If that turns out to be your problem (if, say, files downloaded through other means open in The Unarchiver but files downloaded in Firefox or Camino open in something else), go vote for and post in https://bugzilla.mozilla.org/show_bug.cgi?id=236389.

A default unarchive destination was not something I planned but it would be easy enough to do if I just stuff it in the advanced preferences, so I guess I'll look into that for 1.1.

can't unzip archives with password protection :(

can't unzip archives with password protection :(

The latest archive of MacTranslator (testet with 0.10 and 0.11) from http://sourceforge.net/projects/mactranslator will produce a checksum error on decompression, whereas BOMArchiverHelper.app will do just fine. If you do the decompression in PathFinder instead of Finder, The Unarchiver will not even display the dialog box containing the error. This freezes The Unarchiver and leaves no option to decompress any more archives.

I assume both of the described problems are bugs?

>>62

You can extract some of them. However, there are many kinds of password-protected zip files. Send me the file and password and I will look into it.

>>63

That's funny, I got another similar report, and that one failed on the exact same file in another archive! This is kind of funny.

The second sort of sounds like a bug in PathFinder, but I am largely unfamiliar with it. Does Console.app list any errors?

If it does require Tiger, you should state that on the page.

Thanks.

>>63

I just fixed this.

Cool app, but are there future-plans to support also compressing and not "only" uncompressing?

Would be great to have the PopUp-Window if you right-click on files/folders and don't have to choose only the Apple-implementation of .zip-archive but also from your application and the choice of .rar, .7z and so on…

PS: I know, the name of the application is "Unarchiver", so maybe we need a new name also to satisfy my wish… ;-)

>>67

No, not really. I think compression and uncompression are such different tasks that you are better off using different programs for each. A lot of decompression programs on Windows, at least, are kind of unintuitive and bloated because they combine compression and decompression in the same interface, and I want to avoid that.

Also, I think that using plain .zip is usually the best idea anyway, and OS X's built-in archiver is good enough for that.

>>70

Hmmm. I am not sure the app is told what program launched it. But I'll think about that feature.

It is; using sysctl, you can determine your process's parent process. Unfortunately, this will always be WindowServer, except in rare circumstances (launched from Xcode, executable run directly in Terminal). And even if the parent process was the application that launched the file, that would not help if another file was launched while The Unarchiver was working on the first one (in which case the existing Unarchiver process would be used, rather than a new one created).

Just wanted to chime in and say 'thank you!' for this wonderful little app: fast, beautiful, fast, perfectly integrated, fast (did I say it's fast? :-)

Oh, and I'd like to add my vote of preference for the "black UI": as Adam Betts said, it's more and more used and its wonderful "not in your face" look is perfect for The Unarchiver (Apple is also using it in the upcoming Web Inspector in Safari, and it couldn't look more elegant: http://webkit.org/blog/?p=41 )

>>73

If there was an easy way to add it, I would do it. I wonder how Safari implements it. I guess I'll have to dig into the source.

Ok, I did, and it turns out they build the whole thing with HTML. I definitely won't be doing THAT.

However, if anybody wants to implement the black GUI (without doing it in a WebView), I'd be happy to add it, especially if it's optional.

It won’t decode Sitx files, that is Stuffit deluxe files that require a password to unstuff.

Thanks, I love this alternative to Stuffit expander.
Any chance of a preference to delete compressed file by default on expansion? That would be a huge improvement for me. Better still with reverse behaviour when Option-double-clicking.

Using version 1.0 on Intel Mac Mini.

When I try to extract the VirtueDektops 0.53r220 zip, it gives me a checksum error on a PNG file. The link to the ZIP is:

http://virtuedesktops.info/wp-content/uploads/2006/08/VirtueDesktops_0.53r220.zip

And yeah, the filename encoding dropdown is all messed up on my system too. I'm happy with Unarchiver the way it is, especially the smart create-folder-only-as-necessary feature.

SITX is not supported because it is completely propietary, undocumented and un-reverse-engineered, to my knowledge. If this ever changes, support might be added. I know I'd like to get rid of the last reason to keep StuffIt on my system. But as it is, adding support is beyond my capabilities.

Version 1.1 released:

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.1.zip
http://wakaba.c3.cx/releases/mac/TheUnarchiver1.1_src.zip

• Added the automatic deletion and opening options requested.
• Added the option to always extract to a user-specified folder.
• Fixed the opening-behind-other-windows bug.
• Fixed a number of the extraction bugs reported (although not quite all, either because I lacked a test case or because it involved files being too broken).

Incidentially, I'd welcome some outside help with this project. I have a lot of other things to work on, and don't have much time to work on this. There are a number of things that would be great to have, starting with sitx support, and stuff like better support for encryption of zips and rars, better 7-zip support, more formats, and so on.

PLEASE add version resources to your code!

In the Finder, version 1.0 looks IDENTICAL to version 1.1. I need to be able to know which version of the program file I am looking at.

Thanks,

eo

>>76

“sitx” doesn't mean that the file is encrypted; it means that it is in StuffIt X format, which is Allume's replacement for the older StuffIt 5.5 format (and its predecessors).

>>82

It uses the standard Info.plist version field.

>>84

Right, but that's not visible from the Finder. The suggestion (which I made and Eric O'Brien made) is to put the version into the Finder Get Info string so that the versions of two Unarchiver app bundles can be compared from the Finder.

One thing i realy miss is "Extract where" -> "Ask" like Stuff-it, it this is included in next version i'll delete stuff-it as fast as i can :)

Where is the preference file? The pref pane has gone all unresponsive and I can't alter what Unarchiver should handle. I reinstalled but my selection stayed so somewhere there is a file. Thanks. Oh, by the way, great job. Stuff-it always seemed like it was on the verge of crashing. Funny thing, I was testing relative speeds between your app and stuff-it and stuff-it just crashed on the archive. Ha Ha. I knew it sucked but it hadn't really crashed in a while. My decision was made.

>>87

The associations aren't stored in a preferences file, but the previous ones are, and there's a bug where those get corrupted, so that might be your problem. It should be at ~/Library/Preferences/cx.c3.xee.plist.

>>88

Just drag it where you want it, usually the Applications folder. This is how you normally install program on OS X.

I've been looking at this as a replacement for Stuffit Expander at work (Freeverse Software).

But all of our .sit files produce an empty folder. Is it because we use an older .sit file (compatible with OS 9) for our games?

Thanks !WAHa.06x36.
All selectable now.

>>90

Send me some test files.

same problem as in 90; does not work with my .sit archives. Try for example Nikon Scan 4.0, downloadable from http://www.macupdate.com/download.php/13759/NS4.sit

>>93

That file extracts fine on my macine.

1. What hardware are you running on?
2. Do you get any errors on the console? (Open /Applications/Utilities/Console.app)

I have a bug setting preferences :
In "Archive Formats" I clicked "Select all" then I changed my mind and clicked "Deselect all". "Deselect All" only deselect the first file format (zip). I also can't manually deselect the others.
Mac OS 10.4.7 PPC French language selected

>>95

Yes, others are having this issue, but I can't reproduce it. I really need to know what hardware this is happening on, and if it's producing any errors on the console.

>>96

See >>87,89.

Like some others I am having a problem with SIT files and I found the following in my System.Log file which seem to relate to trying to extract a SIT file:

Sep 22 23:00:08 simon-wolfs-computer kernel[0]: HFS: /rsrc paths are deprecated (..namedfork/rsrc)

However, BetterZip also produces empty folders so I am now wondering if this is a problem in the OS rather than with your application. I am running 10.4.7 on an 2 GHz Intel Core Duo MacBook with 2 GB DDR2 SDRAM.

>>99

Ooh! That finally explains what is going on! Many thanks!

I am not entirely sure how to fix that, but now that I know what's going on, I should finally be able to do something about it.

>>100

Could you do one more thing? Extract an archive to get an empty folder, and then open up the Terminal, cd into that directory, and run ls -la there?

I get this:

simon-wolfs-computer:~/Desktop/DevCon2006 Simon$ ls -la
total 0
drwxr-xr-x 2 Simon Simon 68 Jun 1 11:40 .
drwx------ 14 Simon Simon 476 Sep 23 00:51 ..

I have also had a situation where extracting a SIT file results in a directory being created but it being invisible to Finder. The logs have the same error message for this. Creating a new directory to force a refresh didn't help.

>>102

Does the extraction progress window show up at all? Does it show any of the names of files it is supposed to extract?

An extraction window flashes up very, very briefly so I cannot see what it is reporting.

Minor problem I'm having with 1.1:
The icons for some files are not showing up. For example, .zip (which is associated to Unarchiver) shows up as the unknown document icon (blank page) instead of the nice brown package icon. Works fine for others (RAR, for example).

Any thoughts?

Thanks for this app, it's soooo much nicer than StuffIt.

I should add that I have the same problem as Nick with my SIT files.

>>105-106

Is this for files downloaded with Camino/Firefox, or some other browser?

I'm using Safari. I will try to find a .zip from somewhere other than Safari.

I'm using OnniWeb 5.5.

Seems to be happening on all zip's regardless of where they came from. Tried rebooting, did nothing. .sit icons work fine though.

May have found a fix...

Find a file of the type that is not getting the correct icon (Simon, in your case a .sit).
Get Info on that file, and go to the Opens With... section.
Change it from The Unarchiver to anything else that can open it.
Hit the Change All... button. The icon should change to the new apps icon.
Now go back to the drop down list and change it back to The Unarchiver, and hit Change All... again.

Worked for me.

Thanks Nick. When I changed it to another application the icon stayed blank but then changing it back to The unarchiver sorted it out.

I am tempted to blame Apple's kind of broken UTI handling for that one.

>>93
>>94

hi again, no info on the console.
the hardware is an iMac intel core duo 1.83 ghz with 1.5 Gb ram; os x 10.4.7

hope this helps...

I have a funny feeling that this is a 10.4.7 issue too since it is not just The Unarchiver that seems to be affected. Roll on 10.4.8!

No errors on the console? That makes it more mysterious again.

The last thing you want is a mysterious bug. Sigh.

Hi

Found a bug in the SIT extraction process of unarchiver.
Look at the driver for the Roland RD700SX Stagepiano http://www.rolandmusik.de/ftp/pub/downloads/tecfiles/P_bis_U/OSX_Treiber/RD700sx_drv_OSXi.sit
You will find a difference if you extract it with Stuffit Expander or The Unarchiver.
Hope you can fix it :)

To help with the empty folders.

Try "Create New Folder" INSIDE the empty folder, or move (and move back later) a small file to the empty folder. Doing this should update the folder and suddenly make all the folder contents visible.

Note: apparently there is a way to fix this (not tested by moi) in the preferences in StuffIt Expander. I heard that unchecking the "Set Execute Permissions by Default" will solve this little bug. Give it a try and see if it works.

Hiko, I'd already tried this solution but it doesn't work for me. In fact the extract process doesn't actually appear to work so I simply end up with an empty folder.

Anyway, it may help others I guess.

I think you should offer a solution kinda like Filecutter has.

http://img209.imageshack.us/img209/9479/bild1in0.png

Where you can choose an "Upload to..." option and possibly some other options too.

That would IMO be a BIG ADDITION to this excellent app!

Thank you so far :)

I really like The Unarchiver because it is simple and fits in with the rest of OS X. It would be really nice if the developer would keep it that way instead of piling options upon options (an extraction tool should be very simple) or adding UI that won't fit with the rest of the system (unfortunately, Apple has a habit of doing just that...)

Instead, it would be really nice if the developer could focus on supporting more features from each format. It is probably quite easy to add better support for the 7z format since portable source code is already available from the p7zip project. Personally, I don't support proprietary formats like sitx and haven't seen any software distributed in that format. I think the developer should focus on formats that are more cross-platform and open instead of a closed format like sitx.

>>121

Hmm, I've actually never seen a Mac app do that. It might not a be bad idea if I can figure out how to do it, and find some time to do it.

>>122

The 7-zip code is, unfortunately, quite horrible. When I started out, I was considering using it, because it can extract a lot of formats, but I found it very badly designed, full of Windows-isms, and completely undocumented and uncommented. Well, I am guilty of that last part myself, so I can't really blame the author for that, but it did mean the code was unusable.

Right now I am using the 7z-C code from 7-zip, which is a separate implementation in plain C instead of Windows C++, which is much easier to use, but not as capable.

I agree with >>122, the app should stay simple and not add extra features like the items in >>121.

My two requests:

Concatenate 001, 002, 003 (et cetera) files back into a single archive.

Process PAR/PAR2 files for file recovery.

Also, a request for further down the road: A dock icon, perhaps invoked when you have an archive or collection of files (e.g., a RAR set) that is over a certain size. As it stands now, it's a bit annoying to have to keep re-finding the extraction dialog buried under tons of windows (since it doesn't show in the dock or cmd+tab).

Even with these few things, The Unarchiver is amazingly sweet. Thanks so much!

>>124

There is no way to switch the dock icon behaviour that I know of. Either an app has one all the time, or never.

Multi-part archives are already supported, but this is only triggered for certain naming schemes, such as ".r01/.r02" and "part01.rar/part02.rar" for RAR. If you have files with another naming scheme, give me some example files and it should probably be easy to add support.

PAR/PAR2 has been requested, but I don't know much about it, so it would take some time to implement it. Unfortunately I don't have much time at the moment between all my projects, so I'd really appreciate it someone wanted to help out with this.

(For anyone interested in helping out with this: libxad reads data through a custom callback handler, that implements open/read/seek/close functionality. Multi-part archives are handled transparently through this, for instance. A PAR/PAR2 handler could be written that works like the multi-archive handler but additionally fills in any missing pieces by itself.)

122 & 124

If you dont want the option to extract to a certain folder the simply dont install the finder plugin, if you are not used to e.g. WinRar on windows which has the Extract to.. option.
If you have you are pretty dependent on that, eg. when unararing huge archives > 1gb you want to extract to another physical drive to get a huge speed increase, and that is unfortuneatly not very easy with thuis application atm. You can set a drive as the drive to always unpack to, but when the archive is on that drive it unpacks to the same drive and you loose the aformentioned speed increase.

So !WAHa.06x36 i think you should really look into offering a "Filecutter-like-interface" for using an Extract to... option. If I recall correctly it was just a simple plugin file that you copyed into /Library/Contextual Menu Items/ or something.

That would be kinda the optimal solution cause the people that easily want the option can just copy the file and those who obviously dont just simply ignore that option.

Thanks alot once again for this neat app!

I have checked "delete file after unzip" in the preferences (something to the deletion of the file after being unzipped), but the thing is if it's a 2-part file, it throws the first file into the trash (part 1) and not part 2. Just something you could fix. Great app. Great work :D

>>127

Yes, I know, it'll be fixed in the next version.

Would it be at all possible to add an ETA/estimated finish time to the window?

>>129 Like those are ever accurate anyway.

Right, since it would likely be inaccurate, and is very seldom longer than a minute or two anyway, it seems like it would just be a distraction.

!WAHa:

Have you considered adding support to view the contents of compressed files? I don't think much would be needed, nothing like Finder navigation, but maybe the option to see the contents (maybe if a modifier key is pressed) and extract only one file?

>>132

No. I used to run Windows, where every unarchiver worked like this, and I was always impressed with the minimalist functionalism of Apple's standard unarchiver in comparison to that usability mess. The cases where it would be useful to have this are so few in comparison to the common case that it doesn't really justify the code bloat, and the work for me.

However, if someone wanted to make an unarchiver app like this, I should point out that the libxad engine from The Unarchiver is built as a separate framework, and is very easy to use from any program.

!WAHa.06x36:

I'm with you in the UI, keep it non-existent. The way you've implemented it is superb. Fix that arc hive deletion bug and maybe implement Par2, and it's utterly perfect.

Keep up the good work.

>>93
>>94
>>115

Hello again, I've tried again to use unarchiver on my other computer, a G4 macmini, working on the same sit files (Nikon software) that I couldnt un-sit on my iMac intel and guess what ?... it works !!! It seems that (at least for me) unarchiver works ok for sit files if you use a powerpc, it doesnt on an intel machine.

Hope it helps.

>>139

I suspected as much. I am hoping to get an Intel Mac soon, though, and then I'll be able to test it myself, hopefully.

Archive:
http://dub.washington.edu/projects/denim/download/mac/download_alone.shtml

doesn't extract properly in Unarchiver, but does in Stuffit 9. It's hqx.

(unarchiver is great anyway :)

It extracts fine here. Are you using an Intel machine?

First of all, thank you very much for this app.

Having to use stuffit was one of the major blemishes on my wonderful mac user experience and I'm sure many feel the same.

Don't know if this is Intel chip-related but when I unarchive Japanese files with Japanese encoding, even if I set the confidence level to 100%, it still asks me for confirmation whereas on my PPC iBook it never does and I have it set at 80% as recommended.

>>143

Ah, you probably misunderstood that option. Setting it higher means it will ask more often, because it sets the level of confidence the program needs before proceeding without asking.

However, if there are any files where it asks one one machine but not the other when the confidence level is set the same on both, then that's a bug, and I'd appreciate it if you sent me the file to test.

As Stuffit 11 now lost the contextual menu feature I used most of the day, I wonder if TU can be made to list archive contents in a contextual menu.

Even nicer would be to extract just a selected file from the archive.

Thanks, TU looks very promising.

The latest patch for Sim City 4, in sitx format, doesn't extract at all with The Unarchiver (1.1)...

Nice program otherwise.

SITX is not supported.

Extracting 7z files sets modified of all extracted files to "now", extracting with 7zx works.

>>148

The 7zC code used by The Unarchiver does not provide the date. I've asked the author to fix it, but I don't think he has, yet.

My comment (127) I talked about the autodelete when there has been an extraction of a format. Is it possible for you to get this working in pathfinder? It doesn't delete at all in pathfinder. Can't wait for the next version!

>>150

That sounds more like a Pathfinder bug. Maybe you should try reporting it to them?

Thanks for this great software. With Xee and The Unarchiver you gave us 2 of the most wanted and needed software on mac. I can't understand why nobody did it before, because it's so obvious that this is the way cool apps should works : simple and fast ! :+)
Just for help : I can't extract the archive of WebGrabber you can find here :
http://www.epicware.com/webgrabber.html
It's a normal tar.gz file, and BomArchiveHelper extracted it without problem (as Stuffit).
hth

>>153

Confirmed, I'll add it to the list.

Thanks for this great app! More and more great pieces of software come out for the Mac these days. Very cool. Some of the last things I miss are a good Archiver that does RAR and a good mp3 tagger like mp3tag for windows.

sounds like a nice app, but since it's for 10.4 only, i can't try it. are there significant reasons keeping you from compiling a 10.3.x version?

>>157

Mostly that I don't have a 10.3 machine to test on.

The Unarchiver 1.1 crashes when opening this file:

http://www.pixelglow.com/downloads/graphviz-1.13-v16.zip

I also posted the crash log on pastebin:

http://pastebin.com/811153

>>123

The original 7-zip makes use of many win32 features, but I was talking about p7zip, which is supposed to be very portable.

>>160

p7zip is just exactly the same source code, but with a win32 compatibility layer compiled in alongside. It's a real mess, and compiling it into a separate application is nearly impossible.

The only really portable 7z code is the 7z-C code, which I am using, but which is less capable, as mentioned.

I'm curious about those random files that Unarchiver is unable to decompress properly. Are those because of obscure bugs in the decompression engine that only get triggered by certain files or are they because of bad compressors?

>>162

So far I've encountered one bad compressor, a couple of obscure bugs, and then there are a couple of still outstanding mysteries like the SIT files on Intel. That's PROBABLY another obscure bug, but I don't know yet.

once you get that SIT problem for Intel users sorted, and perhaps the contextual menu, I will gladly donate to you, and i'm sure others will too :)

great app. it's a favourite of mine, along with quicksilver.

The lack of a contextual menu like way to "Extract to..." is the only thing keeping me from donating som of my coins

Good news and bad news: Good news is I finally got an Intel Mac, and I am working my way through a number of Intel-only bugs (and others) now.

Bad news is, I managed to mess up my home directory drive in the move to the new machine, and I lost a whole lot of files. The Unarchiver isn't affected, since I could just download the 1.1 source again and start over with the few bug fixes I'd done so far, but I lost a lot of work on Xee, so that will be even more delayed.

This ZIP file that have a tracking application is not extracted correctly so it does not work when extracted with your aplication.

http://www.peerlessproductions.com/tuts/pages/Icarus.html

Hope this data help you in some way.

Can you reproduce the bug I reported?

>>159

BOMArchiveHelper also have trouble opening this archive.

Instead of implementing the various Finder Contextual Menu feature requests, maybe the developer can consider adding an Applescript dictionary along with a set of Automator Actions and Workflows in a later release.

There are several advantages to this approach:

1. It avoids adding bloat to the Finder menu, much like how windows applications love to add bloat to the explorer menu
2. It allows people to pick and choose which menu items they want
3. It is a lot more flexible. People can utilize TU in their custom scripts and workflows. They also have more options when it comes to accessing these functions: the finder contexual menu, the applescript menu, droplets, folder actions etc.
4. (Very important) It is easier to implement compared to a Finder plugin.

>>168

Oh yeah, I forgot to mention it, I could and I fixed it. Should work in the next version.

Oh, and >>169 is certainly worth thinking about, at least. Although I've found Automator a little annoyingly sluggish to launch on the old Mini, so I am not entirely sure.

Update on 1.2: All outstanding archive handling bugs have been fixed! At least all the ones I've managed to keep track of.

(This doesn't include stuff like SITX or RAR encryption though, sorry.)

This all sounds very promising and I'm looking forward to 1.2.

I'd also like to second the request for an AppleScript dictionary which would be preferable to Automator Actions.

What kind of commands should an AppleScript dictionary have, in this case?

Well I'd imagine that it should be things like having an Archive object which has properties such as:

• Source File
• Target Folder
• Delete After Extraction
• Open Target Folder After Extraction

I wouldn't expect anything too fancy but it would just be nice to be able to handle file extractions via AppleScript.

I use it to extract sit file.. but only find an empty extracted directory. why?

Well, I wouldn't rely on The Unarchiver extracting sit archives correctly. The problem is not with The Unarchiver, but with underlying library it uses, libxad. This library has got some obvious issues with sit archives.

I tried to use libxad for my own purposes. The sit archives I've used to test the library were made with StuffIt Deluxe 10. In many cases, libxad didn't recognised names of the files inside an archive correctly. As a matter of fact, the names were correct, but not full paths. That way, some files and folders ended up in completely wrong places in archive hierarchy, often not even in the same hierarchy level. I could recognise that since I knew what archive I created, but the user trying to extract sit archive with unknown contents is very likely to get messed-up hierarchy of extracted files. In case of app bundles, plug-ins and alikes, this would make them useless.

Another example is archive made with StuffIt Deluxe, all files recognised properly by the libxad library. But then, adding a new file in the root of archive (using StuffIt) results in the library being able to see only that new file, all others (couple of hundreds of files become inaccessible! Deleting newly added file brought everything back to normal concerning library's ability to correctly see all files.

Problems also exist with sit archives containing encrypted files. If only one file inside an archive is encrypted, the library most certainly won't see all files inside. And an attempt to extract those encrypted that are accessible results in library function ending with data corruption error.

So, as a conclusion: I don't know for other archive types, but as for sit, the libxad library, and that also means The Unarchiver, is (unfortunately) not reliable at all. If anyone still needs sit support, I'm afraid there's no escape from StuffIt Expander yet.

>>177

I have fixed quite a number of bugs in libxad's SIT handling, and 1.2 extracts all my test cases correctly. Well, except the encryption, I haven't done anything about that.

Cool, have you submitted those fixes back to the libxad project?

Some of them, but the project seems to be kind of dead and they haven't been incorporated.

Finally, v1.2 is done and released!

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.2.zip
http://wakaba.c3.cx/s/apps/unarchiver.html

New stuff:

• Added several localizations: Japanese, German, French and Spanish. Many thanks to E-WA, Christoph Schmitz, Thomas Steffen, Thomas Didrel, and Oscar A. Mata T. for their work on this!
• Added an option to have The Unarchiver ask for a destination folder. Holding the command key while double-clicking an archive will also make The Unarchiver ask for a destination folder.
• Fixed many unarchiving bugs. Several problems with Zip files fixed, and SIT files should now work much better, especially on Intel machines.
• Fixed some other bugs in the interface, such as some problems with the filetype association list.

As you can see, I did not add some of the requested features like AppleScript support or a context menu item. I looked at both, and finally came to the conclusion that they were both enough work that I would never get this released if I started on them. There is a little workaround for the context menu though, as you can now command-click an archive and The Unarchiver will let you select the destination.

I still like the ideas, though, and I might add them in a later version. Even better would be if somebody wrote it for me and gave me the code, hint hint.

Lovely, thanks for the new release. I'll try it this evening (I have to endure a day of Windows at work) and hopefully it will fix all of my SIT problems. As for the AppleScript support, I certainly wasn't expecting it in the 1.2 release so, from my point of view at least, please mark it down as a 'very nice to have' for a future release at some point. Bug fixes are much more important than what is, I imagine, a fairly niche request.

I have the strangest of defects, so weird I don't even know if it's un unarchiver. I have tried to download the latest two nightly builds of Cyberduck (http://update.cyberduck.ch/nightly/ - builds 2560 and 2574). Using BomArchiveHelper tells me that it can't write to whatever folder I try to unzip to (generally the desktop, as that's where I'm doing all of this). Using unarchiver it chokes when it gets to a classes.nib file, spinning the processors up to max without having anything happen.

Here's the magic - I kill the unarchiver process in activity monitor. I then copy the latest unarchiver app zip file on to my desktop, and unzip it (using unarchiver). Instead of just unzipping the file and giving me the unarchiver app to put in place, I get a folder called 'TheUnarchiver1.2' which contains the unarchiver app, and an apparently functioning copy of the cyberduck app I was trying to unzip :)

If you need more info let me know.

>>184

Ah, yes, that behaviour with the files appearing in later unarchivings is a consequence of The Unarchiver crashing or being killed. It's pretty weird, but I have not bothred to do anything about it, since the program is not SUPPOSED to crash in the first place (and also it DOES let you recover some files).

I can reproduce the unarchiving problem, though, so I will look into the cause of this. (I am guessing it's a broken gzip compressor that causes it, but I'll need to check.)

Update: Yes, the file is not a valid gzip file. I might try to add a work-around for this in a future version, but I think it might be hard to handle it in a useful way.

For now, I suggest you tell the author of the program to switch to a compression program that creates valid gzip files.

(If anybody needs the specifics of the problem, see RFC 1952, http://www.ietf.org/rfc/rfc1952.txt, section 2.3.1, the "ISIZE" and "CRC32" fields are missing in the file.)

Hi,

Thanks a lot for a great utility. I would just like to make a small suggestion for an addition:

In the 'Info.plist' could you also add the 'CFBundleShortVersionString' so that the version number appears in the finder when the application is selected. It just makes it so much easier to know which version one already has.

Thanks

>>187

Added.

>>184

Update 2: There seems to be even more wrong with the file than just that, actually. There isn't much hope of extracting it correctly, but I did fix the bug that causes The Unarchiver to lock up on this kind of corrupted file.

Both of these fixes were small enough that I don't think it warrants a version bump, so I just silently updated the file. Re-download it to get the fixes!

>>180

Stink. If someone else (ie, BetterZip) wanted those fixes would they need to contact you about it?

>>189

They're all in the The Unarchiver source zip in http://wakaba.c3.cx/releases/mac/. It also contains my XADMaster.framework, which abstracts out a lot of the bother of dealing with libxad and presents a nice, Objective-C interface to use instead.

I've started getting errors while trying to build .pkg installers using Iceberg. The builds fail at the pax file portion of the build. The only thing I can think of that might be related is that I've updated to TheUnarchiver 1.2.

The system.log file reports entries like this...
Nov 16 09:54:41 MyMac /bin/pax: open on /tmp/pax.md.KY1o: Cannot allocate memory
Nov 16 09:54:41 MyMac /bin/pax: close on {5: Bad file descriptor
Nov 16 09:54:41 MyMac /bin/pax: error closing files: Bad file descriptor

Is there any possibility that TheUnarchiver is the cause of the problem?

c w a l d r i p a t m a c d o t c o m

>>191

The Unarchiver has no support for pax files (something I'd like to add if I could find the time, though), and looking at that log, it seems to be running the right programs and not anything related to The Unarchiver, so I doubt it. Unless it's something that happens earlier, but I can't think of what that would be.

I am running Unarchiver 1.2 on an Intel Mac running Tiger 10.4.8. Love the app, it is fantastic. However, I have one slight annoyance and I am not sure whether it is actually a bug in the program or something wrong with my Tiger OS.

Every once in a while (this seems to happen at random after restarts/shut downs), all the associations in the preferences for Unarchiver are unselected. I am pretty sure that it is not a Unarchiver bug, because at the same time this problem happens, Firefox ceases to be the default browser and I have to select it as default again.

Sorry for my double post.

>>196

I am not sure what you mean here. You only get the preferences window if you click the icon directly, and the only reason to do this is to change the preferences. When unpacking archives, there's no need to click the program icon.

I just have a tiny request here:

Can you remove the option to associate .jar files with The Unarchiver? While .jar files are zip files, they are meant to be executed rather than decompressed and associating them with an decompression utility would make it difficult for users to run some Java programs. Unfortunately, most novice users aren't aware of this and they just blindly click on the "Select All" button.

>>198

Are they, nowadays? When I last did some Java programming, on Windows a few years back, there was no way to run a jar file direcetly, as I recall. It had to be done from the command line, or through a wrapper. Most Java apps I've seen use some kind of other of wrapper, too.

Is there now some way to run jars directly?

>>199 see things like http://sourceforge.net/projects/wiki-flcelloguy, which runs for me (On Windows, natch) with just a double click.

also, 200GET

On OS X you can (normally) just double click a .jar file to run it using the Apple Applet Runner (or whatever it's called). But it's still nice to have the option to extract it.

Time for a bugfix and internationalization release:

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.3.zip
http://wakaba.c3.cx/s/apps/unarchiver.html

New in this one:

• More localizations: Portugese and Russian. Thanks this time go to Nylson Coelho and Michael Krekin
• Changed the modifier key for extract-to-foler: Either Shift or Option works now. Command was too easy to accidentially trigger when opening a file with Command-O.
• Fixed a bug where app bundles in StuffIt files would not run correctly after being extracted.
• Fixed a bug where apps would be launched when the open-after-extracting option was on.

Plus the other post-1.2 fixes mentioned earlier.

(Sorry, no fix for the jar association yet.)

can unarchiver open the .sitx(not .sit)?????????? pls??

>>204

Not until somebody reverse-engineers the format.

So, which app handles the .sitx format and can one have it installed without interfering with unarchiver?

The Unarchiver crashes very often when cancelling extraction of sit file :(

>>207

Can you post a CrashReporter log?

Sorry for posting like this, can't provide link at the moment. Copy this and then remove the post. There are more chrash reports in the log, but all look similar; it's always Thread 1 that chrashed in function SIT_UnArchive.

**********

Host Name: franks-ibook
Date/Time: 2006-11-27 21:51:04.620 +0100
OS Version: 10.4.8 (Build 8L127)
Report Version: 4

Command: The Unarchiver
Path: /Applications/Utilities/The Unarchiver.app/Contents/MacOS/The Unarchiver
Parent: WindowServer [7068]

Version: 1.3 (1.3)

PID: 7107
Thread: 1

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xfc707aac

Thread 0:
0 libSystem.B.dylib 0x9000ab48 mach_msg_trap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.HIToolbox 0x93203740 RunCurrentEventLoopInMode + 264
5 com.apple.HIToolbox 0x93202dd4 ReceiveNextEventCommon + 380
6 com.apple.HIToolbox 0x93202c40 BlockUntilNextEventMatchingListInMode + 96
7 com.apple.AppKit 0x93706ae4 _DPSNextEvent + 384
8 com.apple.AppKit 0x937067a8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
9 com.apple.AppKit 0x93702cec -[NSApplication run] + 472
10 com.apple.AppKit 0x937f387c NSApplicationMain + 452
11 cx.c3.theunarchiver 0x0000292c _start + 760
12 cx.c3.theunarchiver 0x00002630 start + 48

Thread 1 Crashed:
0 de.dstoecker.xadmaster 0x000b3d84 SIT_UnArchive + 6244
1 de.dstoecker.xadmaster 0x0007a888 xadFileUnArcA + 412
2 de.dstoecker.xadmaster 0x0007a9e0 xadFileUnArc + 240
3 de.dstoecker.xadmaster 0x000bf87c -[XADArchive _extractFileEntry:as:] + 252
4 de.dstoecker.xadmaster 0x000bf75c -[XADArchive _extractEntry:as:] + 540
5 de.dstoecker.xadmaster 0x000bf2f8 -[XADArchive extractEntry:to:overrideWritePermissions:] + 352
6 de.dstoecker.xadmaster 0x000bf0b4 -[XADArchive extractEntries:to:] + 316
7 cx.c3.theunarchiver 0x0000428c -[TUArchiveController extract] + 1052
8 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
9 libSystem.B.dylib 0x9002b508 _pthread_body + 96

Thread 2:
0 libSystem.B.dylib 0x90049ea8 syscall_thread_switch + 8
1 com.apple.Foundation 0x929755d0 +[NSThread sleepUntilDate:] + 152
2 com.apple.AppKit 0x937a3a10 -[NSUIHeartBeat _heartBeatThread:] + 1100
3 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
4 libSystem.B.dylib 0x9002b508 _pthread_body + 96

Thread 1 crashed with PPC Thread State 64:
srr0: 0x00000000000b3d84 srr1: 0x000000000000d030 vrsave: 0x0000000000000000

cr: 0x44000244          xer: 0x0000000000000000   lr: 0x00000000000b3c78  ctr: 0x0000000000000003
r0: 0x0000000000000000   r1: 0x00000000f00803a0   r2: 0x00000000fc32cfc4   r3: 0x00000000003daae8
r4: 0x00000000003daae8   r5: 0x000000000000000c   r6: 0x0000000000000007   r7: 0x0000000000000100
r8: 0x0000000000403b59   r9: 0x0000000000000001  r10: 0x0000000000401b55  r11: 0x0000000000000003

r12: 0x0000000090003138 r13: 0x000000000189914c r14: 0x000000000189955c r15: 0x000000000183b200
r16: 0x0000000000080000 r17: 0x0000000000000003 r18: 0x0000000000000001 r19: 0x0000000000000013
r20: 0x0000000000077ab3 r21: 0x000000000455e008 r22: 0x00000000044dd008 r23: 0x00000000044dd00b
r24: 0x0000000000000000 r25: 0x000000000077f008 r26: 0x0000000000000000 r27: 0x0000000000000000
r28: 0x0000000001898c08 r29: 0x0000000000000001 r30: 0x000000000183b200 r31: 0x00000000000b2530

Binary Images Description:

0x1000 -     0x9fff cx.c3.theunarchiver 1.3	/Applications/Utilities/The Unarchiver.app/Contents/MacOS/The Unarchiver

0x29000 - 0x3cfff org.mozilla.universalchardet ??? (1.0) /Applications/Utilities/The Unarchiver.app/Contents/Frameworks/UniversalDetector.framework/Versions/A/UniversalDetector
0x72000 - 0xd1fff de.dstoecker.xadmaster ??? (1.3 (libxad 13.0, modified)) /Applications/Utilities/The Unarchiver.app/Contents/Frameworks/XADMaster.framework/Versions/A/XADMaster
0x8fe00000 - 0x8fe51fff dyld 45.3 /usr/lib/dyld...
...
...

>>209

I'll look into it.

I was so happy to find a replacement to stuffit expander i could not help but make a donation. I hope one day par support is added to the library as no elegant solution exists for os x

>>211

Many thanks! And I'll keep that in mind.

The Unarchiver is a must-have app.:)
Is there a possibility to add a preview-feature like in Zipeg ( http://macupdate.com/info.php/id/23378 )? This would be awesome!:)
Sometimes Unarchiver isn't capable of extracting certain rar-archives (pasword-protected).

Can I help with Dutch localization? I have XCode installed and can open the Unarchiver source code in it but otherwise I'm pretty clueless where to start. Can you give me a quick rundown? Thanks Roland

>>216

I'll add you to the list of translators, and mail you when there's time for a new release.

I'm having an odd problem with TheUnarchiver v1.3 and multi-part RAR files. Some of them work, but on some I get an error saying "the archive file is corrupted." I read on this discussion thread to check the output from Console, and I get this:

KATAMARI.ISO: crc error (f1c77610!=e8ca0330)

However, UnRarX, and WinRAR (run in Parallels) both say the files are fine, and extract them successfully. I've had this happen on archives named with .rar, .r00, etc, and on .part01.rar, .part02.rar, etc archives.

Email me at coredumperror AT gmail if you'd like a sample file that causes this error. I tried creating some small muilti-part archives using different options from WinRAR (authenticity, lock, recovery, etc) but everything worked except the one that I "locked." It didn't give me an error, though; instead TheUnarchiver just opens briefly and closes without extracting anything.

P.S. Is there any way to check which version of TheUnarchiver I have installed? I just downloaded and installed 1.3 to do these tests, but I wasn't sure if I'd had it installed already.

I have installed the app but it does not excute at all. I have a powerbook G4. when I double click the app from Application folder, I understand that I should be getting a "preferences" window but nothinh happens. There is nothing in Console.log. It does not even show up in the activity monitor.

>>219

Are you using 10.4?

Hi!
This program is great! Congratulations!
Do you have a plan to put support .pax and pax.gz files to The Unarchiver?
It would be great!

>>221

I don't have any plan, but I could make one. Depends on how much work it would take, and whether anybody actually uses the format.

>>222

That formats use any install package inside...
.pax.gz: is a standard gzipped .pax file.
.pax: "The pax utility will read, write, and list the members of an archive file, and will copy directory hierarchies. These operations are independent of the specific archive format, and support a wide variety of different archive formats. A list of supported archive formats can be found under the description of the -x option." it's similar to .cpio.

>>223

Now that you mention it, I did see those when taking apart installers. Maybe there is indeed some use for it, then. I'll add it to the list, at the very least, and whenever I have some spare time (don't hold your breath), I'll see what I can do.

>>220

Yes. I am running 10.4.8.

Triede uninstall & reinstall but no go

Thanks,

The Unarchiver 1.3 fails to expand an 85 part RAR archive. RAR Expander handles it OK.

Rar expansion definitely need improvement. ( The new rar version 3.7 is coming out soon )

Is there anyway i can view what is inside the archive without extracting it?
Anyway to know what the filesname(s) that will be extracted?

I know unarchiver is easy to use but sometimes i have to spend time to find out what is actually extracted out from the archive.

>>226

Can't do anything about it without having an archive that shows the problem.

It's time for a small update to The Unarchiver:

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.4.zip
http://wakaba.c3.cx/releases/mac/TheUnarchiver1.4_src.zip
http://wakaba.c3.cx/s/apps/unarchiver.html

This has a few requested features and bugfixes, and also experimental support for 10.3! Please try it and tell me if it actually works, because I don't have a machine to test it on. The other changes include:

• Support for pax archives.
• Fixed a bug where large archives with lots of resource forks would cause massive memory use.
• Fixed some timezone-related bugs. Some format may still have problems getting the timestamps exactly right, however.
• Various other minor bugfixes.

Hi,
I just found this great app. Everything works great except Stuffit (.sitx) archives... Will you support this too?
Anyway, thanks! It's very cool!
Dan

>>230

I really, really wish that I could support .sitx, but there is no documentation whatsoever for the format, and nobody's managed to reverse-engineer it yet.

Do you implement the password support for RAR files?

It's planned for 2.0.

Is there a way to get back default system icons for all the archives?

Thanks

>>234

While still using The Unarchiver? You can try finding those icons and copying them over the ones inside the The Unarchiver app bundle.

Feature request: the option to automatically scan the decompressed item for viruses using the virus checking app of your choice. Thanks!

Icons for .sit files aren't showing up for me (in fact it's been hard enough getting .sit files to open with The Unarchiver at all - it doesn't show up under the Open With menu).

Also, a minor issue with encrypted .sit files - if you enter the wrong password it will try to extract anyway but complain about corruption.

>>237

Sounds like there's a filetype conflict with some other app, then. The Universal Type system in OS X is a bit buggy that way.

it doesn't support .sitx archives. if it was added,i will delete stuffit。

I love the idea of The Unarchiver. Unfortunately, after installing it, I still had to install Stuffit because The Unarchiver, being able to decompress .sit files, couldn't do with just one. The Blank Dock Separator package available at MaxThemes. I am now on a brand new machine without Stuffit and would like to keep it that way, but have unfortunately forgotten to back up the separators, yet again. Does anyone have them and can repackage them in say .zip for me? Thanks! Kudos to the developers though for a killer app!

>>243

That file unpacks just fine for me. Were you using an older version earlier? There have been a lot of bugfixes to StuffIt unpacking in the later versions.

A small update for The Unarchiver:

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.5.zip

This should, I hope, fix the problem with Xee where archives would fail to open. It also adds a Traditional Chinese localization. Other than that, nothing much has changed.

The .pax support is working great! Thx!
But, if I try unarchive an password protected rar arhive, The Unarchiver popup the password window.
But if I type the CORRECT password (100% it's correct, becase I can unarchive that file with unrar from console with same password) The Unarchiver give me a message window:
"Could not extract the file 'the file name': Command is not supported"

Hi! I found a spelling mistake in the german translation! A pop-up windows says:

Der Inhalt der Datei ... konnte nicht mit diesem Programm entackt werden.

Right:
entpackt (the "p" is missing)

Hi again!

I tested to open a passwort protectet .rar file (I made by myself with SimplyRAR)
but there's no passwort pop-up - instead a pop-up that says:

The contents of the file ... can not be extractet with this program.

RAR password support is not yet implemented. I'm hoping to have it in 2.0, whenever I find the time to work on that.

>>247

Thanks, fixed.

0.5 works fine so far in 10.3.9 so far (1.5GHz 15" PowerBook with 2GB of RAM); I used it for expanding a .tar.bz2. It doesn't have a Dock icon though, but I'm not sure if that's intentional or not.

Thank you very much for adding 10.3.9 support. I had all but written it of for when I get Leopard.

I downloaded phpMyAdmin in .7z format but The Unarchiver gave errors about unknown data formats when trying to extract it. 7zX handled it fine.

http://prdownloads.sourceforge.net/phpmyadmin/phpMyAdmin-2.10.0-rc1-english.7z?download

>>252

The Unarchiver uses the 7zC code from 7-zip, which doesn't support all formats (which is nearly impossible anyway, as 7-zip is defined as supporting a ridiculous amount of formats for no good reason). I've tried to nag the author to update it, but I don't think he has yet.

Hi,
Just a little request, why don't you add growl support > http://growl.info/
Sorry if this has already been asked.

Thank you for this app :)

>>254

I'm not sure it's very useful, as an unarching operation doesn't take more than a few seconds in the average case.

There appears to be a bug, introduced between 1.3 and 1.5, with password handling for encrypted ZIP archives. In 1.3, you can type the password, click Continue, and all files in the archive are extracted successfully. However, in 1.5, roughly half of the files fail to extract. (This is on 10.4.7, by the way.)

>>256

I need a test case to fix it.

Problem ... The Unarchiver simply closes right away if it has no write access to the folder of the clicked RAR file. It would be a good idea to either throw up an error message saying no permission, or ask if the users wants to extract somewhere else instead.

>>258

I'll add that to the list.

Is there a way to get StuffIt to stop stealing The Unarchiver's application default preferences? I even tried the Default Apps preference pane add on and StuffIt just won't stop being a jerk.

>>260

Are you using Firefox or Camino, and getting Zip files associated with StuffIt when downloading? This is caused by a Mozilla bug that they refuse to fix. You can work around it by choosing "Get Info" for one of the affected files, changing it to The Unarchiver, and then clicking "Change All".

Re: 256

I can't give you a test case file (too large, for one thing.) However, here is the problem:

--- /tmp/TheUnarchiver1.3_src/libxad/portable/mac/XADArchive.m 2006-11-24 09:22:52.000000000 -0800
+++ /tmp/TheUnarchiver1.5_src/libxad/portable/mac/XADArchive.m 2007-02-08 17:40:46.000000000 -0800
@@ -1053,7 +1069,8 @@

    else if(detected_encoding) encoding=detected_encoding;
    else encoding=NSWindowsCP1252StringEncoding;

•   return [password cStringUsingEncoding:encoding];

•   return [[password dataUsingEncoding:encoding] bytes];

+// return [password cStringUsingEncoding:encoding];
}

Clients of _encodedPassword (i.e. xadFileUnArc) require that the password be maintained as a null-terminated C string. (This means you can't use any encodings which might have embedded nulls as part of the encoding.) Also, dataUsingEncoding won't null-terminate the data. If a null char happens to immediately follow the data then the password works, but if not then the string continues until a null is reached, and so the password is (often) wrong.

Going back to cStringUsingEncoding for the password works just fine, since it appears xadFileUnArc can't handle anything else.

>>262

Thanks for tracking that down, but the problem is that cStringUsingEncoding is 10.4 only, and thus I can't use that. I'll have to look at other options.

>>263

In that case, this should work (haven't tried compiling yet though!):
char nullChar = '\0';
NSMutableData *pwdData = [NSMutableData dataWithData:[password dataUsingEncoding:encoding]];
[pwdData appendBytes:&nullChar length:sizeof(char)];
return [pwdData bytes];

There will still be problems if the password string's encoding contains any nulls (like Unicode), but I don't think that's going to be a common case, and xadFileUnArc can't handle such encodings anyway.

>>264

Actually, you can just use increaseLengthBy:, as the new data will be initialized to 0. I'll probably go with that.

The Unarchiver hangs when you cancel the extraction of a rar file. Shows "Preparing to extract ..." message as though it is working to extract the file although it was canceled before selecting a destination. I'm running 10.4.8, 1.83 Core Duo with 2GB Ram

>>266

Known bug, will be fixed.

TheUnarchiver used to extract archives into a subfolder of the current folder named after the archive file... it doesn't do that for me any more, and I'd really like it to. Did I screw up a setting, or has that feature been removed? (or maybe I'm just hallucinating again...)

>>268

It does this if there is more than one file or folder in the archive. If there is only one, it is not put in a subfolder.

Ohhhh, that makes sense, I guess. Still, it would be nice if there were an option to always extra to a subfolder, since if you don't know the name of the file inside the archive, it could be an issue finding it in the finder window, since it always alphabetizes on the fly. Making a subfolder with the same name as the archive will make the subfolder show up right next to the archive in Finder, which would be great!

>>270

It's been requested before, so it'll probably show up sooner or later. Maybe not in the next version, but I'll add it at some point.

Hi,

Absolutely bizarre problem with the unarchiver in regards .sit files.

Mac OS does recognize it as an application that can open .sit fles (all other archive types yes, but not.sit)

It can happily open .sit files, but assigning it as the default application seems impossible.

Any ideas?

Well, let's just say that Launch Services, which handles this stuff, is... less than well-designed.

Something similar has happened to me when I had another program installed that defined a UTI with another name for the same extension. You'd have to use something like RCDefaultApp to see if that is the case, or to delete suspicious apps (AND empty the trash, or else it does not count).

If you can find an app that causes it, send me its Info.plist!

Hi, been using The Unarchiver on 10.4.7 (PPC) and again on >=10.4.8 (Intel) with absolutely no errors so far. Thanks for a fantastic app!

Is there any way to automatically associate all supported compression types with The Unarchiver? In the past I just used "Change All" in the Info window as I came along files that opened with BOMArchiveHelper, but having an easy way to set all of them at once would be very convenient.

Also, any plan on making "The Archiver"? Would be nice to replace the "Create Archive" option in Finder's contextual menu with options to create compressed tars (tgz and tbz2 preferably) and such.

>>274

Doubleclick The Unarchiver, and you get a preferences window that has a list for associating filetypes.

Also, sorry, no plans for The Archiver. I am generally happy with what's available already, personally, and I've got lots of work as it is.

Another release of mostly bugfixes and tweaks:

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.6.zip

• Fixed the zip password bug as reported in >>256.
• Added support for zip archives created by ZipIt.
• Added a Dutch localization.
• Fixed a rare RAR bug, and some GUI quirks (like >>258).

As pointed out on MacUpdate, The Unarchiver defines for the system the filetype of "RAR-Archives" as files ending on .rar, .RAR, .r00, r01 etc., as well as .001, .002, .003 etc.

The problem is that multi-part split files also end on .001, .002 etc. The Unarchiver is unable to open/merge these files (which I would not expect it to do, anyway - it is an unpacker, not a filemerger).

I cannot dissociate .001-files from The Unarchiver without dissociating .rar-files as well, since both are defined for the system as rar-archives.

I would like to propose, that in the preferences a seperate filetype for .001-files ("Multi-Part Document"?) is added, which can be ticked or unticked to be opened by The Unarchiver. That way, the user can choose if he wishes to open .001-files with The Unarchiver or a different program.

I hope that is not too much to ask. I feel the program is amazing, and the developer has been doing a great job!

Also (since I seem to be the roll right now :-) ), I would just like to register my vote to keep the current behaviour of The Unarchiver of extracting one file archives into the current folder and archives with multiple files into a new subfolder.

It has been requested on MacUpdate that ALL extractions should be into a new folder, regardless if one or multiple files. I don't think that is a good idea, and at least should be optional for users who prefer the current way.

>>277

Once again, Launch Services is being a useless piece of crap... sigh. Oh well, I guess I'll have to go with making a separate file type for those, although I can just tell that will lead to some other problem instead somewhere down the line.

>>278

Yeah, I'd only ever make than an option, and it definitely wouldn't be the default.

Hmm, I can't extract .sitx. Not supported yet?
Thanks.

Sorry I just founded out with sitx. I hope they release some docs before too long.

It cannot open password protected files!

It cannot open password protected files!

Yes, it can. Just not all of them.

I get errors when trying to extract the zip for NuFile (which BOMArchiveHelper has no issues with) (In the .rtfd/):

http://growlichat.com/downloadredirect.php?id=33

Would it be possible to add the version number to the main window so I can quickly tell which version I have?

>>285

Right-click the app and Get Info. If that doesn't show anything, you have a pretty old version.

Although it appears that file does not open in the current version either. I'll add it to the list.

I haven't tested it recently but it won't extract a working version of Adobe Flex Builder (Beta).

When trying to run Flex, it does nothing. I attempted to extract with Bom and it worked.

>>287

I need the actual file or at least a link to it before I can do anything about it.

>>286

Yes, I realized it was available in the Get Info window (I have the current version), but thought it might be easy/good to list it in the main window, so I wouldn't have to try to find the application to run Get Info on it.

I just noticed after extracting a rather large zip file that the modified date of the folders were set to today if the folder had anything in it and to the original modified date if it was empty. I recognize that the file system is doing this as the folder contents are written. From the point of view that the extraction should result in as exact a copy of the original as possible, shouldn't the folder dates be reset after they have been filled?

How do we donate to you? It looks like a lot of people are loving your application and you're putting in some serious hours on it over the last few months. I'm hanging out for v2.0 and password protected rar support... can I paypal you a few bucks to help with a beverage of your choice while you work?

>>291

There is a donation link on http://wakaba.c3.cx/s/apps/unarchiver.html if you want to!

i love this little tool, but many password-files (for rar's) didnt work with the unarchiever :-( Please do not give up the development. The Speed is amazing!

Just plaudits: Thank you so much for this wonderful, well designed utility. Obviously, a lot of work and thought has gone into it. I can't imagine an unarchiver with a better interface or more complete (useful) functionality. So thank you!

Unless somebody is already doing it, I would be glad to translate The Unarchiver to Italian; all I need to know is which files I have to modify in order to complete the translation. Do I have to translate only the strings inside "Localizable.strings" or there is something else?

Thank you very much

My e-mail address is francesco (at) allascala (DOT) it

I found a case where using Unarchiver v1.6 on a rar file of an iso disk caused Unarchiver to run forevvvvver, using about 70-85% system resources. I eventually Quit the program from Activity Monitor.

I tried the same rar file in UnRAR v2.2, and it ran through the extraction, up to 99 %, looked like it would finish, but then its status window reported a CRC error. and finished the process. The reported error statement from UnRAR: "CRC failed ??? - the file header is corrupt"

So I am guessing that Unarchiver 1.6 got hung on the CRC error and never quit. But why use up all the system resources in that? And no feedback in the Unarchiver other than a perpetual 'spinning' bar.

And I think it would be good if Unarchiver would give some sort of status indicator, both of progress and outcome (or failure).
(I looked in Console logs, did not see anything that looked like unarchiver)

Thank you. All the best.

>>298

That was obviously not intended behaviour. I can't do anything to fix the bug without a file that causes it, though.

i had another 324mb 7z file today, and same result.... i can tell you where to download it from but would rather do it in a private manner... please let me know if you're interested... thanks :)

p.s.
i think it is not necessary though... just create a 300mb+ 7z file using any capable utility, and try extracting it with the unarchiver and you should see the problem...

No Sitx support :(

Goddamnit, I can't wait for the day when I can get rid of stupid Stuffit once and for all.

Would it be possible for the window that appears when you are unarchiving something to be like the BOMArchiveHelper window and float above everything but isn't actually "selected" so you're still in the Finder even though the window is floating above it?

>>300

Unfortunately, it's not really a fixable problem with the current 7-Zip code. I've tried asking the author to improve it, but no luck. I might try to put in some workarounds later, but no guarantees.

>>302

I'll look into it when I find some time.

I'm dying having to use unrarx to get at my password protected rar files (I interface with a bunch of Windows users who use encrypted rar every day!). Can you give us any idea at all on when we this might be ready for release? I am more than willing to help with testing...

I'm dying having to use unrarx to get at my password protected rar files (I interface with a bunch of Windows users who use encrypted rar every day!). Can you give us any idea at all on when we this might be ready for release? I am more than willing to help with testing...

Request: I'd like to have the preferences set to extract archives to the same folder but option+double clicking will give you a dialog and prompt you where to extract it (I'd mainly use archives on network drives so I don't have to transfer the file to my CPU and back again across the network).

Does this program support ace compressed files? Also multi-part ace. Retrogamers on Windows seem to like this method and I have yet to find a solution.

>>307

Sorry, no. The format is propiatery and only available under NDA, apparently. One of the main programmers of libxad, that I use to unpack lots of stuff, has gotten access to the source but hasn't gotten around to implementing it. I don't know if he ever will, and it's beyond my abilities, so, sorry, no time soon.

Is there a known bug concerning Unarchiver's inability to finish extracting an ISO file? I tried two separate files and it hangs on both of them right at the end.

Hi, using The Unarchiver 1.6 I encountered a problem when decompressing a file in a deep subdir from a tar.gz archive. I created a sample archive showing the same problem and uploaded it here: http://www.maxloresti.com/testdir.test01.tar.gz

It only contains a dir and a bunch of subdirs, which in the end contain only one small file called "definition.xml". When I extract the archive using The Unarchiver, the name of the extracted file is "definition.xml0000644". The appended numbers really look like permission bits... :)

StuffIt Expander correctly extracts the file and the whole archive.

Hi,

First off, Unarchiver is a great program. It works so well.

Does anyone know if there are plans to add the ability to open password-protected zip files in a future release? Thanks.

You can already open some password-protected zip files. If you have one that can't be opened, I'd like to see it or else I can not add support for it.

I just found what will make alot people happy about the password glitch that appears to fault some RAR files.

http://www.unrarx.com/faq.html

Download this program and follow the instructions. It's not as sleek as Unarchiver but.... IT DOES the Job when it comes to Passwords on RAR files even split ones. I just thought I'd share this with someone who may have been going up a wall with password files.

Let me know if it works.

>>237

"Icons for .sit files aren't showing up for me (in fact it's been hard enough getting .sit files to open with The Unarchiver at all - it doesn't show up under the Open With menu)."

I'm also getting the same problem as gannet. Anyone else?

>>112

"Find a file of the type that is not getting the correct icon (Simon, in your case a .sit).
Get Info on that file, and go to the Opens With... section.
Change it from The Unarchiver to anything else that can open it.
Hit the Change All... button. The icon should change to the new apps icon.
Now go back to the drop down list and change it back to The Unarchiver, and hit Change All... again."

Nick's fix doesn't work for me.

You probably have some other program installed that conflicts with The Unarchiver's filetypes. Launch Services is pretty broken when it comes to these things.

Are the duplicate extensions in all caps for supported file types really needed?

>>318

I don't really know, but Preview.app has them.

Thank you GaryGnu! UnRarX worked for the password protected rar files at:
http://radiowaves66.blogspot.com/

The Unarchiver kept on giving me errors that the "Command Is Not Supported".

Two questions.
1) Which SIT formats are supported? 1.5? 2.0-4.0? 5.0?

2) Does it support .zip archives whose contents have MacBinary metadata as implemented by Tom Brown's ZipIt?

>>321

1. No idea what the differences are. I've been tweaking it to work with any file people have showed me.
2. Yes, at least the development version, I forget if the latest release has that code or not.

You need to make the program follow the language rules. So if i chose not to install any languages except english and french and I installed the OS, when Unarchiver installs it should only install English and French as languages and not installed any other one. If a user wanted to add another lang. they can download it drom the site and add it through the "Get info" screen. This feature should be added cause it makes the program smaller for the end user.

The app needs to follow OSXs language rules. If i dont install russian with the OS russian should not be installed with the app

Somehow I think most users can afford the extra 400k.

Ha, I've discovered the problem with .sit files! The Unarchiver is simply missing a UTI: com.stuffit.archive.sit
I added this to the info.plist and it works fine now :-)

I have AppleScript code for determining if a file is Stuffit 1.5, 2.0-4.0, or 5.0; it's called StuffTyper. Hmm, looks like I never uploaded it to my website; I can send it to you if you'd like to see the code (it's just a kind of magic number checker). You will then have a way of determining which .sit types people sent you. (It's not a catalogger, but you could modify the script or use it in conjunction with something else, like File Buddy.) If you want me to send it to you, just tell me how you'd like it sent.

Um, I don't quite see the point. The Unarchiver can handle any .sit file already.

Speaking of types though, I believe 'SIT!' is a creator type, not a file type. 'SIT2' perhaps?

I used The Unarchiver on a Windows exe-file and it run forever, I quit the program with Activity Monitor, because there was no response. Now I have lost 10GB of my Diskspace. Is there tmp, I can delete?

>>329

There's probably a hidden folder in the same folder as the file you tried to unpack, which starts with a ".". You should be able to see it from Terminal.app, at least.

yes, SIT! is a creator type for StuffIt Deluxe (Expander is SITx). SIT! is also the file type for StuffIt 1.5 files. StuffIt 2.0-4.0 uses 'SITD' filetype and Stuffit 5.0 filetype is 'SIT5'.
My script checks the internals and sets the filetype metadata accordingly.

Hi there,
same problem as post #320. I always get the errormessage:
"Command Is Not Supported" on archives of page
http://www.doloresoriordan.net/eng/video.htm
even if I specify the correct passwrod. The archives are fine, unpacked them using UnRarX, but your tool is looking much better, so I would like to use your tool.

Password-protected RAR is not supported yet.

Please add an option to use the archive's name for a destination folder. I have a lot of archives with good archive names, but unintelligible or abbreviated folder names inside the archive. When I extract them (especially if processing several at a time), I have no idea what folder matches to what archive.

Already added, but I forget if it's in the release version or just my development version.

>>333
Hm okay, it's just Expander includes recognition of 'SIT2' but not 'SIT!'. Are you sure SITD isn't StuffIt 3.x-4.x with SIT2 being StuffIt 2.x?

Anyway, has that StuffIt UTI I mentioned been added to The Unarchiver?

Would you add a command line interface? I am downloading compressed files, manually processing them with The Unarchiver, then parsing them into a database. I would love to be able you use your tool to automate the process. I would love it even more if it were available in Ruby!

>>339

It's something I've thought would be nice to have, but I haven't actually needed it enough to make it.

If you're feeling like doing some programming yourself, most of the magic is in a framework, which should be pretty easy to use. There's even a very simplistic command-line tool already for testing purposes which might be expanded. Or maybe you can bridge the framework into Ruby somehow.

If you do any of that, do let me know.

When the app is set to extract archives to "Same folder as archive", extracting archives found inside DMG files naturally fails.

In this case, I'd like it to fall back to using the Desktop as the destination folder (like BOMArchiveHelper ?). Prompting for an alternate folder - perhaps defaulting to the Desktop - might be a good option.

Great app - thanks!

>>342

Hmm, good point.

Bug Report :
OS: MacOS 10.4.10 (intel)

the unarchiver 1.6 was crashed when trying expand RAR archive that encoding japanese/korean filename.
I attached crash log file.

**************************

Date/Time: 2007-09-01 17:46:18.864 +0900
OS Version: 10.4.10 (Build 8R2232)
Report Version: 4

Command: Xee
Path: /Applications/Xee.app/Contents/MacOS/Xee
Parent: WindowServer [415]

Version: ??? (2.0)

PID: 709
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0 libSystem.B.dylib 0x90072db2 lmatcher + 132
1 libSystem.B.dylib 0x90030735 regexec + 11065
2 de.dstoecker.xadmaster 0x17fd9b71 -[XADRegex matchesString:] + 75
3 de.dstoecker.xadmaster 0x17fd865f +[XADArchive volumesForFile:] + 546
4 de.dstoecker.xadmaster 0x17fd462f -[XADArchive initWithFile:delegate:error:] + 77
5 de.dstoecker.xadmaster 0x17fd459f -[XADArchive initWithFile:] + 56
6 de.dstoecker.xadmaster 0x17fd82c6 +[XADArchive archiveForFile:] + 62
7 cx.c3.xee 0x000642c2 -[XeeArchiveSource initWithArchive:] + 90
8 cx.c3.xee 0x0000c3e4 -[XeeDelegate application:openFile:] + 1020
9 com.apple.AppKit 0x9326fd98 -[NSApplication _doOpenFile:ok:tryTemp:] + 459
10 com.apple.AppKit 0x9337c3e6 -[NSApplication _doOpenFiles:] + 240
11 com.apple.AppKit 0x9337c2d8 -[NSApplication(NSAppleEventHandling) _handleAEOpenDocuments:] + 87
12 com.apple.AppKit 0x93275701 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 793
13 com.apple.Foundation 0x927f2e65 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 447
14 com.apple.Foundation 0x927f2c8f _NSAppleEventManagerGenericHandler + 91
15 com.apple.AE 0x915236c5 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 147
16 com.apple.AE 0x915235f6 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
17 com.apple.AE 0x915234c2 aeProcessAppleEvent + 190
18 com.apple.HIToolbox 0x92df00e4 AEProcessAppleEvent + 37
19 com.apple.AppKit 0x9327363d _DPSNextEvent + 1044
20 com.apple.AppKit 0x93273056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
21 com.apple.AppKit 0x9326cddb -[NSApplication run] + 512
22 com.apple.AppKit 0x93260d2f NSApplicationMain + 573
23 cx.c3.xee 0x00002d06 _start + 216
24 cx.c3.xee 0x00002c2d start + 41

Thread 1:
0 libSystem.B.dylib 0x90047dd7 semaphore_timedwait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90ce1da9 TSWaitOnSemaphoreCommon + 163
2 ...ickTimeComponents.component 0x982c12a6 ReadSchedulerThreadEntryPoint + 4723
3 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x90047dd7 semaphore_timedwait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90ce1da9 TSWaitOnSemaphoreCommon + 163
2 ...ple.CoreServices.CarbonCore 0x90cebcdc AIOFileThread(void*) + 1068
3 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x90072d3f ecx: 0xffffffff edx: 0x00000001
edi: 0x00000000 esi: 0x00000000 ebp: 0xbfffeef8 esp: 0xbfffeca0
ss: 0x0000001f efl: 0x00010246 eip: 0x90072db2 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:

0x1000 -    0x83fff cx.c3.xee ??? (2.0)	/Applications/Xee.app/Contents/MacOS/Xee

0x7d5000 - 0x7d6fff com.apple.URLMount.CIFSPlugin 1.2.5
.....
.....

>>344

Could you give me a copy of the file, and also a list of all the filenames that were in the same folder as the archive?

The Unarchiver failed tonight extracting files from a 2+ GB zip file. one file inside was a 2.2G DMG file. Other files before it extracted fine. It left the file as a zero length file.

Just to be sure I unarchived it with BOMarchiver and it worked just fine.

The Unarchiver failed tonight extracting files from a 2+ GB zip file. one file inside was a 2.2G DMG file. Other files before it extracted fine. It left the file as a zero length file.

Just to be sure I unarchived it with BOMarchiver and it worked just fine.

I've tried extracting several different RAR files (containing rar, r00, r01 etc.) and the application simply freezes showing a "Preparing to extract..." screen while using 90% of my processor. Moreover, it is impossible to anyhow close or Force Quit the program as it doesn't have the option due to its integration into OS X.

Apart from that, wonderful program, but I hope this problem is solved.

If you have any further questions, e-mail me at rudi[dot]eihenbaums[at]gmail

>>348

I need a file that causes this before I can do anything about it. If there are any messages on the console, post those too. Also, try turning off all InputManagers and haxies.

What do u mean by InputManagers?

I can forward you some files that I've been trying to open, I can't send them to you, because they're about 700MB movie torrents, but I can give you a link so you can look into it.

Here's a screenshot, doesn't help much, but how do I open the console on demand?

>>351

Run /Applications/Utilities/Console.app, then try to get The Unarchiver to lock up again and see if anything appears in Console.

Do you want me to take one of those "Sample" things?

Nothing in the console.. anything else? Want me to give you a link to the torrent file?

>>355

No, just see if The Unarchiver prints any message on the console before it locks up.

>>345

reply was too late. I'm Sorry.

exactly, the unarchiver was crashed when I was trying expand RAR files over network. If target archive's file have wrong encoded filename, It caused crash.

But If you copy file in your macintosh, then the file was expanded normally(the unarchiver was displayed encoding selection dialog box).

Please resolve this problem. I believe you can do it :-)
Thanks, Good Luck!

>>358

Without an example file that can cause the problem, there is not much I can do.

As I said before, nothing appears in the console.

Here's a link to the file I'm having problems with. CD1 unrars properly, CD2 is the thing you should try to select to download in the torrent.

http://www.newtorrents.info/torrent/25718/Knocked.Up.2006.R5.LINE.XViD-PUKKA.html

P.S. It happens with a few other files.

Fails to extract .sit archive file with password protection made with DropStuff 5.5 running on Mac OS 9. It only displays an alert message saying "Could not extract the resource fork for the file"<file name>": Data is corrupted". No problem when without password protection.

Any solutions?

I'm guessing the SIT code might not support encryption? I did not write it, so I am not sure. I never tried any encrypted archives. Does it extract any other, encrypted SIT files?

I found a few other large, multi-part RAR files that the Unarchiver crashes with. Nothing appears in the standard view of the Console - is there maybe a specific place I should look in?

Great program! Would be a great addition having the XAR support (http://code.google.com/p/xar/). Thanks.

Good work,

it runs pretty well for me.
the only bug, i've saw, was an improperly exit when the work was done. It leaves an empty window, that needs to be closed throught "activity monitor"

Great frameworks! Thanks.

I've fixed two memory leaks and done a touch of cleanup.

http://home.comcast.net/~sequential/XADDiffs.zip

>>367
Found another leak, so the file has been updated.

>>367-368

Ah, I knew about the missing free in XADRegex already, actually, but I hadn't catched the one in XADArchive yet, though. However, the nullstring thing is entirely intentional.

>>369
Yeah, the nullstring change was just my preferred coding style.

If this could open rar files that had passwords, my life would get a lot, lot easier. Is there anything we can do to help? Ive already donated once...

>>370

No, I mean, there was a reason it was written exactly like that, which is to make it a value guaranteed to be unique.

I'm having some trouble associating The Unarchiver with Zip files. They reset back to BOMArchiveHelper for some strange reason. When I went to reassociate them (via Get Info), The Unarchiver did not show up as an option on the "Open With" popup menu. If I select it using the "Other..." option, it works and the icon shows up properly. If I select "Change All...", it works - but the icon disappears and becomes a generic document icon!

I'm sure this is something weird on my end, but I thought I'd report it - just in case.

>>373

Sounds like some kind of Launch Services bug. It's a very temperamental system.

Can you please make an option to extract the files directly into the folder same folder as the archive?

As it is, i have to extract, browse into the new folder, copy/paste or move the files (thanks to no Cut on OSX), and finally delete the useless folder!

I honestly can't think of why you would want it any other way - is it to protect against duplicates? Even if the folder already has the files contained in the archive, you could have a dialog appear asking whether or not to overwrite. Considering archives are generally for sending to other people, it is not likely they will have the same files anyway.

Thanks for an otherwise great program! (Xee too!)

Can you please make an option to extract the files directly into the folder same folder as the archive?

As it is, i have to extract, browse into the new folder, copy/paste or move the files (thanks to no Cut on OSX), and finally delete the useless folder!

I honestly can't think of why you would want it any other way - is it to protect against duplicates? Even if the folder already has the files contained in the archive, you could have a dialog appear asking whether or not to overwrite. Considering archives are generally for sending to other people, it is not likely they will have the same files anyway.

Thanks for an otherwise great program! (Xee too!)

Bug: Appears to crash silently while extracting iWork08Trial.mpkg/Contents/Packages/iWork08Trial.pkg/Contents/Archive.pax.gz
Enhancement: Opening a .pkg bundle extracts Contents/Archive.pax.gz
Enhancement: Opening a .mpkg bundle extracts Contents/Packages/*.pkg

Something odd: When I attempt to uncompress a set of .RAR files, the program will lock up. However, I can't see how to get the program to quit since UnArchiver does not show up on the ForceQuit menu. I'm assuming that it has something to do with installation, but I am still unfacile with the Mac OS so I am not sure as to how to troubleshoot it as I would with a PC. Help/Hints? Oh yeah, version 1.6 on a 10.4.10 MacBook.

>>378

Use Activity Monitor.app.

Also, open Console.app and tell me if there are any messages from The Unarchiver.

There does not seem to be anything on the Console.

However, the Activity Monitor worked a trick. If nothing else, thank you for that suggestion. Odd though--for a "locked" up application, it sure was consuming an assload of CPU time; somewhere in the 75% to 85% range.
-
Dean C.

Hi, there is a bug whenever I try to extract more than 1 rar-file: The first file gets extracted, while they other are in the waiting line, but then wehn Unarchiver wants to process the second one in the line it just quits!

I have version 1.6 on my MBP Intel with 10.4.10

>>383

I just yesterday extracted several rar files in a row, so the bug is not that simple. What files are you trying to exist? Does it crash no matter what order you extract them in? Does it work if you extract one by one? Are there any messages on the console?

It'd be really nice if passwords would work with rar files ...

It'd be really nice if passwords would work with rar files ...

the unarchiver is worked in leopard(10.5).
but it can't link ZIP file association perfectly. I check zip format in the unarchiver [preferences>format tab]. but default zip unarchiving application wasn't changed.
please check this problem, and update unarchiver :-)

thanks, good luck!

I had the same problem as 388. Everything works great except for ZIP file associations.

Sounds like Apple went and messed with the UTIs again.

All right, for anyone who wants a workaround for the zip problem until I get around to buying Leopard and making a real fix:

Open up The Unarchiver.app/Contents/Info.plist, and search-and-replace all instances of com.pkware.zip-archive with public.zip-archive.

As suspected, Apple went and changed the UTI for zip files, and this broke all programs that used that UTI. Which apparently was only me because everybody else seems to have understood that UTI handling is totally broken and unreliable.

That works great for now, thank you. I look forward to an updated version of The Unarchiver. :)

Thanks for the workaround!

BTW, it might not be just you since trying to associate Microsoft Remote Desktop config files with other programs also seems broken.

Hey I edited the Info.plist and Zip files now open with The Unarchiver, but the Zip files still have their default icon appearance. They don't have the nice brown Zip icons that is usually the default of Unarchiver. Any ideas? This is so odd.

I don't really know the history behind it all, but after scrolling through this thread, I saw some great looking screenshots from Adam Betts with an HUD window style. This could have been hard back in '06 but with Leopards new developer tools, the option for the HUD window style is built in. Would it be possible to get a preference to switch between the window styles in a future version? Also, for zip archive, I just went into the files info and told Zips to open with The Unarchiver and applied it to all files of that type. That worked perfectly, but like people have said above, I get the default blank page icon.

>>394

Just guessing, but that might just be Launch Services sucking again. Do they still not have the right icon after rebooting?

In case it helps, I DO have the right icons after that patch. It must be something weird, because my machines work just fine.

No I've rebooted plenty of times since then. When I right click and hit get info on a zip file it says it opens with "The Unarchiver" but it still has the default icon. Its making me crazy...I've tried everything.

>>398

What if you use Get Info to select some other app, then select The Unarchiver again, and then click Change All?

Hey that worked! Thanks a lot!

Well, to hopefully inspire someone of authority, I have actually modded The Unarchiver to have a HUD display. This shows that it really is simple enough for an Interface Builder to do (with the new dev tools). Here are some preview screens and a download link to the nib files i modified. The HUD needs a custom status bar, but hopefully this will help speed up and motivate the HUD interface into an Unarchiver release. I like it a lot and I think others will too. Also, The Unarchier rocks! thank you for the development!

Example One: http://www.randomstorage.com/mods/unarchiver/UnarchiverHUDExample_1.png

Example Two: http://www.randomstorage.com/mods/unarchiver/UnarchiverHUDExample_2.png

Unarchiver HUD NIBs: http://www.randomstorage.com/mods/unarchiver/UnarchiverHUD_NIB_Resources.zip

>>402 That looks really nice Pico! I hope something like this can be incorporated.

Thank, you can implement it too using the NIBs, it works perfectly, except for resizing the window, which I don't think is worth fussing with. Anyway, sorry for the double posts, I wasn't sure if i could post html and I wasn't able to delete my post like i thought i would be. Also, in the post I meant to say an "simple enough for an Interface Builder novice to do"

I'll certainly look into it, once I have some spare time to work on it again. What's the problem with resizing, are you putting a big black view to cover up the background painting? In that case, you should just be able to set its size flags so that it resizes properly.

When the window is resized the HUD loses its transparency, and is illegible because of the fact that I made the text white. The progress bar also gets funky, see the 3 different colors on the attached image. I think it does have something to do with the ProgressView but I don't know enough about it to troubleshoot.

Love the app, it's simple, elegant and useful.

As for the ZIP file problem, here's my experience.
Did a clean 10.5 install, and just upgraded to The Unarchiver 1.6.

First I told Unarchiver to open .zip files by checking the .zip format.

For a test, I create a file with .zip extension, e.g. by running "touch testfile.zip" in terminal. The file has a blank sheet icon.

I then get the file's info, change it to open with The Unarchiver (which does NOT show in the quick drop-down, i have to browse for it each time I'm here). This file, and only this file, then changes to the Unarchiver "Box" ZIP icon (yay!). Then I click "Change all" and all ZIPs including this one, go back to blank sheets.

Will update you if restarting fixes anything.

Thanks for your work on one of my favorite utilities.
Regards,
-Dan

I am having the exact same issue as Dan. I have tried all he said and multiple restarts, I also tried changing "com.pkware.zip-archive" to "public.zip-archive" with no luck and also tried changing it to "public.archive" which I saw somewhere after a google search. all to no avail. It would be great to see that awesome icon in my DLs stack!

Same issue here as Dan and Pico.. fingers crossed for an update!

Same issue - despite modification association is not functioning ):

Find :

	<dict>
		<key>CFBundleTypeExtensions</key>
		<array>
			<string>zip</string>
			<string>ZIP</string>
		</array>
		<key>CFBundleTypeIconFile</key>
		<string>zip.icns</string>
		<key>CFBundleTypeMIMETypes</key>
		<array>
			<string>application/zip</string>
			<string>application/x-zip</string>
			<string>application/x-zip-compressed</string>
		</array>
		<key>CFBundleTypeName</key>
		<string>Zip Archive</string>
		<key>CFBundleTypeOSTypes</key>
		<array>
			<string>ZIP </string>
			<string>ZIP_</string>
		</array>
		<key>CFBundleTypeRole</key>
		<string>Viewer</string>
		<key>LSItemContentTypes</key>
		<array>
			<string>com.pkware.zip-archive</string>
		</array>
		<key>LSTypeIsPackage</key>
		<false/>
		<key>NSPersistentStoreTypeKey</key>
		<string>XML</string>
	</dict>

Replace with :

	<dict>
		<key>CFBundleTypeExtensions</key>
		<array>
			<string>zip</string>
		</array>
		<key>CFBundleTypeIconFile</key>
		<string>zip.icns</string>
		<key>CFBundleTypeName</key>
		<string>ZIP archive</string>
		<key>CFBundleTypeRole</key>
		<string>Viewer</string>
	</dict>

It seams to work, believe me!

Ok so i want to get my own board up and running but i am a total noob when i comes to this. I have already installed perl,mysql,apache. I also configured apache to use cgi correctly. No all i have is the actual wakaba files but where do i place them and how do i get them into my database? All help would be greatly appreciated. Also would there be any chance of a guide somewhere? Like a detailed setup guide? All i get when i come here is people who have pretty much got their board working but have other questions about tweaking it. Thanks

>>414

http://wakaba.c3.cx/sup/kareha.pl/1141929669/ -> CTRL-F -> "guide"

>>411

HP... this didn't work for me on 10.5 on PPC.

Have you restarted and tried changing all zips to open with The Unarchiver?

I have restarted twice ;)

But, it started to work, for me, before I have to restart… U have to modify info.plist, move your app (perhaps: /Applications -> ~/Desktop -> /Applications), reassociate (contextual menu) … and after, it could work…

At the moment, all my zips have the icon of "The Unarchiver" :)

In my case 10.5 Intel… but, I don't think syntax used in plist have to deal with processor (may be am I wrong?).

>>411

That will break the formats list inside The Unarchiver, though.

>>391
Just a note, I tried this and it didn't work.
Just yesterday I deleted the unarchiver preferences and downloaded a new copy and tried this again.

It works strangely enough.

>>391

Wow, how did I overlook such a simple troubleshooting procedure? This actually worked for me as well. Thanks!

For those who can't get >>391 to work, it's probably because Launch Services won't read Info.plist again unless the app's container directory's timestamp has changed. That's why moving it around or reinstalling might help.

Or more reliably, use the Terminal to run touch "/Applications/The Unarchiver.app".

I just found out about this right now, but it looks like this HMBlkAppKit framework could be great for The Unarchiver, comes with great looking alternating row colors and custom progress bars already.

http://shiira.jp/hmblkappkit/en.html

I just started using The Unarchiver and it is much faster than BOMArchiveHelper.
However, the files I'm extracting are 5+GB, and all I see is' preparing to extract "myfile.zip"', is never says anything like 'Extracting now'. Just when I think it's hung up, the extracted file's folder pops up. Which is great, but I'd like to see something indicating that it's not hung.

Thanks for the fast product.

Ok i love the app and how it opens Stuffit format, its wonderful since i hate stuffit, tho is there anyway that in the next update you could try and add support for .sitx files? as i have a few that i havn't been about to open for a while :-/

Regards, Hardcore

how about a quicklook plugin, like what betterzip has: http://macitbetter.com/BetterZipQL-1.0

>>431
Why re-invent the wheel?
There's already 4 different quicklook plugins that support at least zip.

Besides if Waha doesn't have Leopard yet, I doubt he'll want to code something that he can't even test or even use.

>>430
Check >>79

Are you still working on it? Just came to say great work and that I look forward to 2.0 with password-protected rar support.

Yeah we want some updates, for Leopard and so on

I have some kind of Leopard fix done, but I need to test it a bit more. Should be out "soon".

I have plans for some big changes to make it easier to add new formats and add support for encryption and such, but it'll take a lot of work that I don't have the time to do at the moment. Perhaps sometime towards spring, I will.

So good to heard that... Can't wait to test it :P

So good to heard that... Can't wait to test it :P

THANK YOU !

this "patch" works fine.

Do you plan to put in a file joining feature so that people don't have to boot up Windows to open split RAR files? Otherwise, I find it works well -- Thanks.

It already supports normal multi-part RAR files.

The Unarchiver is a great utilify; but it doesn't unpack my RAR archives locked by a (long) password. It gives me the error: "Could not extract the file "aaa". Command is not supported". Other unarchivers have no difficulty in unpacking the archive. Can something be fixed? That would really be great!

The Unarchiver is a great utilify; but it doesn't unpack my RAR archives locked by a (long) password. It gives me the error: "Could not extract the file "aaa". Command is not supported". Other unarchivers have no difficulty in unpacking the archive. Can something be fixed? That would really be great!

>>442 Look above, he says he's working on encryption support. As of now it cannot handle encrypted archives.

omg. do i have to wait for spring...? hope you'll seed some betas.

btw I noticed you can find some unarchive bundles in Stuffit Expander.app, and are can those used for The Unarchiver? Maybe its needed to unassemble and hacked?

*Can those be used for The unarchiver
sry mistypes.

>>444

It is an interesting idea, but I suspect it wouldn't work. I'll keep it in mind, though.

The Unarchiver is not functioning properly in Leopard. I can't seem to assign The Unarchiver to open up my zipped files. When I use the Get Info window, I have to navigate to find it. (It's not visible along with Stuffit and Archive Utility.) When I assign it to a zip (or other similar) file and then click on Change All.. the window flashes and it says Archive Utility again. Looking for a solution.

>>447
Read this thread more closely.

it would be really awesome if it would check if i have the terminal version af unrar installet and then use that to unrar files. I have a lot of problems with files rar'ed with winrar stalling the unarchiver but runs just fine from the terminal with unrar e <file>

Christian: I suggest using Platypus and the command-line UNRAR to make yourself a fully working application without waiting for the RAR support. That's what I did within a day (with a little bit of bash scripting) and I'm quite happy (still using the Unarchiver for ZIPs etc.).

Finally put out an attempt at a version to fix the Leopard issues:

http://wakaba.c3.cx/releases/mac/TheUnarchiver1.6.1.zip

Nothing else really new in this, except for some higher-res icons. Hopefully it will work better on Leopard now. Any reports of successes of failures appreciated.

Is there any secret for using expanding Diskdoubler files? Here I send a sample, compressed with DiskDoubler 4.1, that The Unarchiver does not seem to support.

Compressed: http://www.box.net/shared/r0guhi1kwc
Expanded: http://www.box.net/shared/6yos1ggw0o

(I manually added the .dd extension to the compressed file, since that DD identified the compressed nature of the files by its icon, not by the filename)

libxad has the start of a DiskDoubler decompressor, but it does not actually work. I know nothing about it, so I can't do much about it. If anyone was to contribute some code for it, I'd be more than happy to add it.

>>449

You can just merge the official unrar source. I can't find a license, but I think it's alright.

Heya,
I encountered weird behaviour with a large (4gig) archive compressed with os x (10.5.1) archive utility. It just wouldn't extract right with the unarchiver and always ended up with some 500 megabyte file instead of the 4 gigabyte original. Archive utility on the other hand could extract it a-ok. First I thought it was an issue with the archive and compressed the file again a few times before I figured out I could try archive utility.

>>456

That doesn't seem incompatible with the LGPL. (but it would be with the GPL, of course)

>>457
I managed to duplicate this with a 2gb file. (An iso in a zip, in case you're wondering)

вы пидоры!

>>458 Waha releases code under the public domain.

>>461

libxad is LGPL in this configuration
(http://theunarchiver.googlecode.com/svn/trunk/libxad/COPYING and some grep -r GPL)

higher res icons ftw!

The ability to unlock password-protected RAR files is a critically needed feature! I'm looking forward to seeing it added. Thanks.

The ability to unlock password-protected RAR files is a critically needed feature! I look forward to seeing it added. Thanks for your work on this!

i too hope i can decompress rar files with password in the near future, other than that the unarchiver is just great!

just wanted to second, the decompressing password-protected rar files. otherwise, it's perfect! thanks.

It's beautifull program, but one problem, how to open 7z parts files?? This files use 001, 002,... extensions

Thanks!

I love it! Simple and beautiful. But I'm a heavy rar user. The unarchiver fails to unlock password-protected rar files!!! The rest of it is just great!

You rock!!! But when is the new version for password-protected RAR files? Really look forward to it!!!!

Fantastic program. But I'd love it even more if all the alert dialogs offered a "Default" button that responded to ENTER and RETURN keys!

Great app. Use as BOMarchiver replacment.

I do have a suggestion.The way now the unarchiver works is that ut unpacks the archive to a default folder. (On my setup thats /temp). It would be great to have modifier key that would activate the unarchiving function while just drag'n'droping the file to the destination folder. just like copy/move but let's that this woud be a new modifier key. For example:

I want to unarchive files.zip from user/downloads/ to user/movies/. I would drag'ndrop the files.zip to user/movies/ while holding cmd+alt. That would start the unarchiving of the files.zip to the destination I wanted.

Hope this makes sense. maybe there is already a way to use this I just don't know the right keys.

have a jice day and thanks again for a great app.
Stan

>>475
Would be neat, but I'm not sure that's possible. You'd have to be reaching pretty deeply into OS Finder's internals for that sort of functionality.

s/OS Finder's/OS X and Finder's/

Hi. I have a problem.
Unarchiver is a great app and i love the "cue" funktion.
But when i cue up a couple of extractions its a little bit of a gamble if it will go throug or not.
I dont know why and i dont see any patern.
Sometimes it works great and it extracts all the things i have cued up.
But most of the time it stops after a couple of extractions.
Anyone that know what can be wrong?

It's been a while since v.1.6.1 was out. Really look forward to the new version with extracting passworded RAR files so that I can throw Stuffit Expander away!!! :P

well thats two of us!

>>482

I guess maybe there is some limit to the path length in tar files, and some extension to handle longer ones? I'll look into it when I have some free time again, which I hope won't be too far from now... But file a bug on the bug tracker too just so I don't forget.

Does that mean the new version is coming out?!!!! That's terrific! Looking forward to it! Hope password protected RAR files can be extracted this time!

this is a fantastic app! but i'll still wait and see what it's gonna have in the next ver.

I use 1.6.1 and it seems to really choke on 7z files, RAM usage goes through the roof. It seems that it actually only does the real choking if I try to cancel, it takes a few minutes or so to actually do the canceling. I tried 7zX and it works fine. Considered using the p7zip file instead of just libxad?

Of course, it could be because 7zip doesn't provide a progress bar and it was working fine, I just didn't see any progress.

>>486

The 7-zip code is pretty horrible. I'm using the slightly more sane 7zC code, but it's sorely lacking in features, and tends to use up tons of memory. I'd like to improve it, but I'm not sure what's possible.

One thing that appears to be missing is decompression of .tar.lzma and raw .lzma archives.

It shouldn't be too hard to add, but does anybody actually use that?

It's used by Wikipedia to compress SQL dumps, it's used by the corp I work for, for a similar reason. It's basically a direct replacement for gzip and bzip2; as a stream compressor you'd be hard pressed to find better.

Personally, I use it to compress my rather extensive book collection, one file at a time. E.g. I'd like to be able to double-click my .txt.lzma or .html.lzma file, get an uncompressed file I can read, then delete the uncompressed file. My 50+ GB book collection slims down to under 10GB with LZMA. I've been using gzip for this previously.

I've downloaded the code and I have the code for the lzmatools package, so I'll give it a shot myself tonight.

> so I'll give it a shot myself tonight.

Don't bother. The guts of the compression code are being heavily re-written right now, and anything you do would just have to be re-done afterwards. (This is because as it is now, it's far too much work to add new formats.)

V 1.6.1 on Leopard reports corrupt file for some .gz archives (single gzipped files actually). I download gzipped log files from my web hosting server and it coughs (unzips part of it and then says file is corrput) on http logs and unzips OK ftp logs (which are smaller files). I presume both log files were zipped using the same utility. Command line gunzip or BOMArchiveHelper.app handle those archives OK. Here is console log:
28/05/08 09:38:27 The Unarchiver[51785] Warning *** -[NSLock lock]: deadlock (<NSLock: 0x14c5f0> '(null)')
28/05/08 09:38:27 The Unarchiver[51785] Warning *** Break on _NSLockError() to debug.
28/05/08 09:38:33 The Unarchiver[51785] Warning *** -[NSLock unlock]: lock (<NSLock: 0x14c5f0> '(null)') unlocked from thread which did not lock it
28/05/08 09:38:33 The Unarchiver[51785] Warning *** Break on _NSLockError() to debug.

>>492

I'll need files before I can do anything about it.

I emailed you the file.

I just tried your program for opening old DiskDoubler files and it would not. I got error message saying "could not open resource fork".

I still have DiskDoubler but am about to wean off OS 9 finally and was looking for something to open the hundreds of old DD files I have in the future.

Thank you

>>495

Apparently the DiskDoubler code in libxad is not finished. If you want support for it, you probably need to bother them about it, or if you can find some code for unpacking them, I can try adding support at some point.

Hey, I really like the interface of the Unarchiver, and also the function of extracting many files with only one double-click! But it's been a while since the version of 1.6.1 came out. I'm wondering when you'll release the next version. Actually, I'm really looking forward to it since I got so many RAR files with those stupid passwords!

That's how it is with software written in one's spare time.

I've been working on some big internal rewrites lately, to make it easier to expand, but when that will be done, nobody knows.

I'd really like to be able to expend password protected stuffit files (.sit and .sea, which The Unarchiver doesn't seem to support at the moment. when opening a password protected stuffit file it just says the file format is corrupted, instead of asking for the password.

I'm a software developer and won't mind coding it in myself, if some one can give me a hint in regard to the mechanism stuffit is using to password protect it's archives.

I'd really like to be able to expend password protected stuffit files (.sit and .sea, which The Unarchiver doesn't seem to support at the moment. when opening a password protected stuffit file it just says the file format is corrupted, instead of asking for the password.

I'm a software developer and won't mind coding it in myself, if some one can give me a hint in regard to the mechanism stuffit is using to password protect it's archives.

As just an end-user I am obviously way out of my depth here, and I see from the posts that the 7Zip code is "pretty horrible", but as a data point - about a quarter of the 7zip files I have been receiving throw an error similar to the image attached and result in zero length output files. For these files the "app" EZ 7z works fine as long as I move the file to my startup drive. I would send a sample archive but they're all over 100+meg.

It wont open password protected 7Z files, please please please fix that!

Er, Just wanted to make a small suggestion. Maybe .sitx files? I am not sure how hard that is but...For some reason Unarchiver chokes on them. Thanks for everything you do!

7z issue... kinda sucks... going to find another app :(

Sorry, I have trouble downloading your program. Could you put the file on google code's download section?

Is Unarchiver still in Development, as there are some important features on the milestone list (eg. password protected .rar) that I am really waiting for.

>>507

Yes, although somewhat slowly.

Unarchiver produces the wrong filename in some cases:
hd93521_032_01_a_ct.fits.gz gets unzipped to
hd93521_032.01_a_ct_fits
while both BOMArchiveHelper.app and gunzip produce
hd93521_032_01_a_ct.fits (as expected from .gz filename)
Thanks for your excellent free apps!

>>509

Sounds like a libxad bug. I'll look into it, but to make sure I remember post it on the bug tracker at http://code.google.com/p/theunarchiver/issues/list.

The Unarchiver failed at untarring Transmission source transmission-1.33.tar (bz2 decompression succeeded, but fails with untar. CUI version works.) Project page at: http://www.transmissionbt.com/

(By CUI version, I meant typing tar xf at Terminal and not related to The Unarchiver)

>>162

7-zip support seems to be poor? I'm trying to open a 640mb .7z file and it at first it took several minutes to get going and then finally error'd out with a "corruption" error. But tossing it into a window box opened it less than 10 seconds.

Any chances of fixing the issues The Unarchiver is causing for users who try to decompress the PwnageTool for iPhone from http://blog.iphone-dev.org/? They're specifically asking people not to use this application now since it breaks the .tbz files..?

Any progress on a DiskDoubler answer since June? I'm getting same message... have a big pitch coming up and need relevant files from CD dating back to '93!

>>515

No, sorry. I don't know anything about the DiskDoubler format so I'd need someone else to help out with that.

Hi. Unarchiver looks great and I want to ditch Stuffit Exapander but one thing is keeping from doing so. I really need the "always create surrounding folder" option that stuffit has. The newly created folder should have the same name as the archive.

I think you've mentioned adding this feature that people have requested in the past. I really need the "Always create surrounding folder" option for my workflow. The newly created folder should have the same name as the archive. I really want to switch over to Unarchiver and this is the only thing keeping me from doing so.

This software is having issues with a 7zip multipart 4gb archive.

ie:
7z.001
7z.002
7z.003
7z.004

The archive contains 3 files, one of which is a "gi" file - which is a multipart (split) iso file.

On attempting to decompress, unarchiver errors with:
"Could not extract the file "asdf.gi": Unkown data format"

Using 7zip from terminal unzips the files wonderfully.

Questions:
is unarchiver claiming it doesn't like the gi file or the 7z archive?
Is it trying to patch together the gi file?
Does unarchiver detect split files and attempt to join them?
Does unarchiver unzip/join recursively? If so, how to disable that?

Will not open DiskDoubler files on Leopard OS despite it being check-marked and setting it as the default app to open DD files.I do get a message about being unable to open the resource fork or unknown data format. Is this a known issue, or is there anything else to do to make it work other than check-marking it?

>>523

libxad's support for DiskDoubler is not complete, and will likely not work. I don't know anything about DiskDoubler and can't do much about it.

Just a few small annoyances I noticed with The Unarchiver which I would like to fix if I knew how to program (couldn't figure how to build The Unarchiver project in Xcode after I was able to build libxad):

1. The character encoding chooser dialog box. For example, if The Unarchiver had trouble in decompressing 100 files in an archive for character encoding reasons, it'll ask me 100 times with a dialog box pop up. Instead of having to change selection in the pulldown menu from "Arabic" every time (apparently first in alphabetical order), like Finder, I would prefer an "Apply to all" checkbox in the dialog which I could check when I'm sure what the encoding is for all the file names. 100 selections isn't an option for me: I went and used Windows instead.
2. I got asked for the encoding on a 7-Zip archive. Isn't 7-Zip filenames always Unicode?
3. RAR archives. I noticed that for some RAR archives, it would silently fail after decompressing only some of the files. At first I didn't notice this and thought it had succeeded in decompressing everything.

>>525

The character encoding chooser shouldn't appear more than once. If it does, that's a bug, or you've got some very strange broken filenames.

I forget how the encoding issues work with 7-Zip. Give me some problematic archives and I'll look into it. Same with the RAR ones. I can't do anything without test cases.

Hi - I have a .zip that is stuck unarchiving. For over 24 hours.
I can't quit or stop it. can't trash it.
It is in a little window that says "Archive Utility".
Neither Finder nor Spotlight locate anything
called 'AYU".
The enclosing folder is BOMAsomething but again, I can't find any such app or utility with that name.

Closing everything and restarting does not work.Removing battery does not work.

Any ideas?

Many thanks!

>>527

I'm sorry, I have no idea what you're talking about.

hi.
527 must be high.
anyway, the unarchiver is great but it still fails to extract some password protected files like the one on the link.

http://rapidshare.com/files/55338135/rcx_ByMechoDownload.rar
pass: mechodownload

sorry, i just saw this: The RAR and 7-Zip modules do not support encryption at all.
is this the reason?

>>531

Yes. I'm working on some rewriting of the code to make it easier to support this in the future.

thanks for the quick reply. i'll check once in a while.
btw, just for the sake of it, The Unarchiver works really good and it's the only app that extracted well those awesome japanese shmups from http://www.vector.co.jp/

thanks for writting good software.

sorry to bother again.
found another one who returns an error on unzipping some files within the zip folder.

it's mplayer for mac and it's a regular zip. Built-in Archive Helper, Stuffit plugin on Path Finder and BetterZip unzip it fine. If you waanna test it it is is:

http://mplayerosx.sourceforge.net/

best regards.

>>534

All right, I'll have a look at that (it's probably caused by another known bug). However, you might want to download http://mplayerosx.sttz.ch/ instead, the one you linked has been abandoned for years.

i actually use the one at http://www.mplayerhq.hu/design7/dload.html which is more stable than the one on the link i provided but thanks for your tip!
didn't know about this extended version. gonna try it.
thanks again.

I'm not sure if this is a Leopard bug or a TheUnarchiver bug, so if you can't do anything about it, please let me know and I'll stop being grumpy. :)

I decided to make TheUnarchiver take the place of StuffitExpander and Archive Utility, so I started to do a Get Info on a number of different formats to associate them with TheUnarchiver, and to click on "change all". This works fine with Zip. It shows a nice little cardboard box icon labeled "zip", which I assume you made.

It does not, however, work for Sit. (This is plain .sit, not .sitx.) Instead, when you change it to TheUnarchiver, it shows a nice little cardboard box icon labeled "sit". Well and good, right? Not! As soon as I hit "change all", the icon changes to a generic document. Very strange. Is this on your end or on mine? Is there anything that can be done about it? Thanks for your time.

>>537

That sounds like a problem with the really quite buggy and strange LaunchServices in OS X. You might be able to fix it on your end, but how I do not know.

Is there anyone that has an updated version of Disk Doubler or (other program) that will open up DD files that works on a Mac 10.5 (leopard) system?

Thanks
Tim

>>539

I have been working on getting DiskDoubler working lately, actually, but I lack test files. If you have some you want opened, could you send some to me for testing with?

I've been using The Unarchiver for quite awhile, and I love the minimalist approach to the program. I do have one issue that's not really a functionality problem, but still irritating. Whenever I extract an archive, the progress bar races ahead to full, then just sits there while it actually is being extracted. I know it's minor, but I actually like being able to keep an eye on how the progress is going. It could be an issue with my laptop too, I'm not sure

>>541

Sounds like you're only unpacking some specific kind of broken archives. Could you send me a file that does this?

me again.

any chance the unarchiver will ever support PP files (Amiga PowerPack files)?
Amiga had the best compression routines ever, I remember long-play games like Chaos Engine by the Bitmap Bros fitting in a 700kb floppy disk.

If you're interested I can supply you a couple of PowerPack files.

>>543

Well, as an oldtime Amiga user, that idea really is a bit tempting. Although PowerPacker was more of an executable packer and not an archiver, wasn't it?

Feel free to mail me some files, though. I'll definitely look into it at some point.

yes, you're right. powerpacker was actually a cruncher, not an archiver. it was used to crunch single files with a high compression ratio. when crunching a file you could set it as "command file" which made the file executable (it included a 500b header in the file to automatically uncompress it when executed) or as "data file" which you could decrunch later with powerpacker.
more info on the manual on the link below.

i still own a working amiga 500 with zillions of floppies but because of lack of time i have it archived in the garage and use E-UAE and Hi-Toro on my mac for emulation.
still brings a tear to mye eye for all the good times. best computer ever. did more than a pc with 7mhz and 512kb/1mb ram. and yes, it had multitasking, a desktop and window environment before the pc "invented it".

here's some resources you might find useful if you haven't them already. nevertheless is up to you to decide it's worth to implement it on The Unarchiver or not.
i have to call this bro to email me some pp files he has on his amiga1200. i'll send them to you just in case when i have them.
one of the links has a PP file too.

regards.

A VIEW ON POWERPACKER
http://www.atarimagazines.com/compute/issue123/P156_1_DOWNLOAD_FIGHT_CODE_BLOAT_WITH_POWER_PACKER.php

USEFUL AMIGA RESOURCES ON ARCHIVERS, PACKERS AND CRUNCHERS
http://www.amiga-stuff.com/index.html

POWERPACKER DECRUNCHER MAKEFILES FOR AMIGAOS4 AND UNIX (INCLUDES PP FILE)
http://www.os4depot.net/index.php?function=showfile&file=utility/archive/ppunpack.lha

POWERPACKER MANUAL
http://www.amiga-stuff.com/text/crunchers/PowerPacker2.1a.txt

any tips on how to compile the svn source?
XYDMaster and UniversalDetector build without a hitch but The Unarchiver keeps giving me this:
/Users/phil/devstuff/theunarchiver/The Unarchiver/TUController.m:1:48: error: UniversalDetector/UniversalDetector.h: No such file or directory
i've tried adding the frameworks to the xcode project and ~/Library/Frameworks but no dice...
any ideas?
cheers
phil

>>546

First of all, trunk is pretty much guaranteed to not build and work fully. It's being worked on pretty heavily. If that's from 1.6.1, though, I don't really have any clue either.

ok, thanks. in that case i'll just keep on trying:-)
great app btw

Feature request: always expand into a folder with the same name as the archive, unless it was already going to do that. Otherwise expanded folders tend to get lost when they're in archives I get from Share and are called "nekomimi".

Well, I'm worried if the app is still under depelopment. Already discintinued, or slowly going further?

>>550

Didn't have time to work on it for a while, but back on track now. Expect a new version sometime early next year.

has problems when queuing multiple archives for extraction (5+) it suddenly exits after unpack is done of one of the archives, or maybe the second, etc.

>>552

See if you can find some set of files that does this every time you try it, and send the files to me.

1.6.1 on G4 DP 1Ghz. OS 10.4.11, GeForce4 MX

After "select all", when using "deselect all" doesn't work for many types.
Tried prefs. Doesn't work.

What would be the way to uninstall?
What would be the way to deassociate all these "hung" types?

zip, rar, LhA, sit, BinHex, MacBinary, Gzip, Gzip tar, Bzip2, Bzip2 tar, Tar, Unix, Unix tar, Amiga Disk, Compressed Amiga Disk, Amiga DMS

>>555

That's really an OS X bug. If you have another program that you want to handle them, just set it manually through the Finder. If not, what's the problem?

So here's a curious thing. I had the bizarre Launch Services behavior others mention, whereby when you switch a file to open with The Unarchiver it shows the right document icon until you press "Open All With" - at which time they all go blank. This happens for me with tar.bz2 files but not with zip files, which are fine.

So I tried all manner of things. In the end I zapped Launch Services:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

I sent the two files relating to Launch Services in /Library/Caches to the Trash. I sent the plist to the Trash. I rebooted and emptied the Trash. (I also removed The Unarchiver and its plist and reinstalled it.)

Now here's the curious thing. That completely reset Launch Services. For example, if I click on a text document it no longer opens in TextMate but in TextEdit. Nevertheless, the system (or Finder?) seems to "know" about TextMate - it's there as an alternative if I right-click and choose "Open With". But the system (or Finder?) doesn't seem to know about The Unarchiver: it's no longer even there as an alternative if I right-click on a .tar.bz2 file and look at the "Open With" option. But it does know about The Unarchiver when it comes to .zip files, since The Unarchiver is there as an alternative on the right-click menu for those.

It seems like it might be significant that the file-type Finder won't show the icon for is the same one that doesn't appear on the right-click menu till I explicitly make the path to the program. I've seen exactly that behavior before, too. Wish Apple would fix Launch Services.

>>558

You can mail them to [email protected], or if there's a lot of them just mail and we'll arrange something. It would really help to have some decent test cases.

Are you planning to add support for password protected rar archives? Would be really great!

Please do implement support for passworded multi-part rars.

Man, I can just tell the donations will come rolling in once I add support for password-protected RARs.

Every now and then when I download a file a -1 is added, for example. Abcd.dmg-1 and the file will not mount, even if I delete the -1. I am using an iMac Intel and OS 10.5.6

>>564
that's probably a bug in whatever you're using to download the file.

I've just learned of this program, and wondering how I survived without it. Many thanks and good work.

I'll donate $5 if you add support for password-protected RARs.

I’d love to see The Unarchiver include an Automator action. Right now I can invoke The Unarchiver on a set of Finder Items in Automator, but I must follow it with a Pause action to allow enough time for the extraction to complete. If The Unarchiver offered an Automator action of its own, Automator would automatically wait while the extraction process took place.

feature request: show all possible encodings if the detection fails. now if the zip contains Shift-Jis encoded filenames the app tends not to show it in the dropdown list. it shows a list of encodings without it. even if I'm pretty sure that the encoding is Shift-Jis I can't select it

On Leopard, The Unarchiver appears not to be optimized: when extracting large archives, the cpu usage of both cores is really low. I was wondering if it could be optimized to be faster by using the available resources ? Both CPU and RAM, which is 4GB in my system.

Thank you

>>570
That's not a task that's inherently CPU-bound. Most of the time spent is going to be in disk read/write operations.

If people are still looking for an old OS 9 version of DiskDoubler that works (like I have been for years), I finally found one on an old CD-ROM and I've posted it for others to download.

Here: http://www.enews.org/blog/2009/03/opening-diskdoubler-files-from-mac-os-9.html

Whenever I make a mistake and try to unarchive a file that has not finished downloading, , OR unArchiver tries a .rar file it cannot extract (although StuffitExpander HAS been able to extract these except for one out of about 12 failures in about 400 unrars over many months)... the application freezes showing a "Preparing to extract..." . Activity Monitor shows about 16% of INTEL 2coreDuo used. Other people have said they 'forced quit'.
My Force Quit under Apple menu will not display the program so it must indeed be integrated into the OS. So they must mean pressing a ForceShutDown button.
The window currently with this problem is a stack of pending operations, with a partly downloaded one mistakenly included.
It has not hung the download, which is still progressing using AZUREUS in OS 10.4.11.
Is there any way I can change the Queue order, or Force the integration to let go of my system without stopping all work and restarting?

I noticed it doesn't extract some Windows installers that unshield (http://www.freshports.org/archivers/unshield/) / Universal Extractor (http://legroom.net/software/uniextract) can handle. Is there anywhere to stick samples for this kind of thing?

im using latest leopard. whenever i try and add three files to the queue, it breaks. the first two unrar and the third, it just closes, crashes if you will and no message or error is reported.

also, please support password protected rar files please.

I love this little app. Can be much better though. plz. thank you.

>>575

There's a bug for better CAB support, stuff them in there. Also, write some code for it, the new version makes it pretty easy.

Thankyou!.. Love it on my new mac. Much appreciated... :D

How to uninstall The Unarchiver? I don't know how to uninstall The Unarchiver because it still works even if I move it out of the Application directory. But I found cx.c3.theunarchiver.plist in Users>user>Library>Preferences.

Potential 0 day security risk - if you have checked "open the extracted folder" it will open the item automatically if the extracted thing is a Package.

This happened when a friend sent me settings for Boxer which stores its games/settings as packages. It caused Boxer to open and automatically launch the game.

There's some shiny new alphas on the google code repo - any clues as to what's changed?

>>585

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

>> 581

The Unarchiver is uninstalled in the same manner as most OS X applications: by dragging the application to the Trash. Optionally, you can delete the plist file, but leaving it in ~/Library/Preferences will not slow your computer down, unlike what happens with the Windows registry.

Any progress so far, is Unarchiver still in active development?

>>588

As already mentioned, http://wakaba.c3.cx/sup/kareha.pl/1242691148/

Gotta say - the 2.0beta3 version works extremely well (MacIntel 10.5.7). Noticeably faster than before, handles RAR decryption rapidly and has a few tweaks like responding to [Enter] key for default responses. Haven't tried massive archives or other decryption types yet.

Any chance of the app being 64-bit anytime soon?

>>591

It's planned to make the library properly 64-bit, at least, but I'm not sure if there's any real gain in making The Unarchiver itself 64-bit at this point.

Good to hear. :)

Just bought myself a new MBP and am testing Snow Leopard so all the possibilities with all the new 64-bit apps and the new technologies in SL are very exciting.

Something about this dialog box is not right.

>>594

Yes, it's not dialog box from The Unarchiver?

>>595
It's a dialog box from The Unarchiver. Kanji is most likely not Mac OS Roman characters.

>>596

It is not. I don't know what it is from, but it certainly isn't The Unarchiver.

>>596

Those specific kanji are not something you want to be unarchiving anyway. Let it sleep in peace.

All right, 2.0 is finally done and released!

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

The homepage has also been cleaned up somewhat, along with the rest of the site:

http://wakaba.c3.cx/s/apps/unarchiver.html

The change list is something close to this:

• Support for many new formats and algorithms:

  • Partial support for SITX archives. Most archives should open fine, but SITX's special JPEG compression is unsupported. (If you are a programmer and want to help out with getting this working, I'd be happy to hear from you!) Some preprocessing filters are also unsupported.
  • Other new formats: XAR, ALZip, LZMA-utils, Compact Pro, PackIt, ARJ
  • Encrypted RAR archives.
  • WinZip-style encrypted Zip files using AES.
  • Can decompile NSIS installers to get the files inside. This seems to work for versions all the way back to 1.1o or so, but a lot of guessing is involved so it might fail on some files.
  • More compression types in Zip: Deflate64, bzip2, PPMd, LZMA.
  • More compression types in DiskDoubler (but still not all).
  • Better handling of 7-zip, RAR, LZH, tar and RPM files.
  • Extracting files from several emulation formats, such as NDS and ADF.
  • Bugfixes and streamlining for the user interface.
• Option for when to create folders for extracted files.
• Option for how to set the date of extracted folders.

Great. Thank you.

Fantastic! So glad to see support for encrypted RARs!

Can we have an option of Never create a new folder for extracted files?
Thanks!

>>602

Probably not, it would require me to create all kinds of code to handle file collisions gracefully and I am too lazy for that.

big thank you to the developer, now i can finally move away unrarx. this is simply the best app for extracting files now

>>597
You are right. It was from Simple Comic. My bad, got the two confused.

>>606

Any window that does not have a dock icon will act that way. There seems to be no way around it. It tries to jump to front if it needs your attention.

Great work, finally 2.0 can handle passwort protected RARs!
But unfortunately the window always gets itself behind automatically before I can enter the passwort, that is very annoying and it also takes 3-4times longer than with other app such as Betterzip, so maybe you can improve the speed as well.

Great work, finally 2.0 can handle passwort protected RARs!
But unfortunately the window always gets itself behind automatically before I can enter the passwort, that is very annoying and it also takes 3-4times longer than with other app such as Betterzip, so maybe you can improve the speed as well.

Great work, finally 2.0 can handle passwort protected RARs!
But unfortunately the window always gets itself behind automatically before I can enter the passwort, that is very annoying and decompressing also takes 3-4 times longer than with other apps such as Betterzip, so maybe you can improve the speed as well.

I'm having an issue with The Unarchiver 2.0 regarding extraction of encrypted multi-part RARs. They extract fine, but take way too long to do so. I am doing this a lot lately, so it's not just one multi-part RAR that's having trouble, it's every one I try.

I'll give you an example... a recent mutli-part RAR I extracted using The Unarchiver 2.0 took about 3 hours to do. The same multi-part RAR extracted using UnRarX in less than 20 minutes.

Not sure what's going on here, or what I can specifically provide to help. I would love The Unarchiver to by my sole utility for extracting compressed files, but with this problem it's honestly unusable to me for this purpose.

Version 2.0.1 released:

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

This is a minor bugfix release.

• Should now handle concaternated bzip2 files.
• Fixes to the Japanese translation.
• Fixes to the LZMA parser.

>>608.611

Looking into the speed issues.

Have you considered something like Sparkle autoupdates for The Unarchiver?

I would love to see Sparkle added for Auto Updates for sure

64 Bit for Snow Leopard Would be nice too,

http://developer.apple.com/MacOsX/64bit.html

>>616

The library will be updated to support 64 bit at some point soon, so it can be used properly by other apps, but I'm not sure if there's any real need for the app itself to be 64 bit.

Version 2.0.2 released:

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

This is another minor bugfix release.

• The RAR speed issues mentioned above should be much better now.
• Fixed some issues with resource forks in .tar.gz and .tar.bz2 files.

How does the unarchiver handle files while decompressing? I was uncompressing a large 4 GB multi segment RAR when my computer froze and I had to restart it. Now I think I lost a bit of space on my hard drive but I can't find the file(s).

>>620

They are written to a hidden (starting with a dot) directory in the same place the unarchived files will be while unpacking. 2.0 should keep track of directories it has created, and will delete them the next time you start it if it crashed midway. 1.6.1 does not do that, and you have to remove it manually.

WOW! Thanks for the update fixing the RAR extraction speed... it's now even faster than UnRarX! Now The Unarchiver can serve all my purposes!

Hi, Unarchiver seems to try to auto extract every rar file as soon as its downloaded, is there a way to stop it doing this?

>>623

That's your web browser's doing.

I quickly skimmed through the last fifty or so posts and didn't see any mention of this so I hope I'm not reposting:

When I try to open a large number of compressed files all in one go, it seems only four or five of which will actually be queued for extraction in the unarchiver.

>>625

That's strange. If you can file a bug at http://code.google.com/p/theunarchiver/issues/list with a bit more information I'll definitely look into it.

Isn't there a way to stop the app from creating a folder when extracting?

No.

Version 2.0.3 released:

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

More bugfixes and speedups, for RAR again. This format is quite a chore.

>>629
Thanks for the hard work, Waha.
RAR is a bitch, but its still insanely popular for some reason.

2.0.3 is giving me "Error on decrunching" while extracting multi-part RAR on Snow Leopard. Has anyone else had this error?

>>632

Post files that have the error, or I can't fix it.

>>633

Well ummm I don't think it would be good idea since it's an episode from a TV show and it weighs in at ~200Mb.

>>634

Well, then it will remain broken.

2.0.3 is giving me "Error on decrunching" while extracting rar files password.

>>636

Read above.

Here's a file that's giving me "Error on decrunching" on 10.6.1, Unarchiver version is 2.0.3.

http://rs535tg2.rapidshare.com/files/209615230/MI1.rar

Password is:

hostel

>>638

That's more like it, thanks!

>>638

Also, bug found and fixed.

Is there a way to prevent 'The Unarchiver' from taking focus when it opens? I have it decompressing my downloads, and whenever a download completes it comes to the front and I lose whatever I was typing.

I would ditto post 641. It would be preferrable to see the unarchiver appear in the dock and then dissapear when it is done decompressing. A dock icon badge that shows the status of the unzip would be nice although not essential.

Unarchiver needs to stop popping into the foreground.

>>641-642

Then others will complain that it is hiding behind their other apps and they can't find it.

Sorry, I think I wasn't detailed enough in my first question/request. I didn't mean to say it should pop up in the background necessarily, but that it should respect normal focus rules and not automatically take focus. As it is I'm have it launched from the 'command line' (launchd) to handle downloaded archives using the command 'open -a 'The Unarchiver' --background <downloaded file>' and it still takes focus when it extracts archives. So, I will renew my plea a final time, could we at least consider a preference?

Regardless, thank you for your fantastic app. Since I found it I've never looked back.

Sorry again, 'As it is I'm having it' or 'As it is I have it'!

>>640

so, uh... about this fix..??

>>644

Apps without a dock icon do not follow normal focus rules in the first place, is the main problem. I have to take focus, or else The Unarchiver might open up underneath other apps.

>>647

Ah yes, of course, that makes sense. Didn't occur to me at all. Sorry to harangue you about this, but why doesn't The Unarchiver have a presence in the dock? I'm sure there's a good reason, but it's not clear to me at the moment.

>>648

Mostly to make it act like the original BOMArchiveHelper, which didn't have one either. But apparently newer versions do have an icon, so I'm not really sure if it should stay this way. However, some people seem to like it not having an icon.

I always get an error on decrunching for all large multi part Rars, I have 47 part Rar (.rar - r45) with all parts being 50 MB except the last which is 48.2 MB
It seems that if there is more than a certain number of parts it doesn't work, I know 24 50 MB parts work fine
So somewhere in between there it breaks

>>650

Once again, without the files, I can't do a thing about it.

>>649

That makes sense, thanks for putting up with the grilling. My vote, of course, is for the app to mimic the newer versions of BOMArchiveHelper. Thanks again for this plucky little app.

Hi it would be really helpful if when unarchiving multi-RAR files that when you get a corruption error that it is specific explaining which part is corrupt.

Thanks

Version 2.1 has been released:

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

• Added a service for unarchiving files via the the Services menu, or when right-clicking files.
• Some interface tweaks (File menu now works in the preferences window, doesn't ask for destination directories for every archive, archives are not added to the queue twice).
• Proper quarantine propagation for downloaded files.
• Better support for very large Zip and 7-zip files.
• More RAR bugfixes.
• For programmers: The XADMaster library can now be compiled in 64 bit mode, but the The Unarchiver app itself is still only 32 bit.

Hello.
I would like to suggest feature for zip archive file.
Windows Winzip or other Unicode support zip application try to reserve maximum compatibility with legacy zip archive file.
So when Winzip make archive file in particular locale windows, it use specific codepage filename and Unicode same time. If filename can be encoded into windows related codepage( such as CP949 CP936...), it use these codepage.
But if filename can't be converted into local codepage, Winzip use Unicode filename.

As a result, archive file has local codepage filename and Unicode filename in UTF-8.
Fortunately, when Unicode filename is used, 11th bit of general purpose bit flag is set.
We can classify these two different encoding.

Currently in The Unarchiver, it might not aware of this difference. So when I designated specific filename encoding, it will try to extract only one encoding which I gave.

So I would like you to add feature that recognize zip format's 11th bit of general purpose flag. You can found these info. on PKWARE's AppNote.

http://www.pkware.com/documents/casestudies/APPNOTE.TXT

Sincerely
trip2me