FYI
I was having a performance issue w/1 of my MASM programs running
under WTS (Windows Task Scheduler) doing many 'INVOKE FindNextFile's.
In my case, it was SEVERLY dragged down by 2 normal I/O-intensive
tasks because, per Process Explorer, its' I/O Priority was LOW
compared to the other tasks which were NORMAL. It ran 600 times(!)
LONGER than expected!
Fortunately, I found a fix here:
https://bdbits.wordpress.com/2010/04/29/setting-a-scheduled-task-process-priority/
This worked great. Instead of running 30 minutes, it took about a minute.
Still slow due to the others' interference, but WAY BETTER and tolerable!
Strange that this is the default, and not changeable via the WTS GUI?
I've noticed that programs requiring file i/o are often slow on Win7, and much worse on Win8, as compared to XP. Interesting find :t