Bug: Multipart .rar files are seriously mishandled

[Black Dog]

[face=courier]On 31-05-2004 16:52:58 +0000 Loren Pechtel wrote:

LP> I don't see how silently doing something other than what
LP> the user would expect can be considered anything other
LP> than a bug.

Well, who is that "the user"? Some quintessention of user idea, may be? :)
Actually the situation is very simple - Christian, as author of Commander, decides how it should work. So if you don't like the way Commander works, send an e-mail to Christian support with your ideas. Or you just want to say "a bug" as more time as possible? %) This is absolutely useless, actually, 'cause as I told you - Christian do not consider that present day multi-volume RAR archives situation is a bug.[/face]

[Randy]

[face=courier]Just to be clear, I never said that .001 was the standard by which multi-part .rar files are named but I have encountered multi-part .rar files that were named that way by whomever made the compression.

I personally don't understand Christian's logic behind the handling of multi-part .rar files myself but I think this is a problem faced by any program that tries to "do it all"; it creates the expectation that it should actually "do it all" and when it fails to behave how a user expects (regardless of the designer's intent) then they call it a bug because, well, the program isn't "doing it all".

Just a useless and unnecessary opinion.[/face]

[ghisler(Author)]

Multi-volume unrar is a problem because of the used unrar.dll. Only files starting in the current volume can be handled correctly with unrar.dll, therefore unpacking all parts has to be done with external unrar, as it is solved now.

[Loren Pechtel]

Multi-volume unrar is a problem because of the used unrar.dll. Only files starting in the current volume can be handled correctly with unrar.dll, therefore unpacking all parts has to be done with external unrar, as it is solved now.

Then put a warning in there, please!

As a user, you expect something to either work or not work. When it sort of works but silently doesn't do the whole job you lead the user badly astray.


P.S. Thinking about it, the configuration option is use internal unrar if possible. It seems to me that multi-part is a case where the internal isn't possible.

[Black Dog]

[face=courier]On 31-05-2004 20:53:06 +0000 ghisler(Author) wrote:

g> Multi-volume unrar is a problem because of the used
g> unrar.dll. Only files starting in the current volume can
g> be handled correctly with unrar.dll, therefore unpacking
g> all parts has to be done with external unrar, as it is
g> solved now.

Well, I send a letter to Eugene with quotation of your post and ask him is it how the things really are. And this is his answer:

Eugene Roshal:

"No. I just have checked it one more time: compile
UnRDLL.c from unrardll.exe distributive, add unrar.dll
from the same distributive to it and unpack multi-volume
RAR archive successfully using them.

BTW, WinAce and PowerArchiver use the same unrar.dll too
but I never heard about any multi-volume RAR archives
unpacking problems these archivers ever have had."[/face]

[Loren Pechtel]

Well, I send a letter to Eugene with quotation of your post and ask him is it how the things really are. And this is his answer:

Eugene Roshal:

"No. I just have checked it one more time: compile
UnRDLL.c from unrardll.exe distributive, add unrar.dll
from the same distributive to it and unpack multi-volume
RAR archive successfully using them.

BTW, WinAce and PowerArchiver use the same unrar.dll too
but I never heard about any multi-volume RAR archives
unpacking problems these archivers ever have had."

The problem is not with unpacking them--that works fine. What doesn't work is that it doesn't *SEE* them to unpack if they don't start in the current file.

[Black Dog]

[face=courier]On 01-06-2004 21:23:57 +0000 Loren Pechtel wrote:

LP> The problem is not with unpacking them--that works fine.

One more time, for gifted guys - Christian do not add the possibility to ***VIEW*** (and ergo unpack) files, not started at current volume of multi-volume RAR archive 'cause he think that there is a problem with unpacking of a whole multi-volume RAR archive via unrar.dll:

g>> Only files starting in the current volume can be handled
g>> correctly with unrar.dll

Now you have to set external RAR unpacker to unpack whole multi-volume RAR archives. But Eugene doesn't share Christian opinion. So if it is possible somehow (I guess, Eugene does know he talking about) to unpack whole multi-volume RAR archive via unrar.dll, Christian can remove that files, started only in current volume limitation.[/face]

[Sheepdog]

If you look inside a multi -ARJ archive you get the following message:

Code: Select all

"This is a multi-volume ARJ archive. You can only see and unpack the contents of the currently open part of the archive (however, files stretching over multiple parts are correctly unpacked).

Please use 'Unpack specific files' to unpack from all parts!"

This should be displayed also for multi rar archives I think.

sheepdog

[IGL]

Have you tested it with ARJ archive, I thought I had the same problem with ARJ multivolume archives - the file that was split between two volumes was not unpacked and there was no warning.
But it was long time ago and I do not remember the details. Did anyone had such problem with other than RAR files?

[Sheepdog]

Have you tested it with ARJ archive,

Yes I did. I remembered that TC acts that way and so I tried it. But I did search the lng-file for other multi-volume messages and didn't find any other. So probably the same prob with multi zip-files I guess(but I didn't test it with zip).

sheepdog

[FlyingHorse]

Any idea when this bug will get fixed?