Tried v.72 with much anticipation. Still only passes the NVidia temp from TThrottle to BoincTasks. TThrottle v2.001, BT v.72, Win7_64, BOINC v6.10.58.
Follow BoincTasks on Twitter Facebook Visit our website here.
BoincTasks cloud login is working again
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: fred on August 20, 2010, 06:47:04 PMMe too, and loving it :-)Quote from: jjwhalen on August 20, 2010, 06:37:21 PMRetirement , I think I'm busier now than before.
Wasn't trying to rush you, it was low priority...I just noticed it apparently "fell in a crack" In your own good time, and enjoy the trip to France. Which reminds me, I have to take a short trip to the Dog Park - retirement is sweet.
Quote from: fred on August 20, 2010, 06:50:52 PMQuote from: Beyond on August 20, 2010, 06:45:54 PMIf you have a suggestion to improve things and not too specific for FreeHAL let me know.
For sure FreeHAL isn't in the well behaved category. By having a designation such as "Running non-CPU-intensive" as in that old program, it was possible to get it off by itself and out of the way. For example I sort the Tasks window on Status and secondarily on Time Left (10 machines with 54 running tasks at the moment). There seems to be no way to get the FreeHAL tasks out of the way of the rest of the running tasks. Sorting on Use just makes a mess.
Quote from: fred on August 20, 2010, 05:30:48 PMQuote from: Beyond on August 20, 2010, 04:22:23 PMThe non CPU intensive setting is something from the old old days.Quote from: wicked on July 23, 2010, 02:15:51 PM
Hello,
1) A while back I complained about numerous non-CPU intensive FreeHAL WUs taking too much space.
If you look at the old BoincView program it separates non CPU intensive tasks by specifying "Running non-CPU-intensive" under the status tab so that they can be lumped into a different area if the status tab is used as the primary sorting criterion. There is also the ability to alter the sorting order of the various states in the status tab, a very useful feature.
Well behaved programs should use the resources. Like 0.005 Cpu.
And FreeHAL isn't the one in the well behaving category.
Quote from: fred on August 20, 2010, 05:25:27 PMFor those having trouble converting hours to days in their head, maybe going back to school for a while would be a choice with lifelong benefits ;-)
Noted.
But one wants day the next hours, In seconds it's even shorter.
Quote from: wicked on July 23, 2010, 02:15:51 PM
Hello,
1) A while back I complained about numerous non-CPU intensive FreeHAL WUs taking too much space.
Quote from: fred on August 19, 2010, 07:57:54 AM
As of V 2.1 additional information is send to BoincTasks to correctly read the GPU temperatures on mixed systems. Should be implemented in the next BT V 0.72 version.
Quote from: fred on August 19, 2010, 07:55:35 AMv2.1 is installed on my 10 machines and seems to be working properly. Just waiting for BT v.72 to test the temp reporting on the mixed GPU box.
The looping should be solved. in V 2.1
And the ATI GPU, should now read correctly.
Quote from: fred on August 18, 2010, 05:00:50 PMQuote from: Beyond on August 18, 2010, 04:54:43 PMCan you give me this part of the log tab.
Same thing happens on my Brisbane X2. Processor checking loops for hours and never finishes. V2.00, Win7-64.
Core Temperature: 79 °C, Raw Data: 88150000
88130000,88130000,88130000,88130000,88130000,88130000,88150000,88150000,
88140000,88140000,88140000,88140000,88140000,88140000,88140000,88140000,
0123456777777777
Quote from: fred on August 18, 2010, 07:24:45 PMQuote from: Beyond on August 18, 2010, 06:19:44 PMWhat is in the Use column for the NVIDIA and ATI?
V2.001 debug log. For this log I simply replaced the v1.91 exe with the v2.001 exe. Interestingly the temp window with the v2.001 exe now showed incorrectly the same temp for both cards. Copied the v1.91 exe back in and the temps in the temp window reported correctly again. Still not being passed correctly to BoincTasks though:
NVIDIA is probably something like this: 0.04C + 1NV
Is there a device number like (d0) in it?