Randem Systems Support Board

Looks like my previously reported "Already Running" problem has been recognized and corrected in 11.4.4.

You can replace the line automatically in InnoScript by copying the changed line into a the programs template in the [Files] section. Then each time you run InnoScript the line will automatically be replaced. No need for manual editing for that item each time.

Thanks.  That's what I did by removing the regtypelib flag in Inno Setup.

Do not register the file, it might not need to be there at all...

You may be surprised and pleased to know that I've followed your advice and installed Oracle VirtualBox.  I have successfully installed and run our app with the Release file from the modified Inno Setup script on a "clean" Windows XP virtual machine.  I am not yet able to create virtual machine for Windows 7 and Windows 8.1 because I don't have installation CDs (the OS's came pre-installed on the computers).  Therefore, I remain interested in your advice about the registration problem with the stdole2.tlb file on my physical Windows 7 and Windows 8 computers.  Thanks.

I'm guessing that you haven't responded to my last post because you are upset and/or frustrated with the emotional content of the post.  I apologize for that -- it's just that I've been frustrated with the absence of cogent explanations for situations I am seeing.  I am ready to move on.  Actually, the reason for my continued focus on the two remaining situations, other than personal curiosity, was from the standpoint of providing input that could be helpful to you and InnoScript development.  I don't believe these situations will preclude my development of a workable installation package, as follows:

-- With respect to the api....I1-2-0.dll file continuing to appear as missing, in a previous post you said "A file of this type (Windows OS) can safely be placed on the Unsafe list."  Therefore, I assume I can get the same effect by removing it from the Inno Setup script, and I have done so.

-- I will write off the Already Running situation as a "procedural misconception" and continue to use the Save Project button before exiting InnoScript (even though you say I don't have to).

I have installed and successfully run the app with the Inno Setup release file on two "user" (non-development) computers, one Windows 7 Professional and one Windows 7 Home Premium, and on a Windows XP computer that was previously used for development (for a reason you will see below).  I plan to use Oracle VirtualBox for further testing but I first need to get a CD copy Windows 8.1, which was pre-installed.

The only issue I have encountered in installing and running the app was an installation error message which said that the stdole2.tlb file could not be registered.  This occurred on the Windows 7 computers and on my Windows 8.1 development computer; it did not occur on the XP computer.  I "Ignored" the message; the installation proceeded to conclusion and there was no apparent impact when the app was run.  I then did some research which yielded a recommendation that the Regtypelib flag be removed from the Inno Setup script.  (Another part of the research information stated that a TLB alone won't do anything and there's no point in installing a typelib definition if it's not accompanied by a dll, ocx or exe.)  I removed the Regtypelib flag and reinstalled without receiving the error message; there was no apparent effect when the app was run.  I will appreciate your input on this situation.

In your next-to-last post you say: "There is nothing in the pjt file that will show what you are saying. te pjt would never contain such information as a commented out line."  Then you ask: "Where are you getting this script from?"  Well, the pjt certainly does contain the commented-out line when the project is loaded, and I've stated more than once how the script got to be as it is.

In your last post it seems you finally got around to actually looking at the presented script, seeing the commented-out line, and thinking about how it got there (a point which you would have gotten to a lot sooner had you not been "blinded" by an exclusive conceptual focus on how InnoScript generates scripts).  I never said anything about script generation, regeneration or re-running.  All I said is that I ended up with a script that contained a commented-out line, and asked why.  You've finally answered that question and your answer makes sense.  However, do you not think that what you call a "misinterpretation of the script" is confusing to a user who has no knowledge of the internal workings of InnoScript and Inno Setup?

Nonetheless, the commented-out line issue is resolved.  Now that there's some empirical thinking, what about the other issues:

-- Why do I continue to see the missing I1-2-0.dll file when I use your Unsafe file?

-- What about the "Already Running" and lost Settings situations I experience when I exit without using the Save Project button?  The following is my previous input on this:

   -- To test the Already Running situation I exited without first saving the project with the Save Project button.  When I ran InnoScript again I got the Already Running message, which I cleared with Task Manager.  I then ran InnoScript again and opened the project.  The Inno Setup Parameters and Settings were gone (interestingly, two files which I had added to the project with Add Files were still there).

   -- Now comes a new situation.  I completed the Inno Setup Parameters and Settings and created a script.  132 missing files were listed, including the many api.... files and others which weren't previously listed.

There is ONLY one way there could be a misinterpretation of the script. If you ran Inno Setup to edit the script file then return to InnoScript exited out of InnoScript then restarted InnoScript. this would cause InnoScript to reread the script and show it on the screen. This is by NO MEANS a regeneration of the script... Regeneration of the script is to press the "Create Script" button and if done the script would change...

Editing the script then opening the script in another program is not re-running the script. This is the ONLY explanation and this would be a procedural misconception.

No, it is a conceptual issue on your part. There is nothing in the pjt file that will show what you are saying. te pjt would never contain such information as a commented out line... It never happens, you are misinterpreting the information. If you use Inno Setup to edit the script then come back to InnoScript and re-run the script generation there is no way for the comment to appear in a newly create script. It is IMPOSSIBLE, InnoScript has no knowledge of what you did in ANY editor... Unless you told InnoScript to comment out the line inside InnoScript (template), there is NO way for InnoScript to know what you have done...

InnoScript generates the script, it does not take ANY information from the script. Where are you getting this script from?

Attached is the project file.  When you open the project you will see that the api-ms-......I1-2-0.dll file is commented out in the script that is presented.  This is what happens after I do the commenting out in Inno Setup (which I run from the button within InnoScript) and then save the project, exit, and rerun InnoScript.

I believe this is both empirical and logical evidence that what I have said happens actually does happen on my system -- empirical because the line is commented out in the InnoScript script, and logical because how else could it happen if not in some way connected with InnoScript and/or Inno Setup.  I certainly can't edit the script in InnoScript and I haven't done so in any other way.

Yes, it does. There is no way for anything to get add/subtracted from the script by another process in this procedure. there is no way a commented out line could get into the script simply by re-running InnoScript. One can edit the output script all one wants too and that process output cannot get back into InnoScript. This is what you say that is happening...

Now after following this procedure and you re-open the project that is stored in the documents folder area what happens?

1. Done.  All the things I reported a few posts ago were done with InnoScript run As Administrator
2. Done, in the Documents folder
3. Done.  The only "changes" I made was to add two files via Add Files, both of which appeared in the script.
4. Done
5. No changes necessary (other than resolving the one missing file that is listed)
6. Not Applicable
7. Done

With respect to your next to last post, we agree that the first thing to be done is to resolve what you say can't happen with what I have seen happen.  Again, what I did procedure-wise is described in my post and I don't see anything irregular -- do you?  I suggest you try to do on your system what I did for each of the situations.  You already got an okay script with your Unsafe file; I didn't.  I suspect that the same thing will be the case with the other situations, although we will then know that empirically.  The question is why and I don't think it has anything to do with the procedures I followed.

The process should be as follows:

• Run InnoScript As Administrator
• Create a new InnoScript project in an area where the OS does not virtualize (Such as in the Documents folder)
• Enter all InnoScript changes to the project script
• Create the script.
• If missing files are present, either add the file to the Unsafe file list or find add the path to the file to the Search Folder list or Copy the file to a location InnoScript is already searching
• Re-run Script Generation until all files are resolved.
• If any changes need to be made make them in InnoScript using templates or other areas within InnoScript
• Re-Run InnoScript to create script
• Compile in Inno Setup

Following this method will insure that the script gets generated correctly. No other program can introduce additions/subtraction into the scripting process. Re-run as many time as needed to create the script you want.

Yes, One thing at a time. If you jump around things get missed or overlooked. The MOST important part is how can something that cannot happen; happen? This has to be resolved first or nothing else makes any sense. If this can happen then the procedure is flawed and therefore it cannot be trusted nor can the results. If an error has been made or described incorrectly, the results cannot be trusted. It's all about the process.

I have looked empirically at the one thing you keep responding to -- what happened did happen with the process (steps) I've described.  Where do you see a fault in the process I used?

What about the things you haven't responded to -- The listing of only one missing file with your Unsafe file; the Already Running situation; the 132 missing files situation when a script was created after recovery from Already Running?  All of these things are described in my previous post, all of them DID HAPPEN, and I don't see a fault in the process under which they happened.