Jeff,
Have you tried the setidriver program? This program will change the
priority 'on-the-fly' or maintain the settings you store in it's
config file. It also has the additional capability to cache WU's
(as many as you want) to aid in the connection attempts to Seti.
It offers priority settings of low, normal, and high processing
speed.
If you want a solution that doesn't require intervention, this is
the program you want...install it, set it up with the number of
processes to run at the same time (for multiprocessor machines),
how man WU's to cache, and the priority to run them...then set up any
proxy/socks, transmit options, then save those settings.
Whenever you start processing packets with setidriver it will use the
same settings. This is an easy way to accomlpish what your looking to
do. Its worth checking out.
http://www.wakeassoc.com/setidriver/
(Keep your commandline client, you will still need it. This program is
only a frontend to the client.)
Setting Process Priority
================
I'm running SETI@home's text-only client (CLI) on a Windows 9x machine and
wish to have the client automatically start processing work units with a
process priority of 'Normal' rather than the default 'Idle' setting.
I know that I can manually change process priority under Windows 9x with a
third-party task manager such as Igor Arsenin's excellent TaskInfo2000
(http://www.iarsn.com), but this change only sticks as long as the client is
running. If the client is stopped and restarted, it's back to square one
and 'Idle' priority, so what I'm looking for is a solution that doesn't
require repeated manual intervention.
************************************
==
Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html
This list sponsored by talkspace.net: building space communities online.
Mailing list services provided by klx.communications -- www.klx.com
