Posted on

Can I set a unique text color for a button in a menu interface?

In the Buttons tab in the CD-Menu Creator editor you can set a text color for all texts that are displayed on buttons in a menu interface. But the color that you set in the Buttons tab will be the same for all buttons. Sometimes it can be useful to set another text color for specific button, but is it possible with CD-Menu Creator?
Buttons
The answer is yes. You can set a unique text color (and also a unique background color) for every button in a menu if you want that. In the following step-by-step tip that we have published on our website we explain how to do this:

> Tip: Unique text colors for buttons

Posted on

How do I change language for my setup dialog boxes?

The default language for setup dialog boxes, information messages and error messages in the Visual Installer setup tool is English, but you can use another language if you want. You can change language by choosing the Special – Language menu item in Visual Installer’s editor (see the picture below):

Special - Language

All standard texts are stored in separate language files. An English and German language file is included as default, but it is easy to add your own language file to Visual Installer and use it for your localized installations.

New language file

The tip below shows how to do this:

> Create installations in different languages

The language file only contains standard texts. With standard text we mean texts that are the same regardless of project; for example texts for navigation buttons, and information and error messages. When you enter project specific texts, for example about a specific software, these texts are stored together with the project file (.VIP file). In the following tip we show how to add and change project specific texts:

> Setup Dialog Boxes – How to choose, add text & change image

See also
> A German language file is now included in Visual Installer

Posted on

How to check bitness for an .EXE, .DLL or .OCX file

An .EXE file, a .DLL file and a .OCX file (and some other binary file types) can be compiled as a 32 bit file or a 64 bit file. In many cases you can find out whether the file is 32 bit or 64 bit by using one of the following methods:

• Check the filename of the binary file. Does it have a “64” at the end of the filename (like “mydll64.dll”)? Then it is very likely a 64 bit file.

• Right-click on the file in Windows Explorer, choose Properties, open the Details tab and examine if bitness information is included here. Sometimes it is.

• Is the file located in a 64 bit folder? Then it is very likely a 64 bit file (read more about 64 bit folders in this article on our website).

• The following tip works only for EXE files. When the program file is run, open Windows Task manager and open the Processes tab. Look after the filename for the program. If you find the text “*32” after the filename, it is 32 bit file. Otherwise it is a 64 bit file.

Another method – Check file bitness using Visual Installer’s editor
If none of the methods above work for you, there is another method you can use instead. You can use the Visual Installer editor to check bitness for a file. Follow the steps below to check bitness for a file via Visual Installer’s editor:

1. Start Visual Installer.
2. Add the file that you want to examine to Visual Installer’s file list.
3. Right-click on the file in Visual Installer’s file list.
4. Choose the Show file information menu item in the menu that is shown.

5. Check the information to the right of the Bitness field in the File information window.
    The text will be “32 bit” or “64 bit”.

If the text is “32 bit” to the right of the Bitness field, the file is compiled for 32 bit. If the text is “64 bit” to the right of the Bitness field, the file is compiled for 64 bit. The picture below shows an example for a 32 bit file.

And the picture below shows an example for a 64 bit file.

Use correct destination folders for binary files
Different folders are used in Windows depending of a binary file is a 32 bit or 64 bit. For a file that will be installed to Windows system folder it is very important to put the file in correct system folder, otherwise the file will not be found by the software. For a file that will be installed to Windows program files folder it is recommended to put the file in a program files folder intended for the same bitness. However, the software may work if you put a file in wrong program files folder, if the software is aware of this and can handle the situation.

See also
> Blog: How Visual Installer handles 64 bit folders in Windows
> Tip: How to install a 64 bit program
> Article: The ‘Program Files (x86)’ and ‘SysWOW64’ folders explained

Posted on

An update of Visual Installer 2014 is now available

There is now an update of SamLogic Visual Installer 2014 available. The version number is 10.0.27, and some of the news and improvements in this version are:

• A German language file is now included. Texts in setup dialog boxes and message boxes etc. can now be displayed in German in an easy way. Read more.

• A new script command: UNINSTALL_XRUN. Can be used to run a program during an uninstallation. It works like XRUN, but the command is executed during the uninstallation process. This command is useful if some special processing must be done during the uninstallation process, for example to uninstall a Windows service that was installed during the installation process. The picture below shows an example of usage. Read more.

• A new script command: UNINSTALL_MSIEXEC. Can be used to run an external MSI installation or uninstallation during an uninstallation process. By combining MSIEXEC with UNINSTALL_MSIEXEC you have a nice and easy way to handle both installations and uninstallations of MSI files. The picture below shows an example of usage. Read more.

• Improved error handling when using the code signing functions in Visual Installer.

• Improved error handling when adding files to Visual Installer’s file list through a .DEP file.

• Easier to install side-by-side system files / runtime files like MFC42.DLL.

We have also fixed some bugs and other issues that have been reported. For example:

• Forward slashes in the main destination folder made the installation to fail. Visual Installer now converts forward slashes (“/”) to backslashes (“\”) automatically.

• If the source path was a UNC file path (a file path that starts with “\\”) the installation sometimes failed. Visual Installer now checks that the source path starts with a drive letter.

• Some updates in the English languages file. We have removed some outdated text.

How to download the update
If you have Visual Installer 2014 and a 12 months maintenance plan you can download the update from the following download page:

> Download – Visual Installer 2014 – Latest update

If you have an older version of Visual Installer, for example Visual Installer 2012, you can upgrade to the latest version of Visual Installer from this order page:

> Upgrade to Visual Installer 2014

Posted on

A German language file is now included in Visual Installer

In the latest of update of Visual Installer 2014 (version 10.0.27) we have included a German language file. So you can now use German text in your setup packages in an easy way.

German text

To choose German language to a setup project you must first open the Special – Language menu item in Visual Installer’s editor. And thereafter you choose the GERMAN.LNG language file in the list that is shown.

Some project specific texts must be entered via the Dialog boxes tab in Visual Installer’s editor, just as before. For example text that you want to show in the Welcome dialog box.

See also
> How do I change language for my setup dialog boxes?
> The ‘Program Files’ folder in different languages (Technical Article)

Posted on

How to install and uninstall a Windows service using Visual Installer

The Visual Installer installation tool can be used to install and uninstall a Windows service. By combining the XRUN script command with the new script command UNINSTALL_XRUN this is very easy done. UNINSTALL_XRUN is a new script command that vi added to Visual Installer’s scripting language in the version 10.0.27 update of Visual Installer. UNINSTALL_XRUN runs a program during Visual Installer’s uninstallation process.

XRUN can be used to install (register) the Windows service and UNINSTALL_XRUN can be used to uninstall (unregister) the Windows service. In this new tip on our website we will explain in detail how to install and uninstall a Windows service using the scripting language in Visual Installer 2014 / Professional:

> Tip: How to install a Windows service using script

Posted on

New script command in Visual Installer: UNINSTALL_MSIEXEC

Earlier this year we added the MSIEXEC script command to Visual Installer’s script language. MSIEXEC is used to run an MSI installation from a Visual Installer setup package. Windows Installer is used for the setup process. We have now added a new script command that functions like MSIEXEC but it is run during the uninstallation process instead. The name of the new script command is UNINSTALL_MSIEXEC.

Just like MSIEXEC, the UNINSTALL_MSIEXEC command takes three parameters:

%Filename : Full path to the MSI setup package
%Param : Command line parameters to send to Windows Installer
%Wait : Pause Visual Installer until Windows Installer is ready

By combining MSIEXEC with UNINSTALL_MSIEXEC you will have a nice and easy way to support both installation and uninstallation of a MSI setup package in a single Visual Installer project. The picture below shows how to use these two commands in a Visual Installer project:

As you can see, only two lines with script code is needed to handle both an installation and uninstallation of a MSI setup package. MSI_EXEC is run during the installation process and UNINSTALL_MSIEXEC is run during the uninstallation process.

Tips
We have published tips on our website that explains in detail how to use the MSIEXEC and UNINSTALL_MSIEXEC command. Click on the links below to read the tips:

> Tip: How to run an MSI installation from script
> Tip: How to run an MSI uninstallation from script

Posted on

Visual Installer: How to password protect an installation

In Visual Installer you can protect an installation from unauthorized use in two ways: you can protect it with an license key or you can protect it with a password. License key protection and password protection works in a similar way, but there are differences. Below we explain some of the differences:

– When a user enters a license key, all characters that are entered are also shown on the screen. But if the user enters a password, only stars (*) are shown on the screen. Nobody can look on the screen and see which characters are entered.

– Passwords are case sensitive. License keys are not. So if you specify a password like “Orange“, only “Orange” will be accepted. Not “orange” or “ORANGE“. However, if you specify a license key as “Orange“, the user can enter “Orange“, “orange” or “ORANGE“. All three will be accepted by the setup program.

– Only one unique password can be specified for a specific installation. But if you use license keys, you can specify more than one key. In fact, you can specify thousands of unique license keys, if needed.

How to password protect an installation
Below we will show how to password protect an installation:

1. Start Visual Installer, and open an existing project or create a new one.

2. Open the Dialog boxes tab.

The Dialog boxes tab

3. Select the Password option in the Dialog boxes tab.

The Password option

4. Click on the “…” button to the right of the Password option.

5. Enter a password in the Password text box in the Password dialog box.

The Password dialog box

6. Click OK to close the Password dialog box.

You can now create an installation and run it. The Password setup dialog box (see the picture below) will be shown in the setup wizard when you run the installation, and you can not continue the installation until you enter the correct password.

The Password setup dialog box

More tips
More tips for Visual Installer are available on this web page.

Posted on

Visual Installer: How to change registration order during setup

When you install files using Visual Installer, files are normally registered in the order that they appear in the file list. But sometimes this may create a problem, if one file is dependent of another file, and they are registered in the wrong order. To handle a situation like this there is an option in Visual Installer that allows you to register files in a particular order.

If you want to specify in which order files should be registered, you can choose the List – Register files menu item.

The Register files dialog box is then shown (see the picture below). In this dialog box you can specify the registration order by entering one file path per line. Each line must contain an installation path to every file that you want to have registered in another order than the default order. You can use variables in the file path (for example: %SYSDIR\MyDLL1.dll).

Line 1 is registered first. Then line 2. Then Line 3. Then line 4. Etc.

All files that you specify in the Register files dialog box are registered before any file in the file list is registered. So the list in Register files dialog box is handled first.

More information
Additional information is available in Visual Installer’s Help documentation. Click on the Help button in the Register files dialog box to obtain more information.

More tips
More tips for Visual Installer are available on this web page.