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

Thank God for SetiQueue

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
The Magicman;
any new users to your Q will setup a cache but the WU's will have to be manually put in the cache.
once this is done it will work fine till that cache runs dry.
this is what i have been doing for everyone that is connecting to my Q, somwhat messy but it keeps us all running. i have now redistributed all unmarked WU's (check the .ini) with a little redundancy🙂

artemedes;
your client should d/l WU's with no problem now🙂

😎 😎
 
Its Working!!! Thanks The Magicman! Oh by the way, I also tried giving the IP of the machine running the Q, but it cant seem to connect to it. It doesn't even send a result. This machine only has one IP. I think it has something to do with the network setup. It is a Novell netware system using a netware client. My guess is that the netware server ignores the request for the machine to connect back to itself or something like that. dunno really just a guess.


Thanks again.
 
artemedes - try using the ip of 127.0.0.0 (or hostname "localhost&quot😉 to have it connect back to itself and see what happens...
 
Assimilator, yeah I think I passed you the day before SETI went down (hmmm, I smell a conspiracy😉) However, I'm just about all dried up, only 5 of my slowest machines are curently processing, I only had the Q set to 2.5 days deep:frown: So, here's your chance to catch back up!😀
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top