otya128 / winevdm

16-bit Windows (Windows 1.x, 2.x, 3.0, 3.1, etc.) on 64-bit Windows
GNU General Public License v2.0
2.68k stars 152 forks source link

No implementation for GDI.GETSYSTEMICONFONT, setting to 0xdeadbeef #1306

Closed heipiao233 closed 1 year ago

heipiao233 commented 1 year ago

Try the latest version first. Go here and click Environment: THIS_BUILD_IS_RECOMMENDED__VCXPROJ_BUILD=1-> Artifacts 1-> zip to download the latest version.

Describe the bug "0e58:err:fixup:apply_relocations No implementation for GDI.GETSYSTEMICONFONT, setting to 0xdeadbeef" When running progman.exe

Expected behavior Run it successfully

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Additional context Add any other context about the problem here.

It is very helpful to provide a trace file if possible. Please note that this file contains detailed information about the program. Procedure

  1. Run the command prompt.
  2. Set the environment variable:
    set WINEDEBUG=+all,-snoop,-ldt,-fixup,-module,-global,-local,-disasm,-syslevel,-thunk
  3. 
    *old-executable-file* 2> trace.txt

4. Upload trace.txt here.

[a.log](https://github.com/otya128/winevdm/files/12156842/a.log)
cracyc commented 1 year ago

Where did this version of progman.exe come from? GETSYSTEMICONFONT isn't in windows 3.0 or windows 3.1 gdi.exe. It's probably similar to SystemParametersInfo(SPI_GETICONTITLELOGFONT) but it's not possible to implement without knowing what parameters it expects.