Determining the Application Compatibility Fix to Apply
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
The tables in this section include descriptions of some compatibility problems that might occur in applications written for earlier versions of Windows, along with the application compatibility fixes that resolve them. As you test applications and encounter compatibility problems, these tables can help you isolate the most appropriate application compatibility fix to apply. If you are still in the planning phase, skip to "Identifying Strategies for Resolving Special Problems" later in this chapter for additional information on resolving problems.
In some cases, you might need to look at multiple tables to find the application compatibility fix that resolves your compatibility problem. For example, you might want to review both color palette issues (Table 3.12) and display issues (Table 3.13) if elements in the application window are not displayed correctly.
Table 3.9 identifies the application compatibility fixes that you can apply for 16-bit applications that have compatibility problems.
Table 3.9 Application Compatibility Fixes for 16-Bit Application Problems
| Symptom | Application Compatibility Fix |
|---|---|
The installation program or application expects to find Microsoft Windows 95 or Microsoft Windows 98 running. |
WOWCFEX_PLATFORMVERSIONLIE |
The installation program or application expects to find Microsoft Windows NT running. |
WOWCF2_HACKWINFLAGS |
The installation program or application expects to find Service Pack 2 installed. |
WOWCFEX_SP2CSDVERSIONLIE |
The application window is hidden by a second window. |
ForceSeparateVDM |
The application becomes unresponsive. |
WOWCF_NOWAITFORINPUTIDLE |
The application behaves unpredictably. |
WOWCF_USER_DDENOSYNC |
A minimized application cannot be restored. |
WOWCF2_FIXLUNATRAYRECT |
Messages are displayed behind the application. |
WOWCF2_SETFOREGROUND |
A message indicates that a file has not been found. |
WOWCF2_SYNCSYSFILE |
A message indicates that the application requires 256 colors. |
WOWCFEX_DISPMODE256 |
A message indicates that the application requires 256 colors. |
WOWCFEX_EATDEVMODEMSG |
A general protection fault (GP fault) occurs. |
WOWCFEX_FORCEINCDPMI |
The application returns a divide-by-zero error. |
WOWCF2_DELAYTIMEGETTIME |
The Help file does not open. |
WOWCFEX_USEWINHELP32 |
Table 3.10 identifies the application compatibility fixes that you can apply when the application cannot be removed successfully.
Table 3.10 Application Compatibility Fixes for Application Removal Problems
| Symptom | Application Compatibility Fix |
|---|---|
The application returns the "<DirName> refers to a location that is unavailable" error message when an application is removed. |
DelayShowGroup |
During uninstallation, the application returns an error message stating that registry entries cannot be removed. |
LUARedirectReg_Cleanup |
Files are left behind after an application has been uninstalled. |
LUARedirectFS_Cleanup |
Files are left behind after an application has been uninstalled. |
MoveWinInitRenameToReg |
Table 3.11 identifies the application compatibility fixes that you can apply when problems occur with the Clipboard when you perform copy and paste operations.
Table 3.11 Application Compatibility Fixes for Clipboard Problems
| Symptom | Application Compatibility Fix |
|---|---|
The application does not perform copy or paste operations correctly. |
EmptyClipboardtoSet |
When bitmaps are copied to or from the Clipboard, the application returns the "Access violation" error message. |
EmulateClipboardDIBFormat |
Table 3.12 identifies the application compatibility fixes that you can apply when the color palette is distorted or when components of the application window are displayed in the wrong color.
Table 3.12 Application Compatibility Fixes for Color Palette Problems
| Symptom | Application Compatibility Fix |
|---|---|
The application window does not display as expected at startup and during execution. |
IgnoreHungAppPaint |
The application changes the system colors. |
IgnoreSysColChanges |
After the application switches tasks or modes, colors change. |
PaletteRestore |
A palette error occurs. |
EmulateGetDeviceCaps |
A palette error occurs when you quit the application, and it returns the "PM_free():Allocation 001B4498 failed integrity check! (InitPalette)" error message. |
EmulateGetDeviceCaps |
The application returns the "Unhandled Error: User Category 10 Fatal Error: Code 2 Palette Error" message. |
EmulateDeleteObject |
The palette is distorted. |
ForceDefaultSystemPaletteEntries |
After the application switches tasks or modes, images appear corrupted. |
PaletteRestore |
After the application switches tasks or modes, the background turns black. |
PaletteRestore |
After the application switches tasks or modes, buttons disappear. |
PaletteRestore |
Table 3.13 identifies the application compatibility fixes that you can apply when the application has problems with the screen display, such as incorrect screen resolution and color quality settings.
Table 3.13 Application Compatibility Fixes for Display Problems
| Symptom | Application Compatibility Fix |
|---|---|
The application starts up in a 640 x 480 pixel window and does not switch to a full screen. |
Force640x480 |
The application starts up in a 640 x 480 pixel window and does not switch to a full screen. |
Force640x480x16 |
The application starts up in a 640 x 480 pixel window and does not switch to a full screen. |
Force640x480x8 |
Most of the application window runs off the desktop. |
LazyReleaseDC |
The application returns a message that indicates that the display is corrupted. |
Force8BitColor |
Graphics are corrupted in full-screen mode. |
ForceDirectDrawEmulation |
The application returns a message that indicates that 256 colors are required. |
Force8BitColor |
The application returns a message that indicates that 256-color mode is required. |
ForceDisplayMode |
Introductory videos do not play. |
ForceDirectDrawEmulation |
The taskbar is visible when the application is in full-screen mode. |
HideTaskBar |
When the application switches modes, the screen becomes blank. Pressing ALT+TAB restores the video display. |
IgnoreNoModeChange |
When the application closes, the system display mode changes. |
ForceTemporaryModeChange |
When the application closes, the display mode is not restored. |
EmulateUSER |
Table 3.14 identifies the application compatibility fixes that you can apply when the application fails during execution.
Table 3.14 Application Compatibility Fixes for Execution Problems
| Symptom | Application Compatibility Fix |
|---|---|
Access violations occur regularly during application execution. |
DisableBoostThread |
The application shuts down unexpectedly during execution. |
HeapIgnoreMoveable |
The application shuts down unexpectedly during execution. |
HeapLookasideFree |
The application shuts down unexpectedly during execution. |
HeapPadAllocation |
The application shuts down unexpectedly during execution. |
HeapValidateFrees |
The application shuts down unexpectedly when it accesses configuration or user settings. |
LUARedirectFS |
The application periodically shuts down unexpectedly, typically at the same interval at which the screen saver is set to activate. |
DisableScreenSaver |
Access violations occur during normal functioning as the heap becomes corrupted, causing the application to become unresponsive. |
EmulateHeap |
An access violation occurs when the application switches contexts. |
HeapForceGrowable |
The application returns a "Runtime error 6" message when you install add-ons to the application. |
IgnoreVBOverflow |
The application returns a "Runtime error 6" message when you attempt to use Help. |
IgnoreVBOverflow |
Executable programs designed to run at Windows startup, such as application toolbars, do not run for all users. |
LUARedirectReg |
A default screensaver cannot be applied. |
MoveIniToRegistry |
Table 3.15 identifies the application compatibility fixes that you can apply when access violations occur while an application is exiting.
Table 3.15 Application Compatibility Fixes for Exit Problems
| Symptom | Application Compatibility Fix |
|---|---|
Access violations occur when the application is closed. |
EmulateHeap |
Access violations occur when the application is closed. |
IgnoreFreeLibrary |
Access violations occur when the application is closed. |
IgnoreLoadLibrary |
Access violations occur when the application is closed. |
IgnoreCRTExit |
Access violations occur when the application is removed. |
IgnoreCRTExit |
Access violations occur when dialog boxes are canceled. |
IgnoreCRTExit |
Table 3.16 identifies the application compatibility fixes that you can apply when the application has file access problems.
Table 3.16 Application Compatibility Fixes for File Input/Output Problems
| Symptom | Application Compatibility Fix |
|---|---|
During installation or operation, the application reports the incorrect amount of available disk space. |
EmulateGetDiskFreeSpace |
When a user with a DBCS (double-byte character set) name starts the application, the application returns an error message indicating that there are problems with the user’s temp path. |
RedirectDBCSTempPath |
The application returns the "The system file does not exist" error message. |
RedirectWindowsDirToSystem32 |
When you attempt to open certain Audio Video Interleaved (.avi) files, the application returns the "Access violation" error message. |
EmulateWriteFile |
When you attempt to open a file, the application stops responding. |
RemoveOverlappedFlagFromCreateFile |
When you attempt to open a file, the application says that the file is read-only. |
RemoveReadOnlyAttribute |
When you attempt to open a folder, the application says that the folder is read-only. |
RemoveReadOnlyAttribute |
When you move files or projects, the application returns the "Access violation" error message. |
ChangeAuthenticationLevel |
The application returns the "File mapping not created" error message. |
CorrectCreateEventName |
The application returns the "File mapping not created" error message. |
EmulateCreateFileMapping |
When accessing a CD, the application returns either the "Unable to locate files" or the "Unable to install" error message. |
EmulateCDFS |
When accessing a CD, the application quits without generating an error message. |
RemoveNoBufferingFlagFromCreateFile |
The application returns the "Files do not exist" error message. |
EmulateEnvironmentBlock |
Files are not found or error messages or paths are truncated. |
EmulateGetCommandLine |
The Uninstall command fails to remove files and folders from program files. You need to use this fix with the CorrectFilePaths compatibility fix (in Table 3.26). |
CorrectFilePathsUninstall |
Table 3.17 identifies the application compatibility fixes that you can apply when focus within an application is not maintained correctly.
Table 3.17 Application Compatibility Fixes for Focus Problems
| Symptom | Application Compatibility Fix |
|---|---|
When the application starts, the configuration window is minimized. |
ForceKeepFocus |
The application window becomes inactive. |
ForceApplicationFocus |
A message box becomes inactive. |
ForceMessageBoxFocus |
Table 3.18 identifies the application compatibility fixes that you can apply when graphical elements in the application are not displayed correctly.
Table 3.18 Application Compatibility Fixes for Graphics Control Problems
| Symptom | Application Compatibility Fix |
|---|---|
When the application loads, the graphics become corrupted. |
EmulateBitmapStride |
When a minimal installation of the application is performed, graphics are missing and video clips do not play. |
ForceCDStop |
When the application starts, the screen becomes blank. |
ForceSimpleWindow |
When the application starts, the screen becomes blank. |
EmulateDirectDrawSync |
When the application starts, the screen becomes blank. |
WinExecRaceConditionFix |
Either the introductory video does not appear, or the application won’t play in hardware mode. |
ForceSimpleWindow |
Inactive windows do not display as expected. |
AlwaysActiveMenus |
Clicking on an active bitmap image causes the application to become unresponsive. Bitmap images do not load. |
CorrectBitmapHeader |
Instead of an icon, a shadowed block appears. |
CorrectCreateIcon |
When the application loads bitmaps, they do not display as expected. |
CorrectCreateSurface |
The characters of Asian fonts do not display correctly. |
CorrectFarEastFont |
Pressing ESC returns you to a blank window rather than to the application menu. |
DelayWin95VersionLie |
Menu or list box contents do not appear or they do not appear as expected. |
DisableAnimation |
When you enable the FilterKeys option, the graphics do not display as expected. |
DisableFilterKeys |
The application alternates between the currently applied themed view and the nonthemed view. |
DisableThemes |
When the application runs under new themes, the standard message boxes do not appear. |
DisableThemes |
The system buttons (Minimize and Close) do not work. |
DisableThemes |
The title bar of the application window hides the toolbars. |
DisableThemes |
Dialog boxes are truncated. |
DisableThemes |
Buttons overlap. |
DisableThemes |
When the application window is resized, it does not display as expected. |
DisableThemes |
Text does not appear in the menu or in message boxes. |
EmulateDrawText |
The application fails when it attempts to display the menu or message boxes. |
EmulateDrawText |
Bitmaps in the Autorun dialog boxes do not display as expected. |
EmulateGetProfileString |
The application scrolls text too rapidly. |
EmulateGetStringType |
Typed text or text that should be displayed on the menu buttons or on labels does not appear. |
EmulateTextColor |
The application does not display graphics. |
EnlargeGetObjectBufferSize |
A file cannot be inserted as an icon into another file. Attempting to do so produces an "Out of memory or system resources" error. |
ExtractAssociatedIcon |
An application’s attempts to access menus, specifically the File menu, produces an "Access violation" error. |
FailObsoleteShellAPIs |
The menu and toolbar buttons are the wrong color. |
FakeThemeMetrics |
Typed text or text that is displayed on the menu buttons or in labels is the wrong color. |
EmulateTextColor |
Menu commands are replaced with black boxes. |
ForceDefaultSystemPaletteEntries |
The application fails when it returns to the main menu. |
HeapDelayLocalFree |
The mouse pointer appears unexpectedly. |
HideCursor |
A button or other control is corrupted. |
LoadComctl32Version5 |
Resizing a window causes the icons and other visual elements to disappear. |
NoGdiBatching |
The application window flickers and is repeatedly refreshed. |
NoShadow |
The user interface is unresponsive. |
RemoveInvalidW2KWindowStyles |
After you quit the application, the system cursor is not restored. |
RestoreSystemCursors |
Images, and the text associated with them, are displayed backwards. |
UnMirrorImageList |
When you insert an image file, the application returns an "Access violation" error message. |
IgnoreLoadLibrary |
When you modify an image, an access violation occurs. |
DisableThemes |
Table 3.19 identifies the application compatibility fixes that you can apply when the application fails to install.
Table 3.19 Application Compatibility Fixes for Installation Problems
| Symptom | Application Compatibility Fix |
|---|---|
When you attempt to install the application, the application returns the "ComponentMoveData" error message. |
CorrectOpenFileExclusive |
When you attempt to perform a default installation, text in the Destination Directory dialog box is unreadable. |
EmulateGetProfileString |
When you attempt to install the application, the application returns "The application or DLL <drive>:\<%windir%>\system32\ole2.dll is not a valid Windows image" error message. |
CorrectVerInstallFile |
When you attempt to install an application using an Autorun file, the installation fails. |
EmulateCreateProcess |
Attempts to install the application with InstallShield version 5.0 fail when user names with East Asian characters are used. |
IgnoreOemToChar |
The application appears to become unresponsive during setup because a dialog box containing an error message occupies space beyond the visible desktop. |
KeepWindowOnMonitor |
The application fails to install. |
RedirectEXE |
Setup fails unexpectedly. |
EmulateLZHandles |
On a dual processor machine, an application fails during installation or when you attempt to start it. |
SingleProcAffinity |
The application returns the "<x> not installed correctly, please install again" error message, where x is an application component. |
SyncSystemAndSystem32 |
The application cannot find a path during installation when a double-byte character set (DBCS) user name is used. |
HandleDBCSUserName |
The application cannot find a path during installation when a DBCS user name is used. |
HandleDBCSUserName2 |
Access violations occur during installation. |
FileVersionInfoLie |
During installation, when the application is searching for the presence of previous versions, an access violation occurs. |
LimitFindFile |
When the application is installed, an access violation occurs. |
RemoveBroadcastPostMessage |
When the application is installed, an access violation occurs. |
IgnoreFreeLibrary |
The application does not install from an Autorun file, causing an access violation. |
HideDisplayModes |
During installation, the application returns the "Cannot open files" error message. |
FailOpenFile |
After you run the setup program, the application returns the "Access violation" error message. |
DuplicateHandleFix |
The application returns the "Setup32: This product does not support Windows NT" error message. |
DeRandomizeExeName |
The application returns the "Unknown button state" error message. |
DisableW2KOwnerDrawButtonStates |
You are notified that a certain DLL is required for installation. |
EmulateGetProfileString |
The application returns the "Must be an administrator to install" error message. |
ForceAdminAccess |
The Configuration menu is blank. After the application’s setup program finishes, InstallShield fails. |
ForceWorkingDirectoryToEXEPath |
If you do not register the application, the application does not start. |
HeapLookasideFree |
The application fails to start. |
RedirectEXE |
When the application is started, an access violation occurs. |
RemoveBroadcastPostMessage |
The system fails to restart after you confirm the application’s restart request. |
EnableRestarts |
The application fails to register services. |
RedirectEXE |
The Readme.txt file cannot be opened. |
HandleRegExpandSzRegistryKeys |
Table 3.20 identifies the application compatibility fixes that you can apply when entering data with the keyboard or using certain key sequences causes problems.
Table 3.20 Application Compatibility Fixes for Keyboard Input Problems
| Symptom | Application Compatibility Fix |
|---|---|
When you attempt to type in logon information, the application returns the "Unexpected error" message. |
AliasDXDC |
The application does not correctly display the shortcut keys. |
DisableKeyboardCues |
Using the ALT+TAB key combination causes the application window to become blank. |
IgnoreAltTab |
The application becomes unresponsive when you use the ALT+TAB key combination. |
IgnoreAltTab |
The application stops responding when you use the SHIFT key, the CTRL key, or the ALT key 5 times or more in succession. |
DisableStickyKeys |
The keyboard locks up during normal operation. |
EmulateUSER |
The keyboard is sluggish or doesn’t function at all, and the system becomes generally unresponsive. |
LowerThreadPriority |
Table 3.21 identifies the application compatibility fixes that you can apply when the application has problems with sound, graphics, animation, or video.
Table 3.21 Application Compatibility Fixes for Multimedia Problems
| Symptom | Application Compatibility Fix |
|---|---|
Sounds do not play. |
DelayWinMMCallback |
No sound or limited sound plays. |
CorrectACMStreamOpen |
Sounds do not play because the application does not detect sound devices. |
AddWritePermissionsToDeviceFiles |
The application cannot use the sound hardware, so it returns the "Sound hardware already in use" error message. |
AddWritePermissionsToDeviceFiles |
Sounds do not play with Audio Compression Manager drivers. |
CorrectACMArgs |
The application returns the "Active Movie Control: An object or name was not found" error message. |
CorrectActiveMoviePath |
A message indicates that the sound device driver failed to load. |
CorrectSoundDeviceId |
The sound loops perpetually, and the application does not always respond to shutdown requests. |
EmulatePlaySound |
Audio Video Interleaved (.avi) files continue to run behind the menu screen. |
ForceAVIWindow |
The cursor freezes momentarily during background music changes. |
IgnoreMCISTOP |
The application attempts to send sound to the wrong device (usually to an audio card instead of to the desired USB devices). |
WaveOutUsePreferredDevice |
Table 3.22 identifies the application compatibility fix that you can apply when network connections cannot be set up correctly.
Table 3.22 Application Compatibility Fix for a Network Connection Problem
| Symptom | Application Compatibility Fix |
|---|---|
The application automatically selects Serial Connection when you attempt to select a network connection. |
DirectPlayEnumOrder |
Table 3.23 identifies the application compatibility fix that you can apply when permission problems occur.
Table 3.23 Application Compatibility Fix for a Permissions Problem
| Symptom | Application Compatibility Fix |
|---|---|
Insufficient user rights produce errors. |
LUATrackFS |
Table 3.24 identifies the application compatibility fixes that you can apply when printing does not work correctly.
Table 3.24 Application Compatibility Fixes for Printing Problems
| Symptom | Application Compatibility Fix |
|---|---|
Access violations occur when the application starts or when it searches for printers. Consequently, the application returns error messages when you attempt to find, select, or print to a printer. |
EmulatePrinter |
The application shuts down unexpectedly when you attempt to print. |
ForceAnsiWindowProc |
Table 3.25 identifies the application compatibility fixes that you can apply when invalid registry entries cause problems.
Table 3.25 Application Compatibility Fixes for Registry Problems
| Symptom | Application Compatibility Fix |
|---|---|
The application makes a call to a statically loaded .dll file that has not yet been loaded. |
InjectDll |
When you use a limited user account (LUA), the application returns the error message "Failed to update system registry. Please try using RegEdit." |
LUARedirectFS |
Table 3.26 identifies the application compatibility fixes that you can apply when Start menu entries or shortcuts are not created correctly or do not work correctly.
Table 3.26 Application Compatibility Fixes for Start Menu and Shortcut Problems
| Symptom | Application Compatibility Fix |
|---|---|
Shortcuts are not created for all users. |
CorrectFilePaths |
Shortcuts are not created for all users. |
LUARedirectReg |
A desktop shortcut is not created. |
ForceAnsiGetDisplayNameOf |
Shortcuts are not removed for all users. |
CorrectFilePathsUninstall |
A valid and an invalid shortcut appear in the Start menu during application installation. |
DelayShowGroup |
The application does not appear on the Start menu. |
ProfilesEnvStrings |
The application does not appear in the Start menu. |
ProfilesGetFolderPath |
The application does not appear in the Start menu. |
ProfilesRegQueryValueEx |
Shortcuts do not appear on the desktop. |
ProfilesEnvStrings |
Shortcuts do not appear on the desktop. |
ProfilesGetFolderPath |
Shortcuts do not appear on the desktop. |
ProfilesRegQueryValueEx |
Table 3.27 identifies the application compatibility fixes that you can apply when problems occur during application startup or during the startup of a process initiated by the application.
Table 3.27 Application Compatibility Fixes for Startup Problems
| Symptom | Application Compatibility Fix |
|---|---|
The setup program fails to install the application. |
HandleWvsprintfExceptions |
The application cannot load. |
IgnoreDebugOutput |
The application does not start after it is installed. |
EmulateGetStdHandle |
The application does not start, but displays error messages or indicates that an access violation has occurred. |
StackSwap |
When starting, the application causes an access violation. |
HeapPadAllocation |
When you attempt to start the application, it returns an error message indicating that the application is not installed. |
FailGetStdHandle |
When you attempt to start the application, it returns an error message indicating that the application must be installed. |
EmulateGetStdHandle |
The application fails to start, and returns an error message. |
EmulateVerQueryValue |
When the application is started directly after setup is complete, it returns the "No Disc Inserted" error message because it does not detect the CD drive. |
AddWritePermissionsToDeviceFiles |
An access violation occurs when the application starts. |
EmulateGetDeviceCaps |
When you start the application, it returns the "Computer memory full" error message. |
GlobalMemoryStatusLie |
When you attempt to start the application, it returns the "Component failed to be located" error message. |
VirtualRegistry |
The application stops responding immediately after starting. |
HideDisplayModes |
The application quits immediately after starting. |
HeapClearAllocation |
The application becomes unresponsive after starting. |
AddWritePermissionsToDeviceFiles |
The application becomes unresponsive or closes unexpectedly shortly after starting. |
EmulateFindHandles |
When the application starts, it returns an exception error. |
IgnoreCoCreateInstance |
When the application starts, it returns the ".dll not compatible with the application" error message. |
LoadLibraryCWD |
A component or file is not correctly registered or is missing, or the application returns an "Invalid" error message. |
CorrectFilePathInSetDlgItemText |
When the application starts, a window containing only a cursor opens. |
IgnoreException |
The application returns the "Component failed to initialize" error message. |
DelayDllInit |
When you start the application, it automatically minimizes, but sound effects continue to play. The application might or might not run when selected from the taskbar. |
NoGhost |
Runtime errors occur when you start the application or when you start specific components. |
SetEnvironmentVariable |
When the application expects to find a joystick, it quits unexpectedly. |
EmulateJoystick |
When you attempt to start executable programs, such as Scandisk, Disk Defragmenter, or Help, the application displays an error message. |
EmulateMissingEXE |
When the application runs on a high-end machine, its window is blank or it displays an "Access violation" error message. |
EmulateSlowCPU |
When you attempt to start two instances of the application, the application returns an error message. |
EmulateToolHelp32 |
Starting a Safedisk program causes access violations. |
FailCloseProfileUserMapping |
Logging on and starting services take a long time. |
FixServiceStartupCircularDependency |
The application returns a message asking that the correct CD be put in the drive or stating that there is no CD in the drive. |
ForceCDStop |
The application fails to run its startup movie (.avi file) and shuts down. |
ForceCoInitialize |
The application returns the "DirectX does not support the Windows version on the system" error message. |
ForceDXSetupSuccess |
The application does not run in hardware mode. |
ForceSimpleWindow |
The Autorun menu does not appear. |
CorrectBitmapHeader |
The Autorun dialog box does not get refreshed after the application is installed, so that the option to start the application is still disabled. |
HandleAPIExceptions |
The application becomes unresponsive immediately after starting. |
IgnoreException |
The application displays message boxes that give debugging or other extraneous information. |
IgnoreMessageBox |
The application fails to start or performs slowly. |
IgnoreScheduler |
The application does not start, and it returns the "Desktop is running in 0 bit color mode" error message. |
LazyReleaseDC |
The application does not start, or you get error messages when you attempt to start it. |
MapMemoryB0000 |
When the application is run by a user other than the user who installed it, it displays error messages such as "Cannot find <X>" (where x is a folder or file that does exist on the system) or "<X> components were not found or are corrupt, run setup." |
PopulateDefaultHKCUSettings |
When you start the application, it returns the "Not a valid Win32 application" or "Unable to run the command" error message. |
RecopyExeFromCD |
An access violation occurs when you attempt to start another program through the application by linking to Windows components (Internet Explorer Web Links or Windows Explorer folders, for example). |
RemoveDDEFlagFromShellExecuteEx |
When the application attempts to start Windows components (such as Microsoft Paint), it returns the "File or program cannot be found" error message. |
SearchPathInAppPaths |
The application returns the "Files cannot be found or do not exist" error message. |
SetEnvironmentVariable |
Entry-point errors occur for functions within earlier versions of Cryptsys and DirectX DLLs. |
TerminateExe |
The application returns the error message "WinG32.dll has been incorrectly installed in the system folder. Please move it to the System32 folder." |
WinG32SysToSys32 |
Table 3.28 identifies the application compatibility fixes that you can apply when the telephone dialer does not work correctly.
Table 3.28 Application Compatibility Fixes for Telephony Application Programming Interface (TAPI) Problems
| Symptom | Application Compatibility Fix |
|---|---|
A runtime error occurs in Mfc40.dll when the call is disconnected. |
IgnoreTAPIDisconnect |
The phone dialer does not hang up. |
IgnoreTAPIDisconnect |
Table 3.29 identifies the application compatibility fixes that you can apply when the application expects a version of Windows that is not available.
Table 3.29 Application Compatibility Fixes for Versioning Problems
| Symptom | Application Compatibility Fix |
|---|---|
The application requests that Windows 95 be installed. |
Win95VersionLie |
The application requests that Windows 98 be installed. |
Win98VersionLie |
The application requests that Windows NT 4.0 Service Pack 5 be installed. |
WinNT4SP5VersionLie |
The application requests that Windows 2000 be installed. |
Win2000VersionLie |
The application requests that Windows 2000 Service Pack 1 be installed. |
Win2000SP1VersionLie |
The application requests that a previous version of DirectX be installed. |
Win2000VersionLie |
The application requests that a previous version of DirectX be installed. |
WinNT4SP5VersionLie |
The application requests that a previous version of DirectX be installed. |
Win2000SP1VersionLie |
The application reports that it will not function on a Windows NT system. |
Win95VersionLie |
The application reports that it will not function on a Windows NT system. |
Win98VersionLie |
Table 3.30 identifies the application compatibility fixes that you can apply when application windows do not work correctly.
Table 3.30 Application Compatibility Problems for Window Management Problems
| Symptom | Application Compatibility Fix |
|---|---|
An unexpected dialog box appears. |
ForceShellLinkResolveNoUI |
A dialog box does not come to the foreground; you must press ALT+TAB to see it. |
GiveupForeground |
Table 3.31 includes miscellaneous application compatibility fixes that do not fit within any other category.
Table 3.31 Application Compatibility Fixes for Miscellaneous Problems
| Symptom | Application Compatibility Fix |
|---|---|
A spawned process fails to operate properly, although the parent process functions normally. For example, Setup.exe works correctly, but the spawned process, Setup2.exe, fails. |
PropagateProcessHistory |
The application does not display system information properly when you use the System Info button in the About dialog box. |
RemoveIpFromMsInfoCommandLine |