A MINNT build problem with MSVCR71.dll

[MasterShinker]

Hey, I posted a comment at your YT channed that I had a problem with mktools.cmd part of building a MINNT. Actually I tried to use autobuild and it was worked fine, but I'm just interested why it doesn't works correctly if I building it manually in my VM.

Actuelly the error looks like this:

[leecher1337]

I can only guess, maybe some issue with the path settings? Status code and error message says: STATUS_DLL_NOT_FOUND
Because NTOSBE-master\tools\x86\mstools, which also containes cl.exe, should also contain mentioned msvcr71.dll,
maybe it tries to use cl.exe from another path that is lacking the .dll (because maybe other path has precendence?) or it cannot find it for another reason (failed to unpack the dll to given path?).
Have you checked availability of the dll in mentioned path? Can you run cl.exe in there without issues or does it also complain when you directly run cl.exe there?

[MasterShinker]

Yeah I just got a corrupted archive of NTOSBE, not sure which site it was, now it works fine. But can I ask you, why when i'm trying to launch Doom II just two consoles appears and disappears right away? In Virtual Machine Doom II actually works, but never opens at fullscreen and no mouse capturing. And actually when I'm trying to open 16 bit windows programs like Win3.1 apps they're going to crash before they appear. Why's that?

[leecher1337]

Hm, tried running Doom II on Windows 10 x64 with NTVDM, it runs there in one console window:

Which Windows version are you using? On Windows 10, I can load 16bit programs successfully:

However, if you are on latest Windows 11, you may be out of luck, Microsoft removed crucial functions from GDI-Subsystem rendering WOW32 unusable und unrepairable. Use WineVDM instead on such machines.

If 16bit support doesn't startup, check that user.exe and wow32.dll in windows\syswow64 directory are the ones from NTVDMx64 WOW32 dir. If they are stock versions from Windows operating system, they are incompatible and can also cause a crash. If so, replace them with the proper versions from NTVDMx64.

[MasterShinker]

I'm using windows 10 x64, same as as my VM, but it works fine at VM (but without mouse capturing as I said). My friend have the same problem with NTVDMx64, he can't launch Doom too.

Btw I got WOW32 working after changing it to NTVDMx64 version, as you said. But I can open only one 16bit app. If I wanna open another one i must close Shared WOWExec that opens after I opened 16bit app or kill ntvdm.exe process in Task Manager.

[leecher1337]

Hm, tried on a freshly installed Windows 10 x64. 2 x Jewelthief and 1 x regedt16 concurrently opened without issues. You can try to use the WOW tracing capabilites described in the README, if you want to investigate further.