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

ARGH Can't connect to S@H!!

You should still download a caching program. I'm using SetiQ on 2 networks (work and home) and would recommend it if you've got multiple boxes. I'm not sure which program would be best if you've got a single box or boxes that aren't networked. Someone will probably recommend a good one for ya.

Rob
 
I'm using SetiQ on a one ship fleet, running one cli and one gui on a dual machine. Each instance of sah runs from it's own directory, and setiq is in yet another directory. I followed the faq from one of our team members, but I lost the url. The key, I think, is the use of setipac to direct the client to the correct instance of setiq. I'm sure that it's more complicated with multiple machines, but the faq is very useful, maybe someone can post the url.
 
On a single machine using the command line client I'd use SetiDriver. It's by far the easiest to set up.

If your on a network I'd use setiQ. Most everyone patches the client on the setiQ server but I just set the proxy settings on the client to point to setiQ and have had no problems.

Actually setting more machines on a network to use setiq is a breeze. All you have to do is set the client's proxy settings to point to the machine setiQ is running on and to use port 5512 and your good to go.🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top