Comments on: New! :: 7zX 1.5.3

By: Taskman

Taskman — Mon, 22 Jan 2007 09:24:30 +0000

Out of curiousity, what are you trying to compress exactly?

By: Fred

Fred — Sun, 21 Jan 2007 07:18:27 +0000

Uncompresses OK most of the time, but it really needs work for compressing.
The same file compressed on win is much smaller than when compressed on OS X with this app.
It’s a good start, and I would like to see it evolve!

By: OddyOh

OddyOh — Thu, 21 Dec 2006 22:48:30 +0000

Yeah, 7zX still works fine. I just found it odd because I couldn’t recall ever having SafariBlock installed. However, I did some digging and sure enough, I had uninstalled SafariBlock, but it’s ‘inputmanagers’ were still hanging around…cleaned those out, no more errors!

Thanks for the quick response, and agreed, it’s not even your issue! In fact, good on you for even outputting the error in the first place instead of “unknown error occured, etc”.

By: Taskman

Taskman — Thu, 21 Dec 2006 17:48:25 +0000

As you said, there appears to be a conflict with SafariBlock.
To answer your next question, it’s not our fault.

I’m pretty much sure it won’t affect regular 7zX operation.

By: OddyOh

OddyOh — Wed, 20 Dec 2006 16:02:44 +0000

Anyone seen this error? Looks like a conflict with “SafariBLock”, but that’s all I know:

“2006-12-20 09:55:18.642 CocoaDialog[18813] *** -[NSBundle load]: Error loading code /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock for bundle /Library/InputManagers/SafariBlock/SafariBlock.bundle, error code 2 (link edit error code 0, error number 0 ())”

I see this error when I try to unzip a “.7z” file. The growl notifications seem to work though. Thanks in advance.

By: Taskman

Taskman — Mon, 18 Dec 2006 10:01:11 +0000

I doubt that could ever happen. Out of curiosity, however, would you tell me what format you used to compress that folder?

By: Jason Titus

Jason Titus — Sun, 17 Dec 2006 23:17:26 +0000

I’m having a VERY bad bug with 7zx. I created a few archives of folders and everything seemed fine. After tossing a couple of the original files, I thought I wanted to verify things… When I expanded the archives, certain subdirectories weren’t there! Sometimes half of the data was gone, sometimes less.

Has anyone else seen this? This is with 1.5.3 on a Mac Pro running Mac OS X 10.4.8.

By: Taskman

Taskman — Wed, 13 Dec 2006 12:19:34 +0000

Please consider documenting yourself before making such statements. s7z, first introduced with 7zX 1.1 (Feb 2, 2006), is a slight variation of the original 7-Zip format which we developed with the sole purpose of preserving Macintosh resource forks, Spotlight metadata and some other informations which would be otherwise lost while creating regular 7z archives. More informations regarding this format will be made available at a later date, i.e. after the release of version 1.6. I would like to point out that 7zX is also capable of creating standard 7z archives: just deselect the "Preserve Macintosh resource forks" checkbox at the compression options prompt. Remember, however, that this means there will be a potential lose of informations (you could also corrupt certain files if you don't know what you are doing).

By: Leo Kuznetsov

Leo Kuznetsov — Mon, 11 Dec 2006 20:03:02 +0000

why s7z is not compatible with 7z archives?! This is totally against the open source spirit. If I try to use the command line 7za on Mac OSX to extract from s7z I get the [Content] file instead of the original file and it is not what I put into archive. This is actually the abuse. You are trying to use Igor Pavlov’s work to *compete* with him himself. Shame. Please consider changing extension and type back to .7z and staying compatible with the archive format. Thanks

By: Taskman

Taskman — Sun, 03 Dec 2006 15:21:14 +0000

Keep following the development of 7zX, improvements are costantly added.