Mhm. Overall, FreeArc is not very mature yet and it seems that unarc is very bad. Guess it's because hardly anybody uses it. I pointed the author to your post, so he can fix those.MVV wrote:Hm-m, you're right, it really works. But it doesn't work when I try to unpack specific file from archive, e.g.:And it works when I specify arc.exe instead of unarc.exe using same parameters.Code: Select all
unarc.exe x "data-9.freearc.bin" "Character Pimper\AutoPlay\Repository\EP1 Game\_Hybrid\Notes.rtf"
I found reason why unarc is unable to extract files using full path - its chec k function checks only filename, so we need to use -ap parameter. So following works fine:But does it mean that I can't unpack list of files from different directories at once?Code: Select all
unarc.exe x "data-9.freearc.bin" -ap"Character Pimper\AutoPlay\Repository\EP1 Game\_Hybrid" "Notes.rtf"
And anyway it won't work if you specify folder name using wrong character case (e.g. pimper instead of Pimper) - it compares paths using strncmp i.e. check is case sensitive.It will only work right for Unix-like systems.
And, unarc.exe doesn't support filelists with @.
As I see, main Arc.exe application is written in Haskell !!And it processes wrong character case or full path inside of archive correctly.
It is strange why they have such bad unpacker tool.
Haskell was a great language for a project like this.MVV wrote:As I see, main Arc.exe application is written in Haskell !!![]()