Getting Started

Previous Next

Getting Started


Note: In the trial version some functions are disabled and will only work in the full version. This includes when running in a Virtual Machine. No script file will be created when running in trial mode.

Visual Basic 6 Runtime Files Location


Folder in which the Visual Basic Runtime Files are stored for InnoScript to use. These files are included with InnoScript in a folder named "VB6 Runtime" in the installed folder. 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. it is NOT recommended that you use this file for the missing information in the Setup.lst file may still be missing when you create your script. it is BEST to let InnoScript scan your project file and determine the files you need.


Visual Basic Project, Group Project File, .Net Project, Setup.lst (.vbp, vbg, .net)


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). This field is also used to select the exe/dll file, when you are using other programming language exe/dll files to create your script.


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. The default folder location will be automatically added when you select your VBP project file.


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 selecting 'NO' from the drop down box on the left. In some cases templates will automatically be added by InnoScript because it determines that you need some special parameters, files or code routines.


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 (None, 95, 98 and ME)


Select the buttons of the lowest (left) and highest (right) versions of Windows that you want your application to be installed on.

Minimum NT Version (None, NT, 2000, XP and Vista, Windows 7)


Select the buttons of the lowest (left) and highest (right) versions 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 or other programming language for you exe/dll file.


Automatic OS Updater (Win 9x Windows 7) for MDAC/JET/DCOM


       Select the version of Randem Systems 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 users 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.


NOTE: If InnoScript detects that you use a database when creating a script, it will automatically add the correct templates for MDAC and JET installations. In this case you will not need this selection. This selection is for worst case scenarios or when deploying your database application and you cannot get it to work.


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


       Select this button 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. InnoScript will automatically select this option for you if it determines that you are using scripting runtime files in your project.

    1. Download scr56en.exe (Windows Script 5.6 for Windows 98, Windows Me, and Windows NT 4.0).
    2. Download scripten.exe (Windows Script 5.6 for Windows 2000 and XP).
    3. Select MS Scripting Runtime from the main screen and InnoScript will add the needed lines to the script.


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 Setups 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 Setups 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 MDACs (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.


Project Options


Settings

Area where the main selections of the InnoScript project's are handled, such as VB Runtime FIles location, VBP/VBG file location and Script output location as well as other settings


Versioning

Area where the selections of which Windows versions your installation can be installed upon as well as some other installation options such as .NET Framework, VC Runtime files, Crystal Reports installations and Automatic OS Updater installations.


Inno Setup Parameters

Area where the selections many Inno Setup parameters can be selected that can enhance your script's functionality.


Inno Setup Script Editors

Area where you can select which of the many Inno Setup Script editors that you want to be able to use in InnoScript. InnoScript can automatically detect installed versions of Inno Setup, InnoIDE, ISTool and Inno Setup Studio. You can also apply a script editor that we have not automatically detected.


Project Views


Unsafe Files

View/Edit the unsafe file list.


Language File

View/Edit the currently chosen language file.


Registered Components

View/Search the registry for the registered components that are currently on your computer system.


Registered Shared Files

View/Search the registry for the registered shared files that are currently on your computer system.


System Fonts

Change the font that InnoScript uses to display all information.



Project Information


Script

Area where the output of InnoScripts 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 include the folder and all sub-folder underneath the original folder. 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\YourCompanyName\YourApp\Graphics or {app}\YourCompanyName\YourApp\Graphics if you selected {app} and the destination folder was YourCompanyName\YourApp for {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.


WinSxS

Chose which files that InnoScript automatically has determines that may be a candidate for a Windows Side-By-Side installation. Research will still be needed to determine if these files can be used in a WinSxS installation. Not all files that are chosen are suitable.


Messages

View the messages that InnoScript has created for the current run of the script displayed in the Script area.

Created with the Personal Edition of HelpNDoc: Easily create EPub books