After entering "update" on several completed WU's, the connection with the BOING client was lost. Install/re-install of BOINC has not resolved the problem, except, after the reinstall, of course, the Mgr. shows nothing.

My new system is a DELL notebook, 4cpu's, 64-bit, with Windows 7; the old
system was a Sony VAIO, 32-bit, w/Windows Vista.

Any ideas?

Follow-up:

1) BOINC ver. 7.2.41 uninstalled (This one was the one during which
connection w/client was lost.)

2) BOINC ver. 6.12.43 re-installed.

Results: Connection with client was re-established.
WU's are now being run (Rosetta, Einstein, CPDN, QCN).

Update II:

1) BOINC rev. 7.2.42 now successfully running WU's.

2) The problem, now, after restoring to an earlier Windows system,
appears to have been due to one of Window's downloads (The exact
one, causing the disconnect from the client, has not, yet, been
determined.).

Perhaps, other users might profit from this scenario.

That's typically a problem that can be resolved by restarting the system, after that a fresh installation is called for... Why did you list two systems in your first post, did you copy your old drive over to a new one? Any WUs in progress would likely have failed if you did that.

---

My Detailed BOINC Stats

Noderaser --

Current findings:

1) As it was later discovered, BOINC rev. 7.2.42 did not provide an
internet connection for any BOINC 64-bit programs, on my DELL
(Latitude, E7240).

2) The first, 32-bit BOINC version which provided VM ops. (I've forgotten
it's rev. number.) ran all pgrms., including T4T.

They were run on my Sony VAIO, w/Windows VISTA.

3) Switching to 64-bit, on my DELL, w/Windows 7, I am now successfully
running rev. 7.0.64. (Oracle's VB 4.3.10 has been downloaded/installed.)

4) It doesn't appear that, running Windows from different restore points,
made any difference in BOINC internet connection -- at least, from my
present perspective.


Any ideas?

Without going into the various system restore-point issues, I'll focus
on an interesting revelation, from further troubleshooting:

1) BOINC_7.2.42_windows_x86_64_vbox installed, does run, now, with internet access.

2) Other issues:

a) The projects' WU "compatibility" settings must be run at their
original "Windows XP (Service Pack 3)" setting, in order for my
DELL's "sidepanel" gadgets to run (calendar, clocks, etc.).

This has a negative impact on some communicative aspects of QCN.

b) If the projects' WU "compatibility" settings are set for "Windows 7",
BOINC continues to run, with internet connection, but the "sidepanel"
gadget access is lost (Please don't laugh, I like my clocks & calendar.).

c) As far as a cursory look in the registry (via a "gadgets" search),
the values appear to be unchanged, under both conditions.).

Am wondering if other negative developments might occur, in the future,
if the WU's are run at "Windows XP (Service Pack 3)", on my Windows 7
machine.

Also, perhaps I've neglected to properly set up BOINC to run on Windows 7?
It seems that the WU's "Compatibility" settings should automatically reflect
the current operating system (Windows 7, in my case)?

Windows Sidebar Gadgets Problem solved --

After changing all "Compatibility" settings, in both the Program Files*
and ProgramData folders, from "Windows XP (Service Pack 3)" to
"Windows 7"(Located in the ProgramData folder), and, after changing
all the main BOINC programs* (Located in Program Files folder),
all BOINC programs still worked correctly, as well as the Windows
"gadgets".

Summarizing: All "Compatibility" settings had to be changed; nothing
was done automatically, by the installed BOINC program.

This "cruncher" has no regrets, certainly; it was an interesting learning
experience.

Cheers, to all. . .

* boinc (BOINC client), boinccmd, boincmgr, boincscr, boincsvcctrl, boinctray.

Dunno what you've run into, my gadgets work just fine with the stock BOINC installation on Windows 7 Home Premium 64-bit, on two different hosts.

---

My Detailed BOINC Stats

NodeEraser --

You pbly. won't want to change some "Compatibility" settings in the
Program Files BOINC folder, in an attempt to duplicate my own particular
problems. That might shed some light on this issue, however.

I really don't know the technological basics as to why this
set of incompatibilities occurred, for me. Certainly, there are a
large number of hardware/software systems in the BOINC net., and it's
amazing they all run.

One would think BOINC would automatically have sized up each computer,
and adjusted "Compatibility" settings. For my own part, after this
revelation, I went and changed all third-party (non-BOINC) settings
(most were not set to "Windows 7).

My DELL, with Windows 7, is now running okay on the various pgrm. WU's
(as well as T4T).

Let me know, if you find out something, from your end of things.

Cheers,