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:
For actual information on the current state of this project, read on!
>>910
I have tried TheUnarchiver2.7 on PPC G3 and G4 running 10.4.11
Every time TheUnarchiver2.7 will start to unarchive a file, but it never finishes and I need to force quit it.
SHA1 is correct.
Console log:
2011-04-17 10:36:35.561 The Unarchiver[760] *** -[NSFileManager contentsOfDirectoryAtPath:error:]: selector not recognized [self = 0x507c00]
2011-04-17 10:36:35.562 The Unarchiver[760] *** NSThread: ignoring exception '*** -[NSFileManager contentsOfDirectoryAtPath:error:]: selector not recognized [self = 0x507c00]' that raised during delayed perform of target 0x596290 and selector 'extractFinished'
No problem with TheUnarchiver2.6
Any suggestions?
I have exactly the same proble as >>910. So far have attempted to unarchive two fairly large archives (over 300MB), and when it gets to the part where it has to make the tempfolder visible, set the permissions, whatever, it hangs, leaving the Unarchiver window open and permanently present (the X won't kill it). It does get far enough so the progress bar becomes steady Aqua (not pulsating), But I have to go to the Activity Monitor to kill it, and, of course, this leaves invisible and sometimes hard to find GIANT folders behind. It appears to do a good job of unpacking, but only an experienced user will be able to find the files and quit the program window.
I'm not certain if other file tasks are being completed, since the archives I used consisted of multi-thousands of small documents (txt, png, jpg, cvx, eps, ai, etc.). After moving the invisible folders to the desktop and making them visible, they look fine, and taking a random sampling, they all open without any sign of corruption... but with this many files, I have no idea if any were skipped, corrupted, or if naming and permissions were done correctly.
Another note, once it has been force quit, I cannot get it to relaunch properly until I reboot. If an attempt is made to open an archive that is supported, nothing happens. So force quitting IS NOT a valid method of terminating the program.