This compatibility fix modifies the pagefile and physical memory status so that it reports 2 gig of pagefile and 1 gig of ...

This compatibility fix modifies the pagefile and physical memory status so that it reports 2 gig of pagefile and 1 gig of physical memory. This is for use with 64 bit machines which can have more than 2 gig of memory. A COMMAND_LINE can be added to specify a different pagefile and physical memory size. Example: COMMAND_LINE="2147483647,536870911" would set a 2 gig pagefile and a 512 meg physical memory. You should not, of course, use negative numbers or a number higher than 2 gig.

This compatibility fix makes calls to the waveOutOpen, waveOutGetDevCaps, midiOutOpen and midiOutGetDevCaps APIs with the ... This compatibility fix marks this application as needing administrator privileges to run correctly. It will not run correctly ... This compatibility fix marks this application to run in the most privileged security context available to the user. This ... This compatibility fix modifies the memory status structure so that it reports values similar to those that Win9x would have ... This compatibility fix modifies the pagefile and physical memory status so that it reports 2 gig of pagefile and 1 gig of ... This compatibility fix modifies the pagefile and physical memory status so that it reports available pagefile+avail physical ... This compatibility fix modifies the pagefile and physical memory status so that it reports available pagefile+avail physical ... This compatibility fix modifies the return values of QueryPerformanceCounter and QueryPerformanceFrequency in order to emulate ... This compatibility fix permits a NULL buffer to be passed to VerQuery functions. In Windows XP this technique is considered ...