Ann: fhRAR v0.1.0

[TychoBarfy]

I have tried to add some part unicode into plugin for better national simbols support. Please test it and report me any bugs.

Version 0.2.1beta
...

REPORT: OK, works still with german umlauts so far :T

[Postkutscher]

Problem found. Unrar.dll returns rarCurrHeaderDataEx.FileAttr = 0x000081b6 for this strange archive from Unix. Does somebody knows what this means? I have never worked with Unix and with WinRar for Unix.

[TychoBarfy]

Unfortunately there are no sources for RAR for Unix.

This are some links I found. Its all Trial Ware.
http://www.chip.de/downloads/c1_downloads_12995847.html
http://www.rararchiver.com/download.asp

If I would run on Linux I wouldn't pack with RAR but with Bzip2.
How often does someone have such kind of files? Is it important?

[Postkutscher]

2TychoBarfy
Thank you for your help.

2iElectrik
fix for unix archives
DownloadLink: http://rapidshare.com/files/4445597/fhRAR.zip.html

It not solves problem at all , but is better than nothing. Works with archives , such as you have send to me,but forces attribute "archive" for unix archives.

[iElectric]

It happpens every 5th or so multirar i get.. I would be greatful for this fix. Maybe if we ask ghisler will know?

[Postkutscher]

When Mr. Ghisler would implement RARReadHeaderEx call inside of TC with converting unicode filename via WideCharToMultiByte, we need no fhRAR at all.
Support++

[TychoBarfy]

...
2iElectrik
fix for unix archives
DownloadLink: htt...
I kept the archive containing the AVI file from yesterday. Works fine.

[iElectric]

Works for me also! Thanks.. Now this plugin is perfect.. Only simple guide for the noobs how to make this plugin work

Thanks again Postkutscher

[Postkutscher]

Source code http://rapidshare.com/files/4545684/fhRAR_0_2_2source.zip.html

[TychoBarfy]

Hi,

I have an encrypted multi volume rar archive in which the contained files are also encrypted.

If I go into some directories within this archive, some filenames are displayed like this:
f#############################i ################a ##################################################l ################################################### ######################################################### ####################################################
(without the spaces in this case) instead of
file.ext

The first file which is displayed like this causes an error while unpacking.
Can it be that this has something to do with WinRAR 3.6x?

Unpacking this MV archive with WinRAR works fine.

I use the latest here posted version of fhRAR and TC 7pb2.

[TychoBarfy]

Now I tested a little bit and found that its not an issue of fhRAR.

I think it has something to do with my SATA controller.

Sorry for my too fast posting.

cu
TB

[GammelBert]

Thank You. I use this Plugin because it can display encrypted filenames in encrypted rar files. So I don't need external WinRAR program to look inside the rar files. The disadvantage is that I can't unpack in backgrond with this plugin. I would appreciate a function to use your plugin only to view encrypted files and unpack them with external programm. Unchecking the option in TCMD to "use internal un-rar if possible" has no effect when your plugin is installed.

Regards

[TychoBarfy]

2Postkutscher, it was not the SATA controller, but the 260 char limitation.

[TychoBarfy]

I think it's not the 260 char limitation but a problem of unrar.dll.

I created a test file with WinRAR 3.6 and called it fhrar.test.rar.
The password is "test" without quotes.

It's contents:

Code: Select all

E:\This is a folder with a long name containing spaces\
| 
+-+ This is a folder with a long name containing spaces\
| | dummy.txt
| | putty.test.Make.name.a.bit.longer_@could.be.the_reason.exe

If someone is interested, you can download this test file here:
http://www.famlehm.de/deleteme/tychobarfy/files/fhrar.test.rar

The EXE is just the new PuTTY.exe version 1.60.

If I put this file into the root of drive E, the path to the exe including the exe's name is:
"e:\fhrar.test.rar\This is a folder with a long name containing spaces\This is a folder with a long name containing spaces\putty.test.Make.name.a.bit.longer_@could.be.the_reason.exe"

The path's length in this case is 181 bytes (181 chars).
Now if I go into the file using Ctrl+PgDn, I can go into the deepest folder and see the damaged name of the exe. If I want to extract this, I get an error message.

If I put the new unrar.dll (version 3.70.1.336) of TC 7 RC4 into fhRar's folder, there's no error message anymore, and the file can be extracted, but it's name is still truncated.
Same with the newest version 3.70.7.105 of unrar.dll downloaded directly from RarLabs.
http://www.rarlab.com/rar/UnRARDLL.exe

So I think it's not an issue of fhRar but of unrar.dll.

BTW, if I extract this file using WinRAR, there is no problem.

Hope this helps.

[sas2000]

 

I think it's not the 260 char limitation but a problem of unrar.dll.

I am agree about this.