Gammadyne Corporation

This occurs when something in the installer has been altered.  The installer will always check to make sure it has not been changed before installing as a precaution, because there is a good chance the installation will not work.   Not a single byte is allowed to change.

The most common cause of this is a faulty download.  Delete the file (so that it is not cached) and re-download it.

Another common cause is a virus.  Viruses modify executable files when infecting them, which in turn can cause the installer to report that it is corrupt. You should definitely check your system for viruses.

A less likely cause is when the installer has been copied across a faulty network.  Verify that the copied file is exactly the same as the original file.

If the problem occurs after digitally signing the installer, make sure that "Archive Mode" is set to "Embedded" and that "Use Checksums" is unchecked.  Both of these options are on the Build branch.




Multimedia files (wav, gif, jpg, mp3) are already compressed and will not compress any further.  You may want to try compressing the same files with another program as a comparison.




It wouldn't be much of an installer if it didn't.  The file should be listed in the File Specification Table on the Files branch.  For DLL's, set the Type column to "DLL".  For COM/ActiveX/OCX files, set the Type column to "COM".  For a TLB type library, set the Type column to "Type Library".

COM/ActiveX/OCX/TLB files will be automatically registered by the installer and unregistered by the uninstaller.




The operating system will not actually remove the font until the machine is re-booted.




This feature has not been added because it is a really bad idea.  The DOS environment has a very limited amount of space for global variables.  Using up this space can cause severe problems with DOS-based applications.  You should not declare global environment variables under any circumstances - it is an very bad programming practice.




The overhead is approximately 637 KB, which is quite small for everything the installer can do.  Usually compression makes the installer smaller than the sum of the files that are going into it.





Yes, absolutely.  Furthermore, there are no royalties:  the installer is yours to distribute freely.  However, it is necessary to purchase a license for Centurion Setup.




To override the default icon, specify the full path to a new .ICO file in the "Installer Icon" setting on the "Build" branch.




Specify a path and filename to the new icon in the "Uninstaller Icon" setting on the "Uninstall" branch.




To change the text that appears at the top of the installer's background, go to the Display/Background branch, check the "Override Title Text" box, and enter the new title.

If a different title needs to be displayed depending on the language chosen by the end-user, follow these steps:

1. Choose "Edit Interface Strings" from the Tools menu.
2. Choose a language.
3. Choose "Background Title" from the list of strings.
4. Enter the new title at the bottom.  When left blank, the title defaults to the name and version of the product.
5. Repeat steps 2, 3, and 4 for each other language.
6. Choose "Save As" from the File menu and save the new string set to the directory where Centurion Setup is installed.
7. Close the String Editor window by choosing "Exit" from the File menu.
8. On the Display branch, change the "String set" setting to the name of your new string set.
9. Make sure the "Override Title Text" box is unchecked.

You cannot re-install a product to a second location because then all the uninstall information for the first installation would be overwritten.

To relocate a product, you must uninstall it, then reinstall it to the new location.





To install over read-only files, you have two options:

1.  Check the "Overwrite read-only files" box on the Install branch.  No read-only file will be safe!

2.  Before installation, remove the read-only attribute from the file.  This can be done using the DOS 'attrib' command in the Pre-Installation Batch, like this:

attrib -r filename.ext

To install registry keys and values, you can export the data to a .REG file with the registry editor. The .REG file is then imported during installation by using the following statement in the Post-Installation Batch:

regedit /s foo.reg

Notes:

• This assumes that foo.reg is installed in the root of the main installation directory (which is the current working directory for the Post-Installation Batch).  You can specify a relative path to a subdirectory.
• The "/s" switch prevents the user from being asked if they want to modify the registry.
• A robust program does not rely on the presence of registry information.  Your software should be able to use a default value in the absence of registry values, like ours does.
• The registry editor can be found in the main operating system directory (i.e. c:\windows).  The filename is REGEDIT.EXE.  Because the operating system directory is always part of the PATH environment variable, the batch does not need to specify REGEDIT.EXE's directory.
• On the "Locations" branch, there is an option to create a registry key during installation, which is also deleted during uninstallation.  It is recommended you use this feature so that when the product is uninstalled, the registry is cleaned up.
• You may want to delete the .REG file in the Installation-Exit Batch since it is no longer needed.  Use the DOS 'del' command, like this:
  
  

  del foo.reg

Now that your data is in the registry, brace yourself for the unending tech support nightmare that is registry security.




After installation finishes, you can start a program or open a document with the "start" command in the Installation-Exit Batch.  The current directory will be the location where the product was installed, so no path information is necessary.  Here is an example:

start foo.exe

Here is another example that opens an HTML file in a subdirectory of the installation directory:

start foo\bar.htm

No, nor will we ever implement such a feature.  Any conceivable method would be easy to circumvent.




There are two possible causes:
1.  The installer is run in Automatic Mode.
2.  The "Hide DOS Window" box is checked.




To create an empty directory, use the "md" DOS command in the Post-Installation Batch.  To refer to the installation directory, use the %InstallDir% environment variable.  Here is a complete example:

md "%InstallDir%\my directory"

Make sure that "Use Checksums" is unchecked.  It is the third option is on the Build branch.




Make sure your computer's clock is set to the correct date.  If the executable's date is in the future, the Start Menu will continue to treat the product as newly installed.




To set the Add/Remove Programs icon, go to the Uninstall/Data branch, and create an entry named "DisplayIcon". The data for the entry should be something like this:

%InstallDir%\foo.exe,0

Where foo.exe is the name of a executable than contains the icon (0 is the index within the executable if there is more than one icon). The path can also refer to a .ICO file like this:

%InstallDir%\foo.ico

Please note that whatever the source of the icon, it must be specified on the Files branch so that it is installed on the end-users's computer.




To change an interface string, follow this procedure:

1. Open the appropriate project for your installer (File menu > Open Project).
2. On the Display branch, in the String Set field, choose either DEFAULT.STR or ENGLISH.STR from the drop-down list.  DEFAULT.STR contains all languages, ENGLISH.STR contains only English.
3. Click the "Edit" button next to the String Set field.  The "String Editor" window will appear.
4. On the left hand side, click on the language that you wish to edit.
5. On the right hand side, click on the string that you wish to edit.
6. Modify the string in the editbox at the bottom of the window.  Please note that, by default, English strings are blank so that the English Default is used.
7. After all changes are made, choose "Save Project As" from the File menu.  Give your string set a different name, like CUSTOM.STR
8. Choose "Exit" from the File menu.
9. Back on the Display branch, select your new custom string set from the drop-down list.
10. Save the project (File menu > Save Project).
11. Rebuild the installer and test it to ensure that the altered string is being used.

You can find additional information about the String Editor here:
Help file > Table of Contents > Guides > Interface Strings