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

Hey, who did the WU for me?

Ken g6

Programming Moderator, Elite Member
Moderator
I just noticed this in my OK SetiQ History:

ASUS.1625728.3.3.i386-winnt-cmdline

With a 7 hour WU, so I know it's not one of my Athlons.

So, thanks! 😀 But who was it? 😕
 
It could have been one of the OK SETIQueue mixup WU's...seems that OK's Queue changed some of the userinfo.sah files on some of the WU's sent out after/during the CRASH...

🙁

It's been a problem floating around...so check your user_info.sah to make sure all the WU's have the correct ID...

🙂
 
It's probably related to the recent problem with OK's proxy. Someone's user_info.sah must have gotten switched with yours.
 
Well, I'm starting to feel guilty about taking WUs from a stranger. 😱 So if anybody wants to come forward (even if you don't feel the need to correct the situation 😉) the WUs are coming from:

Name: *.strhg1.mi.home.com
Address: 24.255.193.108

Whoever it is must have about 2 stray members of their herd.

And whoever you are, thank you. 🙂
 


<< Well, I'm starting to feel guilty about taking WUs from a stranger. 😱 So if anybody wants to come forward (even if you don't feel the need to correct the situation 😉) the WUs are coming from:

Name: *.strhg1.mi.home.com
Address: 24.255.193.108

Whoever it is must have about 2 stray members of their herd.

And whoever you are, thank you. 🙂
>>




That's my ip. I had the exact same problem with my SetiQ yesterday.
 
Back
Top