• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Problem with SETISpy

Time2Kill

Golden Member
Everything seems to work in SETISpy except for the user stats. The update button is grayed out and my name isn't in blue so I can click on it. But, if I browse through my network, and open SETISpy up from one of my networked machines, it works just fine, and I can update it and get my newest results.

I have tried coping and pasting SETISpy and the ini from one of the other machines and it still doesnt work. Any idea on what I could try?

Thanks
 
same thing happens to me. On some machines I can update and click on the link and on others I cant. I have no idea why it does that.
 
Ok. I've heard SETISpy has some problems with XP, but it should be ok with 2K.

If you're using SETI Driver, are you checking the "Use SETISpy" box in SETI Driver?
 
I confirm what CRV said above
I had this problem, followed the instructions in the link and it started working!
 
I'd like to try running SETISpy but I have XP and it seems there are problems with running it in XP. SETISpy just said that XP users may experience crashes - does that mean SETISpy crashing or the whole computer/XP crashing? Has anyone here tried running SETISpy on XP? What have been your results? Thanks.
 
The only time I have experienced SetSpy crashes is at boot--I have it in my startup folder. I would estimate it crashes less than 5-10% of the time but I don't boot up that much with XP (24/7 😉), and it does not affect anything other than SetiSpy. When I manually restart it, it works like a charm. I used bootvis to reorder my start up files, and run SetiSpy in W2K mode with visual themes diasbled. It really is not a big issue anymore.
 


<< The only time I have experienced SetSpy crashes is at boot--I have it in my startup folder. I would estimate it crashes less than 5-10% of the time but I don't boot up that much with XP (24/7 😉), and it does not affect anything other than SetiSpy. When I manually restart it, it works like a charm. I used bootvis to reorder my start up files, and run SetiSpy in W2K mode with visual themes diasbled. It really is not a big issue anymore. >>



Great, thanks.
 
Back
Top