In addiction, the results I got so far doesn't seem very easily replicable.
To make the whole stuff working there is the need to hook the invisible bh2000.exe and make it propagate the DLL injection to its son, a thing that in theory should work, but so far the hooked bh2000.exe refuses to work. All these configurations, though, require DLL injection. So, the current situation is that I got a valid DxWnd configuration for bh2000.exe and beachhead\beachhead16.exe, so that I can separately run a useless menu and a new game. beachhead15.exe and beachhead16.exe are the actual 3D gun engines for 15BPP and 16BPP video modes respectively. When it terminates, it tells its father bh2000.exe the chosen action through the exit code It also checks the video modes and sets a 640x480 resolution with either 15 or 16 BPP color depth. bh.exe is the program that show the game main menu and some intro stuff, options and everything is NOT 3D. Its purpose is to run, in turn either BH.exe or one of the twin programs beachhead\beachhead15.exe or beachhead\beachhead16.exe bh2000.exe is an invisible and mute frontend. The problem with this game is its splitted logic: if you check the running processes or simply look at the calls within each module, Iyou can see the folllowing:
0 kommentar(er)
