- Joined
- Sep 15, 2003
- Location
- Yakima, WA - USA
I'm having trouble with seti driver. lol I went back through the archives here and didn't find anything that would work with this situation.
Came home from work and checked the status of the comp and it was sitting idle with about 40 wu's waiting to process. That's great I thought, wasted cpu cycles. Closed spy and everything closed with it. Rebooted comp. Still idled, maybe I'm just getting adled.
At this point I uploaded what was done and del all the seti files except for the wu cache. Then I reinstalled everything and it didn't do anything but sit idle. Brought up the task panel and the clc (3.03) was at zero %. Closed spy and the driver didn't close (driver usually closes with the spy). Closed the driver and the clc removed it self from the task panel.
Went into the seti folder and opened the clc and it started up ok and the cpu usage went to 99%. At this point spy would tell me what the progress was. Opened driver and it came up idle and loaded a 2nd clc in the task panel. This 2nd clc was idle at 0%. This 2nd clc managed to suck up 900k+ of ram sitting there. The 1st clc was using about 15mb of ram give or take about 500k with the cpu load at 99%.
Closed the seti progs and deleted everything again except for the wu cache and went online and downloaded the latest and greatest versions of spy and driver. I kept the 3.03 clc as it seems to shave a few minutes off the crunch time per wu.
After getting the new files, I followed the sticky to the letter on how to get everything working together. Didn't work. Loaded up spy and it loaded the driver which brought up the clc in the task panel. Clc at 0% for cpu usage.
. Closed the spy and had to manually close the driver as it didn't go with the spy. When the driver left the building so did the idled clc from the task panel.
Opened the seti folder and started up the clc and spy was able to read the progress and the clc cpu usage was normal at 99%. Driver still will not do anything except load a 2nd clc at 0% usage... (sigh)
I'm getting tired of messing with it tonight. Seems the closer I get to a 1000 wu's completed the more troubles I have. In the past when I had this trouble I removed the old software and reinstalled it and then rebooted and everything worked fine.
Didn't seem to work tonight. I did reboot the system between reinstalls of the seti software.
Maybe I should whack the entire dir and start over with fresh wu's also? That's the only thing I haven't done yet...
Any ideas? Thanks team.
Don't know what importance it is, but the probs are with the p4 rig and it's running win xp pro. Computer isn't o/c'd and hasn't been for some time.
Oh well... I'll let the clc go by itself with the spy and check it before I leave for work in the morning to see what it's done.
Don't suppose the clc will use the cache without the driver being loaded? If it will, I may just do away with the driver and save myself the problems from now on... But I would like to use the driver if possible. Anyway...
Sleepy time. Good night.
-Tyrinon
Came home from work and checked the status of the comp and it was sitting idle with about 40 wu's waiting to process. That's great I thought, wasted cpu cycles. Closed spy and everything closed with it. Rebooted comp. Still idled, maybe I'm just getting adled.
At this point I uploaded what was done and del all the seti files except for the wu cache. Then I reinstalled everything and it didn't do anything but sit idle. Brought up the task panel and the clc (3.03) was at zero %. Closed spy and the driver didn't close (driver usually closes with the spy). Closed the driver and the clc removed it self from the task panel.
Went into the seti folder and opened the clc and it started up ok and the cpu usage went to 99%. At this point spy would tell me what the progress was. Opened driver and it came up idle and loaded a 2nd clc in the task panel. This 2nd clc was idle at 0%. This 2nd clc managed to suck up 900k+ of ram sitting there. The 1st clc was using about 15mb of ram give or take about 500k with the cpu load at 99%.
Closed the seti progs and deleted everything again except for the wu cache and went online and downloaded the latest and greatest versions of spy and driver. I kept the 3.03 clc as it seems to shave a few minutes off the crunch time per wu.
After getting the new files, I followed the sticky to the letter on how to get everything working together. Didn't work. Loaded up spy and it loaded the driver which brought up the clc in the task panel. Clc at 0% for cpu usage.
. Closed the spy and had to manually close the driver as it didn't go with the spy. When the driver left the building so did the idled clc from the task panel.Opened the seti folder and started up the clc and spy was able to read the progress and the clc cpu usage was normal at 99%. Driver still will not do anything except load a 2nd clc at 0% usage... (sigh)
I'm getting tired of messing with it tonight. Seems the closer I get to a 1000 wu's completed the more troubles I have. In the past when I had this trouble I removed the old software and reinstalled it and then rebooted and everything worked fine.
Didn't seem to work tonight. I did reboot the system between reinstalls of the seti software.
Maybe I should whack the entire dir and start over with fresh wu's also? That's the only thing I haven't done yet...
Any ideas? Thanks team.
Don't know what importance it is, but the probs are with the p4 rig and it's running win xp pro. Computer isn't o/c'd and hasn't been for some time.
Oh well... I'll let the clc go by itself with the spy and check it before I leave for work in the morning to see what it's done.
Don't suppose the clc will use the cache without the driver being loaded? If it will, I may just do away with the driver and save myself the problems from now on... But I would like to use the driver if possible. Anyway...
Sleepy time. Good night.
-Tyrinon
