GBL finished.
Weird bug on the final level.
PPCs wouldn't show, and the hole in the ship was never created automatically. I had to shoot randomly where I vaguely remembered it would be to eventually make it myself.
The premise is that your ship does it.
Not sure what could cause this.

myne wrote on 2023-11-18, 22:56:

Nevermind. Working.
It MUST be the first CD by letter.

Yes that was a requirement even in Win95 too

myne wrote on 2023-11-19, 03:25:

GBL finished. Weird bug on the final level. PPCs wouldn't show, and the hole in the ship was never created automatically. I had […]
Show full quote

GBL finished.
Weird bug on the final level.
PPCs wouldn't show, and the hole in the ship was never created automatically. I had to shoot randomly where I vaguely remembered it would be to eventually make it myself.
The premise is that your ship does it.
Not sure what could cause this.

Could well be a glitch or a game bug considering there wasn't a problem elsewhere...

Did you use the 31stCC profile or Mercs profile for GBL? Did you finish 31stCC?

Finished all now.
I used the 31cc profile as per the installer.
I did change some settings here and there, like single core only.

myne wrote on 2023-11-19, 06:28:

Finished all now.
I used the 31cc profile as per the installer.
I did change some settings here and there, like single core only.

Okay that means the games work decent enough. I saw a game crash when accessing Mercnet but I don't think its worth investigating.

Did you try the Direct3D modes of the game?

Nah didn't really see the point. It looks worse

Well, I'm counting Titanium as a solved problem

Would you like to add it the zip to your original post?
I've updated the original one I posted it in.

Pentium edition doesn't seem stable on mine.
If you've got newer fixes I can test it out and update the installer for it.

myne wrote on 2023-11-20, 10:18:

Well, I'm counting Titanium as a solved problem […]
Show full quote

Well, I'm counting Titanium as a solved problem

Would you like to add it the zip to your original post?
I've updated the original one I posted it in.

Pentium edition doesn't seem stable on mine.
If you've got newer fixes I can test it out and update the installer for it.

About the D3D mode, you can use dgVoodoo2 there as well and it still looked fine. The only reason I don't usually use dgVoodoo2 with the game is because it sometimes gets to a cornered window (failed SetDisplayMode change and the game is stuck in corner). If that's not an issue, dgVoodoo2 is absolutely fine, although I tested the option to run without it natively too.

About the mw2prm.cfg, did you change it? I can't check right now since I am not on the desktop.

Yes Pentium Edition has some stability issues, but most of it seemed gone (at least till Win10) by enabling Libs/EmulateHeap.

I also wanted to finish the Battlepack edition, I know it's a weird middle ground between the two, but it has even greater stability issues in GDI/User32-DirectDraw interactions.

Btw Titanium Edition also supports Rendition API. RReady emulator supports the game, although I played it at the default resplutoon in-app (so that game configures it)

Btw I saw this here
www.mech2.org/forum/viewtopic.php?f=5&t=6379

What's that crash?

Dgvoodoo worked fine. Some graphical glitches but the game was never perfect to start with.

Never touched mw2prm.cfg

Pentium wouldn't load full screen or a mission for me. Segfault(equivalent).

You want to fix the most broken of them all? Lol

Rendition api?

Crash was because my copy was corrupt. We discussed a page or 2 ago.

myne wrote on 2023-11-20, 12:07:

Dgvoodoo worked fine. Some graphical glitches but the game was never perfect to start with. […]
Show full quote

Dgvoodoo worked fine. Some graphical glitches but the game was never perfect to start with.

Never touched mw2prm.cfg

Pentium wouldn't load full screen or a mission for me. Segfault(equivalent).

You want to fix the most broken of them all? Lol

Rendition api?

Crash was because my copy was corrupt. We discussed a page or 2 ago.

For graphical glitches, it would be better to report Dege in the dgVoodoo2 thread instead, since I can't control it. At least he has a working MW2 now.

Maybe you didn't mw2prm.cfg because you didn't install with the setup? That could be case. When I compiled the text, I used to not install games.

It should load mission. I mean how does it crash, like is there a hang or, you press Launch (in Trials of Grievance) and then you see a screen and a circling cursor and crash...

Yes I mean everything was going smooth so I decided to throw a hand on it and it worked ALMOST okay...but that's not a way to play a game

Yes, rendition api. That even worked fine too.

You could change the text in the mech2.org site

It was always glitchy though even 25 years ago.

I'm not sure what you're talking about with mw2prm.cfg tbh

Crashes on mission load. It's also complaining "error writing career file" prior to that. Possibly an issue with the path? Dunno.

Your dedication is... next level. Personally, I'm of the opinion that Titanium works, so that's good enough. I only did the pentium installer because your instructions were there.

Never heard of rendition tbh

Post changed.

myne wrote on 2023-11-21, 00:41:

Crashes on mission load. It's also complaining "error writing career file" prior to that. Possibly an issue with the path? Dunno.
mw2pentiumcrash.JPG

Funny thing is I got both the issue in 2021, but I didn't archive the knowledge I did to fix it. So let me try from a scratch, maybe it could be a little different from what you did.

1. Install that .sdb file through .bat file.
2. Run DxWnd as ADMIN.
3. Import the MECH2 DxW profile to DxWnd.
4. Select the game in DxWnd interface, go to Tools > Clear Compatibility flags, click OK to anything that follows.
5. Double-click on the DxWnd entry and go wherever the crash occurs, don't change anything else in the profile.

The error code is for a 64-bit application and I can't remember how I got that. Error writing career file was something probably related to an error in FindFileA API but we fixed it already.

Btw, where did you install the game, and did you copy the files or install it? I assume you used the Special Installer. DPLAY.DLL, did you copy it from System32 or SysWOW64 or the CD, it CANNOT be from System32 (if SysWOW64 exists) since that's 64-bit.

I'd prefer to get the instructions to the point where it's automatable and as simple as titanium.
You've used the script right? Now that's simple. Here: doubleclick this.

Yeah I used the script. Give it a try.
TBF I did integrate the patch so it's possibly that.

myne wrote on 2023-11-21, 08:03:

I'd prefer to get the instructions to the point where it's automatable and as simple as titanium. You've used the script right? […]
Show full quote

I'd prefer to get the instructions to the point where it's automatable and as simple as titanium.
You've used the script right? Now that's simple. Here: doubleclick this.

Yeah I used the script. Give it a try.
TBF I did integrate the patch so it's possibly that.

There's an error you can look into. The patch doesn't copy DxWnd either. It renames mech2.exe to mw2tit.exe.
Btw I changed things as I needed to to run it, and I got the error you got. It is circumventable, but I will give a followup in a while, the problem is with the game installation.

Hmm. I don't recall seeing that.
Could be I did * instead of *.*
Try changing line 255 to
copy $95fixes\*.* $Installpath -Force

ah. oops wrong version

I got a solution, but I don't know how it happens.

So what I did is, after your setup copies the file, I copy-replace the MW2PRM.CFG and MW2REG.CFG from CD to game, and the error (error writing career file) is gone!

BEEN_Nath_58 wrote on 2023-11-21, 08:33:

I got a solution, but I don't know how it happens.

So what I did is, after your setup copies the file, I copy-replace the MW2PRM.CFG and MW2REG.CFG from CD to game, and the error (error writing career file) is gone!

Ah got it in a second. Every file is read-only copied by PS!

Remove the read only setting and game works!

Your replacement code part gives another error

1At C:\Users\thesa\Downloads\PentiumTest\TitaniumInstaller.ps1:284 char:1
2+ }
3+ ~
4Unexpected token '}' in expression or statement.
5    + CategoryInfo          : ParserError: (:) [], ParseException
6    + FullyQualifiedErrorId : UnexpectedToken

Of course. CDs are RO.
😒
Gimme a bit.

I successfully made it worse.
It now crashes on mission launch without any 0x### error.

myne wrote on 2023-11-21, 09:08:

I successfully made it worse.
It now crashes on mission launch without any 0x### error.

No you didn't make it worse. You copied "lesser DxWnd files" than required.
Case is probably solved: your package doesn't have "libogg.dll"

Edit: Your configuration has the "X, Y coordinate" setting changed to "Desktop". Changing this setting will break the Title bar of the game. I noticed you opted to choose the Titanium profile for the Pentium version, even when I had a different profile for the Pentium version...?