Problem with SETISpy

Time2Kill

Golden Member
Nov 20, 1999
1,816
4
81
www.brooksidestorage.com
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
 

SWScorch

Diamond Member
May 13, 2001
9,520
1
76
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.
 

Sukhoi

Elite Member
Dec 5, 1999
15,350
106
106
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?
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
I confirm what CRV said above
I had this problem, followed the instructions in the link and it started working!
 

BMdoobieW

Diamond Member
Oct 26, 2000
3,166
0
76
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.
 

JimMc

Platinum Member
Oct 9, 1999
2,305
0
0
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.
 

BMdoobieW

Diamond Member
Oct 26, 2000
3,166
0
76


<< 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.