F@H dial-up users

[leconc]

I use dsl, but a friend has a few machines he would like to set up on dial-up. Can you use more than 1 machine on dial-up and how? I assume it wouldn't be worthwhile to check the 5mb box in configure for obvious reasons. To keep thing moving as far as downloads can you set up an automatic connect scenario where it won't trash you conversation if your on the phone? He plans to run 24/7 making these issues important. Thanks

 

[r0tt3n1]

One possibility for dial-up users is to set the client to grab `timeless Tinkers`. They have no deadline, so a constant connection isnt needed. This also will download a few wu's at a time. Then they can make the client connect when they want to, or still set it to automatic. To do this with the CLI client, stop it, then restart with the -config flag. When asked to change advanced options type yes and then for the option `Request work units without deadlines` type yes. Sorry, I dunno how to do this with the GUI client...
hth

 

[GLeeM]

If you have the machines networked together one of them can be the rig that connects. The others connect through it.

When Dial-up is set to connect on demand, it can also be set to only dial when there is a dial tone. So if you are on the phone talking it will not dial. Be prepared for the computer using the phone when you want to make a call.

Timeless WUs is probably the way to go. The WUs download size is small, ten are queued, after seven are completed it will want to connect.

F@H can also be configured to ask before connecting. It pops up an annoying, always on top little window asking to connect.

 

[ProviaFan]

I did the multiple F@H clients on a network through NAT'ed dialup until getting DSL recently. That was before I knew about Timeless Tinkers (a pet name for work units using the Tinker core and without deadlines) with the v5 client, so the occasional large Gromacs could be a PITA. Anyway, you just need one computer set up to be the "server" with ICS if you're using Windows 2000 or XP. You could also use Windows 2003 Server with Routing and Remote Access Services (which I did for a short while), or a Linux system with demand-dial PPP (or whatever they call it).

Gleem has covered most everything you need to know about settings, but if you have trouble getting the F@H client that is installed on the dialup server itself to trigger an autodial, shoot me a PM and I'll try to help you through it as I've dealt with that issue multiple times. It's not fun when everyone on the official F@H support forum blows you off and ignores that the issue exists. (sorry, can you tell that I hate having to deal with autodial settings on Windows?) Oh, and the new v5 client has improved sending procedures to ensure that WUs get sent on connections that take a minute to get established. Us dialup old-timers who remember having to shut down the service and do a "-send all" every week or so to flush out the "stuck" WUs appreciate the new v5 clients a lot! 🙂

Sorry, I'm rambling, I'll shut up now...