=========try the following====

From the cmd prompt of the windows system with the old boinc version, or from the terminal prompt of the older linux system (what.ever is the ip address of the newer system)

telnet 192.168.what.ever 31416

if you see "unable to connect to the remote .." then you got a firewall problem

if you see a bunch of strange characters and cant seem to exit then you connected but are not authorized

Well, I don't have telnet available as a DOS command with this Vista 32

It can be enabled in windows components.

=========try the following====

From the cmd prompt of the windows system with the old boinc version, or from the terminal prompt of the older linux system (what.ever is the ip address of the newer system)

telnet 192.168.what.ever 31416

if you see "unable to connect to the remote .." then you got a firewall problem

if you see a bunch of strange characters and cant seem to exit then you connected but are not authorized

Well, I don't have telnet available as a DOS command with this Vista 32

It can be enabled in windows components.

More help for the telecomm impaired :D
Got it now, thanks again.

Well, I don't have telnet available as a DOS command with this Vista 32 machine, but I did double check the firewall on the Windows 7 remote host and for some reason the machine was conneted as a "Public" network instead of "Private" as I had it originally. The Windows firewall was indeed blocking it. Wierd: no idea why or how that happened.

As soon as I changed the network connection back to "Home or work (Private) Networks" everything works normally even with Windows firewall enabled.

I had this happen to me last month. I tracked it down to the network changing to Public, like you. The only thing that had happened on it recently was a windows update. A "feature" of windows updates under Win7?

---

BOINC blog

Version 6.10.44 has solved the host name problem.

I did not have the CUDA drivers installed; I installed the CUDA Toolkit instead. Having installed them and restarting, the GPU is now found.

Thanks for your help.

2. It can't resolve the host name.

Please install 6.10.44 (development version).

Its main fix is:
- Mac: Build with c-ares 1.6.0 instead of c-ares 1.7.0, because the newer c-ares has problems resolving host names on OS 10.6 with default settings when used with AT&T U-Verse 2Wire gateway routers and Airport.

GPU not found problems is normally a drivers problem. Make sure you installed the correct CUDA 3.0 ones. You won't find any GPU related management options in the menus when the GPUs aren't detected. Also make sure you didn't set <no_gpus> in a cc_config.xml file in a gray past. ;-)

@Urs, thanks. :-)

---

I've noticed, when running the latest 6.10.44 for Linux, even with my prefs set to maintain a 10 day queue, SETI only downloads 1 or 2 wu's at a time. Has anyone else noticed this?

---

I'd say with three CPDN tasks onboard, you have far more than ten days to work on. :-)

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

So the new client version counts the total queue, instead of per-project?

---

So the new client version counts the total queue, instead of per-project?

I think that's the way it always has been. At least my 5.8.16 and 5.10.45 versions do so too.

Gruß,
Gundolf

Before I switched to .44, I used to get 10-12 SETI at a time, so the change was especially noticeable. I thought the 10-day work queue was per-project.

---

There's not enough work to be had from Seti at this time to get 10 days worth of work immediately. You can easily check that in your messages though.

---

So the new client version counts the total queue, instead of per-project?

I think that's the way it always has been. At least my 5.8.16 and 5.10.45 versions do so too.

Gruß,
Gundolf

If it did, there would be no way for BOINC to honor resource share. Cache size has to be a consideration, but there also has to be some sort of allowance for really long tasks.

---

So the new client version counts the total queue, instead of per-project?

I think that's the way it always has been. At least my 5.8.16 and 5.10.45 versions do so too.

If it did, there would be no way for BOINC to honor resource share. Cache size has to be a consideration, but there also has to be some sort of allowance for really long tasks.

Yeah, I didn't think that through to the end, but I haven't done CPDN tasks for a long time and my SETI and Einstein tasks sum up pretty well to my cache preferences.

Gruß,
Gundolf

Since upgrading to 6.10.43 several days ago, have found BM locking up. On clicking the icon in taskbar, nothing happens. Have to log off & back in to be able to access BM.

Never had this before, problem with .10.43?

---

The new BOINC 6.10.43 is locking up my PC when the screen saver starts. I am running XP Pro on an old Athlon XP 3000+ processor, 2.1 Ghz. Graphic card is VIA/S3G UniChrome Graphics. I don't recall a previous version of BOINC causing a problem. Does anyone have an idea as to how to fix this lockup?
Thank you.

---

"It is often darkest just before it turns completely black."

6.10.43 is still "half baking" work units.

please tell me how this is a desired behavior!

half baked is defined as starting a work unit and not completing it.

---

6.10.43 is still "half baking" work units.

please tell me how this is a desired behavior!

half baked is defined as starting a work unit and not completing it.

I've been able to make this happen by hand-editing DCF, and I'm sure you could stop it the same way.

From what I've seen this happens when the initial estimate is too high, meaning it will miss the deadline, and as it crunches it becomes clear that this work unit is safe.

DCF won't start correcting until work is finished.

It's not a question of "desirable behaviour" as it is the amount of work it'd take for BOINC to figure out that it doesn't actually need to switch.

This is an incredibly tough problem to solve, but the "problem" is mostly cosmetic. It looks goofy, but as long as work gets done and reported on time, there is no actual harm.

It's likely that the same thing would happen when there is a run of "shorties."

---

The new BOINC 6.10.43 is locking up my PC when the screen saver starts.

Which screensaver, BOINC or SETI?

Does "Show graphics" work?

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Could all be an aspect of the new item in BM. Check out Advanced / Preferences and "While processor usage isless then ... percent (0 means no restriction)

Change the low setting to zero and things may perk up again. I suspect this feature is causing one or two problems and there was no announcement of this feature when 6.10.43 was announced. Leastways there was none that I saw - and ir does make a very great difference as BM cuts out and in on a regular basis while you are using the machine.

---

6.10.43 is still "half baking" work units.

please tell me how this is a desired behavior!

half baked is defined as starting a work unit and not completing it.

v6.10.43 includes atleast one bug in EDF-selection that hopefully is fixed in v6.10.45, atleast I've not seen it yet.

If the bug-fix also fixes the "half baking"-problem I'm not sure on, since I've not had a task-mix after upgrade that would give this problem...

---

Well, I do not know which screensaver. When the screensaver starts, it has a BOINC stamp on it. Then the SETI frequency plot starts. So, I need to test and get more information.
Also, I cannot find "Show Graphics" in the BOINC menus. Where can I test "Show Graphics".
I have tested without the screensaver turned on, and BOINC/SETI works fine in the background.
I will get back to you with updated test information.
I like to run the screensaver and see the frequency spectra.
So, I miss this.
Thank you for your help.

---

"It is often darkest just before it turns completely black."