It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Let's rise this traditional topic.
Windows platforms below Windows 10 claimed to be unsupported in the recent ND port.
But doom_gog.exe is actually a MSVC8 64-bit application with minimal platform version to run of 6.0 (Windows Vista). And, AFAIKS, the only component which really requiers Win10 API is PartyWin.dll. Looks like hardware abstraction wrapper.
VxKex still does not resolves the issue: "The procedure entry point GetAddrInfoExOverlappedResult could not be located in the dynamic link library kxnet".
But it seems kxnet.dll is nowhere to be found. Any versions?

P.S. Before posting blabberish answer about "upgrade Windows" or "why do you need this" etc., think of the question of mine as a sort of a sport.
Post edited August 10, 2024 by Schwertz
Ok. Figured out. ws2_32.dll (Windows Sockets v2) does not provide all entry point required by PartyWin.dll. Wrapper needed.

--- Update ---
That was not quite correct. Ws2_32.dll on Windows 7 indeed does not provide entry points required by PartyWin.dll. But error message about dynamic link library kxnet actually refers to kxnet.dll injected by VxKex, NOT to the componet of the KEX engine. It's just a case of confusing naming. Result is the same, though: VxKex functionality has to be extended for this port to work on Windows 7.
Post edited August 30, 2024 by Schwertz
How did you get past the missing DLLs?

e.g.:

api-ms-win-eventing-classicprovider-l1-1-0.dll
api-ms-win-core-libraryloader-l1-2-0.dll
api-ms-win-eventing-provider-l1-1-0.dll
api-ms-win-core-version-l1-1-0.dll

I could find that some of the needed functions in those DLLs are provided by already existing DLLs.

api-ms-win-eventing-classicprovider-l1-1-0.dll: GetTraceEnableLevel() -> found in advapi32.dll
api-ms-win-core-libraryloader-l1-2-0.dll: DisableThreadLibraryCalls() -> found in kernel32.dll

Copying the existing DLLs to the game directory and renaming accordingly would let the game startup progress further.

However it's very tedious, and I haven't continued investigating on potentially even more missing DLLs yet.
avatar
shadax: How did you get past the missing DLLs?
With this small compatibility wrapper: https://github.com/i486/VxKex
Read the warning, though: https://github.com/i486/VxKex/releases/tag/Version1.1.1.1375
Since M$ tried to silently take the project down. And impostors with potenially maliciuos intent appeared on the Github at that moment.
avatar
shadax: Copying the existing DLLs to the game directory and renaming accordingly would let the game startup progress further.
I did not experimented further till far but it's doubtable that blatant and simple "transplanation" of Windows Sockets DLL from Windows 10 will help.
If the the problem with network stack will be resolved, it might become necessary to address renderer as well. DXVK, probably.
Post edited August 11, 2024 by Schwertz
DXVK? Isnt KEX itself compatible with old true Win NT? Not looks like there is for real any API cant be compatible with Win7. Or it is for real newer build of engine and really ised D3D12 (as lart of official required DirectX12) this time?

There is on github some wrapper to mislead application OS are actually Win10 that work/implement in OS UI as Compatibility tab do work. Allow to chose "compatibility" with Win10.

Having backuped of WinD3D-for-Win and DXVK-for-Win are mandatory anyway, Win7-unrelated.
avatar
QWEEDDYZ: DXVK? Isnt KEX itself compatible with old true Win NT? Not looks like there is for real any API cant be compatible with Win7. Or it is for real newer build of engine and really ised D3D12 (as lart of official required DirectX12) this time?
I have not got that far to answer this question. Currently I'm stuck on the network code initialization.
It would be easier if we had fill-fledged WINE-on-Windows. But it looks like currently there is no such initiative with ready to use results.
Post edited August 31, 2024 by Schwertz
With the help of someone much smarter than me, (dotexe1337, creator of the Extended Windows 7 Kernel) I figured out how to get this working on Windows 7 with some caveats.

The big issue is PartyWin.dll as mentioned here, but if you don't care for multiplayer you can get this running perfectly on Windows 7.

Step 1. Download CFF Explorer (included in Explorer Suite, check the NTCore website)

Step 2. Launch CFF Explorer and open the doom-gog.exe file

Step 3. Click on Import Directory (Image 1)

Step 4. Left click PartyWin.dll and click on Delete Import Descriptor (Image 2)

Step 5. Save file, if your Windows 7 is fully up to date the game should launch just fine.

Huzzah, the game works albeit without multiplayer. Could not sign into Bethesda.net on GOG, but with the same steps I was logged in on steam just fine. So I imagine when GOG fixes the Bethesda.net issue (happened to me on Windows 10 as well) it should work perfectly

Credit to: dotexe1337, creator of the Extended Windows 7 Kernel

P.S. If it asks you to overwrite click yes

P.S.S. If it still does not work after this you may need to have the extended Kernel installed or VxKex activated.
Attachments:
1.png (51 Kb)
2.png (67 Kb)
Post edited September 05, 2024 by BibleMetalFTW
avatar
BibleMetalFTW: With the help of someone much smarter than me, (dotexe1337, creator of the Extended Windows 7 Kernel) I figured out how to get this working on Windows 7 with some caveats.

The big issue is PartyWin.dll as mentioned here, but if you don't care for multiplayer you can get this running perfectly on Windows 7.
Confirmed. This method works almost flawleslly. VxKex is not required if imports from PartyWin.dll are removed.

Thank you and dotexe1337 very much.

Now, to the next exercise: make PartyWin.dll work. )))
Post edited September 05, 2024 by Schwertz