SETIQ and SETI on same machine <help>

[Michael]

JWMiddleton just jumped a little a head of me. I need more juice for SETI. If I run Seti on my machine with SETIQ running and do not patch it, will it connect directly to the seti server and bypass SETIQ? That is acceptable to me.

I need a little more juice or I'll be 0/2 in races. I seem to have inspired a little more effort from JW, at least <grin>.

Michael

 

[artemedes]

Mabe I misunderstand what you are trying to do. I have setiq running on two machines now, and if it does not connect to setiq then the next time it cannot connect directly to the seti server you will not get any work units. So unless you have other machines connecting to the setiq on that machine then it is pointless to run it.

Ok, as far as I know it will not connect to setiq on the same machine without patching it. Unless you have a static IP address. I think I had mine working by just putting in the same ip address as the machine under proxy settings, but that was with the gui version and not the command line.

The instructions on the team seti page for setiq helped me alot. (Thanks MGallik)
http://hobbitt.worldkey.net/~seti/setiqueue.html

 

[Michael]

I have three other machines connecting to SETIQ on my main machine. I usually run RC5 on it as RC5 is a little nicer about getting out of the way when I fire up UT and other programs. I need a short term SETI boost as I'm trying to beat JWMiddleton to 400 WU's and the <great guy> @*@&amp;%%^@%^@(^ just slipped past me. I want to throw my C850 into the fray without patching the SETI file and going through a bunch of extra work.

It seems to go ok and I just need 2-3 days of working until one of us hits 400.

Michael

 

[Ken g6]

If the computer is on the network, connecting by TCP/IP (that may be a stupid question; I don't know much about LANs), you just need to set it to HTTP proxy 127.0.0.1:5512, or &quot;-proxy 127.0.0.1:5512&quot; on the CLi client. I do.

Edit: spelnk It's late...

 

[Michael]

So by using the local ip number I do not have to patch the SETI client? The computer that is running SETIQ and SETI as well is on the LAN. It is my main computer that has two NICs. One connected to the cable modem and one connected to my LAN.

Michael

 

[blade47]

I'm running seiq on my network and all I did was set the proxy settings to localhost:5512 for the client on the setiq server and everything works just fine. It connects to setiq to get the wu with no problems. I've done the command line and gui this way. Neither was patched.

On another system that's not on a lan I'm running setiq &amp; the command line client. I didn't patch it, all I did was add localhost:5512 for the client's proxy settings and it connects to setiq with no problems.

BTW I'm running win98. I don't know what patching the client actually does but I haven't had any trouble. All the wu's and stats have been doing as they should.

Edit: Sorry Michael I didn't read your second post to closely. To run like you want it to, all you should have to do is install seti like you would if you weren't running setiq and it should run just fine.

 

[VirusTLC]

Yes, you have to patch the client if you are using dial-up-networking, even if you have an IP address. Do you need help patching the client? It's pretty easy and it will no longer dial up each time it wants a packet from SetiQ.

 

[MGallik]

...or you could back up the client and patch the operational one.
Replace it when you get where you need to be.

 

[Assimilator1]

VirusTLC

If he has a static IP from Network card then he doesn't need to patch it .He can enter the IP add or he can do as Blade_47 said

Blade 47

Ref using proxxy 5512 for unpatched clients with no LAN ,I think thats a new way of doing it.Should be added to our FAQ

 

[blade47]

Assimilator1

I was wondering why everyone patches the client. I'm using the localhost:5512 proxy setting on my sister stand alone dialup system and it works fine with the command line client or gui without being patched. And it only dials in at the specified time it doesn't try to dial in when it gets a wu from setique. Everyone always says it'll try to dial in when getting a wu but hers doesn't. I'm not really sure what patching the client actually does. Could someone inform me on what it accomplishes?

 

[VirusTLC]

Not entirely true. I have 2 pc's that are connected by a hub, both with static IP's. One running win2k server and the other running 98. I had to patch the win98 pc because it kept dialing out as if it wanted to get a new packet, but once a dial up connection was made it pulled the packet from setiq. I had the same problem on 2 pc's at work and the patch solved the problem.