problems with wfx_Registry 4.8

English support forum

Moderators: Hacker, petermad, Stefan2, white

Post Reply
User avatar
Nigurrath
Senior Member
Senior Member
Posts: 227
Joined: 2003-02-05, 12:41 UTC

problems with wfx_Registry 4.8

Post by *Nigurrath »

Hi all,
I have some strange problems with Registry wfx 4.8 (http://www.totalcmd.net/plugring/registry.html).

When I install the plugin and immediately start using it it works perfectly, while if I just close and reopen TC I get this error: "Error, could not load plugin! C:\wincmd\Plugins\WFX\Registry.wfx"

this is really strange, because the same plugin on another PC is running fine and is more strange because just after having installed it without closing TC it works. It just stops working (w that error) if I close and open TC and from that moment is not working anymore, except when I install it again overwriting the previous installation.

Is a TC but or a Registry bug??
User avatar
MVV
Power Member
Power Member
Posts: 8711
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV »

When you will overwrite file next time, please compare it in binary mode with original before.
Perhaps you have some virus that damages file after you use it (e.g. because its packed and virus can't operate with such packer, but virus may modify file only when its not used, i.e. after you close TC), so you can't load it anymore.
User avatar
Nigurrath
Senior Member
Senior Member
Posts: 227
Joined: 2003-02-05, 12:41 UTC

Post by *Nigurrath »

thanks MVV, that was the first verify I did, no infections and files are identical.

What I noticed is that it works when there's no ini file. If I erase the ini file the plugin works the first time, it then creates a default ini file and stops working. Probably there's a mismatch between the correct ini settings and the default values written in the ini when it is created for the first time.
always latest 32b TC on a WIN10 64b
User avatar
MVV
Power Member
Power Member
Posts: 8711
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV »

Interesting. What if you set read-only attribute (or even permission for all users) for that INI file?
User avatar
deus-ex
Power Member
Power Member
Posts: 991
Joined: 2003-02-10, 17:45 UTC

Post by *deus-ex »

Nigurrath wrote:Probably there's a mismatch between the correct ini settings and the default values written in the ini when it is created for the first time.
Try and copy/paste my INI settings and see if they work for you. It's optimized to only contain necessary (at least for me) entries, where possible I removed those entries with default settings unchanged.
If it does work for you, use it as a base and change it to your preferences (if necessary) step by step, add one change after the other and do a test run after each change.

Code: Select all

[Options]
AdditionalColumns=0
AllowRemoteConnections=0
ExpandedIconSet=0
ExportUNICODE=0
ImprovedKeyIcon=0
ShowAddValueFile=0
ShowExportProgress=0
ShowExportSetup=0
ShowExportSetupSingleFile=0
_____________
Kind regards,
deus-ex
User avatar
Nigurrath
Senior Member
Senior Member
Posts: 227
Joined: 2003-02-05, 12:41 UTC

Post by *Nigurrath »

humm strangely wont' work! Dunno why and don't really have a glue

I anyway did a better test.

1. erased file registry_vk.ini
2. restarted TC
3. tried to enter registry filesystem
4. the new registry_vk.ini is created
5. the dialog box telling that registry.wfx cannot be loaded is shown

apparently TC enters the plugin because it creates a new registry_vk.ini file with the default values, but after this something strange happens and forces TC to exit reporting that dialog..

The strange is that if I delete the registry plugin from TC (from filesystem and ini files) and do the following steps:

1. install the plugin from scratch
2. the installation terminated but at the end a box appears ("Error loading the plugin, probably some dll missing blah blah")
3. I ignore the message (checked deeply -reading IAT of .wfx- there are no missing dlls, absolutely nothing, it's a general message due to an error that happens for some other reason) and go on
4. now I enter the registry without closing TC
3. it works
4. restart TC
5. it won't work as above said.

Moreover during the beta tests of TC that registry plugin was working fine and the OS is exactly the same (so no dll are missing because the system is the same and it was working earlier)!

At this stage I really don't have a glue on this! What I can think of are two things: a strange bug into TC, a strange bug into registry!

BR
always latest 32b TC on a WIN10 64b
User avatar
Nigurrath
Senior Member
Senior Member
Posts: 227
Joined: 2003-02-05, 12:41 UTC

Post by *Nigurrath »

seems like it's a problems of this last version, version 3.4 (sent to me by Christian) works fine, but is really old. Does anyone have version 4.7 for example??
always latest 32b TC on a WIN10 64b
User avatar
sqa_wizard
Power Member
Power Member
Posts: 3897
Joined: 2003-02-06, 11:41 UTC
Location: Germany

Post by *sqa_wizard »

May a overeager antivirus is blocking access to the file ?
#5767 Personal license
User avatar
MVV
Power Member
Power Member
Posts: 8711
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV »

I've checked, it works fine on my work PC (XP SP2).

BTW, during my VP plugin debug, I've seen sometimes that TC didn't load my plugin and showed similar error message. I think that plugin may cause some exception during load and TC kills it. But where and why - I don't know. Exceptions are good sometimes, but sometimes it is hard to know place where error happens because of them.
Giovanni
Member
Member
Posts: 154
Joined: 2005-03-23, 18:28 UTC

Post by *Giovanni »

I'm having exactly the same problem as the original poster. Was a solution for this issue ever found?
User avatar
Nigurrath
Senior Member
Senior Member
Posts: 227
Joined: 2003-02-05, 12:41 UTC

Post by *Nigurrath »

at the moment I have not, I simply avoid to use that plugin.
always latest 32b TC on a WIN10 64b
karapuz79
Junior Member
Junior Member
Posts: 21
Joined: 2012-01-07, 17:57 UTC

Post by *karapuz79 »

As it turned out the problem was that *.lng files from other plugins were in the same folder - obviously that caused the crash.

Registry plugin (like ANY other TC plugin) must be installed into its own folder, otherwise all sorts of unexplained issues can be experienced.

Never ever assume that plugins created by different developers around the world will suddenly be 100% compatible when installed into a common folder.

--
Author of Registry plugin.
TC 8.01RC4 x64, Win7 x64 SP1
Post Reply