Posts by DeMatt

1) Questions and Answers : Windows : Interrupted download glitches CC v4.19 (Message 6114) Posted 25 Feb 2005 by DeMatt Post: My computer was in the midst of downloading the Sixtrack v4.64 program (2.6 MB), when my Internet connection got disconnected. When I returned to my computer to check on it, I reconnected to the Internet, and told BOINC to continue downloading the program. BOINC apparently redownloaded the whole program and appended it to what it had already downloaded, resulting in a Sixtrack program some 4.4 MB in size. It then failed the WU (because of the bad program) and started repeatedly downloading and failing the program. I then reset the project; this caused BOINC to delete everything but the Sixtrack program and redownload it. Observing the continued existence of the glitched program, I shut BOINC down, deleted the program, and started BOINC back up, whereupon it once again downloaded Sixtrack, but this time correctly. Everything seems to be working fine now, but I think this situation needs to be passed on to the BOINC dev team. Network setup: Computer Router Cable Modem Internet The disconnect occured at my cable modem. Computer: Dell Latitude CPx -Pentium 3 @ 500MHz, 128MB RAM -Windows 98SE -BOINC CC v4.19
2) Questions and Answers : Windows : Detached and cannot reattach (Message 6112) Posted 25 Feb 2005 by DeMatt Post: It's a glitch on the server side. When the server is overloaded by requests, it's supposed to send a message to clients that it's busy, can't talk to them right now, and to call back in 3600 seconds. Unfortunately, the message it generates is not completely XML-like, the way the BOINC client expects it. Net result: Client goes "huh"? Just like you describe. There should be a file in your BOINC directory, called "sched_reply_lhcathome.cern.ch.xml", which contains the server's message. You can look at it (with Notepad) if you want. The only real solution right now is to try again at a different time.
3) Questions and Answers : Sixtrack : LHC@home - 2005-02-22 02:47:14 - Message from server: You may have an outdated code verification key. This may prevent you from accepting new executables. If the problem persists, detach/attach the project. (Message 5778) Posted 22 Feb 2005 by DeMatt Post: A "code verification key" is a long block of characters that the BOINC server "signs" programs with, to ensure their authenticity. It is automatically given to a client when that client first signs up with a project. What that message means is that the key your client has is old. It's possible that the server may send programs to your client with a new key, which doesn't match the key the client has, and therefore the client will reject the programs as fake. If this happens, simply detach your client from LHC@Home, then re-attach to it. Your client will be forced to "forget" the old key and obtain a new one.
4) Questions and Answers : Windows : strange problem (Message 3826) Posted 15 Oct 2004 by DeMatt Post: There is a known bug in the LHC@Home screensaver -- under earlier versions (pre 4.46) it leaked memory. The CERN programmers aren't certain whether they've killed that bug or not. Possibly the memory leaks are interfering with your rendering program? Possibly the LHC@Home screensaver uses your computer's graphics hardware in some other way, which interferes with your rendering program? Maybe try selecting a different screensaver for your computer, say "Flying Through Space" or something equally simple. BOINC will still process as per your settings. Don't know if that'll help, but it's worth a try.

LHC@home