Played 1 mission of mw2 titanium. Seems fine.
No errors. No leaks. Memory under 200mb.

Disc=
TITAN_MW2-TITW95-Titanium Trilogy

myne wrote on 2024-11-04, 06:14:

Its a bit of a mess. Some people are reporting memory leaks. So I backtracked a year. That one seems to work with mercs. You say […]
Show full quote

Its a bit of a mess. Some people are reporting memory leaks.
So I backtracked a year.
That one seems to work with mercs.
You say it doesn't work with mw2. Ok.

Does the main one?

Well, actualy nothing is works for me so far, i even tryed to do it for ourself, with all stage, with sdb and other stuff, but its wont help.

DOS wersion on MechVM works fine, i even can Launch titanium to menu stage on it (its just crash when launching mission).

Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
I used this.
See PM

Ok, i try.

BEEN_Nath_58 wrote on 2024-11-03, 13:28:

Alright then, download MechVM from here: https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z […]
Show full quote

ChronoReaperX wrote on 2024-11-03, 11:03:

BEEN_Nath_58 wrote on 2024-11-03, 08:14:

The game doesn't run on MechVM, I am asking if you would be able to test the game when I provide the instructions

Yes sure... I can try

Alright then, download MechVM from here:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Install your Titanium Mercenaries, but run MechVM.exe as administrator.
After installation, go to the games folder of MechVM, then to the mw2-mercs-tt folder, and rename mercswin.exe to something else.
Copy all the files from "Install/data" folder of your CD to your installed game, but don't overwrite.
Copy all the files from "Install/16bit" folder of your CD to your installed game, again don't overwrite.

Use the attached profile in the latest DxWnd version downloaded from SourceForge. Let me know what changes (if any) you face.

Still the same problem. HUD disappeared during the later part of some mission. Mechs also disappeared including the in game menu (when pressing esc).

Weird. Got through the first few missions and then it started glitching.
Not sure why these issues weren't apparent a year ago. I literally finished the whole game without issue.

myne wrote on 2024-11-04, 06:58:

Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
I used this.
See PM

Same result - Error with GetThreadContext error = 5

AweDeus wrote on 2024-11-04, 07:25:

myne wrote on 2024-11-04, 06:58:

Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
I used this.
See PM

Same result - Error with GetThreadContext error = 5

Go to the game folder and run the main executable (mercswin.exe?) directly. It should output an error, what's that?

ChronoReaperX wrote on 2024-11-04, 07:05:

BEEN_Nath_58 wrote on 2024-11-03, 13:28:

Alright then, download MechVM from here: https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z […]
Show full quote

ChronoReaperX wrote on 2024-11-03, 11:03:

Yes sure... I can try

Alright then, download MechVM from here:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Install your Titanium Mercenaries, but run MechVM.exe as administrator.
After installation, go to the games folder of MechVM, then to the mw2-mercs-tt folder, and rename mercswin.exe to something else.
Copy all the files from "Install/data" folder of your CD to your installed game, but don't overwrite.
Copy all the files from "Install/16bit" folder of your CD to your installed game, again don't overwrite.

Use the attached profile in the latest DxWnd version downloaded from SourceForge. Let me know what changes (if any) you face.

Still the same problem. HUD disappeared during the later part of some mission. Mechs also disappeared including the in game menu (when pressing esc).

So basically the MechVM game didn't change anything. That's sad, the MechVM fixes were also from https://gitlab.com/retropc/mw2hook

I probably have one thing left: put the main game executable back to Windows 98 compat mode, and run DxWnd as admin, and try. This is the only thing I removed from the previous test.

Also if it is easy to get to the bug, glitch, you may share the savegame or explain how to reach the part of the game.

myne wrote on 2024-11-04, 05:22:

Why...? It's working. Why fix it? […]
Show full quote

Why...?
It's working. Why fix it?

This is worth testing. It's the OLD files sdbs etc and the new install script.
Not sure why people weren't reporting issues earlier.

Still experiencing memory leaks

BEEN_Nath_58 wrote on 2024-11-04, 07:33:

AweDeus wrote on 2024-11-04, 07:25:

myne wrote on 2024-11-04, 06:58:

Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
I used this.
See PM

Same result - Error with GetThreadContext error = 5

Go to the game folder and run the main executable (mercswin.exe?) directly. It should output an error, what's that?

Well, i try to launch MW2 31 titanium, error with code 0xc0000142

UPD - ok, i figure out whats the problem with injection - Windows Data Execution Prevention (DEP) Service in windows performance tab - if add DxWND and Mw2Tit.exe to exception then all goind well, BUT - i got another error https://i.imgur.com/CLdZU4W.png

also, ive got an error in PS when installing a game:

copy-item : Cannot find path 'L:\setup\' because it does not exist.
At D:\GAMES\mw2Installer\mw2Installer.ps1:455 char:10
+ copy-item -path "$CDDRIVE\$folder\" -destination "$InstallPa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (L:\setup\:String) [Copy-Item], Ite
mNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItem
Command

AweDeus wrote on 2024-11-04, 08:40:

Well, i try to launch MW2 31 titanium, error with code 0xc0000142 […]
Show full quote

BEEN_Nath_58 wrote on 2024-11-04, 07:33:

AweDeus wrote on 2024-11-04, 07:25:

Same result - Error with GetThreadContext error = 5

Go to the game folder and run the main executable (mercswin.exe?) directly. It should output an error, what's that?

Well, i try to launch MW2 31 titanium, error with code 0xc0000142

UPD - ok, i figure out whats the problem with injection - Windows Data Execution Prevention (DEP) Service in windows performance tab - if add DxWND and Mw2Tit.exe to exception then all goind well, BUT - i got another error https://i.imgur.com/CLdZU4W.png

also, ive got an error in PS when installing a game:

copy-item : Cannot find path 'L:\setup\' because it does not exist.
At D:\GAMES\mw2Installer\mw2Installer.ps1:455 char:10
+ copy-item -path "$CDDRIVE\$folder\" -destination "$InstallPa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (L:\setup\:String) [Copy-Item], Ite
mNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItem
Command

The PS error should be irrelevant. Now I need to find how to emulate the error you got.

To note, the mw2installer package was made checking how the InstallShield would install the game.

I don't know if it's an installation issue, but you can install the game with the CD to make sure it isn't. Put Windows 95 compat mode on the Autorun of the game, and proceed, it should run the InstallShield setup correctly (you need OTVDM installed for 16bit apps to execute).

At least you aren't alone, the only thing that comes to mind is testing the game on another language of Windows: https://sourceforge.net/p/dxwnd/discussion/ge … /310b/b7ba/3487

ZOMG - im successfully launch it and enter the mission, for this i install Titanium version from scratch and copying all files from autoinstall folder. At first ive got game crash with 3dfx video option, but seems that DirectX is working fine.

Also - the error

MW2 BATTLE.EXE - fatal error #41: Edition\mw2t.BWN ID -1

may appear if you use compability mode, because i was launching it with compability mode and its crashed. So i hope someone who, like me, has spent a lot of time trying to find the right combination will read this, check the compatibility and finally get it running.

UPD

BEEN_Nath_58 wrote on 2024-11-04, 08:48:

The PS error should be irrelevant. Now I need to find how to emulate the error you got. […]
Show full quote

AweDeus wrote on 2024-11-04, 08:40:

Well, i try to launch MW2 31 titanium, error with code 0xc0000142 […]
Show full quote

BEEN_Nath_58 wrote on 2024-11-04, 07:33:

Go to the game folder and run the main executable (mercswin.exe?) directly. It should output an error, what's that?

Well, i try to launch MW2 31 titanium, error with code 0xc0000142

UPD - ok, i figure out whats the problem with injection - Windows Data Execution Prevention (DEP) Service in windows performance tab - if add DxWND and Mw2Tit.exe to exception then all goind well, BUT - i got another error https://i.imgur.com/CLdZU4W.png

also, ive got an error in PS when installing a game:

copy-item : Cannot find path 'L:\setup\' because it does not exist.
At D:\GAMES\mw2Installer\mw2Installer.ps1:455 char:10
+ copy-item -path "$CDDRIVE\$folder\" -destination "$InstallPa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (L:\setup\:String) [Copy-Item], Ite
mNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItem
Command

The PS error should be irrelevant. Now I need to find how to emulate the error you got.

To note, the mw2installer package was made checking how the InstallShield would install the game.

I don't know if it's an installation issue, but you can install the game with the CD to make sure it isn't. Put Windows 95 compat mode on the Autorun of the game, and proceed, it should run the InstallShield setup correctly (you need OTVDM installed for 16bit apps to execute).

At least you aren't alone, the only thing that comes to mind is testing the game on another language of Windows: https://sourceforge.net/p/dxwnd/discussion/ge … /310b/b7ba/3487

I think error with code 0xc0000142 may appear because of "Windows Data Execution Prevention (DEP)" Settings. Hope its also helps someone.

Also - you dont need to install OTVDM all that you need it set compatability mode with win95 on setup.exe and setup.exe in "install" folder and analyze wait chain for setup process in task manager after launching it - you have to kill all process that shows in analyze wait chain tab and after that installing will be start.

AweDeus wrote on 2024-11-04, 09:00:

ZOMG - im successfully launch it and enter the mission, for this i install Titanium version from scratch and copying all files f […]
Show full quote

ZOMG - im successfully launch it and enter the mission, for this i install Titanium version from scratch and copying all files from autoinstall folder. At first ive got game crash with 3dfx video option, but seems that DirectX is working fine.

Also - the error

MW2 BATTLE.EXE - fatal error #41: Edition\mw2t.BWN ID -1

may appear if you use compability mode, because i was launching it with compability mode and its crashed. So i hope someone who, like me, has spent a lot of time trying to find the right combination will read this, check the compatibility and finally get it running.

Right, the crash comes from the compatibility modes, I don't remember well but maybe it is the GetCommandLine shim.

And how did you get the game, you installed using the setup executable then, right?

For the 3Dfx modes, you need dgVoodoo2

AweDeus wrote on 2024-11-04, 09:00:

UPD

I think error with code 0xc0000142 may appear because of "Windows Data Execution Prevention (DEP)" Settings. Hope its also helps someone.

Also - you dont need to install OTVDM all that you need it set compatability mode with win95 on setup.exe and setup.exe in "install" folder and analyze wait chain for setup process in task manager after launching it - you have to kill all process that shows in analyze wait chain tab and after that installing will be start.

Yes the error is related to DEP. I have only had one issue with DEP ever, in Diablo, so I have little knowledge on what to do actually.

On Windows 10, the 16-bit stub of IS is somewhat present so it will work nonetheless. On Win11 it was completely removed.

ChronoReaperX wrote on 2024-11-04, 07:35:

myne wrote on 2024-11-04, 05:22:

Why...? It's working. Why fix it? […]
Show full quote

Why...?
It's working. Why fix it?

This is worth testing. It's the OLD files sdbs etc and the new install script.
Not sure why people weren't reporting issues earlier.

Still experiencing memory leaks

Hi can you provide saves of the place where you get the memory leak and if not, the fastest way to get there, or as to how long to play to get there.

BEEN_Nath_58 wrote on 2024-11-04, 13:06:

ChronoReaperX wrote on 2024-11-04, 07:35:

myne wrote on 2024-11-04, 05:22:

Why...? It's working. Why fix it? […]
Show full quote

Why...?
It's working. Why fix it?

This is worth testing. It's the OLD files sdbs etc and the new install script.
Not sure why people weren't reporting issues earlier.

Still experiencing memory leaks

Hi can you provide saves of the place where you get the memory leak and if not, the fastest way to get there, or as to how long to play to get there.

The fastest way I think is the mission 2 of Ghost Bear's Legacy campaign. Named Defend on Mannedorf. You play it until you've repelled the third wave (two Mechs heading to your base after you finished off a team of Ravens descending from above your base). While your are waiting for the fourth wave (two Mechs from afar), then then problem will happen.

BEEN_Nath_58 wrote on 2024-11-04, 10:37:

Right, the crash comes from the compatibility modes, I don't remember well but maybe it is the GetCommandLine shim. […]
Show full quote

AweDeus wrote on 2024-11-04, 09:00:

ZOMG - im successfully launch it and enter the mission, for this i install Titanium version from scratch and copying all files f […]
Show full quote

ZOMG - im successfully launch it and enter the mission, for this i install Titanium version from scratch and copying all files from autoinstall folder. At first ive got game crash with 3dfx video option, but seems that DirectX is working fine.

Also - the error

MW2 BATTLE.EXE - fatal error #41: Edition\mw2t.BWN ID -1

may appear if you use compability mode, because i was launching it with compability mode and its crashed. So i hope someone who, like me, has spent a lot of time trying to find the right combination will read this, check the compatibility and finally get it running.

Right, the crash comes from the compatibility modes, I don't remember well but maybe it is the GetCommandLine shim.

And how did you get the game, you installed using the setup executable then, right?

For the 3Dfx modes, you need dgVoodoo2

AweDeus wrote on 2024-11-04, 09:00:

UPD

I think error with code 0xc0000142 may appear because of "Windows Data Execution Prevention (DEP)" Settings. Hope its also helps someone.

Also - you dont need to install OTVDM all that you need it set compatability mode with win95 on setup.exe and setup.exe in "install" folder and analyze wait chain for setup process in task manager after launching it - you have to kill all process that shows in analyze wait chain tab and after that installing will be start.

Yes the error is related to DEP. I have only had one issue with DEP ever, in Diablo, so I have little knowledge on what to do actually.

On Windows 10, the 16-bit stub of IS is somewhat present so it will work nonetheless. On Win11 it was completely removed.

>And how did you get the game, you installed using the setup executable then, right?
at first im used the installing script, then i installed the game from ISO, after that i just copying files from first folder to second with replace.

But i think that the problem was in DEP and anti hook behevor. Im also got this error in Diablo long time ago, and it is why i remembered this way to fix that.

So you just need to find windows Performance Options utility ((You may find it in windows searching), it is the place where you also could set you virtual memory limit), and in that window you could add to exclusion you .exe files on "Data Execute Prevension" tab

>For the 3Dfx modes, you need dgVoodoo2
Yes, actualy on the second try 3dfx mode start working well (I already had glide files idk why its happens at first)

BEEN_Nath_58 wrote on 2024-11-02, 12:25:

@ChronoReaperX @Khoidoan1@ hotmail.co […]
Show full quote

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

Sorry I've been dealing with something deeply personal so I've not been able to really test Mercs 2 all that much. It does still have the memory leak if played directly from DXwnd. For some reason at least for me, the game will run for hours without issues if an instant action is started and then aborted. Max mem usage is 2600 or so.

Khoidoan1@hotmail.co wrote on 2024-11-06, 18:09:

BEEN_Nath_58 wrote on 2024-11-02, 12:25:

@ChronoReaperX @Khoidoan1@ hotmail.co […]
Show full quote

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

Sorry I've been dealing with something deeply personal so I've not been able to really test Mercs 2 all that much. It does still have the memory leak if played directly from DXwnd. For some reason at least for me, the game will run for hours without issues if an instant action is started and then aborted. Max mem usage is 2600 or so.

I haven't got the time to test GBL for ChromeReaperX either. Anyways...

The game working fine after aborting a mission could be a sign of where to look. If you read some of the previous discussions on this thread, you will get comments on the game flickering unless the game is Aborted and re-run.

What I assume is, DxWnd isn't correctly hooking the game interface on the first run in mission. The mission window is a separate DirectDraw hWnd, forced to skip the DDSCL_EXCLUSIVE flag but keeping the game contactless from other apps through a modal window (which fails on the first run). On the Abort -> Replay Mission the Modal window was drawn correctly, and simultaneously your game doesn't get a memory leak.

You can continue to run the game in this fashion, and if the leak no longer happens, I think we found the issue

BEEN_Nath_58 wrote on 2024-11-06, 18:18:

I haven't got the time to test GBL for ChromeReaperX either. Anyways... […]
Show full quote

Khoidoan1@hotmail.co wrote on 2024-11-06, 18:09:

BEEN_Nath_58 wrote on 2024-11-02, 12:25:

@ChronoReaperX @Khoidoan1@ hotmail.co […]
Show full quote

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

Sorry I've been dealing with something deeply personal so I've not been able to really test Mercs 2 all that much. It does still have the memory leak if played directly from DXwnd. For some reason at least for me, the game will run for hours without issues if an instant action is started and then aborted. Max mem usage is 2600 or so.

I haven't got the time to test GBL for ChromeReaperX either. Anyways...

The game working fine after aborting a mission could be a sign of where to look. If you read some of the previous discussions on this thread, you will get comments on the game flickering unless the game is Aborted and re-run.

What I assume is, DxWnd isn't correctly hooking the game interface on the first run in mission. The mission window is a separate DirectDraw hWnd, forced to skip the DDSCL_EXCLUSIVE flag but keeping the game contactless from other apps through a modal window (which fails on the first run). On the Abort -> Replay Mission the Modal window was drawn correctly, and simultaneously your game doesn't get a memory leak.

You can continue to run the game in this fashion, and if the leak no longer happens, I think we found the issue

Ok I will try and test what you said. Start a mission then abort, after that, restart it back, right?

ChronoReaperX wrote on 2024-11-07, 06:54:

BEEN_Nath_58 wrote on 2024-11-06, 18:18:

I haven't got the time to test GBL for ChromeReaperX either. Anyways... […]
Show full quote

Khoidoan1@hotmail.co wrote on 2024-11-06, 18:09:

Sorry I've been dealing with something deeply personal so I've not been able to really test Mercs 2 all that much. It does still have the memory leak if played directly from DXwnd. For some reason at least for me, the game will run for hours without issues if an instant action is started and then aborted. Max mem usage is 2600 or so.

I haven't got the time to test GBL for ChromeReaperX either. Anyways...

The game working fine after aborting a mission could be a sign of where to look. If you read some of the previous discussions on this thread, you will get comments on the game flickering unless the game is Aborted and re-run.

What I assume is, DxWnd isn't correctly hooking the game interface on the first run in mission. The mission window is a separate DirectDraw hWnd, forced to skip the DDSCL_EXCLUSIVE flag but keeping the game contactless from other apps through a modal window (which fails on the first run). On the Abort -> Replay Mission the Modal window was drawn correctly, and simultaneously your game doesn't get a memory leak.

You can continue to run the game in this fashion, and if the leak no longer happens, I think we found the issue

Ok I will try and test what you said. Start a mission then abort, after that, restart it back, right?

yes