Uplink+seti work units timings

[backitcaise]

Using Suse 8.1, whilst running uplink it screws up seti`s unit timings by adding uplinks cpu time to the units time giving extra long unit results, have tried changing priority of both progs and renicing one above the other but still no joy, this means that my records on seti are reading wrong, no other prog does this, been running seti since it started, any ideas?

[Cold Fusion]

heh, that's definitely a new one.

I've got SETI@home running, I'll check in a few hours to see if Uplink affects it. I'm running Windows though, so I don't know if that makes a difference.

[backitcaise]

Thanx, I will have to try and see if it does the same on my win2000 machine, only got the game on monday so have not had time to "play" properly with it yet.

[NeoThermic]

I think you will find its because Uplink uses up processor time. Therfore, SETI cant process its units during Uplink playing, and therfore the timer continues on the length of your SETI unit.

If it totaly stops SETI, then I recommend stopping SETI during game play and starting it after uplink game play. either that or set SETI to a higher processor schedual setting.

Also note that anything that needs lots of processor time will get it over SETI, because SETI runs idle, and therefor if there are no spare clock cycles, SETI can't use them

Good Luck
NeoThermic

[backitcaise]

yep have tried juggling the priorities of both progs, and even with seti running higher it still amalgamates the total cpu time of uplink+seti, I can run other intensive progs without it affecting seti ( even half/life under wine does not corrupt seit`s calculation of the cpu time used on a unit .

I am doing one work unit in approx 3:30hrs normal operation 24/7 on an xp2000 for the last 6 months and have been with seti for nearly 4 years and have never had another prog interfere before.  If I run uplink the seti unit reports double cpu time,  I will post on seti group to see if anyone there can give me a hint.

PS why does uplink run with the lowest prority as default ( 19 )? I would have thought it would need higher on for slower machines.