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

OT: Setiqueue & debugging a defunct athlon

onelin

Senior member
I dug up some posts and found a list of SETIqueues, but also the info that I should ask the queue's operator before beginning use (plus I'm not too sure how). Any help on this would be great since I have a ton to get done today, but can't let production drop!!!

The other thing is my poor athlon seems to be crashing every single night, and since it's a monitorless SETI box it's quite a pain. My debug idea: write a tool that pings it every minute and logs once it starts responding so I know the exact idea. I'm sure windows has some kind of error reporting that I can check, too, but I'm not sure what. It's running XP pro. It started with it never logging me in over remote desktop, but now it just drops off entirely. Hooking up a monitor the other night (when it was "frozen") did not turn the monitor on, of course it didn't have a keyboard plugged in at boot, so my keypresses didn't really help. I should have hooked up a USB mouse to see if it just lost network connectivity.
 
ken008: I'll check, but I have always configured all of my machines as always on so it's unlikely

RaySun2Be: Sweet! saves me the trouble

Xemus: That I haven't, and that's quite possible since the athlon fan is a total POS (stock fan)
 
On the SetiQ thing...go ahead and connect to mine, whenever you want. I have it set to automagically start issuing you WUs. (many Q operators set theirs to manual, so you have to contact them in order to get work put into your Q)
 
Back
Top