Configuring for “Compatibility Mode”

Under both 32-bit and 64-bit editions of Windows 7 and Server 2008 any installer for a “legacy” 32-bit application (such as Syscob Export-It and Export-It Plus) must be run by the Administrator user in “Compatibility Mode” for an earlier Windows® edition.  This requirement is the only way that Windows 7, or a later edition, knows to allow traditional access rights and privileges by the installer user.  This topic explains how to configure an installer (which includes both the initial “installs” and the Syscob “Icon & Rego” utility as well as update installers) so that it will execute properly on a 32-bit or 64-bit edition of Windows 7, Vista, Server 2008 or Server 2011.

Microsoft restricts the specification of the necessary “Compatibility Mode” and “Privilege Level” properties to executables that reside on the computer itself — as a means to prevent vulnerability to external threats such as a virus or trojan.  That means that installers cannot be run from a CD, from an external or network drive or from the web.  So the first step that must precede use of a “legacy” 32-bit installer is to copy, or download, it to a “local” hard drive.

Setting Installer Properties

Once an “installer” application is copied to the local hard drive (the install for Export-It version F-33 is used in this example) the first step is to open Windows Explorer then browse to the executable and right-click on it in order to access its pop-up context menu.  Then select Properties as can be seen in this capture:

When the file Properties dialog opens go to the Compatibility tab and select “Run this program in compatibility mode for: Windows XP (Service Pack 3)” as seen in the next image.  If there is no Compatibility tab then the executable is either not on a physical non-removable drive or this is not an executable file (and installers are executables) — so copy the file to a local HDD before performing this step:

After selecting the compatibility mode click on the “Run this program as an Administrator” checkbox to enable installer access to the Registry, Windows® directory, Desktop and Start button programs menu:

The dialog will now look like the sample above, but these property changes are only for the current user!  Yet a Syscob installer makes changes that affect all the users of the computer so press the Change settings for all users button to ensure that the installer runs this way for all users (this is especially critical for the “Icon & Rego” utility):

Make the same changes (i.e. “Run this program in compatibility mode for: Windows XP (Service Pack 3)” and “Run this program as an Administrator”) then press the OK button to save the “all users” changes:

Finally, back in the original Properties dialog, press the OK button to save the changes which have been made:

At this point the installer program may be run properly on either 32-bit or 64-bit editions of Windows® software.

Avoiding Problems

Windows 7, Vista, Server 2008 and Server 2011 have a number of new security features that are poorly understood by users and many IT staff members.  Most frequently the fact that a member of the Administrators security group no longer has true administrative rights, unless the Linking Security Tokens “fix” has been applied, is only noticed afterwards when some application raises unusual error dialogs.  The second most common issue arises when a user, or IT staff, simply perform a “no brain” install in the manner in which they have always done it in the past.

The purpose of the four topics in this group is to avoid such an embarrassment by describing, in advance, what needs to be done to assure the successful use of a “legacy” application (i.e. one that can run on previous editions of Windows® software).  Syscob strongly recommends that the time be taken to read and understand the four web pages in this group of topics.  That will provide the best insurance for a succesful installation and an acceptable user experience with minimal effort.

Compatibility Mode

Under Windows Vista, XP, 2000 and NT4 a member of the Administrators security group had full adminstrative privileges and access rights (for Windows 95, 98, 98SE and ME admin capability was inherent).  Therefore most instructions for the installation or update of software included a statement like “this install must be done by a menber of the Administrators group.”  But that is no longer sufficient under Windows 7 and later editions.  In addition to the limits imposed on Administrators the new Windows® editions also require that all “legacy” application installers be run using the new “Compatibility Mode” feature.

Executing an installer in “Compatibility Mode” tells Windows® that the program needs access to areas that are now more tightly constrained by the new security paradigms.  And, in the case of 64-bit editions, it tells the system that the install should default to the new \Program Files (x86) folder where 32-bit programs that run under “WoW64” [Win32 on Win64] are normally installed.  That is not critical for Syscob applications, which do not install software into the traditional \Program Files folder, but the flagging of 32-bit excutables which also occurs when an install is done in “Compatibility Mode” is of extreme importance to avoid future problems for the application user.