31
Setup & Installation / MARKEXE vs EXECMODE - differences?
« on: October 15, 2022, 05:47:06 pm »
Hi everyone,
I've had a persistent problem with some apps putting a complete soft-lock of my machine. This normally happens during application start-up, but occasionally it would also happen throughout execution. I know, it sounds weird, but it's absolutely consistent and in appears to be related to an underlying component DLL, although I'm still working through pegging that detail.
Anyways, so to avoid that dreaded outcome I found that the best way to deal with this problem is to start up the "offending" app with all CPU cores but core_0 disabled. I do this with the handy setproc utiility.
Alright...but doing this manually is a PITA, so I have a quick SMPOFF/ON wrapper *.cmd template that I have been using for such apps.
However, it would seem to me that perhaps flagging to offending EXE as SMP-unsafe would provide a better result. Well, I tried this but with rather bleak results, or to be more precise, no results. The lock still occurs, and maybe it's because it's a DLL issue as opposed to the main EXE (therefore parent vs child execution path issue).
But...if my understanding of how these two utilities control the SMP flags is incorrect, well, that may have a key bearing on what I'm seeing.
They both enable you to flag a particular EXE as MPU unsafe, and yet for exmaple flagging a sample EXE with execmode doesn't seem to show the correct status when querying it up in markexe, so what gives?
I've got some examples here to illustarte this, but for starters I'm looking for a general understanding of what's different in terms of how these two utilities mark a EXE?
I've had a persistent problem with some apps putting a complete soft-lock of my machine. This normally happens during application start-up, but occasionally it would also happen throughout execution. I know, it sounds weird, but it's absolutely consistent and in appears to be related to an underlying component DLL, although I'm still working through pegging that detail.
Anyways, so to avoid that dreaded outcome I found that the best way to deal with this problem is to start up the "offending" app with all CPU cores but core_0 disabled. I do this with the handy setproc utiility.
Alright...but doing this manually is a PITA, so I have a quick SMPOFF/ON wrapper *.cmd template that I have been using for such apps.
However, it would seem to me that perhaps flagging to offending EXE as SMP-unsafe would provide a better result. Well, I tried this but with rather bleak results, or to be more precise, no results. The lock still occurs, and maybe it's because it's a DLL issue as opposed to the main EXE (therefore parent vs child execution path issue).
But...if my understanding of how these two utilities control the SMP flags is incorrect, well, that may have a key bearing on what I'm seeing.
They both enable you to flag a particular EXE as MPU unsafe, and yet for exmaple flagging a sample EXE with execmode doesn't seem to show the correct status when querying it up in markexe, so what gives?
I've got some examples here to illustarte this, but for starters I'm looking for a general understanding of what's different in terms of how these two utilities mark a EXE?