I've installed InnoScript on a Windows 8.1/64-bit system. I started a new project based on a VB6 .vbp file located in a standalone folder and used the default Versioning setting of XP to Windows 8. I've encountered the following problems after generating the script:
-- I get the following missing file: api-ms-WIN-SECURITY-BASE-11-2.dll
-- After the project is saved and I reload it in a new run of InnoScript there are no Inno Setup Parameters and the Settings are blank (do not show the .vbp file).
-- A minor situation: How can I clear the Recent Files list that's shown from the Files submenu?
Thanks.
To clear the Recent Project List, look in the InnoScript.ini file under the section of [Projects] and you will find the list of recent projects.
The InnoScript.ini file is located at C:\Users\YOURUSERNAME\AppData\Local\Randem Systems\InnoScript\Release
As far as the project setting disappearing we have seen that if you attempt to save the data in a location that you do not have write permissions. In those cases Windows will virtualize the location and place the data somewhere else. The project will appear empty every time for InnoScript will not look in the virtualize location but in the original location where you have Read privileges and the file will not be there.
What about the missing file: api-ms-WIN-SECURITY-BASE-11-2.dll?
I am not understanding the question; missing files have been handle the same way for years. Add them to the Unsafe file list and they will not appear in any future script generations. Not sure of what you are asking.
If you are asking why the file is missing; that is because a file you are using was compiled with the reference to this file. They may have never used it but it is referenced just the same so it appears in the file list. A file of the type you mentioned (Windows OS) can safely be placed on the unsafe list. Hopefully this will answer your question.
I have never seen this file associated with the app, the .vbp or the PDW, or in scripts generated with the same .vbp under Windows XP. I have no idea why it appears as missing in the script. Could this be a Win8.1/64-bit situation? I'll follow your Unsafe Files recommendation and see what happens.
My other problem continues. I started over with a new project as follows:
-- When prompted at the start for saving the project file I specified a folder that I had created via New Folder.
-- I entered all the info and created the script that contained the missing file situation.
-- When I exited the project file was saved in the folder mentioned above and a .iss file was created.
-- When I ran InnoScript again and opened the project file the Inno Setup Parameters and Settings were blank.
Here's a new situation. Sometimes when I start InnoScript fresh from the Desktop I get a message that it is running. I then need to restart the computer to clear things. I did the "CheckForUpdates=False" modification of the .ini file but it has not resolved the situation.
If InnoScript is Running, all you need to do is to open Task Manager and end the task named InnoScript; You do not need to restart the computer. InnoScript would stay running if it were shutdown improperly or another application is preventing it from closing.
As far as the file is concerned; you do not need to see it anywhere for it is an OS file and they are different for each OS and you should NEVER transfer/install OS files less you may crash the system you install your application on. It is nothing to worry about.
You never mentioned where you created the folder and what permissions you have on that folder.
When the "still running" situation occurred I opened Task Manager -- InnoScript was not there.
I created the New Folder on Drive C and named it Inno. On its Security tab in Properties it has Full Control for Users.
InnoScript would have to be in Task Manager if it were still running. Sort the tasks alphabetically and it should be there.
It looks like you are creating a folder in the root of drive c. You may need SPECIAL privileges to write there. Try telling InnoScript to use your Documents folder. Create a folder there.
All of the problems I am experiencing with InnoScript remain:
-- The "Already Running" situation continues and InnoScript is NOT in the Apps section of Task Manager when it does.
-- I created a folder in Documents and started a new project with the same specs. I added the api-ms-win-security-base-11-2.dll file to the Windows section of Unsafe Files and modified the Unsafe.fil file in the InnoScript installation folder. I created a script -- the api-ms-win-security-base-11-2 file again was listed as a missing file. A .iss file was created. I exited and the project file was saved to the created folder in Documents.
-- I ran InnoScript again and opened the project file from the created folder in Documents. The Inno Setup Parameters and Settings were blank.
I may have worked around the problems with InnoSetup. I edited the .iss file to comment out the missing file line, compiled, and installed the app with the Release file. The app appears to be working properly on both the Windows 8.1 computer (yeah, I know, don't test on the development machine) and on a Windows XP computer.
An update to my last post. I ran InnoScript As Administrator, created the project again as a new project and was able to save the project and reload it without losing the settings. I am also not getting the "Already Running" situation when I exit and rerun. However, the api-ms-win-....... file continues to appear as missing in the generated script.
PS With respect to the previous "Already Running" situation, I have noticed that when InnoScript is running it is listed in the Background Processes area of Task Manager (not the Apps section). Therefore, disregard my previous input of not finding it in Task Manager.
You will not achieve much by editing the UnSafe File in the installation folder, the files there are not for user usage. You have to edit the Unsafe file within InnoScript (on the left side menu in the top square area) Unless you know where the actual physical location is. Yes, in the updated Windows OS systems you may need to run as administrator or Windows will virtualize the data (even though you are an administrator on your computer). Basically you are an administrator but you need to be a super admin to write to some locations and that is totally under Windows Security control.
As far as testing your installation use a Virtual Machine. The software is free and there are a few to choose from. We prefer Oracles VM Virtual Box.
I modified the UnSafe file in both Unsafe Files on the left (as you mention) and in the InnoScript Installation Folder. It's still being listed as missing.
Not probable... Let's see how you entered the filename. Post the unsafe file (please attach the file).
The file is attached
What is the location of this unsafe.fil. BTW this file has the extension of .txt. InnoScript will not look in this file.
The file is in the folder I created in Documents. Its file name in that folder is Unsafe.fil This folder also contains the Project file, and the Log and Templates subfolders placed there by InnoScript.
I don't know why the .txt extension got added. Again, the file name in the folder in Documents is Unsafe.fil. Because I'm responding from a XP computer, I copied the file from the Windows 8.1 computer to a Flash Drive and attached from the Flash Drive on the XP computer. When the file was copied to the Flash Drive the name appeared in the file list as Unsafe.fil. When I plugged in the Flash Drive on the XP computer the name appeared in the file list with the .txt extension added. I just did the copy and transfer again and the same thing happened.
However, the file content is the same as the Unsafe.fil seen by InnoScript.
The proper file location for the Unsafe.fil would be C:\Users\YOURUSERNAME\AppData\Local\Randem Systems\InnoScript\Release
No other file location is acknowledged by InnoScript
I just checked and a more recent Unsafe.fil is in the folder you mention, and it contains the added line in the Windows section (api-ms-win-security-base-11-2.dll).
I tried to attach the file in the folder you mention with the name Unsafe.fil, but I got an error message which said that the file type could not be attached.
Ok, Copy that file to a new location then rename it to .txt, then upload it
Here you go, direct from the Windows 8.1 computer. However, when I renamed the file and tried to attach it, it appeared as Unsafe.txt.fil in the attach box. So, I copied just the file content through the Windows section and used Notepad to prepare the file that's attached.
Ok, now with that file in place run InnoScript on your projects and post the logs InnoScript generates.
Okay, but that will have to wait until tomorrow. It's 1:15 AM here and I'm going to bed.
Specifically, which Log files do you want?
All of them... Run, Debug, Error
Here's Try #1. I attached the three files consecutively via the Attach Box.
Well, that didn't work. Here's a Zip file with the three logs.
Oh Boy!! We've been dealing with a "typo" in the name of the missing api-ms-..... file, as follows:
Originally Used Name: api-ms-win-security-base-11-2.dll
Actual Name: api-ms-win-security-base-I1-2.dll (Note the letter I versus the number 1)
I modified the Unsafe files and ran the script again. Now the missing file is listed as:
api-ms-win-security-base-I1-2-0.dll (Note the addition of the -0)
I modified Unsafe Files to reflect the missing file name and ran the script again. The file is still listed as missing.
The attached Zip file contains the 3 Log files and the Unsafe.fil file.
Ok, getting somewhere. Could you attach the generated script.
the best approach for adding files to the Unsafe file list is to cut and paste. It will avoid such errors in the future.
Also, if you look in the Dependencies area of InnoScript on the bottom left menu (after a script generation). You can tell which file is generating these missing files and can either work on removing this file or adding the dependencies to the unsafe file list.
BTW: I don't see api-ms-win-security-base-I1-2.dll in the unsafe file list but I do see api-ms-win-security-base-I1-2-0.dll. They both need to be there, you add to the list not subtract. If you subtract it will cause other issues with missing files.
I added the I1-2 file to the Unsafe Files (so both the I1-2 and I1-2-0 are there) and reran the script. The I1-2-0 is listed as a missing file. You may be able to but I can't determine anything by looking in the Dependencies areas -- it's just a list of files to me.
The script (.iss) is attached. The will see that I'm confused about the MDAC/JET files. I have MDAC_typ_281and Jet40SP8 files (and some others) on my computer, did Add Files for them, and they appear in the [Run] section. What I'm confused about is the location of \Scripts\Output\Support for them to be added by InnoScript.
FYI, The I1-2-0 file is in the list of Dependencies. Also, I got around the \Scripts\Output\Support situation by modifying the script in Inno Setup to reference the location of the files on my computer. As I mentioned previously, I also commented out the missing file line.
OK, take a screenshot of the dependencies where the missing file exist. Basically it tells you from which file the reference to the missing file comes from.
The \Scripts\Output\Support\ folder is where you would place any downloaded installation from our website so that InnoScript can find the installations (which would be the JET & MDAC installations). Manually modifying the script will only cause more work and the possibility of mistakes. InnoScript was build so that you should not need to manually modify the output script. In this manner the same script could be generated each time without forgetting to modify anything...
The screen shot is attached. As you will see, there is no info for the I1-2-0 file.
As for \Scripts\Output\Support, where is it, or do I have to create it?
I am not following... \Scripts\Output\Support\ is where you find you find your .exe installation file (\Scripts\Output\) and that is in the folder where you project resides...
I think I got it. In the folder where the installation .exe is created the \Scripts\Output\Support subfolder contains the MDAC/Jet files, and I now see that InnoScript picked them up. I was confused by the .. before \Scripts\Output\Support. I thought that meant I had to add a prefix. Thanks for your patience in putting up with me.
It looks like the only remaining issue is the I1-2-0 file.
Not a problem. :) All that should need to be done is to add both files to the correct Unsafe.fil (Inside InnoScript).
Both files are in Unsafe Files but the -0 file is still being listed as missing.
And it is the Unsafe Files within InnoScript, i.e. in C:\Users\Tom\AppData............\Innoscript\Release. As I mentioned previously, I commented out the missing file line in Inno Setup and the installed app didn't seem to be affected. I'm okay with the situation unless you advise otherwise, but I would think you are interested in understanding/resolving the situation in InnoScript.
Are you sure it's a 0 not an O? Did you cut/paste the names in the unsafe.file list? Are there any trailing/leading spaces? This should be handled anyway but just checking. Could you zip your project's .vbp & .exe file and post it? I would like to run it here.
I've checked the Unsafe file several times character by character, but you can see for yourself. The Unsafe file is included in the attached Zip file, along with the .vbp and .exe.
You may find the following scenario interesting:
-- Opened the project in InnoScript; created the script; the I1-2-0.dll file is listed as missing.
-- Ran Inno Setup from within InnoScript; commented out the I1-2-0.dll line and compiled.
-- Upon return to InnoScript saved the project and exited.
-- Ran InnoScript again. In the presented script the line for the I1-2-0.dll file is a comment (; prefix and in Green).
-- Created the script again; the I1-2-0.dll file is listed as missing.
I ran your project here on Windows 8 and found the following files missing:
api-ms-win-downlevel-user32-l1-1-0.dll
api-ms-win-downlevel-shell32-l1-1-0.dll
api-ms-win-downlevel-version-l1-1-0.dll
api-ms-win-downlevel-normaliz-l1-1-0.dll
api-ms-win-core-registry-l1-1-0.dll
api-ms-win-core-com-l1-1-0.dll
api-ms-win-core-localization-l1-2-0.dll
api-ms-win-core-interlocked-l1-2-0.dll
api-ms-win-core-synch-l1-2-0.dll
api-ms-win-core-string-l1-1-0.dll
api-ms-win-core-processenvironment-l1-2-0.dll
api-ms-win-core-processthreads-l1-1-1.dll
api-ms-win-core-errorhandling-l1-1-1.dll
api-ms-win-core-debug-l1-1-1.dll
api-ms-win-core-libraryloader-l1-1-1.dll
api-ms-win-core-file-l1-2-0.dll
api-ms-win-core-memory-l1-1-1.dll
api-ms-win-core-sysinfo-l1-2-0.dll
api-ms-win-core-handle-l1-1-0.dll
api-ms-win-core-heap-l1-2-0.dll
api-ms-win-security-base-l1-2-0.dll
api-ms-win-core-datetime-l1-1-1.dll
api-ms-win-core-profile-l1-1-0.dll
api-ms-win-core-kernel32-private-l1-1-0.dll
api-ms-win-core-localization-obsolete-l1-1-0.dll
api-ms-win-core-string-obsolete-l1-1-0.dll
api-ms-win-core-wow64-l1-1-0.dll
api-ms-win-core-localization-private-l1-1-0.dll
api-ms-win-core-localization-l2-1-0.dll
api-ms-win-core-apiquery-l1-1-0.dll
api-ms-win-core-delayload-l1-1-1.dll
api-ms-win-core-threadpool-l1-2-0.dll
api-ms-win-core-fibers-l1-1-1.dll
api-ms-win-core-rtlsupport-l1-2-0.dll
api-ms-win-eventing-provider-l1-1-0.dll
api-ms-win-core-util-l1-1-0.dll
api-ms-win-core-kernel32-legacy-l1-1-0.dll
api-ms-win-core-heap-obsolete-l1-1-0.dll
api-ms-win-core-privateprofile-l1-1-0.dll
api-ms-win-core-sidebyside-l1-1-0.dll
I copy/pasted these files t the Unsafe.fil and re-ran InnoScript and all files were removed. I am not sure why you only have one or two files...
The same scenario occurs when Inno Setup is run separately -- that is, outside of InnoScript. It appears that InnoScript is recognizing the commented-out line from Inno Setup when the InnoScript project is loaded after Inno Setup has been used.
In regard to your missing files post:
-- At this point there's only one api......... file that is listed as missing -- the I1-2-0. I don't know what happened to the previous I1-2.
-- I'm running Windows 8.1. Don't know if there's a difference with your Windows 8 -- is it 8.0 or 8.1?
Seems like we have a mystery.
That is not possible... Here is the script I generated with your files. You must have a misconception about the operations. There is NO possible way that you can comment out a line in the script then re-run InnoScript and the line comes out of InnoScript commented out. InnoScript does not read the script...
Windows 8.0 or 8.1 the operations are still the same. If you put the file in the unsafe file and re-run InnoScript the file WILL be removed no exceptions. Please check your process of operations.
I don't know what more I can check. You have the Unsafe file I sent with the vbp and exe files. The I1-2-0 is in there. Also, the scenarios I provided below HAPPENED!
Here is my unsafe file, Run InnoScript using this file.
I just got back from dinner and a movie. I'll work on the Unsafe situation tomorrow and get back to you then. Also, I have some new information about the previous situation of "Already Running" that I discovered during experimentation earlier today:
-- If I exit InnoScript without first clicking the Save Project button, when I next run the program I get "Already Running." After I clear that in Task Manager, run the program and load the project, the Inno Setup Parameters and Settings are gone.
I realize that using the Save Project button before Exit is logical and I had been doing that before today's experiment. However, when an exit is made without first using the button there are "Saving Settings" and "Saving Project" messages that flash at the bottom of the screen. In the least, that's misleading. Worse, it seems that the messages are false.
No, the messages about saving are true and correct. Something like that would have popped up long ago since we use InnoScript to create InnoScript; we would have noticed that we were not changing anything...
Remember to modify your shortcut to "Run as Administrator" and that should solve that. If the OS virtualizes your data; there is not much InnoScript can do...
Okay -- fresh start. Just to be really fresh I uninstalled/reinstalled InnoScript (reinstall from the erroneously labelled Build 2 link on the Randem website which installs Build 3). I modified the Desktop icon to always Run as Administrator, which I know is now the case because if I right-click on the icon, Run as Administrator is bolded. I then created the project as a New Project and substituted your Unsafe file in C:\Users\Tom\AppData\Local......\Release. Sorry to say, there is no change in the results, as follows:
-- I created the script. Same as before, only one missing file was listed -- the I1-2-0.dll
-- 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.
-- After deleting the project I recreated it as a New Project (again with your Unsafe file) to test the previous situation where if I comment out the missing file in Inno Setup, recompile, return to InnoScript and save the project via the Save Project button, exit and then open the project in Inno Script, the I1-2-0 statement in the script is commented out. The result was the same as before -- only the same one file was listed as missing when I created the script and it was commented out in the script after I did the Inno Setup thing and reopened the project in InnoScript.
What next? Obviously, something is going on in my system that is not going on in yours. From one standpoint I can live with the situation because when I install the app with the Release file it appears to work properly, including on my XP system. However, I guess I can't be sure that will be the case on customer systems. Further, I'm intrigued with the problems/differences we are seeing, as I would think you are.
PS Out of curiosity I did an Internet search for the I1-2-0.dll file. I didn't find it anywhere, including in a Microsoft Support search. The only api-ms-win-security-base- file that appears in any search is I1-1-0.dll.
I am not perplexed at all. These are the dangers of testing on your development system, you cannot trust the results. Do yourself a favor, get the Oracle VM VirtualBox (https://www.virtualbox.org/); install a clean Windows OS and test there. NONE of what you mention can be true about the comments . There is ABSOLUTELY no way that you can comment out something in Inno Setup and it appears in InnoScript after a new run... NOT EVEN A CHANCE... InnoScript recreates the script from scratch and does not care about what you have done in Inno Setup...
BTW: You never have to save the project. On exit InnoScript will automatically save it if any changes were made.
I am disappointed with your latest response. I understand your advice about testing on a development system and will follow it. I also have a Windows 7 system on which development has never been done. However, your testing advice has nothing to do with the four items I mentioned about my work with InnoScript. You say: "NONE of what you mention can be true." I say they certainly are true because I have seen them happen, and I believe the testing process I used when they happened was legitimate.
In my years of providing support for our apps I have had a number of situations where I could not reproduce a reported customer problem. My reaction has always been to ask myself "What could possibly cause this?" and proceed to try to identify and evaluate possibilities on both the customer side and the app side. I would have expected something similar from you. Again, the four InnoScript situations DID HAPPEN!
Sorry, but modifying a script in Inno Setup would have no effect on InnoScript in any manner shape or form. It is impossible... InnoScript does not care about the output of Inno Setup. You have to be mistaken about this. You have to have a procedural error to see a case where comments after the script is generated to be included in the next generation of the script. It's the cart and the horse... If in your procedure you see this effect; then your procedures cannot be trusted or the equipment cannot be trusted. The after effect cannot have an effect before the effect itself.
Please look at this logically. If you change something after it is created, how can it be there BEFORE it is created then be inserted in the creation? You cannot do that in InnoScript without the templates; and that would have nothing to do with Inno Setup...
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.
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.
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.
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.
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?
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.
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?
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.
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.
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.
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.
Do not register the file, it might not need to be there at all...
Thanks. That's what I did by removing the regtypelib flag in Inno Setup.
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.
Looks like my previously reported "Already Running" problem has been recognized and corrected in 11.4.4.
Given our previous interaction on the subject I almost hate to bring this up, but the "Already Running" situation on my Windows 8.1 system with the latest InnoScript 11.4.4 is not resolved. As previously, if I exit InnoScript without first clicking the Save Project button, when I run InnoScript again I get the Already Running error window. After clearing the situation via Task Manager and running InnoScript, the Settings and Inno Setup Parameters are gone. FYI, in Task Manager the "Inno Setup Script Generator (32..." entry is under Background Processes, not Apps.
This situation no longer affects me because I have a working Inno Setup Release file from previous work and I will continue to always use the Save Project button before exiting InnoScript. I bring this up only for the purpose of giving you information that may be helpful in InnoScript development.
To add to my last post, I tested the situation on our Windows XP system and the situation is the same there.
Do you have any further input on why I continue to experience the "Already Running" situation?
That was handled in Version 11.4 Build 4. See InnoScript History thread for details and other fixes / changes.
we are checking on Windows 8.1 for this issue.
This will solve the issue in Windows 8. Just replace the InnoScript.exe in the folder where InnoScript was installed
Sorry to say that the new .exe file did not resolve the situation; in fact, it made it worse. I could not exit the program via the Exit item in the File submenu. Clicking Exit resulted in nothing and I had to go to Task Manager to end the program.
Try clicking the red x on the upper right to exit
Clicking the Red X does result in an exit, both with and without loading a project. And, after loading a project and exiting via the Red X without using the Save Project button, upon re-running InnoScript the Settings and Inno Setup Parameters are NOT lost. So, it looks like the new .exe resolves the lost settings problem. Once you get the Exit item in the File submenu to act like the Red X things should be fine.
This one works in both areas...
Surprise, and not a good one. The Exit item in the File submenu now works for exiting the program; but, when I load a project and exit without using the Save Project button, upon re-running InnoScript the Settings and Inno Setup Parameters are lost. Curiously, when I respecify the Settings and exit via the Red X without using the Save Project button, upon re-running InnoScript the Settings and Inno Seup Parameters are not lost. So, I conclude that there's a difference between the two ways of exiting.
They are both the same in this one.
Bingo - you got it! All is good. BTW and FYI, the original new .exe situation with the Exit item on the Files submenu also occurred on our Windows XP system, but it is okay with the latest .exe. So, the changes you've made are not Windows 8.1-exclusive. Again, all is good -- I'm going to bed at 12:30 PM.
This one will fix the Recent Projects list
InnoScript 11.5 has been release which fixes and add functionality. Download it from the website https://randemsystems.com/innoscript// (https://randemsystems.com/innoscript//)