Posts by Richard Haselgrove

1) Message boards : Technical News : Albert@Home down due to migration to Drupal (Message 132576)
Posted 1 day ago by Richard Haselgrove
Any news about Albert, did it get lost in the crossfire?

All I see there is You don't have permission to access /index.php on this server.

Details posted at
2) Message boards : Problems and Bug Reports : Validate error - What this really means! (Message 132484)
Posted 4 days ago by Richard Haselgrove
Agreed, all GTX 6xx and 7xx cards are reported with an unknown speed and number of cores. The cards were manufactured after this app was built, and the app can't predict the future.
3) Message boards : Cruncher's Corner : a new (?) netgear router. (Message 132441)
Posted 6 days ago by Richard Haselgrove

Your picture is interesting, I have been only swapping the middle two pairs of wires, not every pair of wires. But as you said as long as both ends of the cable are the same the router will just send the signal down the wire to the next connection. I just did a speed test on my laptop and while it is running 'g' it is only getting 25/18. My desktop, which is hard wired, is getting 43/34, so my wireless IS slower. Time to run more wires I guess!!

What's more, it's a standard - specifically, TIA/EIA-568 - and I've always found it's better to follow standards if it costs no more than doing it any-which-way.

Specifically, Mike has illustrated T568A (as it's usually known): I've always found that to be commoner in telephone systems. Computer network wiring is more commonly made up to T568B - which is electrically the same, but with the white/orange - orange/white pair connected to the top pins 1 and 2, and the white/green - green/white pair connected to the symmetrical pins 3 and 6.

I too have done the sort of networking which starts with an electric drill, a 18" masonry bit, and a set of stepladders.....

... and I've still got the boxes of Cat 5 cable in my cellar to this day.

Note that Cat 5 cable can be bought in two forms: solid core and stranded. The stuff which comes in 1,000-foot boxes is almost always solid core: it's designed for permanent, fixed, infrastructure situations. It's designed for connection to patch panels or the faceplates on wall outlets, using an IDC 'punchdown' tool. That's the sort of setup I'd use for your project: run the stiff solid-core cable as far as the skirting board (baseboard? floor moulding? kick board?), and terminate it with a fixed socket.

Those little RJ45 plugs with the catch which breaks off are much easier to fit on the softer, more flexible, stranded cable: use that to make up short-length patch cables to connect your equipment to the wall socket. I used to make those up too, until I got bored and found that if you purchase wisely, you can buy them ready-made and certified for much the same price as the cost of the parts. Just don't buy them in high-street computer shops, where the mark-up can be horrendous.

Personally, I like the ones with an integral strain relief like this:

- doesn't get in the way of the latch for unplugging, but does stop the wires working loose in the connector. I usually break the latches off by tripping over the cable and ripping it forcefully out of the socket: no sleeve or boot is ever going to stop it breaking under those conditions.
4) Message boards : Wish List : Improved handling of low speed internet links (Message 132127)
Posted 20 days ago by Richard Haselgrove
Could it be changed to allow the user to set a limit of one file transfer at a time, until this limit is no longer desired?

That exists already. Using a cc_config.xml file (see Client configuration), you can set (separately)

Maximum number of simultaneous file transfers (default 8).
Maximum number of simultaneous file transfers per project (default 2).
5) Message boards : Problems and Bug Reports : Work Running 100% Of Time Despite Settings? (Message 132000)
Posted 25 days ago by Richard Haselgrove
Or, from the official ClientSchedOctTen document,

This will tend to get large (max-min) clumps of work for a single project, and variety will be lower than the current policy.
6) Message boards : Problems and Bug Reports : question about last checkpoint (Message 131829)
Posted 32 days ago by Richard Haselgrove
The last batch I saw like that checkpointed 11 times during the run, or after each 9.09% of progress.

With the 'recommended' 7.2.42 version of BOINC that you are using, the early stages of progress (before the first checkpoint) are not accurately recorded: they are simply an estimate based on time spent so far (earlier versions of BOINC displayed no progress at all during this phase, which was even worse).

If you can, leave the computer running until the progress% shows exactly 9.090% (it should then stop changing, until a second big jump to 18.181%). You should then be able to look up the CPU time at the first checkpoint: you would need to leave the computer running for at least that long in each session, to make progress with these tasks. If that's not possible, you might be better off choosing a different type of Einstein or BOINC work.
7) Message boards : Cruncher's Corner : BOINC weirdness again (Message 131743)
Posted 35 days ago by Richard Haselgrove
That may have been me. They are *started* in FIFO order.

There is an override, in which tasks are marked "high priority" in BOINC Manager: we tend to call it 'EDF' for Earliest Deadline First on project message boards. That should have kicked in here, but clearly didn't.
8) Message boards : Cruncher's Corner : PC with 2 NVIDIA and 1 INTEL CPU/GPU, how to assign WU's (Message 131468)
Posted 49 days ago by Richard Haselgrove
The full list from is

IntelĀ® HD Graphics 5200 / 5100 / 5000 / 4600 / 4400 / 4200 / 4000 / 2500

9) Message boards : Problems and Bug Reports : "Run only the selected applications" problem (Message 131415)
Posted 52 days ago by Richard Haselgrove
I've bitten the bullet, and installed

08/06/2014 14:06:35 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version, device version OpenCL 1.2, 1298MB, 1298MB available, 184 GFLOPS peak)

from the this time the setup.exe worked properly, and I didn't have to resort to a manual install.

First task is running now, apparently without problems. Timings won't be comparable, because the CPU is doing some heavyweight Albert testing at the moment, and I find that affects things. Previously, timings were tightly clustered around 660 seconds (11 minutes) when running 'lightweight' BOINC CPU tasks on three of the four cores: they rose to over an hour when all four cores were loaded. I suppose I should repeat that test with the new driver sometime.

OK, first task finished successfully in 13:38, against a 'current configuration' estimate of 13:21. Not fair to judge on that basis, because I was typing on the keyboard and had multiple windows open for at least some of the time - but not a disaster. Task 439781685, if you want to watch for validation.
10) Message boards : Problems and Bug Reports : "Run only the selected applications" problem (Message 131413)
Posted 53 days ago by Richard Haselgrove
My download file was I see the current download for 64-bit Windows is I might try that later - this is a test machine I can afford to mess with.

Please do report on how the new driver behaves if you decide to try it!

You wouldn't happen to have the installer for, would you?
I'd be willing to test a newer driver if only I had the installer for the current one so I could back down again if the newer driver won't work.

Yes, I've got

Release Version: Production Version

Package: 206289

Intel(R) Graphics Driver:
Intel(R) Display Audio Driver:

Operating System(s):

Microsoft Windows* 7-64
Microsoft Windows* 8-64

Release Date: August 2, 2013

in both .zip and .exe formats - file is Win64_153117

It's about 140 MB in either format, so would take time to upload to a dropbox. Unless you have an FTP server?

I've downloaded 153322, but not tried installing it yet. Maybe after the next coffee...

Next 10

Home · Your account · Message boards

This material is based upon work supported by the National Science Foundation (NSF) under Grants PHY-1104902, PHY-1104617 and PHY-1105572 and by the Max Planck Gesellschaft (MPG). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the investigators and do not necessarily reflect the views of the NSF or the MPG.

Copyright © 2014 Bruce Allen