Windows Tip: Launching a low priority process
A friend of mine who is a petroleum engineer recently told me about a problem he was having. He was launching a series of batch jobs (big simulation jobs) on his Windows XP workstation from the command line by running a batch file that contained a series of commands like job5.exe -i input.dat, and his problem was that these jobs were hogging so much of his machine's processing power that foreground tasks became unresponsive. Once these processes were running however, he could open Task Manager and change their priority to Low, and then he could work normally on the machine while the jobs ran in the background. He was wondering if there was a way to start an application with Low priority instead of Normal. It turns out there are several solutions to this problem.
View full article »
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
Parameters
Please show an example of how to launch a command in low priority where the command includes parameters that must be specified in quotes (e.g. parameters that are filenames with spaces)Yes please.
Yes please.Solution
OK, the solution to the first poster's problem is to put some text (it doesn't matter what) in quotes before any of the other quoted stuff. As good a place as any to put it is right after the START clause.The reason is that the START command automatically assumes the first quoted string is the name you want to give the new window. Regardless of whatever the first quoted string is actually supposed to do.
Bad design decision on Microsoft's part. They should have made it so that the name of the new window follows an actual flag. But they didn't. So we have to fix their mistake.