Packer plugin problem ?

[m^2]

Peti]
1. If so, why does Ultima use this fhRAR?!
2. I think I finally figured it out, TC UP is ok, fhRAR itself is ok, TOTALCMD may be different, it may work different -> it doesn't support fhRAR any longer, at least not on my comuter...

1.

It has one so called "drawback" though - it's a command line prog, so it shows a console window (can be minimized) and you don't have a fancy dialog box to write passwords in.

2. Nope, the wcx interface (and related code) didn't change for quite a long time. It seems that fhrar just has a bug and it's author cannot track it down.

[[HUN]Peti]

What happens when I select a plugin in Configuration? Does it load the dll (wcx) or not? Because if it doesn't then TC has the bug, if it does, the problem is in fhRAR.

[m^2]

Peti]
What happens when I select a plugin in Configuration? Does it load the dll (wcx) or not? Because if it doesn't then TC has the bug, if it does, the problem is in fhRAR.

Can you write it more precisely? I don't understand where's the problem...

[[HUN]Peti]

When I open Configuration, and set fhRAR for rar files, it displays an error message that this isn't a wcx plugin or something, what I want to know is that how TC identifies wcx plugins:
a) So if I select it, it loads the plugin to check if it's working or not.
b) Scan the file for Version information or something like this.

If a, then the bug is in fhRAR, it doesn't load perfectly...
This may be because of different PCs, fhRAR is not compatibel with mine, but if so, why was it compatible with 2.6? I checked it with 2.6, and it's ok.
If b, then TC has changed the plugin identifying mechanism and that's why fhRAR doesn't "look like" a wcx plugin anymore.

[m^2]

Peti]
When I open Configuration, and set fhRAR for rar files, it displays an error message that this isn't a wcx plugin or something, what I want to know is that how TC identifies wcx plugins:
a) So if I select it, it loads the plugin to check if it's working or not.
b) Scan the file for Version information or something like this.

If a, then the bug is in fhRAR, it doesn't load perfectly...
This may be because of different PCs, fhRAR is not compatibel with mine, but if so, why was it compatible with 2.6? I checked it with 2.6, and it's ok.
If b, then TC has changed the plugin identifying mechanism and that's why fhRAR doesn't "look like" a wcx plugin anymore.

TC does what you wrote ni a).
BTW from previous posts in this topic it wasn't obvious that even the bug happens so early.
I'll post a link to this topic to the plugin writer...maybe this info will help him in fixing the bug.

[[HUN]Peti]

This is strange, I restored the TOTALCMD of 2.6 in my 2.8 and it isn't working. I tried to replace fhRAR.wcx, still not working.

[m^2]

Peti]
This is strange, I restored the TOTALCMD of 2.6 in my 2.8 and it isn't working. I tried to replace fhRAR.wcx, still not working.

Maybe try a clean Total Commander installation just with fhRar?
There was also a suggestion there's some mess with environment varibles..can you try TC UP that in't started by tc_up.exe but totalcmd.exe AND with unrar.dll copied to the main TC UP directory ?

[[HUN]Peti]

Yeah, of course I can.
But now I know what the problem is ... was.
I copied unrar.dll to %COMMANDER_PATH% and it is working.
So the problem was with directories, maybe ENV VARs.

[m^2]

Peti]
Yeah, of course I can.
But now I know what the problem is ... was.
I copied unrar.dll to %COMMANDER_PATH% and it is working.
So the problem was with directories, maybe ENV VARs.

Great! That's 90% of solution. It seems that fhrar uses a strange form of loading libraries, one that ignores %PATH%.(maybe it tries to specify path directly..I don't know). The author of the plugin definitely should know this

[[HUN]Peti]

yeah, but i think copying unrar.dll is a bit easier than asking the author... 160kB only, and installer's size won't increase, it will store the 2 same files in the same space.