Here is the list of changes:
- Fixed: Search window does not disappear right after opening (x64 only)
- Fixed: Recompiled in VS2008 for compatibility with Windows 2000 (also fixed search)
- Fixed: Better work in some x64 systems - no more duplicate Wow6432Node keys in WinXP x64, no crash during search
- Fixed: Crash when accessing remote registry (TC 8.01)
- Fixed: Main icon was not displayed in some systems
- Changed: Show found key path as if inside HKEY_CLASSES_ROOT only when searching in HKEY_CLASSES_ROOT, otherwise keep original HKLM path
karapuz79 wrote:- Fixed: Recompiled in VS2008 for compatibility with Windows 2000 (also fixed search)
I can confirm the fix. Version 5.0 is working on Win2k again (including the search).
- Fixed: Better work in some x64 systems - no more duplicate Wow6432Node keys in WinXP x64, no crash during search
I can NOT confirm this! See this screenshot. On Win7 it is working fine (as it did in Version 4.9) but not on XP x64 using TC 8.0 32 bit. The plugin's 64-bit version is working fine though.
Nigurrath wrote:on windows 7 it says that the plugin is usign a missing dll and anyway it won't run.
NOT confirmed. The plugin loads as expected on Win7 (as on the other Windows versions since Win2k) on TC 8.0 32 and 64 bit.
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
don't really know what to say. I inspected the the wfx import table and all seems to be ok, but even during the installation TC says that there are some missing dlls and even after the installation there's no way to make it running.
Indeed it is a problem that even the version before had.
NTRegistry on the other hand works flawlessly.
In the past this problem I see has been mentioned by someone else for older versions.. ??
2Nigurrath
Please ensure that you have English.lng in the plugin folder - though theoretically it should show a message box about the missing language file: "Cannot find the default language file 'English.lng', please re-install the plugin!"
And sorry about that, it is a long shot, but - are you sure you are using 32-bit plugin version with 32-bit TC? If you try to use 64-bit version (.wfx64) from 32-bit TC then indeed you get "The plugin probably needs some DLLs missing on your system". Same about 64-bit TC and 32-bit plugin (.wfx).
2Dalai
I do not see an issue on the screenshot - if you run 32-bit version and ask it to access 64-bit registry then it is exactly what it does on the picture. In my system for example there really is second Wow6432Node inside of the first one, but its content is different and regedit shows the same.
yes of course am using the 32b version and as well the lng file is present. I tried all these "simple" combinations indeed..I have tc 32b on a win32 bit and not a single *64 plugin installed..
this is what happens: I let plugin to autoinstall, just after the "file system plugins" dialogbox (the one with all the installed file system plugins) I get this error dialog appearing: "the plugin probably needs some dlls missing from your system". It's clearly a wrong message, but it's a signal of an error during the loaddll process. Something is therefore missing from my system which prevents loading..dunno what.
The plugin anyway is able to create the registry_vk.ini file before stopping with that error.
2Nigurrath
Thanks, I will take a look what is going on after ini file generation. Since TC managed to call the Init method it means that DLLs are loaded ok, but something fails in the method itself...
karapuz79 wrote:2Dalai
I do not see an issue on the screenshot - if you run 32-bit version and ask it to access 64-bit registry then it is exactly what it does on the picture.
I see a problem there. Wow6432Node shouldn't show up a second time in the first place. The plugin doesn't do it on Win7 x64 as you can see in this picture.
In my system for example there really is second Wow6432Node inside of the first one, but its content is different and regedit shows the same.