To apply Sierra's patch: 1) Restore original .exe from CD 2) Apply Sierra's patch 3) Apply my patch, it will fail on patching the executable, but as long as the RUN386.EXE from my patch is correctly in place, it still works. DETACHES_PROCESS flag is present then, but RUN386.EXE is not a DOS process, it is a Win32 process launching a DOS process as subprocess, so it's not a big deal that patching PCHESS.EXE fails. I cannot patch the PCHESS.EXE from Sierra's PCHESS98 patch, because PUSH 8 instruction...
To apply Sierra's patch: 1) Restore original .exe from CD 2) Apply Sierra's patch 3) Apply my patch, it will fail on patching the executable, but as long as the RUN386.EXE from my patch is correctly in place, it still works. DETACHES_PROCESS flag is present then, but RUN386.EXE is not a DOS process, it is a Win32 process launching a DOS process as subprocess, so it's not a big deal that patching PCHESS.EXE fails. I cannot patch the PCHESS.EXE from Sierra's PCHESS98 patch, because PUSH 8 instruction...
Tried PCHESS98 patch in Win98, it doesn't fix your savegame-issue, so I guess Save works as it works by design (you can change main line to last move anyway in windowthat contains all moves and it also seems to be by design that a saved game cannot be continued against the opponent, it just saves the move history). Anyway, regarding PCHESS98 patch: My Patcher fails for byte pattern patch for CreateProcess call, but it's not a big problem, as CreateProcess flags in patched version changed so that...
Not related to patch, same behaviour under plain Win98.
Btw.: In case setup.exe crashes for you, I now updated NTVDMx64 to fix this issue.
Updated patcher to now also patch PowerChess 98 executable, runs fine on Windows 11
Tested Win11 loader on Win10, also works, so should also work with SecureBoot enabled with most recent ntvdmx64 which offers this possibility of installation on a system with Secure Boot enabled.
I don't quite understand, what do you mean that I should check?
Maybe just use AppCompat infrastructure which Windows Loader uses itself to accomplish patching? They you can rely on an established infrastructure for patching components. Using AppCompat for PCHESS patching would i.e. involve of writing a CreateProcess AppCompat wrapper which just changes the Process creation flags, so it's somewhat like IAT-Hooking provided by the OS loader. You could also do in-memory patching and scanning with FLIRT-Signatures, like I did, of course, but I guess, for most stuff,...
Windows 11 ntvdmx64 loader works without secure boot. theoretically, the Win 11 loader should also work on Win10 (not tested yet, though, but current installation routine offers to try it out). Which Windows Version is your target?
Attached is an image of running PowerChess under Windows 7x64 with ntvdmx64
Maybe we should clerify 2 things first, so that I can give instructions: Which PowerChess Version (Power Chess or Power Chess 98?) Which Windows Version? Then I can test it on the appropriate combination and give feedback with instructions.
Remark: 0x99 is joker so that patcher can find patched and unpatched signature. So it is: Search: 0x50, 0x6A, 0x00, 0x68, 0x08, 0x08, 0x00, 0x00, 0x6A, 0x01 Replace: 0x50, 0x6A, 0x00, 0x68, 0x00, 0x08, 0x00, 0x08, 0x6A, 0x01 What I do not understand is, why do you use DxWnd for this game anyway, I just ran it on plain Windows and it worked OK. Regarding BSOD, I guess that this must be some problem not replated to PowerChess 98 or the Patcher, as there is no Kernel Mode code involved, it's just plain...
I tested with this version: https://www.old-games.ru/game/download/7740.html I didn't test Powerchess 98, though. Which version do you use? Btw.: Location of patcher.exe is irelevant, it looks up installation path from C:\Windows\sierra.ini
Seems like you are not used to github? There is a "Releases" section where you can find the precompiled .exe https://github.com/leecher1337/pchess/releases/tag/v1.0.0
Here you go: https://github.com/leecher1337/pchess
I'll patch PCHESS.EXE, CreateProcess call needs to be without DETACHED_PROCESS flag and commandline needs to be adapted by prepending CMD /C, then it seems to work (at least it started OK with these modifications in my tests on Win XP). Don't know yet if I can patch cmd /C into PCHESS.EXE too, or if I shuold just write a simple RUN386.EXE wrapper, I'll check both options.
RUN386.EXE is a launcher for Pharlap Dos Extender. Die KING.EXE and QUEEN.EXE are in Pharlap .EXP format (old header). As these are not MZ .exe files, you get the memory error when you run them without run386, because DOS doesn't recognize any MZ exe header and this tries to load them as .COM, but Fiels are >64 KB in size (and also don't contain any valid .COM code), so you get OOM error, when you launch them directly. The PCHESS.exe just tries to communicate iwht it via stdin, stdout and stderr...
RUN386.EXE is a launcher for Pharlap Dos Extender. Die KING.EXE and QUEEN.EXE are in Pharlap .EXP format (old header). As these are not .MZ .exe files, you get the memory error when you run them withotu run386, because DOS doesn't recognize any MZ exe header and this tries to load them as .COM, but Fiels are >64 KB in size (and also don't contain any valid .COM code), so you get OOM error, when you launch them directory. The PCHESS.exe just tries to communicate iwht it via stdin, stdout and stderr...
HTTP Address book support
com2tcp patches for NTLM auth, Microsoft Telnet Server compatibility and Monitoring of sessions