Randem Systems Support Board

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.

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.

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.

Both files are in Unsafe Files but the -0 file is still being listed as missing.

Not a problem. All that should need to be done is to add both files to the correct Unsafe.fil (Inside InnoScript).

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.

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...

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?

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...

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.

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.

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.

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.

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.

Well, that didn't work.  Here's a Zip file with the three logs.