Would some using SetiTEAM...do a test run & report

[Smoke]

I have been getting a strange error message when trying to do a COMPARE after running an UPDATE.

I have already written the author of the program about it but he is in Europe and won't be available until tomorrow sometime. It would be helpful to find out if the problem is just with my system or is it something wide spread...caused by another change in the way Seti At Home handles its webpages.

I would appreciate it if any of you running SetiTEAM would do a test run and try to compare with a saved file...and report the results back to this thread.

Thanks.

 

[ScottMoDSLR]

SetiTeam is returning: " is not a valid integer value

Its happening to all the teams. Seems SetiTeam is not parsing something correctly & gets hung up. I tries versions c,h, & i and none of them work.

At DSLR, a teammate gave me this work around:

As a work around for the current setiteam problem, if you update the stats, with the auto compare turned off, shut down setiteam and then edit the setiteam.sav file by adding the following lines after the 1,1,(#1) line :
3,1,0
4,1,0 years
5,1,0 hr 0 min 0 sec
Restart setiteam and do the compare.

Worked for me. Might want to give it a go.

 

[Smoke]

Thanks for that, ScottMoDSLR.

I have already fired off an email to Sqiz about the problem. He is usually very responsive to me when a problem like this occurs. I wanted to be able to verify that it was a wide spread problem and not just something screwy in my setup. You have answered that question and I'll forward that on to Sqiz (the author of SetiTEAM).

I may try the work-around if Sqiz cannot get the fix up by later this morning. I've got a 1:00 PM CST Update I do everyday so I'll need it working by then or I'll have some very disappointed "customers".

Thanks again.

 

[Baldy18]

No stats makes Baldy18 sad.

 

[Orange Kid]

Still a no go?

Any reply from Sqiz?

Weekly stats could suffer too:frown:

Whats up with S@H and the constant changes:disgust:

 

[Smoke]

Nothing from Sqiz so far. He may be home for the holidays and won't be back until after the new year. He has in the past sent me beta versions that I test out for him and as soon as they seem stable he puts them up on his website. I'll be sure to let you know as soon this current problem gets worked out.

I had fits today with the work around suggested by ScottMoDSLR. It failed to work 5 or 6 times and then I'd get a successful COMPARE. Then it wouldn't work for a dozen more trys. Really a pain in the butt. It completely spoiled the records I've been keeping for us, DSLR, and IBM. So I'll have a gap in the historical data for today. And the same will be true tomorrow and the next if this doesn't get fixed.

BTW, OK Baldy18 sent me this LINK to a spreadsheet program. I tried this months ago but couldn't get it to work properly. I seem to remember you needed to do 14 days of data fetching before any usuable reports start getting generated. I see they have upgraded it lately and I was wondering if you have used it in the past or are currently using it?