I don't think that acemd.exe changes it's default priority. The default priority seems to be "below normal", and what Mouser is suggesting is that once PT changes it to "normal", it's being changed back to "below normal" (after quite variable time spans, which seems strange, anyway).
On all other machines with which I run acemd.exe, there is no problem. It's just this one PC with an older CPU, where acemd.exe suddenly stopps running. And what I have found out was that this does NOT happen once it's priority is at "normal".
This is the reason behind the whole thing.
Ah, that's interesting.
From what you know, does this mean that the default
priority of the process/program acemd.exe
, is "below normal"
computers where it is installed, but that it is just on the single older computer that you suspect that is what causes the program to abend with no(?) error message?
Are all these computers running the same OS and, if not, then what are the differences?
Is there an Event Log for the computer (with the abending process) in question? That might help to identify/indicate a possible root cause of the abend. Similarly, the Event Logs for the other computers might be able to throw some light on the behaviour of the non-abending process' default operation.
At the moment, it seems that you cannot be certain as to what the root cause of the abend actually is.
You only know (presumably by trial-and-error) that the abend seems to not
occur if the process priority is set to normal. (Is that correct?)
Thus, altering the process priority with PT (Process Tamer) might only be a workaround to an as yet undefined problem, at best.