Questions about SETI

[Jeff]

I just signed up on the FQ team and started running SETI@home

I have two computers I want to try:
1.) A dual PII 450, 512 megs ram, Windows NT 4.0 (connected via modem, my work machine for graphics, so SETI when I'm not working.)
2.) A dual PPro 200, 192 megs ram, Windows NT 4.0 (not connected to the internet, but can run SETI 24/7.)

Questions:
1.) Is there a way to utilize 2 CPU's under NT 4.0?  I would prefer not to run SETI as service unless I must.

2.) What is the best way to utilize Computer 2?  Move the SETI data over, run, then move the data back to return results and get new data?  Or would it be easy enough to setup Computer 1 as a proxy server for Computer 2 to get and send its data?  (using a crossover cable for lack of a hub


[This message has been edited by Jeff (edited 09-29-00@05:10 am)]

[jwlai]

Jeff,

Welcome to FQ SETI team.

If you are using command-line client, you can use the cpu options:
-cpu N          set client to run on cpu N

You can get the command-line client for NT in this page
http://setiathome.ssl.berkeley.edu/unix.html
Platform:  i386-winnt-cmdline.exe

I believe the best way is to use proxy server for your computer2. There are several freeware and shareware proxy servers, you can find them in here.
http://winfiles.cnet.com/apps/nt/servers-proxy.html
------------------
Jerry
Taipei, Taiwan

[Jeff]

Hey thanks.

I thought that I would be able to setup the proxy server with what NT has built in, but I simply couldn't get it to work.

The command line version runs very smoothly

Now watch out -- I might catch you in 3 - 5 years  

[Hitek333]

I have an NT4 and a Linux machine, and I tried to use NT's proxy server too. I had a lot of trouble :-( I've no doubt this is at least partly because of my extremely average networking knowledge, but there seem to be other problems too.

I did eventually get it working. I think I used the default proxy configuration (or possibly just disabled all authorisations). I setup the Linux ("client&quot machine to use port 80 to connect to the NT proxy server.

I found however that if a connection attempt was made through the proxy server when the NT machine wasn't connected to the Internet, the Linux client would fail with a (possibly misleading?) error message. Not unreasonable I supposed. Unfortunately, after that had happened once, the Linux machine could never, ever connect through the proxy, even if the NT machine was online.

Re-booting seemed to "re-enable" the proxy. I also found that if I stopped and restarted the web publishing service (Control Panel, Services) it would have the same effect.

All very confusing.

The good news is that I don't need to worry about this anymore, because I've switched to using SetiGate, which I think is extremely excellent:

   http://www.aota.net/ubb/Forum5/HTML/001062-1.html

Although it doesn't yet include functions to monitor SETI processes on other machines, SetiGate is being actively developed, and I wouldn't be surprised to see this and other features included soon :-)