I just noticed that Logos5.1 (RC2) is running at "Below Normal" priority (according to Windows Task Manager (Win7).
Is this on purpose? If so, why?!!
This is either a bug, or a problem specific to my system.
Adding this to the above (rather than editing):
I set Logos5 to "Normal" but after restarting Logos, it was reset to "Below Normal." This would be expected if the program is designed to start at "Below Normal" priority.
Something is wrong.
Logos 5 runs "Normal" for me in Win 7 but some tune-up utilities will lower this as an optimisation when it starts.
I can't reproduce this (on Windows 8), and I don't know of any code in Logos 5 that would set the process priority to Below Normal.
I suspect a problem specific to your system, although I don't know of any built-in Windows features to set the default process priority, so I'm not sure how this could be happening.
Supposing the Logos indexer runs at "Below Normal" and I noticed that LogosCom.exe was also running at "Below Normal". If this setting is in a config file or the system registry, might either one of those files gotten confused? If the setting is in the EXE, which EXE would it be in. I'd be happy to send it for inspection.
(Running "Repair" from Windows "Programs and Features" did not change the priority on restart of Logos5.)
I may have it figured out.
It looks like when I start Logos (or other programs) from a keyboard button on my Microsoft Ergonomic 4000, the program starts "Below Normal" This happens for any program started by this specialized keyboard.
If I start from a short-cut, it starts just fine. Sounds like a problem with the MS Intellitype / Intellimouse system, being not so "intelli..."
I suspect a problem specific to your system, although I don't know of any built-in Windows features to set the default process priority, so I'm not sure how this could be happening. I may have it figured out. It looks like when I start Logos (or other programs) from a keyboard button on my Microsoft Ergonomic 4000, the program starts "Below Normal" This happens for any program started by this specialized keyboard. If I start from a short-cut, it starts just fine. Sounds like a problem with the MS Intellitype / Intellimouse system, being not so "intelli..."
Update: I did get this resolved.
For those who are interested, the problem is that the hot keys for the keyboard are driven by MS Intellitype (itype.exe), which was recently updated to start from the Task Scheduler (TS), rather than through another startup scheme. TS by default, starts programs at "Below Normal" priority, with no way to change this in the TS UI. When itype is running at "Below Normal" priority, programs started via hot keys start at "Below Normal" too. The solution is to get itype to start at "Normal." (One normally cannot change the startup priority of a program in the Windows OS without a 3rd party solution.) However, since itype is started by TS, the startup priority is possible to change, by exporting, editing and then importing the task parameters (changing the Priority parameters from 7 ("Below Normal") to 6, 5, or 4 (all of which are "Normal")). BTW, there are 2 tasks started by TS which run itype. (I know that sounds complex, which explains why it took so long to figure out and solve. Thanks, btw to a "community star" at the MS forums for finding the solution to my problem.)
This is definitely a MS issue, not a Logos issue. If there's a case for this at Logos (which I doubt), it should be closed.
