
InnoScript 4.0.6 Instructions
(InnoScript and Inno Setup are two separate packages by two different companies)
InnoScript Support Site: http://www.innoscript.com/cgi-bin/discus/discus.cgi


	InnoScript is best used in Video mode of 1024 x 768 or greater resolution. This version is not compatible 
with versions prior to 3.1.0. It allows you to save your selections as projects (.pjt) instead of having all the entries 
saved into the one ini file. If you install 3.1.x over previous versions the program may not work properly. In order to 
correct this situation you will need to rename the InnoScript.ini file and then re-run InnoScript. This will create a new 
properly formatted .ini file for the new version. You will then need to create a project (.pjt) for each Visual Basic 
Project (.vbp or vbg). 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.
        
        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 conversions to be run.

        Visual Basic Projects (.vbp or vbg) 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.

	Put yourself on our InnoScript's e-mail list to be notified of future releases. Send a request to 
innoscriptlist-subscribe@randem.com. Please put InnoScript in the subject line. Your feedback, thoughts, comments 
and suggestions are welcome.

	Add new files and folders to your script by using the Add Files and Add Folders buttons. Just select the files 
and /or folders to add them to the list and InnoScript will do the rest.

	Run InnoScript in batch mode by issuing the following command syntax at the command prompt:

		Ex. InnoScript (full .pjt name)

	Create a batch file with several commands to create multiple projects in batch mode.

	InnoScript will now take a more aggressive approach to seeking dependency information. It will look through 
all the dll/ocx/exe in your project for each dll/ocx/exe that is dependent on it and see if it can be used in the script. If 
the top level file is found in the UnSafe.fil, it will be eliminated from any searches and be deleted from the script. 
Dependency searching will still check the .dep files that are associated with any files also. In this more aggressive 
approach you may see files that are not on your computer and will never be. This may be due to the developer of the 
dll/exe/ocx using other functions in the file that were not public and not for deployment (IE for debugging/testing).

	In the View Menu; to help you with your development. The program will scan your computer's registry 
and 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 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).




Product Information

	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 a free utility that will convert your P&DW script or VBP file to an 
Inno Setup Script. It will give you a complete ready to compile script that can generate your setup immediately.

	InnoScript was created out of necessity. We were creating our packages using the P&DW 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 file processing. No need to have an intermediate operation.
*		The VB6 Runtime distribution files are copied with InnoScript installation into the installation folder.

	To help your installations be flawless, you should make our Automatic OS Updater part of your package. It 
will install the latest 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. The Automatic OS Updater can now be included in your scripts by checking the Auto OS 
Updater check box inside InnoScript. It has to be downloaded separately and placed into the folder where InnoScript 
was installed. The Automatic OS Updater has a dependency file (installed with InnoScript) that must also be present 
in the installation folder as well for InnoScript to locate it and process it correctly.


 Helpful Hints

	After initial installation, go to the "Parameters" menu selection and fill in any missing elements. If you are 
upgrading from a previous version, you can get most of these entries from your old ini file.

	The parameter screen is available to initialize some basic Inno Setup variable when the script is created. Just 
select Parameters from the main menu to get to this screen. Check Inno Setup help section for more information on 
these parameters.

The following Inno Setup parameters can be used on this screen:

InfoBeforeFile			AllowNoIcons
InfoAfterFile			DesktopIcon
AppSupportURL		QuickLaunchIcon	
AppPublisherURL		
AppUpdatesURL		
WizardImageFile
WizardSmallImageFile
DefaultDirName
DefaultGroupName
AppCopyright
OutputBaseFilename
PrivilegesRequired

The following InnoScript options can be used on this screen:

AutomaticOSUpdater  		Check for Unsafe Files
Searching

        If searching takes longer than you expect on a conversion... (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 path and it will be found the next time you attempt a conversion.

	 HINT: Add the new folder to the start of the search path area.

 	The Path Refresh button will get the computers current path and replace the text in the search path area.

 	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 replace your search path area with only 
the folders where files were actually found. This will speed up searching on the next conversion. This is because the 
program searches the search path area folders first when attempting to find files.


Unsafe File Processing

	InnoScript comes with a file named UnSafe.fil that resides in the same location where InnoScript was 
installed. Using this feature you can select if you want the program to check to see 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 these folders for files.

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


Dependency Information

	InnoScript aggressively searches for dependency information and this search info can be reviewed by you 
after each run. Just look in the debug log file (.dbg) in the name of your project in the \log\ folder where InnoScript is 
installed, you will find all the dependency information for all the files in your project. This can be accessed from the 
main screen also. You should use this information to update your Unsafe File list (Unsafe.fil).

	To help you with the template processing, a sample template file has been included with the installation in the 
installation folder. The name of the file is InnoScript.tpl and it has a few lines in this file to help guide you on to 
making script templates of your own.

	You can run Inno Setup with your newly created .iss script file from within InnoScript. After conversion just 
press the Run Inno Setup button and Inno Setup will be started with your script. Improve the speed that InnoScript 
takes to process your dependency information by Doing a Windows search for all .dep files and copying them to one 
folder for InnoScript to search. Place the folder name at the beginning of the search path area.

    
Operational Procedures
    
    InnoScript will convert your Visual Basic 5 or Visual Basic 6 Project file into an Inno Setup Script (.iss). 
It will automatically put in the appropriate runtime files for each of the versions of VB. By itself InnoScript 
is just a tool to help you move to Inno Setup by providing a simple way to get your project converted into an 
Inno Setup installer package without knowing too much about Inno Setup.
    
    The basic procedure to run InnoScript:

1.	Install InnoScript.     http://www.randem.com/innoscript.html
2.	Install Inno Setup (InnoScript uses Inno Setup).     http://www.jrsoftware.org
3.	Create a InnoScript Project for your Visual Basic Project.
4.	Fill in parameter screen for Inno Setup directives (can be done at a later time).
5.	Select your vbp/vbg and the name and location of the output .iss file (.tpl file is optional).
6.	Add any file or folders that your app needs.
7.	Press OK to convert your project file.
8.	Edit your script (.iss) with Inno Setup.
9.	Compile your script with Inno Setup.

    More complex processes can be done once you familiarize yourself with InnoScript's features:

1.	Safe Mode			Do not get any files from any systems folders.		Default
2.	Unsafe Mode			Get files from systems folders.
3.	Normal Script			Process without a template.					Default
4.	Template Script		Merge fixed template script with generated script.
5.	VBP files			Process VB 5 or VB 6 Project files.				Default
6.	Setup.lst Files			Process VB 6 Package and Deployment Wizard Files.
7.	UNC				Add UNC paths to the script for source files
8.	VB6 Version			Process VB 6 Project Files.					Default
9.	VB5 Version			Process VB 5 Project Files.
10.	Min Windows Version	Minimum Version of Windows that your app will install on.
11.	Min NT Version		Minimum Version of NT that your app will install on
12.	Service Pack Level		Add Operating System Service Pack checking (NT only).
13.	Beta Version			Just appends the word Beta on the output file name.
14.	Add Files			Add files to the script.
15.	Add Folders			Add the contents of folders to the script.
16.	Automatic OS Updater	Include the Auto OS Updater in your script.
17.	Check for Unsafe Files	Checks and eliminates unsafe files from your script.
18.	Run Log			View what happened in the current run.
19.	Debug Log			View dependency search info.
20.	Unsafe Files			View/Edit the unsafe files list.



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

1.	Use unsafe mode.
2.	Add folder paths to your Search Path Area.
3.	Remove the bad file names from the dependency files.
4.	Place the file names in the UnSafe.fil file. 

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

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.

Package and Deployment Wizard Setup.lst File

	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. This is the file that InnoScript will need if you choose PDW file processing.

Visual Basic Project or Group Project File (.vbp or vbg)

	Location of the .vbp or vbg file for your project that you created with Visual Basic 5 or 6. This is the file that 
you used to edit, test and compile your project with. InnoScript will need this file if you choose VBP file processing.

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 File

	Location of your template script file (.tpl). This script will be merged with your newly create script.

Source File Search Paths

	Just beneath the Visual Basic Project folder drop down; there is an area that contains the current path. This 
path can be modified to steer InnoScript to locations that contain your files that go into the script for faster searches 
and to find files that might not be found under normal conditions.



Auto OS Updater

	Mark the check box to include the Randem System's Automatic OS Updater into your script. This updater 
will update your MDAC, Jet and ODBC drivers to current standards. For more info on the Automatic OS Updater, 
please visit the website at: http://www.innoscript.com/support.html

Service Pack Level

	Add to your script which OS Service pack installations of which to install your package or not to install on.

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.

	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.

Asterick		Force addition of template line into script (no attempted replacement).
Semi-colon	Add line as a comment only. (No attempted replacement)

	The default properties of the template procedure is to replace or add lines to 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.

    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]						 - Subkey:


NOTE: If you want lines added to the script without processing (not attempting to replace) add an 
Asterick to the front of the line. The Asterick 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

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.

Minimum Windows Version

	Taken straight from Inno Setup, this will allow you to tell Inno Setup not to install your app if the 
Windows version is 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.

Minimum NT Version

	The same as Minimum Windows Version but will operate in the same parameters but checking for 
NT version. ie. Windows NT 4, Windows 2000 and Windows XP.

Service Pack Level

	Operates in conjunction with Minimum NT Version to allow you to select specific service packs for 
the selected NT Operating System that must be installed before your app will install.



VBP / Setup.lst Processing

	Allow 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 file processing (that is... if you have it).

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. 

Batch File Processing Mode

	InnoScript can be run from the command line to be able to generate batches of project scripts. The 
main reason to run it this way is for a developer that has many scripts to product and does not want to do 
them one at a time. This is a great time to utilize template processing along with the batch. Let say, you 
worked on your project of multiple project and installation parts. You can re-generate all your scripts 
automatically. Your static files are all in your templates and all InnoScript has to do is pick-up or drop any 
new additions or subtractions to your project and recreate all your scripts.

The command line syntax is:

InnoScript  myProj.isr

	Where myProject.isr is the name of your file that contains your preset information to use in the 
creation of your script. These .isr files can be create by simply taking your InnoScript.ini file and  removing 
all the items that do not pertain to your project. It is best to do this immediately after generating your script 
manually so that all the settings are based on the current script that was generated, such as in the example 
below:

Example of an .isr file:

[InnoScript]
MinWinVersion=1
MinNTVersion=2
SearchPath=c:\windows\crystal;C:\Program Files\Seagate Software\NOTES\;C:\Program Files\Seagate 
Software\NOTES\DATA\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;"C:\Program Files\Symantec\Norton 
Ghost 2003\";C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\Microsoft 
SDK\Bin\.;C:\Program Files\Microsoft SDK\Bin\WinNT\.;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program 
Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft 
Visual Studio\VC98\bin;C:\Program Files\Microsoft SDK\Bin\.;C:\Program Files\Microsoft SDK\Bin\WinNT\.;
UseUNCPath=0
ProcessFile=1
TemplateFile=1
NTServicePack=3
UnSafeFiles=1
AppDir1=i:\Develop\InnoScript\InnoScript.exe
PDWFile1=\\ace\randem\Develop\InnoScript\InnoScript.vbp
VB6Dir1=I:\Develop\VB 6 Redist Files\
InnoSetupFile1=i:\Develop\InnoScript\Scripts\InnoScript 2.2.iss
TemplateFile1=I:\Develop\InnoScript\Scripts\InnoScript.tpl
VBVersion=6

Multiple lines can be added to a batch file (.bat or .cmd) to be executed by the system. One thing to remember is that 
if you call these commands directly from a program all the commands will run concurrently (all at the same time). 
Running these commands in a batch file, they will run sequentially (one has to finish before the next one starts).

Notes

        Care needs to be taken on the machine 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 file 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 tell InnoScript what files belong to a particular component. If the dependency file is 
missing... then so would those files be.

	Something good to consider especially if you are a novice in the art of VB installer do's and don'ts, 
use the Automatic Installer to get your target system up-to-date so that you will not have installation or 
operational problems. It can be downloaded from the website: http://www.randem.com/support.html

Automatic Installation

Automatic OS updater for MDAC/JET/DCOM (32.4 mb)

Note: This can be placed into your script by InnoScript automatically.

	The automatic updater will detect your OS and then install the MDAC 2.8, MDAC 2.0 and Jet Engines 4.0 (Access 2000 
and up) and 3.51 (Access 97). This you might want to include in your packages to make sure that the user's computers are current 
before installing your app. You can run the utility silently with no user intervention by including the /VERYSILENT 
/NORESTART switches in your command line.

	Ex.
	c:\ > VB_DCOM_MDAC_JET_Autosetup.exe /VERY SILENT /NORESTART

	Or you can add this to your Inno Setup Script using (of course change the source file location):

	[Files]
	Source: "..\Support\MDAC\Scripts\Output\VB_DCOM_MDAC_JET_AutoSetup.exe"; DestDir: "{tmp}"; MinVersion: 
4.1,4.0; Flags:  ignoreversion deleteafterinstall
	[Run]
	Filename: "{tmp}\VB_DCOM_MDAC_JET_AutoSetup.exe"; Parameters: /NORESTART /VERYSILENT WorkingDir: 
{tmp}; 	MinVersion: 4.0,4.0


Randem Systems
(808) 344-0256
innoscript@randem.com	                   InnoScript Documentation	                   http://www.randem.com	
8/4/2005	                         Randem Systems, Inc		1 of 11
