Hi Roderick
From my perspective this way of fixing stuff is the same as throwing mutt at the wall and see if it sticks.
I think everybody is putting Glenn on the wrong foot to make him replace pmmerge.dll. It might fix the crash the but nobody even knows why the crash occurs in the first place. So if you backlevel the last version of pmmerge.dll with an older one. The program might start to work, but then what is broken ?
I mean its all well intended but what is causing the crash in the first place ? PMMERGE.DLL is pretty important system dll and not something that should just be swapped out like spare tire from the trunk of your car.
I took these words as your opinion and FUD against the OS4 development..
Regards
I told you that already 3 times Martin its not, not not. End of story. I thought we would try as community project see how we could analyze the issue and learn how to trace the issue in the way you can trace it with tools from IBM.
Why do you think I asked in the second posting for the popuplog.os2 entry to see what is going on ?
https://www.os2world.com/forum/index.php/topic,3063.msg34814.html#msg34814Why do you think I asked for this ? If the version of PMMERGE.DLL matches with the PMMERGE.DLL you MIGHT be able to trace the crash.
The crash could be caused by an font installed. I have seen that happen as well.
Why do you think I suggested using PMDF and making a procdump of the process crashing ?
I will not try and get engaged anymore to try and help debug a problem anymore.
Good luck swapping files around.
Roderick