I've noticed a significant increase in stability of the scheduler and multitasking under XP when changing Max to High priority via Windows Task Manager. However, when trying to invoke High priority mode via a .bat file as
start /HIGH /d"C:Program FilesCycling '74MaxMSP 4.5" max.exe
..inspecting the priority under task manager shows it UNCHANGED as Normal priority, requiring it to be set manually. I could have my syntax above incorrect (god help me), but it seems to me that starting max with a High priority may be locked. I do know that the following works correctly...
start /HIGH notepad.exe
inspecting taskmanager shows that the priority as successfully changed..
Now I wouldn't normally mind but setting Max to high seems to work wonders when using vsts and OSC messages, I get no breakups when changing max out of the foreground and such, and would love to see either whatever it is that prevents priority alteration at max startup unlocked or an option somewhere for us windows users, it really does make things a lot more stable! Of course, it works only by setting in manually in the task manager at the current time.