Centurion Setup – an easy-to-use tool for software developers that allows users to quickly create the final installation files. It has taken only a few minutes to create a professional installer for a family of Windows, having self-executing file in compressed form. The program has support for multiple languages, interface configuration, installation DLL, password protection and much more. Put files in the archive can be by simply dragging them from Explorer or you can specify the folder from which files and subfolders will be included. If any of the files used by another application, the program will add it to the archive at the next startup.
Key Features * Self-Contained Executable : Centurion Setup creates executable installation programs that are self-contained in a single file. A single file is easily downloaded, requires no software such as WinZip to decompress, and ensures that all installation files are present. The installer’s overhead is only 440 KB and the compression engine achieves a very high compression ratio. You will be amazed at how small Centurion Setup can make the installer. * Uninstall Support : Centurion Setup can optionally provide support for uninstalling the product. The user will be able to uninstall the product by one of the following methods:
> The “Add/Remove Programs” option in Control Panel. > A Start Menu shortcut (optional). > A Desktop shortcut (optional).
* Multilingualism and Interface Customization : The installer is capable of presenting the user interface in English, French, German, Spanish, Dutch, Norwegian, Italian, Portuguese, Swedish, Danish, Finnish, and Afrikaans. All strings that are displayed in the user interface can be edited. Entire languages can be added. * Shared File Support : The installer can install operating system DLL’s (such as those required by Visual Basic). If a DLL is currently in use, the user will be instructed to reboot the computer to complete the installation. Version and date checking is performed on DLL’s according to Microsoft guidelines. The installer can install reference counted shared files in a company directory. Shared files can be used by multiple applications, and are only replaced by more recently dated files. Only when uninstalling the last program using a shared file will the file be uninstalled. * DOS Batch Support : To satisfy special needs, a batch of MS-DOS commands can be executed before and after both installation and uninstallation. Another batch can be run after the installer exits, perhaps to launch a custom configuration program. Batches of DOS commands can be used to execute, copy, move, rename, and delete files. A full set of environment variables are automatically assigned to assist you. These variables contain the location of the installer/uninstaller, the installation directory, and the location of certain Operating System directories. * Multiple Disk Support : Centurion Setup can create installers that span multiple disks. You can choose from several standard media sizes, or specify any arbitrary capacity. Centurion Setup uses compression and every last byte of the media to ensure that the minimum number of disks are required. Once the installer is built, Centurion Setup can copy it to the media, verifying that all files were copied perfectly. During installation, if each file in the spanned installer is present in the same directory, the user will not be unnecessarily prompted to insert disks. * File Associations : The installer can install an association between a file type and one of your programs, like the way .TXT files are associated with Notepad. Once the file type is associated, the user can double click on any file of that type to launch your program. Or, the user can right click on the associated file for a menu of options. If there happens to be an existing association for the file type, the installer will create a backup that is restored by the uninstaller. Also, you are permitted to install context options for a common file type, such as .TXT files.
Additional Features > Centurion Setup and the installers that it creates run on all versions of Windows® 95, 98, NT4, 2000, ME, XP, 2003, Vista, 2008, and 7. > Installers created by Centurion Setup may be distributed completely royalty-free. > A Centurion Setup installer is bullet-proof and extremely reliable. You will never get a complaint from a customer that the installation program has crashed. > Learning how to use Centurion Setup is a snap. A complete help file is provided, and every control is linked directly to the appropriate spot within the help file. Each control also has balloon help and a context menu. > Files can be added to the installer by dragging and dropping from Windows Explorer. Or simply specify a directory that contains an image of the installation. Or, enter a list of files (wildcards permitted). > If any file cannot be replaced (usually because it is in use), the installer can direct the system to replace the file during the next reboot. The end-user will be informed that they need to reboot to complete the installation. > COM files can be installed and registered with the operating system. This includes ActiveX controls and .TLB type libraries. > Centurion Setup’s installers can be digitally signed. Uncheck the “Use Checksums” box on the Build branch so that the installer will not report that it has been damaged. > The end-user can be forced to agree to an End-User License Agreement (EULA) before installing. > The end-user can be shown a “readme” file before installing. > The end-user is informed when the product is already installed, and if the pre-existing installation is newer, older, or the same version. The end-user can be forced to uninstall a previous installation first. It can also be made mandatory that another product be installed first. > The installer can install to a default location or ask the end-user where the files should be installed. > The installer can create Desktop and/or Start Menu shortcuts to any installed file. Desktop shortcuts can optionally be placed in a folder. Desktop and Start Menu shortcuts can optionally be made available to all users or only the user who installed the product. > The installer can set up a file to be opened (or a program to be executed) every time the machine boots up. > The installer can create a registry key for the application under HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE. > Registry keys are deleted during uninstallation. > The installer can display a bitmap in the background, a transition from one color to another, or use the default window colors of the end-user. The background can optionally cover the taskbar, or leave it visible. There can even be no background at all. > After the installer is built, it can be automatically placed in a .ZIP file. > The installer can require the end-user to enter a password before installation can begin. > The installer can be bloated (with random data) to any size to help discourage piracy. > The installer can refuse to install on certain platforms, such as Windows 95. > Fonts can be installed and registered with the Operating System so that they are available to all applications. The end-user can be given the option to keep the font during uninstallation. > The date and time of installed files are preserved. File attributes (read-only, hidden, etc.) can optionally be preserved. > Installers can be set to expire after a certain date. After the expiration date, the installer will no longer install. > 64-bit applications are supported. > The installer can warn or refuse to install if the user does not have administrator rights. > The installer can loosen the security settings of the product’s directory so that all users will have rights to use it. > The installer verifies its intergrity to ensure that it has not been damaged, altered, or infected by viruses. > The installer can delete existing files based on date or size criteria. This can be useful when installing over old versions of your software. > Installers can be built from the command line (DOS prompt). This allows you to create a desktop shortcut that will build an installer with a click of the mouse. > When the user is unable to uninstall because of a locked file or other problem, the uninstall operation can be resumed later.