• 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 with Dialup??

sduguid

Senior member
I've been slowly gathering parts to make a computer for a friend. It'll be at least a 1 Gig Duron but more likely an Athlon XP 1600+ rig. Naturally, I will install Seti as my fee. There are some complications, though.

I will be using Windows 98SE. I need Seti to be hidden so it doesn't confuse the users. I haven't had much luck with the Win98 Service installs but I'm sure there are plenty of people who would be willing to help me with that.

The bigger problem is that this will be a dialup machine and I want to be able to submit WU's automatically when a dialup connection is established.

I noticed SetiLauncher in Sukhoi's help thread but I don't really know what it does and I can't seem to find any info on it.

Is there any way for seti(or any of the helper programs) to sense a dialup connection and send and retrieve WU's in the background?

I won't really have ready access to the machine but, if it comes down to it, I guess I could make a visit every 27 days to flush WU's. If that's the only option, it'd be worth it because that would be close to 200 WU's a month :Q

 
Well, I'm running the CLI with SETI Driver with Win ME on dialup here at home. Even with "Auto-Transmit" selected, the computer doesn't automatically connect when it's finished with a work unit. Whenever someone does dialup, SETI Driver immediately starts flushing whatever it's completed and downloads new work units.

I'm not sure if this is a unique situation on my computer, or the way SETI Driver and Windows DUN works in general.
 


<< I won't really have ready access to the machine but, if it comes down to it, I guess I could make a visit every 27 days to flush WU's. If that's the only option, it'd be worth it because that would be close to 200 WU's a month :Q >>

Friendly FYI: If you're planning on joining the race with that machine, you need to flush at least once/week or so in order to be compliant with the rules. 200 WUs/month is definately a plus for the TeAm though - go for it!
 
No, I don't think it'll be set up before the race ends so that shouldn't be a problem.

For some reason, it never occurred to me that I should throw together an old system from parts and hook up a modem and just try it myself!

It might be a month or so but I'll let everyone know what works and what doesn't. 🙂

That doesn't mean I won't accept further advice 😛
 
I have the same "problem"
When you just set auto-transmit, it will bring up the dial-up script every time a wu is finished (about every 4-5 hrs on a XP1600+)
Is it possible to avoid this?
 


<< I have the same "problem"
When you just set auto-transmit, it will bring up the dial-up script every time a wu is finished (about every 4-5 hrs on a XP1600+)
Is it possible to avoid this?
>>



Get DSL😛
 
I think Didio or somebody with a name similar to that wrote SETI Launcher. I've never used it, but I believe you stick it in the SETI Driver folder, and then put a link to it in the StartUp folder. When it senses a dial-up connection it will start another instance of SETI Driver and have that new instance transmit and get WUs.
 
Just so you know, I have my DUN setup so that "Connect Automatically" is un-checked. When SETI Driver finishes crunching a work unit, it brings up the Connect dialog box, but does not dial out. It just waits for someone to click "Connect" and then it'll start dumping.

This is an acceptable situation for my family, since my family dials up all the time, but I don't know if it's okay with your situation.
 
Back
Top