Randem Systems Support Board

Thanks for that, I'll check it out.

The stdole2.tlb file is not on my Vista box so it was installed by one of the apps on your machine. It probably installed the wrong version, this file is not native to Vista

If you do not have a properties tab then you might have the wrong version I will check on my Vista Box. Process Monitor is just as easy to use the filter as RegMon. Operate is basically the same.

I'm running Vista so it appears I can't use RegMon, it tells me to use ProcessMonitor but I'm unable to use it to achieve the same thing as suggested in your article. I know it's me but a blank/corrupted ProcessMonitor Help file desn't help in telling me how to set the filter, but I'll keep at it.  
 
As for my version of strole2.tlb file, I can't get the version via file Properties but when I read it using Notepad right at the end it says the version is 6.0.6000.16386. Again, I'll keep at it and see how I go.  
 
Thanks a lot for all your help.

The issue is not with InnoScript it is with the .tlb file check your version for 5.1.2600.5512

Thanks for that and I'll check it out.
 
I'm still a bit confused though in that old InnoScript (V9.3.0) doesn't have that problem?

Ok, great. Well, not exactly great but this means that your machine has a problem with the registry. The call that issues the invocation of the program has been changed but the results are the same.
 
Check your registry, that file has seemingly gotten unregistered and the Windows call wants to auto register it and cannot. Either you have a permissions problem in your registry that will not allow the tlb file to be registered properly.
 
This may help: https://randemsystems.com/olereg.html

Unfortunatelly the same thing happens, as per attachment.
 

If you could try the same test with this file. It is ONLY for testing do not run with this version it is still in development. Just want to see if this issue is solved.
 
Just rename your exe and replace it with this one.  
 

And thank you for such prompt response.

OK, That was what I was looking for. I have never seen that error but I will look into it. Thanks for reporting this issue.

When I opened InnoSetup via the InnoScript Toolbar and ran the script I got the error however when I double clicked the (just created) 'Inno Setup Script' file and ran the script then it worked ok.
 
Seems like there may be a descrepancy in the way InnoSetup is invoked by InnoScript.
 
Cheers

OK, try this:
 
a) run InnoScript by double clicking on my (InnoScript) project file
b) in InnoScript click

Thanks for that advice randem.  
 
I found that in one of my associations {app}MyApp.exe I used the quotes and once I removed them all came good so once again, thanks.
 
As for my second problem, I installed the latest InnoScript and InnoSetup and did some testing/experimentation and have a really weird outcome. This is what I did:
 
a)   run InnoScript by double clicking on my (InnoScript) project file
b)   in InnoScript click

Aloha,
 
It looks like when you use a replaceable parameter in that field that expands to a long file name you need double quotes there instead of single quotes.
 
I do not understand why you are getting a typelib error. That has to be something else. Have you run the script thru the Inno Setup debugger?