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!

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.