-
This has happened to me too.
I'll try to come up with a patch. Seems the UnrarX developer has left the boat...
2009-10-26 23:36:24 UTC by onitake
-
I see the exactly same behavior.
In case I find time, I'll make a patch.
2009-10-26 23:34:55 UTC by onitake
-
im running snow leopard 10.6.1 and 2.2 UnRarX. it works great consistently. only problem ive had is this:
in the UnRarX application, there is an apple grey part of the UnrarX window and, below that, a white part of the window. the white part is where i can read output showing me the results and status of the operation. when i highlight a group of rar's and then click them or drag them into...
2009-10-15 17:49:35 UTC by https://www.google.com/accounts
-
When the names of compressed files in a .rar contain Unicode characters, unrar will output them as UTF-8, which is correct behaviour on Mac OS X.
UnRarX on the other hand doesn't interpret that output correctly and will just display garbled Mac Roman.
This doesn't affect functionality, but it would be nice if the text field could use UTF-8 instead.
2009-07-23 10:17:20 UTC by nobody
-
Hello! If i recieve a rar file wihich is passwordprotectet and the sender has been using æøå in his password then i cannot unrar it on mac and have to use a pc. Can this be solved?
Best regards
Lars Petersen.
2009-04-09 13:35:35 UTC by nobody
-
Hello, I have a MacBook Pro 2.4 Core 2 Duo with 2GB 667 DD2 SDRAM and I am running Mac OS X 10.5.2 and using UnRarX 2.2.
I find it kinda slow for this processor and system when it unrars files of 2GB or 4GB in size.
Thanks, I hope this helps.
Ryan
Toronto, Ontario.
2008-03-09 21:54:27 UTC by nobody
-
hello,
When the "Overwrite Existing Files" preference is UN-checked, and the
application finds an existing file when attempting to UNRAR, the GUI goes
into a loop where it displayes options of what to do, but it continually
repeats them, and keyboard input has no effect.
This is on 10.4.8, all updates applied, dual-proc G4.
In conjunction, the need for this would be greatly...
2006-10-15 15:49:42 UTC by nobody
-
Logged In: YES
user_id=189212
Well, two mistakes with this. First, need to change fseek to fseeko in all three
places that it is used in diskfile.cpp, since fseek takes a 32-bit long.
Second, I think I was wrong about the change to LengthType and MaxLength.
I'm pretty sure only OffsetType and MaxOffset need to change.
After making those fixes, I have verified that it can, in fact...
2006-10-04 06:49:23 UTC by dgatwood
-
Logged In: YES
user_id=189212
I've fixed the bug. It's a bug in the par2 tool. In the file diskfile.cpp, after the
"#else // !WIN32", change the four #define statements to the following four
lines:
#define OffsetType off_t
#define MaxOffset (sizeof(off_t) == 8 ? 0x7fffffffffffffffLL : 0x7fffffffL)
#define LengthType fpos_t
#define MaxLength (sizeof(fpos_t) == 8 ?...
2006-10-04 03:55:18 UTC by dgatwood
-
It appears UnRarX falls over dead if a file is over two gigs or so in size
with the error message
File size for /path/to/file.rar is too large. Target: "file.rar" - missing.
What's up with that!?!
2006-10-03 02:12:05 UTC by nobody
