A few weeks ago I used the 'From file rename script version 2.1' created by Henrik Ripa. That was on DOpus version 9.1.1.8.
After the recent upgrade to version 9.1.2.0, the script no longer works, but it has nothing to do with the script itself. In the Output window on the Script panel DOpus says that "Script Engine 'vbscript' could not be opened". Reinstalling 9.1.2.0 did not help and I would rather not reinstall 9.1.1.8...
Did anybody experience the same problem 
Rename scripts still work fine for me in 9.1.2.0 and I don't think anything was changed in that part of the code.
I think something has damaged your registry. If so, you can repair it by doing the thing that NightProbe said fixed it for him (found by Googling for the error message):
[quote="NightProbe"]1. Open a CMD.EXE window.
regsvr32 /s %SystemRoot%\System32\vbscript.dll[/quote]
(If you are on Vista or Windows 7 with UAC, make sure that's an Administrator command prompt.)
Even though I didn't find any errors in the registry that suggestion sounded reasonable so I tried it. And failed 
The dll was re-registered, but that didn't help. I also tried to unregister it first and re-register it after much the same without any positive results.
The problem still persists. Depressing
How are you looking for errors in the registry? Using a registry cleaner tool? IMO those tools tend do more harm than good and can get you into these situations more often than out of them.
Not sure how best to go about finding/fixing the cause of the problem. It's possible that all VBScript stuff will be broken on your machine, which may cause other things to fail, not just rename scripting in Opus.
I'm aware of that. I didn't say anything about cleaning I checked only. I used to clean the registry to get rid of orphaned and obsolete file shortcuts (these are regularly created during normal use of an operating system, e.g. you move some files). I clean those and those only and only after checking they are really not needed. I do that for years without any problems so I'm quite sure that this does not do anything that would result in such an error.
There are other vbscripts I use in some of my Excel files, so the VBScript stuff seems to work.
Maybe it's not version 9.1.2.0. I updated to it yesterday just after I installed Vista sp2. This could also introduce some new problems, it wouldn't be the first time to "repair something away" with a service pack. I'll dig into it deeper when I find time. Still I'd like to know if there are others with Vista sp2 and the same problem that is not fixed by re-registering the .dll.
I've been using Vista SP2 for a few days and don't have the problem so it's probably not that.
Excel uses VBA rather than VBScript so it might not be a good test. Not sure what the best test is, but it might be worth going to this test page using Internet Explorer and seeing if it says "VBScript is enabled and working!" (see my screenshot below):
I don't know if IE uses VBScript via the ActiveScript API which Opus uses but it's VBScript so it's a closer test than Excel.
[quote="leo"]I've been using Vista SP2 for a few days and don't have the problem so it's probably not that.
Excel uses VBA rather than VBScript so it might not be a good test. Not sure what the best test is, but it might be worth going to this test page using Internet Explorer and seeing if it says "VBScript is enabled and working!" (see my screenshot below):
I don't know if IE uses VBScript via the ActiveScript API which Opus uses but it's VBScript so it's a closer test than Excel.[/quote]
It was a good idea, thx for showing me that test page. Still it didn't end up as it should.
That is not the source of the problem. It's either IE not using VBScript via ActiveScript API or it's even ActiveScript API working correctly. That's becoming ridiculous 
Where can I find old versions? I've been trying to get my rename scripts to work for a days now, and would be glad to go back if it might fix the problem. I know nothing about debugging scripts.
It seems like this was broken by Vista SP2 for x64 users (and the same problem exists in Windows 7).
Rolling back to the previous version of Opus won't help you. We will have a fix for this issue in the next version.
As Jon says, I was wrong there. SP2 did break this, but only for x64 users. My main machine is 32-bit Vista SP2 so it continued to work for me. I can confirm the problem on a 64-bit Vista SP2 machine, and also that SP2 did modify the DLLs involved (apparently removing one of the COM interfaces, but it's easily worked around so don't panic).
That makes sp2 64bit the villain of the piece in this case 
Maybe if I told my op is 64bit we could identify the problem more easily. Well, every day I learn something new. Being more detailed was the lesson today.
leo, jon, thanks for your help and effort. Looking forward to next version 
bye
