Some very strange findings when I went "snooping" into this problem.
My comp was giving me random freezes about a week ago after a annual shakedown and cleaning. I reseated all cards and RAM, thinking some dust got in there and shorted something out as it was running. Didn't solve the problem.
Thought it was the hdd- did diagnostics with NDD and Maxtors' PowerMax certification (handy little utility from
www.maxtor.com)- these both gave a clean bill of health.
Then my friend said- "use MS scandisk- it might pick something up" I didn't think so, but tried anyway. Low and behold- bootlog has been corrupted. Tthere are 125 missing clusters in 1 chain. I prompted to fix them and all has been fine since- except SetiQ.
SetiQ was starting maximized- when I had previously had it set to minimized. It has reset all my SetiQ to clients data as if I just started my Q 2 days ago when I fixxed this. SetiQ to SetiServer stats remain the same as before. IP and subnet mask were not correct (thanks Confused). Now my password is inaccessible. When I change settings in the local machine it resets them to no value. Don't know how to get this straightened out???