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

SETI Q setup question

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Have i told you guys lately that i love you :Q😀

Setup per Confused last post & all seems OK, so far. /crosses fingers 😉


So now here's what i have.
Computer #1 name- Polaris (this is the one that the SETI Q is on)
Computer name #2- Aldebaran

In SETI Q there is already a Polaris client. I entered Polaris for the host & 5517 for the port# in SETI Driver
If i enter the same info in SETI Driver on the Aldebaran computer, it will start an Aldebaran client, correct? Or does SETI Q see these as only one client?
 
You will get a 2nd client shown up in SETIQ/clients with a name of Aldebaran🙂
SETIQ by default uses the IP number to identify the SETI client

(And yeah different IPs sure will stop different PC's seeing each other,dunno why I didn't suggest that!😉)
 
😀

Thanks Confused for following up. 😀 It sounded like they weren't using the same IP scheme to me, thus the request for the IP addresses. Sure enough, that was it. 🙂

I was busy today helping my son install the new speakers he got for Xmas in the door panels of his car. 😀

 
Originally posted by: JWMiddleton


Now, quit messing with those machines and start crunchin! 😀
Sounds good to me 😀

One more question, for now.
I keep getting a dialog box popping up from SETI Q. This just started yesterday, i think. "Can't create file: (null)"
Anyone know anything about that? There's only an "OK" button there. Q seems to be working fine though.
 
I get that "null" message in XP Pro when I switch users without logging the current user off. SetiQ and SetiDriver keep running in the background for the first user and rig can't fire them up properly for the second user because only 1 instance of it can run on the computer. This is only a problem when the first user does not log off prior to switching, and give the rig a minute to refresh itself before logging in another user.

My solution:
I rarely switch users without logging the previous user off.
 
Originally posted by: JustStarting
I get that "null" message in XP Pro when I switch users without logging the current user off. SetiQ and SetiDriver keep running in the background for the first user and rig can't fire them up properly for the second user because only 1 instance of it can run on the computer. This is only a problem when the first user does not log off prior to switching, and give the rig a minute to refresh itself before logging in another user.

My solution:
I rarely switch users without logging the previous user off.

Before doing the next steps, make sure you set up all the required options for SetiQueue, and enable a Web Password, so that you can access it by going to http://localhost:5517 on the machine it's installed to and log in.


If you are using more than one user account on the SetiQ machine, install SetiQ as a service. Go to Start, Run, then type there

C:\Program Files\SetiQueue\setiqueue.exe -i

(Or change the directory to wherever it's installed) and this will install SetiQ as a service. This way, it will always run, no matter whether users are logged off/on 🙂

Once running that command, right click on "My Computer", go to Manage, then down to Services and Applications, then Services, and look in the list for SetiQueue. Go to Properties for it, and set the Startup Type to Automatic (this will make it start up as soon as the computer is turned on) and under Recovery, set all 3 boxes to say "Restart the Service". This will make SetiQueue restart if it's closed for any reason.
Under the "Log On" tab, make sure it's set to use Local Account, but don't select "Allow service to interact with the desktop". Click on OK, then right click and "Start" the service 🙂


Any probs with this, just LMK 🙂



Garry
 
Back
Top