Randem Systems Support Board

Let me check to see what the case may be...

Oh boy - I just downloaded and installed the new beta version.  When I attempted to run it I got:
 
Run-time error 430 - Class does not support Automation or does not support expected interface.
 
Uninstall/Reinstall did not resolve.

Changes have been made and a new version uploaded. Check .InnoScript History for new changes.

Considering this is a Beta version This is exactly the kind of response I wanted so that certain procedures could be refined. Perhaps InnoScript need a way to remove Items from the script.

I also realize that if I was doing the standard thing of keeping my data files in a folder separate from the app folder we wouldn't be discussing this.

I used the script with Inno Setup and the changes in Red were accepted without error.  I also checked the Colors tab in InnoScript (which you will say I should have done when the Red situation occurred).  Actually, the default color for Added Lines is dark Magenta, which is very close to Red and a source of confusion.  I've changed my Added Lines color to a lighter shade of Magenta (so at least I'm not confused anymore).
 
You said in a previous post: To remove you eliminate the process that included it in the first place or remove it manually.  I assume that the process that included it is the  provision of default [UninstallDelete] items by InnoScript.  Have I (again) missed something that would allow me to modify the defaults?  Also, I assume that the only present way to remove it manually is via editing of the script in Inno Setup - is that true?

Why not red??? You can change those colors...  
 
The other items that are changed in the template (in the [Files} section) show up in blue.  I would think these changes should be in the same color.  Besides, red usually means error.

Why not red??? You can change those colors...
 
That file is removed because it is a VB runtime file and since you included the OS Update those files are not needed since the OS Updater installs the VB Runtime file also. No need to have them installed twice.

With respect to add, see my previous post.  Using the asterisk resulted in the line being add, but in a red color.  Why the red?
 
I don't want to delete the {app} folder.  I don't know how to eliminate the process that included it  and I guess the only way to remmove it manually is via editing of the script in Inno Setup.
 
OLEPRO32.DLL is listed in the Dependencies and also in Deleted Files.

You don't remove anything thru the template process, you only add and modify. To remove you eliminate the process that included it in the first place or remove it manually. Perhaps a removal in the template may be productive...
 
No, I never cause it to be included. That is exactly what the documentation in the script is for. So that you can tell what was removed or added between runs.

For give my frusration, and I understand yours with me.  Although I think an editing process would be less complex and easier than a template process, I suppose templates are necessary because InnoScript is a script generator from VB project files, etc. But enough, templates it is.
 
The whatever comes for your documentation and from the template example in your Examples folder.  I thought I understood how to add items to the template via the first-character asterisk, e.g:  
 
*Type: files; Name: {app}GHM.exe  
 
The line gets added when I run the script but it's in red - ??
 
I don't yet understand how to remove a generated item.  For example, if a have a generated item in [UninstallDelete] of:
 
Type: filesandorfolders; Name: {app}
 
how do I remove it?
 
I'll do some research in my VB References about why OLEPRO32.DLL is missing.  It may be related to something I removed.  Perhaps you what causes that file to be included as a reference.

Why should InnoScript recognize change made to a script after InnoScript created it??? I repeatedly stated that you should make changes in the template file in InnoScript so that when you re-run InnoScript you would not loose changes. You constantly ignore those suggestions...
 
The template process is described in the documentation and I have given you examples. All you need to do is to take the line that InnoScript created copy it to the template file under the proper section and then make your changes to it. The next time you run it will change the line...
 
I can't tell you where whatever came from I don't know where you got it from.
 
The check box issue we will be working on. Thank you for bring it up.
 
If you removed the reference it will not show up. I create the script with what you had given me.

Progress, although not complete progress.  I now have an Inno Setup with my revised [UninstallDelete] section.  However, I went a bit nutso in doing so.  Here's why.
 
I created a script in InnoScript and edited it in Inno Setup to make the [UninstallDelete] changes.  However, if I go back to InnoScript to do anything and run it again (I'm wearing out the traffic light) the script changes I made in Inno Setup are lost and I have to do them over again.  Questions:
 
-- Why doesn't Inno Script recognize the script changes made in Inno Setup?  Or, why is there no capability to edit a script in InnoScript?
 
Perhaps the best way to do the [UninstallDelete] changes is via my Template but I'm not sure how to do so.  For example, how do I delete a line generated by InnoScript?  This time I did read the documentation but didn't find it definitive.  It mentions keywords but I'm not sure what they are.  In the example:
 
Type: files; Name: {app}InnoScript.url: whatever
 
What is whatever?  Also, why the inclusion of quote marks (there are none in an actual Template file)?
 
Here's another usability situation.  When I return from double-clicking a Template to edit it the checkbox that was previously checked is unchecked.  It took me a while to recognize that this was happening.  Why does it happen?  (If I am editing a Template I sure want to continue to use it.)
 
One final question regards my script.  The original script you sent me included a Reference to OLEPRO32.DLL which is no longer included when I run the script - ??

Yes, that will work...

Why would you not want to remove the files on an uninstall?
 
Because, for now at least, I'm stuck with the data files being in the same folder as the app.  And, for future releases of the app I want both this common folder and the user's data files to remain.
 
I realize that a separate data folder is a better approach and eventually I will go that route.  But, for now can I just do a series of:
 
Type: files; Name {app}filename
 
for the files I want to uninstall?