Custom Query (981 matches)
Results (109 - 111 of 981)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #936 | fixed | CUDA devices not detected when logged in through Remote Desktop | ||
| Description |
In Windows Vista on x64: Connecting to a system via Remote Desktop (rather than through the primary display) and launching the Boinc Manager (as is normally done on said login) prevents BOINC from detecting any CUDA devices. |
|||
| #937 | fixed | broken link | ||
| Description |
The page http://boinc.berkeley.edu/links.php#stats points to "BOINC Project Status" which isn't available any more I think. |
|||
| #947 | duplicate | Lose of Internet = Bizzar Behaviour | ||
| Description |
This morning, our Internet was out.. all over the area actually. Our 3 computers would NOT respond to either Boinc Manager or Boinc.NET. Boinc Manager could not get past the 'trying to connect to host' popup.. I would close it and it would pop right back up. The core was NOT listening at all even tho it was running in plain sight. Boinc.Net was getting nothing or partial data back from RPC calls. I am running them in stand alone.. not as a service.. just the core client.. boinc.exe so the console window is visible. All 3 systems are running 6.6.36... I looked to see what was up in their console windows and noticed they were stuck trying to do network communication. They keep requesting updates. Work for CPU and GPU or combinations of this. There was NO resting at this.. Very aggresive and fairly fast. The core would say it was backing off for N then request again. Very strange! They didnt back off at all and actually went balistic trying to re-establish a connection. I could understand one doing this as a fluke but not all three. I think you can duplicate this just by unpluging the router from the modem. On a single system, just unpluging the RJ45 will probably do it. If this has been reported already, Kill this ticket :) --Mike |
|||
