Message boards :
Number crunching :
Screensaver locking up mouse
Message board moderation
| Author | Message |
|---|---|
 Kathy ApplebaumSend message Joined: 27 Sep 04 Posts: 4 Credit: 60,443 RAC: 0 
|
Working on Sixtrack 4.67, after the screensaver has started I have no use of my mouse until I restart the machine (or put it on standby and then take it out of standby.) This only happens with LHC, not any of the other BOINC projects I'm running, and is only happening with the two workunits most recently downloaded. Running XP Pro SP2 on a plain vanilla Pentium 4 machine. I'm not running LHC on any of my other machines, so I don't know if it's limited to just this one box or is more widespread. |
|
Keck_Komputers Send message Joined: 1 Sep 04 Posts: 275 Credit: 2,652,452 RAC: 0 |
The latest recomended client (5.4.9) should save from this problem. It is supposed to kill the graphics thread if it is not responding, this usually aborts the workunit as well. It is not really a fix but it makes things alot easier to live with. BOINC WIKI   BOINCing since 2002/12/8 |
|
Kathy Applebaum Send message Joined: 27 Sep 04 Posts: 4 Credit: 60,443 RAC: 0
|
Thanks -- I'll download it tomorrow. The latest recomended client (5.4.9) should save from this problem. It is supposed to kill the graphics thread if it is not responding, this usually aborts the workunit as well. It is not really a fix but it makes things alot easier to live with. |
|
Send message Joined: 28 Sep 04 Posts: 16 Credit: 2,678,563 RAC: 0 |
The latest recomended client (5.4.9) should save from this problem. It is supposed to kill the graphics thread if it is not responding, this usually aborts the workunit as well. It is not really a fix but it makes things alot easier to live with. i beleive that recomended client is still 4.45 on LHC site <br /> -- marshall 
|
|
Send message Joined: 1 Sep 04 Posts: 506 Credit: 118,619 RAC: 0 |
The latest recomended client (5.4.9) should save from this problem. It is supposed to kill the graphics thread if it is not responding, this usually aborts the workunit as well. It is not really a fix but it makes things alot easier to live with. There is precious little resource available to maintain the BOINC system at LHC. At present there isn't an administrator (except that Chrulle does a bit sometimes, even though he's left) so this is just an oversight, and should be updated. There are many user, myself included, using version 5 clients successfully. Version 5.4.9 works well on the only box I have installed it on. I haven't yet had time to upgrade my other systems. Gaspode the UnDressed http://www.littlevale.co.uk |
|
Keck_Komputers Send message Joined: 1 Sep 04 Posts: 275 Credit: 2,652,452 RAC: 0 |
The latest recomended client (5.4.9) should save from this problem. It is supposed to kill the graphics thread if it is not responding, this usually aborts the workunit as well. It is not really a fix but it makes things alot easier to live with. Try the BOINC download site. It is more up to date. BOINC WIKI BOINCing since 2002/12/8 |
 Send message Joined: 29 Jul 05 Posts: 2 Credit: 2,681,810 RAC: 0 |
Hmmm it looks like 5.4.9 my have kept mine from locking up like it use to (no lock up errors on LHC for sveral months). I got the error when I returned to my desk and the error in the log is when I moved the mouse. 6/1/2006 1:57:51 PM|LHC@home|Unrecoverable error for result wmay1B_v6s4hvnom_mqx-hlf__19__64.289_59.299__4_6__6__50_1_sixvf_boinc260028_1 ( - exit code -1 (0xffffffff)) 
|
©2024 CERN