Seti driver, anyways to stop it from taking over?

[Adul]

Well not taking over, but I leave my pc on all the time like a goodseti guy should. And for some reason, after a few days or more, the setidriver sort of refuses to die. I end up with 2 sessions of it running. I go into the task manager to kill both of them and it returns. I wouldn't normally care except sometimes i causes my pc to lag.

 

[htmlmasterdave]

That seems weird...

 

[medic]

Try setting the priority down a notch?

 

[Migroo]

<< That seems weird... >>



Yes, I havent experienced the problem you describe Adul...

 

[Robor]

Where does SetiDriver load from? Registry or Startup folder? Maybe it's in both by accident and starts 2 sessions?

 

[Megatomic]

To backup Robor, I start my SetiDriver from the startup folder for my profile and I don't have this problem.

 

[Adul]

startup folder.


First thing that will happen is the seti driver will disappear from the task bar. Then when i notice that I try to kill it. But it will not die. Keeps restarting itself.


I run windows XP

 

[Poof]

Adul - there was a somewhat similar problem posted at Ars last month except that for the poster, the machine appeared to hang. Mike Ober (Setidriver author) suggested that what might be happening is that there was a crashed client (due to a bad WU) and at that point, Setidriver doesn't know what to do next.

Normally, Setidriver uses little or no CPU time on its own. It basically sits there while the CLI does all the work, until such time that the CLI needs to upload/download WUs.

You might consider flushing your cache and starting fresh.

 

[Robor]

I know on my Win9x clients that are running SetiLog to hide the CL client to end the task I have to kill SetiLog first then the SETI process after that. Killing the SETI process doesn't work as SetiLog automatically restarts it. Maybe it's the same way with SetiDriver?