E-M Script Debugging
(1) as you can see I figured out how to download and include Scripten.exe.
(2) i tried to add folders Search Folders to help locate red lined file but every time I ran Create Script it still could not find the files and when I went back to Add Folders, the folder I added was gone.
So why is there an Add and Remove button if what i put there does not stick?
(3) i tried Path Refresh. Path Refresh added folders that i tried to add with add folders. Again the Create Script could not find those files in the Path Refresh folders even though they were actually there. And the Search Folders tab was again missing the folders that Path Refresh added.
(4) i then tried to Add Files and got different results. For vbcript.dll that was red lined, I added that file in Add Files. The next Create Script then showed this to NOT now be redlined.
In the Help file it said that once I add a file with Add Files, that this folder would be added to the search list. Well, it did not because several other files that were redlined and are in the same folder where still redlined.
i.e. mswinsck.ocx
msflxgrd.ocx
(5) I also note that when files like bscript.dll and RICHTX32.OCX get corrected (as in not redlined) that the Source: has no path. Whys is this?
It look just like the other redlined Source: statments except that {sys} changes to {app}.
Does {sys} mean C:\Windows\System32 ?
Which is it supposed to be?
So how do I set the search path to automatically locate all the files in C:\Windows\System32 that are referenced?
What is the significance of redlined files like mswinsck.ocx?
When the install happens, as the script is now written, what happens with files lile mswinsck.ocx? Does a file version per the install Win OS get checked and updated or not? These are not part of the VB 6 Redist Files so
how is version control done? e.g. I might have installed a different app some time ago or some time after the current one and the versions of RICHTX32.OCX might be different.
What is the significance of the ***ERROR*** Invalid ... wbemdisp.tlb message?
What other probems do you see?
The generated script with errors is attached.
Thanks for the help.
You really are going to have to at least look over the help direction...
It explains in detail why you cannot use \Windows\System32\, this is explained in InnoScript as well as Inno Setup. There is also a message windows at the end of every script generation that that explains what you need to do for missing files also. You just don't willy-nilly start adding things without knowing how they react with one another.
If files are not found in a folder in the search folder tab the folder will be removed for there is no reason to search that folder.
Files that are not found in any search path are marked in RED.
You must take care of one issue at a time. In doing so you will find the other issues disappear because you also corrected them when you corrected the first issue.
Please copy all the files you need from the system folder and place them somewhere else then tell InnoScript in the search tab where this folder is...