1.if possible, i would like to know the process step by step.
2. in which cases this helps?
_________________
ELVIS LIVES
<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-03 15:35 ]</font>
<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-04 04:05 ]</font>
sfp startup in below normal priority
it might help if you are really maxing out your computer(running two heavy audio apps, lots of tracks and vsts). it's easy to change priority on the fly anyway. just hit cntrl-alt-delete, choose the "Processes" tab, right click on the app in question(for example "SFP.exe"), and then select "Set Priority" and highlight your choice of priority. experiment a little to find how your machine runs best before going any further and don't play with it if there's no reason to(imho).
make a new text file and enter the priority you want to use and the path of your sfp.exe, now save the file as .bat
Double click this file to run scope.
This is the text you must edit:
Echo off
Start /low c:sfpAppBinSFP.exe
p.s. with this example you must run scope without the startup project, otherwise you must edit the following text:
Echo off
Start /low c:sfpAppBinsfp.exe -s
save it as .bat
go to the windows registry (regedit)
search the string : sfp.exe -s , double click on it and change the address with the one of the .bat file you have created.
<font size=-1>[ This Message was edited by: djmicron on 2006-03-03 16:54 ]</font>
<font size=-1>[ This Message was edited by: djmicron on 2006-03-04 04:43 ]</font>
Double click this file to run scope.
This is the text you must edit:
Echo off
Start /low c:sfpAppBinSFP.exe
p.s. with this example you must run scope without the startup project, otherwise you must edit the following text:
Echo off
Start /low c:sfpAppBinsfp.exe -s
save it as .bat
go to the windows registry (regedit)
search the string : sfp.exe -s , double click on it and change the address with the one of the .bat file you have created.
<font size=-1>[ This Message was edited by: djmicron on 2006-03-03 16:54 ]</font>
<font size=-1>[ This Message was edited by: djmicron on 2006-03-04 04:43 ]</font>
ok thanks, i downloaded the file ok.... and i think that i found an easier way to do it found in "Xona.com"
Run Tasks in Low Priority
"This article explains how to have any task (program) run in various priority settings by default. Most tasks default to "Normal" base priority. "Windows Task Manager" runs in "High" base priority by default. (By the way, "Windows Task Manager" is how to manually set already executing tasks to different priority settings.) Typically, if you ever want to change a task's default priority setting, you will probably want to set it to a lower priority, either "BelowNormal" or "Low".
Running a task in low priority does not mean that it will run slow. Unless it is competing heavily with another CPU-intensive program, it will run (almost) as fast as normal. The benefit is that in low priority it will take the "back seat" whenever you want to use the computer to do something non-CPU-intensive, like open up Internet Explorer or check your email. Normally, when you do something CPU-intensive, like running an Adobe Photoshop filter, your computer becomes inoperable while the task executes. This does not have to happen. A CPU-intensive task should give you a few seconds of CPU resources to accomplish something as simple as checking your email, if you want it to. Setting the CPU-intensive task to a lower priority accomplishes exactly that. The few seconds lost by that CPU-intensive task will, more than likely, be unnoticeable. Even if it was noticeable, wouldn't you want your computer to response to you when you ask it to do something else, even at the cost of slowing down a long-running CPU-intensive task?
However, there are limitations. Remember that a lower priority task will always take the back seat to a higher priority task until that higher priority task is finished. This means if you have two long-running tasks competing for CPU resources, and they are set at different priority levels, then one will take the "back seat" to the other until one is finished.
(For your information, the information found in this article is extracted out of my Windows XP Setup Tweaks & Tips article. It may contain extra information beneficial to you.)
How To Run Tasks in Low Priority Automatically in Windows XP:
* Create a copy of the icon of the task. This is a precaution; In case you ruin the icon, you will still have the original. From herein, we are dealing with the new copy of the icon in question.
* Right-click the icon of task, "Properties", "Shortcut", "Target:"
* I will use Adobe Photoshop as an example.
* Modify as follows...
* But first, pay very special attention to the quotes as I have to quote quotation marks to show you how to do this. You actually have to use some quotation marks, so do not quoted quotation marks!
* Change...
* "C:Program FilesAdobePhotoshop 6.0Photoshp.exe" (with quotes)
* ...to...
* C:WINDOWSsystem32cmd.exe /c start "Adobe Photoshop" /belownormal "C:Program FilesAdobePhotoshop 6.0Photoshp.exe" (with quotes; notice there is no quote at the beginning)
* /c is a command line parameter to cmd.exe. It "Carries out the command specified by string and then terminates." This is necessary as you do not want cmd.exe running in the background after opening the task.
* start is actually a program. Try running "start /?" (without quotes) from the command prompt to see all the options.
* "Adobe Photoshop" (with quotes) is the title of the task. You can set this text to whatever you want. I set it the same as the original task.
* The /belownormal sets the priority to "below normal". You can double check this in Windows Task Manager (CTRL-ALT-DEL) after you run the task. You could have also used /low to set the priority to "low".
* "C:Program FilesAdobePhotoshop 6.0Photoshp.exe" (with quotes) is the orinigal task itself. Notice that this does not change from before to after.
How To Run Tasks in Low Priority Automatically in Windows 2000:
Follow the How To Run Tasks in Low Priority Automatically in Windows XP" section above, only change "C:WINDOWSsystem32" part to "C:WINNTsystem32".
in windows xp and our case: C:WINDOWSsystem32cmd.exe /c start "ScopeFusion"/belownormal "C:Scope_4_5AppBinSFP.exe"
_________________
ELVIS LIVES
<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-04 03:16 ]</font>
<font size=-1>[ This Message was edited by: arcadios on 2006-03-04 04:00 ]</font>
<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-04 04:02 ]</font>
Run Tasks in Low Priority
"This article explains how to have any task (program) run in various priority settings by default. Most tasks default to "Normal" base priority. "Windows Task Manager" runs in "High" base priority by default. (By the way, "Windows Task Manager" is how to manually set already executing tasks to different priority settings.) Typically, if you ever want to change a task's default priority setting, you will probably want to set it to a lower priority, either "BelowNormal" or "Low".
Running a task in low priority does not mean that it will run slow. Unless it is competing heavily with another CPU-intensive program, it will run (almost) as fast as normal. The benefit is that in low priority it will take the "back seat" whenever you want to use the computer to do something non-CPU-intensive, like open up Internet Explorer or check your email. Normally, when you do something CPU-intensive, like running an Adobe Photoshop filter, your computer becomes inoperable while the task executes. This does not have to happen. A CPU-intensive task should give you a few seconds of CPU resources to accomplish something as simple as checking your email, if you want it to. Setting the CPU-intensive task to a lower priority accomplishes exactly that. The few seconds lost by that CPU-intensive task will, more than likely, be unnoticeable. Even if it was noticeable, wouldn't you want your computer to response to you when you ask it to do something else, even at the cost of slowing down a long-running CPU-intensive task?
However, there are limitations. Remember that a lower priority task will always take the back seat to a higher priority task until that higher priority task is finished. This means if you have two long-running tasks competing for CPU resources, and they are set at different priority levels, then one will take the "back seat" to the other until one is finished.
(For your information, the information found in this article is extracted out of my Windows XP Setup Tweaks & Tips article. It may contain extra information beneficial to you.)
How To Run Tasks in Low Priority Automatically in Windows XP:
* Create a copy of the icon of the task. This is a precaution; In case you ruin the icon, you will still have the original. From herein, we are dealing with the new copy of the icon in question.
* Right-click the icon of task, "Properties", "Shortcut", "Target:"
* I will use Adobe Photoshop as an example.
* Modify as follows...
* But first, pay very special attention to the quotes as I have to quote quotation marks to show you how to do this. You actually have to use some quotation marks, so do not quoted quotation marks!
* Change...
* "C:Program FilesAdobePhotoshop 6.0Photoshp.exe" (with quotes)
* ...to...
* C:WINDOWSsystem32cmd.exe /c start "Adobe Photoshop" /belownormal "C:Program FilesAdobePhotoshop 6.0Photoshp.exe" (with quotes; notice there is no quote at the beginning)
* /c is a command line parameter to cmd.exe. It "Carries out the command specified by string and then terminates." This is necessary as you do not want cmd.exe running in the background after opening the task.
* start is actually a program. Try running "start /?" (without quotes) from the command prompt to see all the options.
* "Adobe Photoshop" (with quotes) is the title of the task. You can set this text to whatever you want. I set it the same as the original task.
* The /belownormal sets the priority to "below normal". You can double check this in Windows Task Manager (CTRL-ALT-DEL) after you run the task. You could have also used /low to set the priority to "low".
* "C:Program FilesAdobePhotoshop 6.0Photoshp.exe" (with quotes) is the orinigal task itself. Notice that this does not change from before to after.
How To Run Tasks in Low Priority Automatically in Windows 2000:
Follow the How To Run Tasks in Low Priority Automatically in Windows XP" section above, only change "C:WINDOWSsystem32" part to "C:WINNTsystem32".
in windows xp and our case: C:WINDOWSsystem32cmd.exe /c start "ScopeFusion"/belownormal "C:Scope_4_5AppBinSFP.exe"
_________________
ELVIS LIVES
<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-04 03:16 ]</font>
<font size=-1>[ This Message was edited by: arcadios on 2006-03-04 04:00 ]</font>
<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-04 04:02 ]</font>
the "-s" switch starts scope in the tray, it doesn't change its priority. the prefix "start /low" does start scope in low priority.On 2006-03-04 04:13, arela wrote:
The easyest way of setting SFP to start in low priority is to right clik SFP icon on your desktop and right click the icon.
Now choose properties, then ad -s, apply and ok
eg
C:SFP4AppBinSFP.exe
is now
C:SFP4AppBinSFP.exe -s
Does anybody now the syntax for above normal?
more has been done with less
https://soundcloud.com/at0m-studio
https://soundcloud.com/at0m-studio