On Sun Apr 20 20:42:19 2025 +0000, Pali Rohár wrote:
Yes, this is known technique described in the Andrew Schulman book: Unauthorized Windows 95. kernel32.dll VxDCall function allows to call DPMI functions directly from native 32-bit applications. Code samples of VxDCall usage are part of the book. The DPMI physical address mapping function (as described in the commit message) is used for example by SysToolsLib or by WinIO or by lspci. All of them are checking for carry flag to figure out if the DPMI function call failed or not.
The problem is that it's not unlikely that some app currently works because we don't report failure. So we shouldn't change everything to report errors just because the spec says so. Only cases that demonstrably fix an actual app should be changed.