This is because there is no concept of background or foreground for threads
which are marked as THREAD_PRIORITY_IDLE or THREAD_PRIORITY_TIME_CRITICAL
The scheduler will not discern between them back and fore with those
priorities.
THREAD_PRIORITY_TIME_CRITICAL Indicates a base priority level of 15 for
IDLE_PRIORITY_CLASS, NORMAL_PRIORITY_CLASS, or HIGH_PRIORITY_CLASS
processes, and a base priority level of 31 for REALTIME_PRIORITY_CLASS
processes.
THREAD_PRIORITY_IDLE Indicates a base priority level of 1 for
IDLE_PRIORITY_CLASS, NORMAL_PRIORITY_CLASS, or HIGH_PRIORITY_CLASS
processes, and a base priority level of 16 for REALTIME_PRIORITY_CLASS
processes, so it doesn't matter if it's back or fore.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/perfmon/bas
e/threadentry32_str.asp
Andy Mortimer [MS]
Please do not send email directly to this alias. This alias is for
newsgroup purposes only
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm "