Question about setidriver

[Civic2oo1x]

Hey guys, thanks for all the help so far. I'm running the CLI and can say it's done wondering for my WU time. While the GUI looked nice and all, it wasn't giving me the WU numbers I was looking for. (Avg. 14 hours per WU) Now that I have CLI up and running it's cut it down to around 6 hours. Now the thing is it says processing one, 17 waiting to be processed, 7 to fill, and 3 ready to transmit. When will it transmit those 3? When all 25 are done? I'm a little confused here. Thanks for any help guys. Keep the crunching going!

 

[Smoke]

What type of internet connection do you have? 56K or DSL/Cable and are you online 24/7 or do you logon to do things on the internet?

 

[Civic2oo1x]

I'm running Windows XP and I'm on my school's ethernet connection so it's up 24/7. I've been running Setidriver non-stop for at least 4 days now.

 

[Smoke]

Then the answer is really easy. Place a check mark next to AUTO TRANSMIT and then click on the SAVE CONFIG button and you are done...forever!

Did you put a startup shortcut in the startup folder?

 

[Civic2oo1x]

Yeah, the Auto transmit is checked and I do have a copy of setidriver in my startup folder. I figured that maybe seti would be down, but this latest WU just started at 11PM EST.

 

[MaxSiren]

If "Auto-Transmit" isn't checked, you have to click the "Transmit" button to have it return results and refill the queue.

If it is checked, it should be returning and refilling on the fly. However, with Berkeley's recent bandwidth limitations, you may have trouble making a connection. As a result, it may not be successful in transmitting and will take several hours, if at all, to finish returning and refilling.

If the latter is the case, I suggest making use of one of the TeAm SetiQ proxies. The main one being OrangeKid's.

In the "proxy server" box, enter: orangekid.teamanandtech.com

In the "port" box, enter: 5001


If you can't connect to his, try my server (in my sig)

 

[Smoke]

Ha, ole Max beat me to the next step. You can continue on your own and when Berkeley's bandwidth improves around 3 hours from now your computer/SetiDriver will make contact and upload/download those WUs. My mini-team's Q is slowly slipping in a few right now.

I'd suggest we start spreading people around a little. Eggs in one basket idea.

Do as Max outlined. You will need to place a DOT next to PROXY SERVER to open the HOST and the PORT boxes.

If you need any further help, please don't hesitate to ask.

 

[Civic2oo1x]

Will it only try to connect when the WU being worked on is complete? Or does it try every so often? Max and because you've been really helpful to me lately, I've decided to use your queue. Is the host siren.2y.net and port 5001?

 

[Smoke]

It tries to connect when a WU is done. If it fails to connect, it times out for a while and then tries again later. It will keep doing that until it makes contact.

The advantage of using one of the team Qs is that you should be able to get to them when Berkeley is down or clogged. Of course sometimes the team Qs have their problems too so it is not fool proof. But lately it appears that Berkeley starts getting overloaded and hard to contact starting around mid morning until just before dawn using the Central Time Zone for reference.

 

[paf077]

If you put a check in auto transmit it will retry every hour or so! and after a wu is finished!

Smoke ball beet me to it!

 

[Smoke]

That's good we have a lot of people willing to help out. That is one of the reasons this is the greatest team in the world.

 

[Civic2oo1x]

Yeah, it really is. I just wish I remembed about seti sooner. (I have fond memories of running seti on my work computer when I used to work at my computer job 3 years ago. Boy what a P2 can get you back then).

 

[Smoke]

Well, that's about it for tonight for me gang. See you all later in the day.

 

[ober]

SETI Driver Auto-Transmit

When SETI Driver completes a WU, it starts the next WU and then checks the Auto Transmit checkbox. If it's checked, it then starts a transmit pass if there isn't one already running. Should the transmit pass fail on any WU, a 6 hour timer is set and another transmit pass will automatically start in 6 hours, when the next WU completes (and Auto Transmit is checked), or when the user clicks the Transmit button. The 6 hour timer is stopped when the transmit pass begins. The 6 hour timer is 21600 seconds as requested on the Command Line download page.

Don't confuse SETI Driver's 6 hour timer with the client's 1 hour timer when it can't connect. The client appears to try twice and then exit after the second attempt. SETI Driver will wait for the client to exit before going looking for the next WU to transmit.

Mike Ober.

 

[Civic2oo1x]

Well I'm still having problems connecting, so you guys think I should take the auto transmit off and try to transmit manually?

 

[Smoke]

Berkeley is open at the moment. So click on the TRANSMIT button and see if that doesn't send them on their way.

Have you done a reboot? Then click on the TRANSMIT button. It ought to go unless you have a firewall or something. Are you going straight to Berkelely with the DOT next to NO PROXY/SOCKS? Or are you using a PROXY SERVER?

 

[Civic2oo1x]

Edit: Nevermind, it seems to have worked as the icon in my system tray is yellow and it appears that 3 WU's were set, as Seti spy says I now have 15 WU's complete.

 

[Smoke]

When the icon is YELLOW it means it has "work" to be transmitted.

Go look at this site: Seti Driver

Look around and you will learn a lot about SetiDriver.

The author of the program is Mike Ober who posted a reply to your thread just a little while ago.