Windows 7 is internally tagged as Version 6.1, and is essentially an update to Windows Vista (Version 6.0). This is conceptually similar to XP (5.1) as the update to Windows 2000. Just as XP was more widely accepted than 2000, 7 appears to be on a similar track to be generally accepted more than Vista.

IMG software compatible with Windows 7 is now available via the downloads pages or on the IMG Products Disc.

The following is some notes regarding IMG software and Windows 7

• The "Insert & Go" feature via the Autorun/Autoplay for USB drives has been disabled in Windows 7 (for security purposes). We tend to think there may be registry updates, or other options available to address this in the future. As we are made aware of any options for customers, we will update them here. Currently you need to browse the drive, and run the IMGSTART.EXE manually.
• Older versions (pre Release 4 in 2009) are not supported in Windows 7. There may be options via compatibility settings, but due to the persistence of these settings, we do not recommend you enable them. See below for notes and the registry location info. In general, what can happen is you configure an older version, and set compatibility settings, and then when you install the REAL compatible version, the persistence of these settings makes the REAL compatible software fail.

The other contributing factor is the "Program Compatibility Assistant" (PCA), which records information based on its own criteria, and in some cases, may be be overreaching and causing a problem. The following is an excerpt from Microsoft notes, and registry information regarding the actions of the PCA - the preferred approach would be to use regedit, check these registry entries, and delete any references to IMG Vista compatible products.
Managing settings made by PCA - The compatibility modes will be applied to programs by setting a registry key under HKEY_LOCAL_MACHINE \ Windows NT \ CurrentVersion \ AppCompatFlags \ Layers with key name = "full path to the exe" and string value = "name of the compatibility mode being applied"
The registry key will be set under HKEY_LOCAL_MACHINE to apply the solutions to be effective for all users except for the scenario where the ELEVATECREATEPROCESS compatibility mode is applied automatically before the PCA dialog shows up. In that scenario, the registry key will be set under HKEY_CURRENT_USER and the solution will only be effective for the current user.
Refer to these locations:
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows NT \ CurrentVersion \ AppCompatFlags \ Compatibility Assistant \ Persisted, and
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows NT \ CurrentVersion \ AppCompatFlags \ Layers

The Virtual Store misdirection issue is a solution to the problem where the limited user cannot save/write to files under the \Program Files location, but older software may require this. To resolve this, files are actually saved in the user's Application Data area - \Users\[username]\AppData\Local\VirtualStore\Program Files directory. This, however, creates a new problem and potential source of confusion, in that a user can be looking at what they think is in the \Program Files\MyProg folder, but in reality, they are being misdirected, and actually looking at their own copy in \Users\[username]\AppData\Local\VirtualStore\Program Files\MyProg location. This can cause problems in the program itself (since it is looking in the \Program Files location), or to other users (since they don't have access to the file modified by a different user). It may be enlightening to see what files/programs are using this virtual store location.

Information on Windows

Windows Vista Information
Windows 7 Information
Windows 8 Information
Windows 10 Information

Notes:

• Depending on product, release version, OS version, and specific technical issue, some tech items are very specific, and some may span to other products/versions
• Downloadable files can also be accessed by anonymous FTP at ftp://downloads.imgpresents.com
• Older files are moved into a separate archive location - see notes/details/new location in *.archived.txt text file

• Return to Technical Support

As seen in ...