This may be an os specific problem so I posted under windows (seti page) also. I'm running XP and 98SE and have tried all manner of auto-connect (internet options settings) in control panel. The Internet Explorer startup ALWAYS works (i.e. auto dial up and disconnect occurs as configured).

The problem is that BOINC does not reliably (i.e. ALWAYS) auto-connect and does not reliable (i.e. ALWAYS) auto-disconnect. (The 98SE machines also get into a hung state at times in the screensaver and do not "come back" from screen save mode.)

The rest of my experience with BOINC is GREAT. Fix the dialup connect/disconnect problems and i will switch from seti classic. 'till then i have no choice but to stay with classic (as long as i can).

I have 3 systems, 2 98SE and 1 XP. Again, BOINC is GREAT, it's just the dialup interface/api that needs attention.

Thanks,
Lee

---

The problem is that BOINC does not reliably (i.e. ALWAYS) auto-connect and does not reliable (i.e. ALWAYS) auto-disconnect.

There are some dial-up fixes in V4.72, I think there are more in V5.x beta - I'm assuming that you're running V4.45. I don't know if it would solve your problem, but you can try 4.72 (first) or 5.x (last resort, still changing too quickly, won't connect to some projects, although I think SETI is okay). Get them here;

http://boinc.berkeley.edu/dl/

---

I tried 5.1.4, hoping the latest was the greatest. I'll try 4.72 next.

Here are the results for 5.1.4:


In "Messages" window:

9/22/2005 9:38:16 PM|SETI@home|Fetching master file
-> I heard my modem go off hook and start dialing here...

-> ... then while the modem was still working at establishing the connection,
-> the following error messages were reported.
9/22/2005 9:38:17 PM||Couldn't resolve hostname [setiathome.berkeley.edu]
9/22/2005 9:38:21 PM|SETI@home|Master file fetch failed
9/22/2005 9:38:21 PM|SETI@home|Too many backoffs - fetching master file
9/22/2005 9:38:26 PM|SETI@home|Deferring communication with project for 2 days, 17 hours, 38 minutes, and 37 seconds

-> After connecting a message appeared near the task bar indicating that BOINC
-> had successfully established a network connection.
-> It immediately broke the connection, and reported that BOINC had successfully
-> disconnected from the network.

Please pass this on if it could be of any use in debug.

Thanks,
Lee

---

Ok, the latest:

4.72 is working fine with XP.
5.1.4 does not work with XP.

AT present, nothing is working with my 98SE systems.
Tried 4.72 and 5.1.4. (and the official release 4.45 also)

For now my 98SE systems are running seti "classic"

Thanks,
Lee

---

For now my 98SE systems are running seti "classic"

Does your 98SE machine have the specs to run BOINC or SETI-BOINC? My Win98SE is running SETI and Protein with no problems. Doesn't have the specs for Einstein or CPDN, haven't tried any others on that one.

MJ

---

I'm back using classic on all systems (98SE(2) XP(1)).
Dialup is just not running reliably in BOINC.

Classic seems to dial, connect, disconnect perfectly
using the standard IE Internet Options control panel
app configuration for "dial when a connection is needed".

Thanks for all your help.
I'll be back to try again with new versions after 5.1.4.
'Till then it's time for classic.

,Lee

---

This may (or may not) help. In BOINC 4.72 there is a new tab on the Options window (Under tools), named 'Connections'.

Connections is setup to 'Automitically detect network connection settings'. There is a 'Use my Dial-up and VPN network connection'. This should force it always check for dial-up.

---