http://bugs.winehq.org/show_bug.cgi?id=58637
--- Comment #15 from Stian Low wineryyyyy@gmail.com --- Created attachment 79207 --> http://bugs.winehq.org/attachment.cgi?id=79207 Screenshot of "new WoW64" running WIN95/SC2K/WINSCURK.EXE
(In reply to Zeb Figura from comment #13)
New wow64 won't run the setup yet (this is bug 54670), but a previously installed copy works fine for me, with both old wow64 and new wow64. I did not use anything from sc2kfix.
Confirming 16-bit related install errors for "new WoW64" (built for commit 93b6570ef4e via: ./configure --enable-archs=i386,x86_64):
00ec:fixme:shell:IShellBrowser_fnOnViewWindowActive stub, 00007FFFFEBCD240 (00007FFFFEBF5560) 00ec:fixme:exec:SHELL_execute flags ignored: 0x0000000c 0164:err:environ:init_peb starting L"C:\windows\syswow64\winevdm.exe" in experimental wow64 mode 0164:fixme:wow:wow64_NtSetLdtEntries 0107 0488323f 0000f37a 0000 00000000 00000000: stub 0164:err:module:loader_init "krnl386.exe16" failed to initialize, aborting 0164:err:module:loader_init Initializing dlls for L"C:\windows\syswow64\winevdm.exe" failed, status c0000005
Shared "old WoW64" installs and runs without issues.
So Wine 9.0 release notes regarding lack of 16-bit code support seems still relevant for the latest versions using "new WoW64": https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0#wow64
However, attached is a screenshot of WIN95/SC2K/WINSCURK.EXE running which backs Zeb's claim that it's mostly just an installer issue because the 32-bit parts not involving 16-bit seems to work for "new WoW64" which is why it's able to run if already installed.