A couple of observations:
1. At the completion of the update for the new version a message windows appears which says that the installation folder was not found. Not true but could be confusing to some.
2. Upon loading an existing project with the new version the Messages showed Files Not Found as zero but the script lines for a mdac and Jet file were colored all Red (the files were in fact missing). I recreated the script; Files Not Found was again zero in Messages; the mdac and Jet file script lines were now all Blue (but still missing as confirmed in Inno Setup).
I resolved the missing files situation by placing the mdac and Jet files in the \Scripts\Output\Support subfolder of the folder where the installation .exe file is to be placed. However, a question. If I'm recalling correctly (which I may not be), with the project under the previous 11-4 version the mdac and Jet files were not shown as missing. Was something changed with respect to handling of the location of mdac/Jet files?
Also, a curiosity question. Why MUST the mdac and Jet files be in the \Scripts\Output\Support subfolder of the folder where the installation .exe file is to be placed? I'm guessing that it has something to do with finding the files when the built Inno Setup script runs them, but I'm not sure. (BTW and FYI, in the process of resolving the missing files situation I tried to add to the Search Folders a folder where I knew the mdac/Jet files resided. Didn't work -- the files were still reported as missing and the Search Folders entry was deleted.)
The MDAC / JET file come from a template of which InnoScript NEVER checks for, so they would not be listed as missing. The files are not in RED but in another color (use color legend for reference). the files MUST be in the \Scripts\Output\Support location mentioned because that is where the template states that they should be found. If you were to change path in the template file the files would need to be in the location you changed the path to in the template file.
NOTE: InnoScript does not check anything in the template files for validity.
As far as the message after installation. Please show the error message, I don't believe it is stating the installation folder does not exist..
I saw what I saw. When the existing project was loaded for the first time with 11-5 the mdac and Jet script lines in the presented script were Red; after recreating the script these lines were Blue (Replaced Lines per the color codes). However, let's not belabor this. I now know where the mdac/Jet files need to be, and why. Thanks.
As for the message after installation (which I did via the Check for Updates tab), I can't reproduce the message because the update is installed. The message may have said "missing" or "not found" -- I'm not sure. But, the message did reference the folder \Randem Systems\InnoScript\InnoScript 11. Again, this is of little or no consequence. If you're curious you may wish search the code for a similar message and see what triggers it.
\Randem Systems\InnoScript\InnoScript 11 is not the default location for InnoScript, that is probably something it was complaining about. The default location would be \Randem Systems\InnoScript 11 so that was probably just an informational message that something was pointing to a different location. So, when InnoScript went to look at that location for a file, the file was not there. I will take a look into this more..
What is your actual installation folder location?
Install Location: C:\Program Files (x86)\Randem Systems\InnoScript\InnoScript 11. The InnoScript application resides there.
I have created a new InnoScript project for our app with Versioning from XP through Windows 8. Thre are two situations which I don't understand and which may be a basis for an update to InnoScript:
1) The previous missing file situation with the api-ms-win-security-base-I1.2.0.dll file remains, despite the fact that the file has been added to the Unsafe File list.
2) The Flag "OnlyBelowVersion: 0,6" is not present in the script line for stdole2.tlb. This flag is present for the other VB Runtime Files.
Zip and attach your script, pjt and your unsafe file list. Here is a script we used to create InnoScript in Windows 8. You will see that all is correct. No missing api- files and the stdole2.tlb file line is correct. There is something suspicious on your side that we cannot duplicate. This script was created on a clean Windows 8 systems after installation of InnoScript.
Files attached. Note that the .iss file has been modified to comment out the api file script line and add the OnlyBelowVersion flag to the stdole2.tlb script line.
Now please zip and attache the .vbp & .exe files.
Here you go.
These are the missing files That are needed. Please zip and attach these files. Attached you will find the complete script and a new InnoScript exe to use to remedy the OnlyBelowVersion issue. As of yet nothing there has been no missing api- files listed. Possibly when I get these files I will see them.
Source: vfpoledb.dll; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: DYMO.DLS.SDK.tlb; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: DYMOPrintingSupport.dll; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: ResizeKit.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: LVbuttons.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: csxgraph.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;
Here are the files, but I don't think they will have any impact on the missing api file situation. Although you have previous discounted the possibility, I continue to wonder about Windows 8.1 being a factor versus Windows 8 on which you are testing. The following are some results from further testing with the 11.5-1 version of InnoScript:
-- The OnlyBelowVersion flags now appear on all the VB Runtime Files (including stdole2.tlb) but when the script is compiled in Inno Setup there's an "Unrecognized parameter name" error on all these files. The reason is a missing colon (:) after OnlyBelowVersion.
-- The missing api file situation continues. A sidelight observation that's probably of little consequence -- when I eliminate the file via the project's template it no longer appears in the script but Messages continues to report 1 Missing File.
-- There's a situation with the two Dymo files that I think may be related to the PDW and InnoScript's interface with it. Because I don't need these files I deleted (unchecked) them during PDW processing to exclude them but they continue to appear in generated scripts.
-- There's a situation with the LVbuttons.ocx file that may also be related to the PDW. I changed the PDW packaging folder from a Support subfolder of the folder where the VB project resides to a Package\Support subfolder, included the file there, and deleted the file from the original Support subfolder. But, within InnoScript the file continues to be listed as sourced from the original Support subfolder without being reported as missing, despite the facts that the file doesn't exist there and that I placed the Support subfolder in Exclude Folders.
I can handle the last two situations via the project's template but I'm wondering why they exist.
Disregard the last item in my last post -- the item about LVbuttons.ocx. I was misunderstanding the PDW folders. BTW, what's the Smiley in my last post. I entered the : symbol for a colon in parentheses.
This exe corrects the colon issue... I used your files and the api-ms-win-security-base-l1-2-0.dll file showed up. I typed the file name into the unsafe file list in InnoScript, saved the unsafe file list then re-generated the script and the file was removed from the script as expected. This is in Windows 8 and I will install Windows 8.1 but expect the same results...
All the correct files are found and there are no situations.
Also if your project does not need the files; remove them from being referenced in the VB6 project and that will take care of ALL situations because they will not be presented to InnoScript and InnoScript will not attempt to deal with them.
Thanks. With respect to the api-ms-win-security-base-l1-2-0.dll file, my Unsafe Files contains the file name in the Windows section. It got there by editing the file via the Unsafe Files item in the InnoScript left side menu. However, when I re-generate the script the file continues to be reported as missing. Is there another Unsafe.fil somewhere else that needs to be updated?
No, that is the only Unsafe file list that needs to be edited. It must be saved before regenerating script. This time I used a CLEAN Windows 8.1 and many api- files appeared. I copy/pasted the files into the Unsafe file list that is viewed from inside InnoScript and re-generated the script; ALL the api- files were removed as you can see from the logs.
Mysteries continue, but this time one that's good for the sanity of both of us. Just for confirmation, I removed the deletion of the api-ms-win-security-base-l1-2-0.dll file that I had in the project template and re-generated the script. The file is not reported as missing. The mystery is that previously the file was always reported as missing in numerous script re-generations. The situation is apparently resolved but I can't help to wonder -- was something done in the latest version you sent that caused this different result?
No. If you need to satisfy your wondering just load a previous version exe. Nothing changed in that aspect... It has worked as it always has. If something changed we would just tell you... Why do you think we would need to hide it?
Well, there have been other things that were claimed to be "has worked as it always has" that turned out not to be true. One more time, "I saw what I saw" in numerous script re-generations on more than one previous version.
But, no more wondering and no more contention from me. With your assistance I now have a clean and workable installation. Thanks.