Harrys Tools 2 - Installation Problem

[George]

I've just downloaded Harry's VRDTools 2.104, but can't get it to run. On executing, I get a Windows "VRDTools has encountered a problem and needs to close" error.

I already have version 0.32, which works without any problem.

I couldn't find any specific installation instructions for VRDTools, so I've placed
VRDTools.exe VRDTools.pdb and ComControl.dll into the VRD directory (I tried ComControl.dll in Windows\System32, but there's no change in behaviour).

When I open VRDTools.exe, VideoReDo opens for a split second and then disappears from view and is replaced by the Windows error message. The VideoReDo process remains running however.

I've used SysInternal's NTFileMon to monitored exactly what VRDTools is doing, and almost the last thing that it does before crashing (or calling DW20.EXE to generate a run-time error) is to check for the existence of C:\Windows\Microsoft.NET\Framework\v2.0.50727\VERS ION.dll. This file doesn't exist on my system, even though I have a clean install of .NET v2.0.50727. There is a C:\WINDOWS\system32\VERSION.dll, but VRDTools.exe doesn't attempt to open this. After failing to access VERSION.dll, VRDTools.exe reads a few more blocks of its own code then calls DW20.EXE.

Any thoughts, anyone? Am I missing something about the installation process?

Thanks

[Harry]

that's strange. you don't need to install anything, just unpack into a folder and launch the exe file in a recent .Net environment. everything is done by .Net. and i don't have a version.dll either in that dir.

do you have other problems with .Net? my only suggestion is to reinstall the latest version of the .Net framework.

greetz
Harry

ps: i suggest not to put the tools into the videoredo folder, put it into a separate folder as it's a separate program.

[George]

Thanks for the response, Harry.

I've succeeded in getting VRDTools working by installing the latest beta of VideoReDo (479), and it works OK with that (but still not with 455).

Before that, I tried re-installing .NET and DirectX (9.0c), but it didn't have any effect.

So, I'm OK with continuing to use the beta, but if you want me to try out any tests on the failing 455, let me know.

Thanks for the help, Harry, and also for writing the tools!