This compatibility fix addresses two separate issues with the PROCESSENTRY32 API. The first converts the standard Windows XP usage of the szExeFile field from the image name to the Windows 9x style, which includes the full path and executable name. The second issue addressed is that of the cntUsage field, which on Windows 9x is always non-zero, and on Windows XP is always zero. Applies to: Windows 95, Windows 98
This compatibility fix addresses issues that may be encountered when an application uses various API calls to verify if the ...
This compatibility fix addresses issues with APIs that may not gracefully handle receiving bad parameters. Currently, this ...
This compatibility fix addresses potential problems with applications that may need help with heap memory free calls. The ...
This compatibility fix addresses the problem of contention with the CD drive. Some applications may try to access the CD ...
This compatibility fix addresses two separate issues with the PROCESSENTRY32 API. The first converts the standard Windows ...
This compatibility fix adjusts the CreateWindow API parameters to make only very simple windows. This is useful for fixing ...
This compatibility fix allocates additional memory for every allocation made through the HeapAlloc API. This fix is command ...
This compatibility fix applies to applications that may not correctly handle broadcast messages to their window process. ...
This compatibility fix applies to applications that require a specific resolution to run. It takes a command line to specify ...