Dos utility running 100% in XPpro

[Geoff]

Hi All

One of my clients is running a dos util which grabs 100% of the proccessor. I can go into Task manager and set the virtual dos manager to low prority but I can't seem to find where I can set this to start automaticly low.
Can any one help please.

[3fingersalute]

Hi All

One of my clients is running a dos util which grabs 100% of the proccessor. I can go into Task manager and set the virtual dos manager to low prority but I can't seem to find where I can set this to start automaticly low.
Can any one help please.

What is the utility??

[Geoff]

What is the utility??

The utility is a a home made dos program which scans a dir for files and then prints them and then changes the extension. I'm not sure what its writen in.
I was hoping for a tick box somewhere to tick

[FatalException0E]

You can launch it from a batch file or shortcut and use the start command to set the priority.
Here's an excerpt from running start /?

START ["title"] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
[/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL]
[/WAIT] [/B] [command/program]
[parameters]

"title" Title to display in window title bar.
path Starting directory
B Start application without creating a new window. The
application has ^C handling ignored. Unless the application
enables ^C processing, ^Break is the only way to interrupt
the application
I The new environment will be the original environment passed
to the cmd.exe and not the current environment.
MIN Start window minimized
MAX Start window maximized
SEPARATE Start 16-bit Windows program in separate memory space
SHARED Start 16-bit Windows program in shared memory space
LOW Start application in the IDLE priority class
NORMAL Start application in the NORMAL priority class
HIGH Start application in the HIGH priority class
REALTIME Start application in the REALTIME priority class
ABOVENORMAL Start application in the ABOVENORMAL priority class
BELOWNORMAL Start application in the BELOWNORMAL priority class
WAIT Start application and wait for it to terminate
command/program
If it is an internal cmd command or a batch file then
the command processor is run with the /K switch to cmd.exe.
This means that the window will remain after the command
has been run.

If it is not an internal cmd command or batch file then
it is a program and will run as either a windowed application
or a console application.

[Geoff]

That looks just the job. I'll have a go when I get back on site.

Thanks for your help

Geoff