InnoScript 9.1 Instructions
(InnoScript and Inno Setup are two separate packages by different companies with no affiliations)
ALL SUPPORT IS DONE THROUGH THE WEBSITE
InnoScript Support Site: http://www.innoscript.com/cgi-bin/discus/discus.cgi
This version of InnoScript supports multi-language in
the installation of InnoScript as well as in the operations. You can change the
language that you want to view InnoScript in from the Languages menu on the
main screen. InnoScript will allow you to deploy your apps to Vista properly
without needing admin privileges to run them (unless you do some other bad
things in your code). However in order to do this you may need to change where
your app uses it’s data files that it needs to update and write to. These data
files should be in a folder inside your Local APPDATA or your Roaming
APPDATA folder not in your app folder. You can get your APPDATA
locations using the following code which you can find at http://www.randem.com/freeware.html
under the title
Make Your Application Limited User Compliant
InnoScript is to be used in Video modes of 1024 x 768 or greater resolution. InnoScript allows you to save your script selections as projects files (.pjt). If you create a .pjt file for the .vbg file you do not need to create a .pjt file for all the associated .vbp files within the vbg..It is advisable to use a group project file (vbg) when your project uses components from other VB projects. This will insure that you retrieve all components your app needs.
When initially started, InnoScript may appear to be frozen or hung. This is not the case; you must open or create a project for InnoScript’s graphical menus to be accessible or a script to be created.
Visual Basic Projects (.vbp, vbg or .net) to Inno Setup Script (iss) conversion is this programs strength. It will allow users to go straight from a Visual Basic Project file to an Inno Setup Script of course it can handle the Package and Deployment Wizard's Setup.lst file also, but it is advised against using the PDW file for it maybe lacking in all the things that are needed for a proper installation. Put yourself on our InnoScript's e-mail list to be notified of future releases. Visit our support site at http://www.innoscript.com/cgi-bin/discus/discus.cgi, your feedback, thoughts, comments and suggestions are welcome. You can also report problems and find solutions to your problems should you have any.
In the View Menu you will find two selections to help you with your development, “Registered Components” and “Registered Shared Files”. InnoScript will scan your computer’s registry then generate a list of all registered components and registered shared files. You may find this useful when you need to know if a file is registered, how many times it was and where it is located or just even which file is used with a particular system. (The count is the number of times the file was registered as a shared file). You can also remove these entries from the registry from this screen. All entries that are not found or unrecognized on your system will be shown in red.
Product Information</a>
InnoScript is a utility to help one migrate to Inno Setup from Microsoft's Package and Deployment Wizard or straight from your Visual Basic Project (this is the advised method). This is a utility that can convert your PDW script or VBP file to an Inno Setup Script. It will give you a complete, ready to compile script that can generate your installation immediately.
InnoScript was created out of necessity. We were creating our packages using PDW and then converting them by hand to Inno Setup (a tedious process and prone to mistakes). So we came up with this idea of how to do it automatically.
· Full VBP/VBG/.NET file processing. No need to have an intermediate operation.
· The VB5/VB6 universal runtime distribution files are copied into the InnoScript installation folder.
To help your database installations be flawless, you should make our Automatic OS Updater part of your package. It will install the proper MDAC, DCOM and JET engines to bring your clients computer up-to-date so that your installation is smooth. The updater and more details can be found on our support page, it should be run before or while installing your app. It has to be downloaded separately and InnoScript need to be told where it is located by placing the path in the search area box.
Helpful Hints
If running in safe mode and you have copied the files from the system folder to another folder. Place the path of that folder into the Search Folder Tab so that the files can be found there. You should also copy any .dep files for the same files there also.
The log files can be very helpful in diagnosing problems and courses of action. You should look at them whenever you have an issue to double check what you think you actually did.
The following Inno Setup parameters can be used on the parameter screen:
InfoBeforeFile AllowNoIcons PrivilegesRequired
InfoAfterFile DesktopIcon DefaultGroupName
AppSupportURL QuickLaunchIcon DefaultDirName
AppPublisherURL AppCopyright WizardSmallImageFile
AppUpdatesURL OutputBaseFilename WizardImageFile
AppName, AppVersion and AppPublisher are not included on the screen but are added to the script and are taken from the VBP project file from the following areas: Project->Project Properties->Make
AppName = Product Name
AppVersion = Product Name + Major + Minor + Revision
AppPublisher = Company Name
The following InnoScript options can also be used from this screen:
Automatic OS Updater Filename Check for Unsafe Files .Net Framework Filename
Searching
If searching takes longer than you expect on a script creation... (The program may seem to be hung), you can change the primary search paths that InnoScript takes in its search for source files. If files are not found, just add the folder to the Search Folder Tab and it will be found the next time you attempt a script creation. You can also eliminate any folders that you do not want InnoScript to search when looking for files. Select the Exclude Folder Tab then add the folders to the list of folders that you do not want searched. Note: Any sub-folders under that folder will not be searched either.
The Path Refresh button will get the computers current path then add the folders to the Search Folders Tab. UNC path names can be added automatically to the .iss output file by just depressing the UNC button in the toolbar. If you do not want UNC path names, leave it un-depressed. After searching for the files that belong to the script, InnoScript will add to the Search Folders Tab the folders where files were actually found. This will speed up searching on the next script creation. This is because the program searches the folders in the Search Folders Tab first when attempting to find files.
Unsafe File Processing
InnoScript comes with a file named UnSafe.fil that resides in the Local APPDATA folder for InnoScript. By using this feature you can select if you want InnoScript to check if the files in the script are unsafe and if found in the list they will be eliminated from the script. Unsafe File Processing is not to be confused with Unsafe Mode, of which if selected InnoScript will search the Windows System folders for files, otherwise in Safe Mode the program will not search the Windows System folders for files regardless of if you place the system folder in the Search Folders Tab.
The only time it will seem like the Windows System folders are searched is when InnoScript finds files that are in the systems folder even though Safe Mode is on. This is because the registry is checked to see if the file is registered and if so it may take the source location from the registry.
You can edit the Unsafe.fil file to include any files that are not on the list at the time of release. You can open this file from the main screen to edit or browse it.
Internal Installs
References: AutoOSUpdater, Scripting Runtime or .Net Framework
Defaults to No (unchecked). This will NOT include the referenced files in the installation exe. Thus making it smaller in size, but you will still need to place these into a folder named \Support that should be in the same folder where the installation exe resides. You will need to deploy your exe and this folder for your app to install properly. Check this box if you want to include the installations of the referenced files in your installation exe making it much larger in size but only having to deploy the exe without the Support folder. InnoScript will automatically create an empty Support Folder in the folder where the installation exe will be created, if one does not already exist.
Dependency Information
InnoScript aggressively searches for dependency information and this search info can be reviewed after each script creation. Just select the Debug Tab after the run, you will find all the dependency information for all the files in your project. You should use this information to update your Unsafe File list (Unsafe.fil). Select the Dependency Tab to show you all the files found that your project is dependent upon. Any PDW created .dep files should be in the same folder with the file they represent.
You can run Inno Setup with your newly created .iss script file from within InnoScript. After script creation, just press the Run Inno Setup button and Inno Setup will be started with your script.
Operational Procedures
InnoScript will use your Visual Basic 5, Visual Basic 6 or Visual Basic .NET Project file to create an Inno Setup Script (.iss). It will automatically put in the appropriate VB Runtime files for VB5 and VB6. By itself InnoScript is just a tool to help you move to Inno Setup by providing a simple way to get your project packaged in Inno Setup without knowing too much about Inno Setup.
The basic procedure to run InnoScript:
Complex processes can be done once you familiarize yourself with InnoScript’s features:
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).
2. Insert missing folder paths in your Search Folder Tab.
3. Remove the bad file names from the dependency files (.dep).
4. Place the file names in the UnSafe.fil file.
5. Add templates to add them.
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.
Support for Crystal Reports 9, X an XI 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 Merge Modules 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 merge modules. After you download and extract the support module, all you need to do is to add the matching template for the module and InnoScript will do the rest (or change the template to point to the folder where you extracted the file to).
Note: All the Crystal Report dll’s and ocx’s should be removed from your script. The easiest way to do this is to add the Crystal Reports Referenced dll’s/ocx’s to the Unsafe file so that they will never be included in the script (or scanned for dependencies). You can get the names of the dll’s from the script that InnoScript creates or from the .dep files that Crystal Reports files may come with. 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. Do not add these filename to the unsafe file list.
Getting Started
Visual Basic 6 Runtime Files Location
Folder in which the Visual Basic Runtime Files are stored. These files are included with InnoScript and copied to the installed folder location in a folder named "VB6 Runtime". The default location will appear when you create a new InnoScript project. These are the universal VB Runtime files that are needed for proper deployment.
Package and Deployment Wizard Setup.lst File (PDW)
Location to the Setup.lst file for your project that you created with PDW (PDW puts it in the Package folder by default). When you went through the setup process with PDW, it created this file for it's setup program to use to install your application.
Visual Basic Project, Group Project File, .Net Project, Setup.lst (.vbp, vbg, .net, .lst)
Location of the .vbp, vbg or vbproj file for your project that you created with Visual Basic 5 or 6 or Visual Basic .Net. This is the file that you used to edit, test and compile your project with. Allows you to process your Visual Basic Project file directly or you can process the Package and Deployment Wizards Setup.lst file. This is just a throwback to the early days of InnoScript when that was all it could process. You should always use the .vbp/.vbg/.net file processing (that is… if you have the project files).
Inno Setup Script Output File
Location and file name of where you want your new Inno Setup script (.iss) file to be located. This can be anywhere that you like. Our suggestion is to keep it with your VB Project but in a separate folder.
Template Script Files
From the Templates Tab, you can select/add multiple templates to be processed into your script. You can also selectively choose which templates not to process by not ticking the check box.
Source File Search Paths (Search Path Area)
The Search Folder Tab will originally contain the current path on your computer. This path can be modified to steer InnoScript to locations that contain your files that may go into the script. This should be done for faster searches and to find files that might not be found under normal conditions. InnoScript will not search your whole hard disk unless you specify to do this by placing c:\ in the search area. This however will be very time consuming and should not be done. Normally if you have added files through the Add Files button that will also tell InnoScript to search that folder for files.
Minimum Windows Version (95, 98 and ME only)
Mark the selection of the lowest version of Windows that you want your application to be installed on.
Minimum NT Version (NT, 2000, XP and Vista only)
Mark the selection of the lowest version of NT that you want your application to be installed on.
Visual Basic Version (5, 6, 8 - .Net)
Mark the selection of the Visual Basic Project your application is coded in.
Automatic OS Updater (Win 9x – Vista) for MDAC/JET/DCOM
Select the version of Randem System’s Automatic OS Updater to be included in your script. There is one that covers all Versions of Windows (95-Vista) and there is a separate OS Updater for each individual Operating System. This updater will update your MDAC, DCOM, JET and ODBC drivers to current standards for that OS. For more info on the Automatic OS Updater, please visit the website at: http://www.innoscript.com/support.html. You will need to download the OS Updater selected, for it to be included in your script. If you choose to include the OSUpdater in your script, InnoScript will automatically remove the VB Runtime files from your script because the OS Updater installs them also, so there is no need to have them installed twice.
The Automatic OS Updater will detect your OS and then install MDAC 2.8 (if needed), MDAC 2.0, Jet Engines 4.0 (Access 2000 and up) and 3.51 (Access 97) or DCOM components on Win95 & Win98. This you might want to include in your packages to make sure that the user’s computers are current while installing your app. You can also run the utility from the command silently with no user intervention by from the command line by including the /VERYSILENT /NORESTART switches in your command line.
.Net Framework
Mark the check box to include the Microsoft .Net Framework file in your script. This file will need to be found on your computer for it to be added to your installation. You will need to download this file from Microsoft if it is not already on your computer (dotnetfx.exe). You can change the name of this file in the parameter screen if needed.
MS Scripting Runtime
Mark this check box to include the Microsoft Scripting Runtime in your script. Note that on Windows NT 4.0, users must have Internet Explorer 3.02 or later installed, according to the Microsoft web site.
Service Pack Level (NT, 2000, XP, Vista only)
Add to your script the minimum OS Service pack installation of which your package will install on. Used with Inno Setup’s Minimum NT Version parameter, to allow you to select specific service packs for the selected NT Operating System that must be installed before your app will install. Used with Inno Setup’s Minimum NT Version parameter, to allow you to select specific service packs for the selected NT Operating System that must be installed before your app will install.
Minimum Windows Version (95, 98, Me only)
Mark the selection of the lowest version of windows that you want your application to be installed on. Taken straight from Inno Setup, this will allow you to tell Inno Setup not to install your app if the Windows version is not at least the one you selected. What this means is that if you indicate that you do not want your app to install on systems with Operating Systems before Windows Me, It will not install on Windows 95 or Windows 98.
Safe / Unsafe Mode
In Safe mode, no files will be taken from the system folders. In Unsafe mode, files can be taken from anywhere (including the system folder). Future versions of Inno Setup may not allow unsafe file processing. This mode is safety mechanism to help prevent you from crippling the computers that you deploy your completed installation package on. You can turn safe mode off to make sure you know what files belong in your installation, but you should turn it back on after you find out.
This is just a prevention method to get your attention, to warn you that you could cause severe problems to the computers that you install your app on. You should however create another folder and add the safe version of these files to it. Even some of these files could be eliminated if you deploy service packs with your app, such as the JET engines and MDAC’s (if you have a database app).
Unsafe Files
This is just a text file that InnoScript uses to eliminate certain files from appearing in the installation script under any circumstance. Just add the files that you do not want to appear in the script to this file and InnoScript will automatically remove them so that they do not appear in any scripts. This file is found in your application folder where you installed the app with the name of UnSafe.fil. The format of the file is one filename entry per lines. This is a help when you know about unsafe files and do not want to bother trying to avoid them in future generations of scripts.
UNC Processing
Use this as documentation only to know where the files are stored if the happen to be stored on another server in your organization. This will get the server name and shared folder names and place them into the script as the source file parameter. The reason being is that if you have a drive F: and you are getting files from a server that drive F: is mapped to. It may be useful to document where these files were stored for future reference.
Tabs
Script
Area where the output of InnoScript’s script is displayed after the run.
Run Log
Information about the current run of InnoScript will be displayed here.
Debug Log
Information from the current run will be displayed here to help you debug the script generation process.
Error Log
Errors from the current run will be displayed here to help you debug the creation of the script.
Templates
Templates for the project are added/edited/removed here, they can be edited by double clicking on the item you want to change. Templates must conform to Inno Setup Script rules. Basically templates are mini Inno Setup Scripts. If you want to selectively run templates, just select ‘No’ for the template and it will not be included in the next script creation.
Add Folders
Add complete contents of folder of which to include in your installation. This would include all files that are in the folder at the time of the compilation of the script. This would not include other folders inside of that folder. Each folder would need to be added separately. The folder contents will only be copied to your target installation not installed. Use this to copy a folder of graphic files that your application needs to run. If you select the destination location, these files will be copied to that folder when it gets resolved on the target machine. Ex. If the installation destination location was {app} then C:\mydevapp\Graphics would be copied to c:\program files\myCompanyName\myApp\Graphics or {app}\myCompanyName\myApp\Graphics if you selected {app}.
Note: The myCompanyName folder name will come from your VBP file. This property is set from the Company Name property from the Project->Project Properties->Make Tab from the VB 6 IDE. If it is blank then there will be no company name folder created.
Add Files
Add other files that are needed by your application that normally would not be found in a search. This would be files such as text, doc, database files or any other files that your application needs in order to run properly. These files will only be copied to your target installation not installed unless {sys} or {dao} is selected and the source file is a dll/ocx/exe. Use this to copy individual files that your application needs to run. Just choose the destination folder where you want these files copied on the target machine.
Exclude Folders
List the folders where you DO NOT want InnoScipt to search for files. Any folder that starts with the folder names in this list will not be searched. Folders that have a ‘No’ selected will not be used to exclude other folders from being searched. It will work the same way as if the folder was not in the list at all.
File Associations
Associate any file extensions that your program uses to itself so that if one were to double click on the extension your app would run with that file as a parameter. You can add, edit or delete file associations for your script. An example of the fields to add is formatted as follows:
Description: InnoScript Project Files
File Extension: .pjt
Icon Filename (.ico): InnoScript.ico
App Filename (.exe): InnoScript.exe
Reg Entry (xxx.xxx): InnoScript.ProjectFiles
Dependencies
Lists all the dependencies that your app needs to run. This is shown only available after a run is finished.
External Installs
Add any file (installation) that you want to automatically run after the installation is complete. These files will be run prior to your application being launched after installation.
Fonts
Add fonts that you want to be included in your installation.
Search Folders
This tab is the key to the success in the job of finding all the files that are to be included in your script. Add folders that you want InnoScript to search to find the files that are to be included in your script. After each run the tab will be updated with the locations where InnoScript actually found files.
Note: Each folder under these folders will be searched as well.
Template Script Processing
This can be a very powerful tool to use, especially if you generate a few projects that have the same programs or files needed in them that are not contained in your projects. Another way to use it on a single project that you need to update, you will not have to manually enter these files again.
To help you with the template processing, a sample template project has been included with InnoScript in the installation folder. The name of the folder is SAMPLE and it has a few lines in this file to help guide you on to making script templates of your own.
A template is simply nothing more than a cut down script, that’s it. It contains the lines of text that you would like to have added to or replace within your script when it is generated. These lines are generally the addition or modifications you want to make to the script as it is generated. Some default properties of the template process can be overridden by using special characters in the first line of the script line.
No Indicator Attempt replacement if cannot replace then add the line
+ Plus Sign Force addition of template line into script (no attempted replacement).
; Semi-colon Add line as a comment only. (No attempted replacement).
- Minus Sign Delete the line. (No attempted replacement).
& Ampersand Comment the line. (No attempted replacement).
The default properties of the template procedure is to replace, add, delete or comment the marked lines from the final script depending on value on the line itself and the section it is in. The default sequence is to replace the line if it can and if not then just add it. The sections are processed by using keywords and/or getting the parameter from the left of the equal sign. The keywords are the whole parameter except where notated. There is a sample template project in the folder named SAMPLE in the location where InnoScript was installed. Look in this folder for helpful hints on how to use template processing. Template processing can be a powerful tool to generate different scripts types from one base script by replacing one line with another.
Section Value
[Setup], [LangOptions], [Messages] - Left of equal sign.
[Files] - Source:
[Tasks], [UninstallDelete], [Components],
[Dirs], [Languages], [InstallDelete] - Name:
[Run], [INI], [UninstallRun] - Filename: (File name only)
[Icons] - Filename:
[Types] - Description:
[Registry] - Sub key:
NOTE: If you want lines added to the script without processing (not attempting to replace) add an asterisk to the front of the line. The asterisk will be removed when the line is added to the script. Adding a semi-colon to the front of the line will just add the line with the semi-colon in the same position.
Do not use indentation on script lines that are to be processed!!!!
Example Template
An example of what a template file should look like (*.tpl):
; The parameter to the left of the equal sign has to match Ex. DefaultGroupName
[Setup]
DefaultGroupName=InnoScript
AppPublisher=InnoScript
AppVersion=2.1
AppCopyright=Copyright 2002
PrivilegesRequired=admin
DefaultDirName={pf}\InnoScript
AppName=InnoScript
; The Name parameter has to match Ex. "quicklaunchicon"
[Tasks]
Name: "quicklaunchicon"; DestDir: "{sys}"
; The filename (of the Source parameter) has to match (without path) Ex. RICHED32.DLL
[Files]
Source: "C:\Windows\system32\RICHED32.DLL"; DestDir: "{sys}"; MinVersion: 4.1,4.0; Flags: onlyifdoesntexist
Source: "C:\Windows\system32\RICHTX32.OCX"; DestDir: "{sys}"; MinVersion: 4.1,4.0; Flags: onlyifdoesntexist
Source: "c:\windows\system32\Test.ocx"; DestDir: "{sys}"; MinVersion: 4.0,4.0; Flags: regserver sharedfile
Source: "\\ace\randem\develop\innoscript\Test.exe"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
; The filename parameter has to match (without path) Ex. InnoScript.url
[INI]
Filename: "{app}\InnoScript.url"; Section: "InternetShortcut"; Key: "URL"; String: "http://www.randem.com"
; The parameter to the left of the equal sign has to match Ex. DefaultGroupName
[LangOptions]
LanguageName=English
; The filename parameter has to match (without path) Ex. InnoScript.url
[Icons]
Name: "{group}\InnoScript on the Web"; Filename: "{app}\InnoScript.url" : Whatever
; The filename parameter has to match (without path) Ex. InnoScript.exe
[Run]
Filename: "{app}\InnoScript.exe"; Description: "Launch InnoScript"; Flags: postinstall skipifsilent
; The Name parameter has to match Ex. "{app}\InnoScript.url"
[UninstallDelete]
Type: files; Name: "{app}\InnoScript.url" : whatever
; The filename parameter has to match (without path) Ex. InnoScript.exe
[InstallRun]
Filename: "{app}\InnoScript.exe"; Description: "Launch InnoScript"; Flags: postinstall skipifsilent
Actual Sample Template
; Modified output to create a directory with just the VB5 and VB6 Runtime files, so that InnoScript can use this directory
; to get the files needed for the user installation during conversion.
[Setup]
AppPublisherURL=http://www.randem.com
AppSupportURL=http://www.randem.com/support.html
AppUpdatesURL=http://www.randem.com/InnoScript.html
DefaultDirName={pf}\Randem Systems\InnoScript\InnoScript 2.3
;WizardSmallImageFile=Wizsmallimage.bmp
;WizardImageFile=Wizimage.bmp
DefaultGroupName=InnoScript
AllowNoIcons=yes
InfoBeforeFile=I:\Develop\InnoScript\Scripts\Setup.txt
InfoAfterFile=I:\Develop\InnoScript\Scripts\ReadMe.txt
AppCopyright= Copyright (c) 2002 - 2003, Randem Systems, Inc.
OutputBaseFilename=InnoScript230
[Tasks]
Name: "desktopicon"; Description: "Create a &desktop icon"; GroupDescription: "Additional Icons:"
Name: "quicklaunchicon"; Description: "Create a &Quick Launch icon"; GroupDescription: "Additional Icons:"; Flags: unchecked
Name: "liveupdate"; Description: "Automatic &LiveUpdate (Startup Folder)"; GroupDescription: "Additional Icons:"; Flags: unchecked
[Files]
Source: "I:\Develop\InnoScript\Doc\InnoScript.rtf"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
Source: "I:\Develop\InnoScript\VB5Dep.ini"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
Source: "I:\Develop\InnoScript\VB6Dep.ini"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
Source: "I:\Develop\InnoScript\LiveUpdate\AutoUpdate.exe"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
Source: "I:\Develop\InnoScript\Doc\InnoScript.tpl"; DestDir: "{app}\Template"; MinVersion: 4.0,4.0; Flags: ignoreversion
Source: "I:\Develop\InnoScript\Doc\UnSafe.fil"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
Source: "I:\Develop\InnoScript\InnoScript.isr"; DestDir: "{app}"; MinVersion: 4.0,4.0; Flags: ignoreversion
; Put VB5 and VB6 Runtime files inside the app folder
*Source: "I:\Develop\VB 5 Redist Files\*.*"; DestDir: "{app}\VB5 Runtime"; MinVersion: 4.0,4.0; Flags: ignoreversion
*Source: "I:\Develop\VB 6 Redist Files\*.*"; DestDir: "{app}\VB6 Runtime"; MinVersion: 4.0,4.0; Flags: ignoreversion
[INI]
Filename: "{app}\InnoScript.url"; Section: "InternetShortcut"; Key: "URL"; String: "http://www.randem.com/innoscript.html"
Filename: "{app}\InnoScript.ini"; Section: "InnoScript"; Key: "VB6Dir1"; String: "{app}\VB6 Runtime\"
Filename: "{app}\InnoScript.ini"; Section: "InnoScript"; Key: "VB6Dir2"; String: "{app}\VB5 Runtime\"
[Icons]
*Name: "{group}\LiveUpdate"; Filename: "{app}\AutoUpdate.exe"; WorkingDir: "{app}"
*Name: "{userstartup}\LiveUpdate"; Filename: "{app}\AutoUpdate.exe"; Tasks: liveupdate
*Name: "{commondesktop}\InnoScript"; Filename: "{app}\InnoScript.exe"; Tasks: desktopicon; WorkingDir: "{app}"
*Name: "{commonstartup}\LiveUpdate"; Filename: "{app}\AutoUpdate.exe"; Tasks: liveupdate; WorkingDir: "{app}"; Parameters: "/Auto"
*Name: "{userappdata}\Microsoft\Internet Explorer\Quick Launch\InnoScript"; Filename: "{app}\ AutoUpdate.exe"; WorkingDir: "{app}"; Tasks: quicklaunchicon
Notes
Care needs to be taken on the computer where you run InnoScipt to make sure you get all the files your installation needs. Your machine must have the development environment installed or predictable errors will occur. InnoScript uses files in your development area to locate and determine what files belong with your application. If you were to run InnoScript on a non development machine, some files will not be found and may not be marked as missing. The reason would be that InnoScript never knew that the files existed and were supposed to be part of the package. Example, dependency files (.dep) help to tell InnoScript what files belong to a particular component. If the dependency file is missing... then it maybe possible that those files will be also.
Something good to consider especially if you are a novice in the art of VB installer do’s and don’ts, use the Automatic OS Updater to get your target system up-to-date with MDAC/JET/DCOM/ (mostly for databases) so that you will not have installation or operational problems. It can be downloaded from the website: http://www.randem.com/support.html
Suggested Reading: http://www.randem.com/installerproblems.html
Randem Systems, Inc.
(808) 344-0256