Seti still giving me headaches

[andz]

Altough I'm caching only 2 W/Us, seti 3 still shows up error messages. The system hangs, or restart all by itself. Will delete seti one last time. Will install seti/spy/driver once again, this time will set driver to cache only 2 W/Us from the beggining. Last time I did set the cache for 5 and after trouble showing up, backed it to 2 W/Us. Any other piece of advice... this is the moment. I will try it on monday. Also will change the memory stick to another slot (it is just something I heard round here but will give it a try too)...

[TC]

I have no idea what to tell you. That's plain odd.

[chawken]

Originally posted by andz
Altough I'm caching only 2 W/Us, seti 3 still shows up error messages. The system hangs, or restart all by itself. Will delete seti one last time. Will install seti/spy/driver once again, this time will set driver to cache only 2 W/Us from the beggining. Last time I did set the cache for 5 and after trouble showing up, backed it to 2 W/Us. Any other piece of advice... this is the moment. I will try it on monday. Also will change the memory stick to another slot (it is just something I heard round here but will give it a try too)...

Setiathome-3 error is nothing to do with your cache. If you look in your task manager, that is the client. When running the client, two progs show up in the task manager - Setiathome-3 and winoldap. Now I have found that in a lot of instances, if a corrupt WU is being transmitted, it will cause Setiathome-3 to perform an illegal operation. Not much you can do except reboot the computer, and try to clear that corrupt WU out. Since there have been a lot of corrupt WU's, you will probably see quite a few Setiathome-3 errors - I know that I have to clear at least half of my machines every day now.

[andz]

Thanx a lot for the valuable info. Haven't installed seti yet. But will very soon ...

[M@€$†®Ö™]

Like TC said that is strange !

Maestro

[chawken]

Originally posted by Maestro
Like TC said that is strange !

Maestro

It is. There is something in the corrupt WU's that just screws everything up. Setiathome-3 will perform an illegal operation, and if you don't catch it, you aren't crunching anymore. This has been happening for about a month - and about 10 days ago, Berkeley finally owned up to the problem. Last week my dual amd machine was off the network for a couple of days. When we got our network up and running again (due to the nimda virus) I had 16 units ready for transmit. Every one of them caused Setiathome-3 to perform an illegal operation. All 16 units were corrupt. That is when I tried to transmit about a 105 WU's and only got credit for 10 or so.

[andz]

Installed it last night, (the seti combo) Crunched 2 W/Us and no problems yet. Now caching 2 W/Us... Will keep ya all informed about progress........