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

Help, problems with SETIQ & v3.03.....

Assimilator1

Assimilator1

Elite Member
I was running V3.0 CLI with SETIQ 78b no probs ,I had patched the clients to connect to SETIQ.
Today & yesterday I switched to v3.03 ,patched them the same way I had before & altered no settings.
I come back from work today to find my SETI had stalled 🙁 ,it was unable to connect to SETIQ .

In the end I switched to an unpatched client & used the IP add in the command line which eventually worked ,no probs here.
But I have a 3rd machine which I have to disable the Networkcard when not needed or it crashes far more often (It's got a PC chips board :disgust: & a very old LAN card).If I'm to use SETIQ on this I must get the patch to work.My 3rd PC will go idle tommorow morning if I can't get it sorted 🙁

BTW I'd rather not use SETIdriver because I would lose some SETIQ stats ,but I will if theior is no choice.
So has anyone used the patch successfully with v3.03 ? if so,how?

Thanks 🙂
 
I'm not certain what your setup is. Do you have 1 machine running setiQ for the network or a copy of setiQ on each machine?😕

You do remember the only client you patch is the one on the setiQ server itself?

If you're running 1 setiQ server feeding the entire network then getting around your problem would be very easy. Install SetiDriver on the machine that you have to disable the NIC in. Set the proxy settings in SetiDriver to point to setiQ & disable auto transmit. Have SetiDriver download a couple of days worth of wu's from setiQ. Then you can manually flush the wu's from that machine to the setiQ proxy. This way you still get the setiQ stats & the machine has wu's when you disable the NIC.🙂
 
Atm I have 1SETIQ per machine.
Yep to your 2nd point🙂

And thats a good way to get around the SETIQ problem 🙂,even though it doesn't get the Q going on that machine.
Thanks😎
 
Oh well ,I guess no one else uses the SETIQ patch here! lol

Looks like I'll be using SETIDriver to feed off SETIQ 😉
 
Hey Assim1, here's my setup.
1 Machine running setiQ to feed the network. I have SetiDriver installed on it as well. I did this because it's easier to me to just set the proxy settings in setidriver to point it to setiq instead of fooling with a shortcut with proxy settings or patching the client.

2nd & 3rd Machines running setidriver with proxy settings pointed to setiq.

SetiQ has 5 days worth of wus stored & each machine has 1 days worth stored in setidriver. So if my network or setiq server goes down the other 2 can keep running & I don't have to try & hide the setiq dos box on them either.

Not the smoothest setup but very easy to configure, reconfigure & update the clients.🙂



 
I have it setup now 🙂

My main PC has SETIQ on it ,I have SETI pointing to the Q just by putting the IP add in the command line & qseti.txt (it's that easy! 😉😛) ,my other (temporary) PC has SETIdriver on it with just over 1 days worth of WU's on it ,it fetches WU's from SETIQ on my main PC when I enable the LAN card when I get back from work.

Oh just 1 thing! ,I didn't realise that SETIDriver would trash a partly finished WU when you 1st run it!:| ,it was at 80% too (about 14hrs worth).
Oh well at least its running now ,thanks again for the help 🙂

BTW 1 feature of SETIDriver that I really like is it's ability to switch(upgrade) clients 🙂
 
Yes that upgrade feature is very nice. You don't have to sit around & wait for the unit to finish to keep from losing it. I think it was just added in the last update to the program. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top