When files are not found

Parent Previous Next

What to do when InnoScript does not find files

       After running InnoScript to create your script, you may find some files that are not found. This can be remedied in ways that may mean combining several different options then re-running InnoScript.

    1. Use unsafe mode (Not recommended). This should only be used to identify files in the system area that you NEED to copy elsewhere to use.
    2. Insert folder paths to the files in your Search Folder selection to identify the location of the files.
    3. Remove the bad file names from the dependency files (.dep).
    4. Place the missing file names in the UnSafe.fil file (Only do this if you know you don't need the files).
    5. Add templates to add the missing files with their locations.

       Removing file names from the dependency files should only be done when you know that these files are never needed. Files such as u255store.dll and u25total.dll from Crystal Reports 8.5 are examples of such files that are never needed but the dependency file were never updated to reflect this. These file will never be found on current versions of Crystal Reports and can be eliminated from your script.

       InnoScript has support for Crystal Reports 8.5, 9, X, XI and 12. All support except for CR 8.5 is accomplished with merge modules. The merge module support for Inno Setup is handled differently than from the Windows Installer. A link to the Crystal Report support for Inno Setup can be found on the InnoScript web page (http://www.randem.com/crsupport.html). InnoScript comes with templates for each of these sub installation that is automatically added when you select one of these sub-installations. After you download and extract the sub-installation, tell InnoScript where it is and InnoScript will do the rest.

Note: All the Crystal Report dlls and ocxs should be removed from your script. The easiest way to do this is to add the Crystal Reports Referenced dlls/ocxs to the Unsafe file so that they will never be included in the script. You can get the names of the dlls from the script that InnoScript creates or from the .dep files that Crystal Reports files may come with. Another way is to use the Orca Editor to view inside the merge modules to find the names of exe/ocx/dlls that you will need to include in the unsafe file list. Just look at the top of the script in the comments for References and Components and you will find all the references/components that your VBP project uses. Look for lines with Crystal Reports in them and in the parenthesis on that line the dll name for the reference/component you used will be shown. Add these filenames to the unsafe file list.

Created with the Personal Edition of HelpNDoc: Free help authoring environment