- Welcome to eFMer - BoincTasks and TThrottle forum.
eFMer - BoincTasks and TThrottle forum
News:
Follow BoincTasks on Twitter
Facebook Visit our website here.
BoincTasks-M on Android and iOS should be ready soon
Recent posts
#51
Wish List / Re: Fix "exclusive application...
Last post by hucker - March 30, 2025, 05:37:46 AMSo I'd have to add the full location, since the other options are referring to this computer, not the remote one?
#52
Wish List / Re: Remember dialog box positi...
Last post by fred - March 30, 2025, 01:04:57 AMI'm running Windows 11 on several computers.
Windows generally uses both screens as one big screen.
So BoincTasks only sees coordinates.
When one monitor is lost, all bets are off, Windows sometimes does strange things and moves everthing to the monitor that is working.
Windows generally uses both screens as one big screen.
So BoincTasks only sees coordinates.
When one monitor is lost, all bets are off, Windows sometimes does strange things and moves everthing to the monitor that is working.
#53
Wish List / Re: Fix "exclusive application...
Last post by fred - March 30, 2025, 01:00:46 AMWith the first line you can add an app from any folder
The second does something simular but with the running programs.
The third is the actual exclusive app, selected by the first 2.
Or you can add the full app location like C:\Windows\explorer.exe
The second does something simular but with the running programs.
The third is the actual exclusive app, selected by the first 2.
Or you can add the full app location like C:\Windows\explorer.exe
#54
Wish List / Re: BOINC's project list often...
Last post by fred - March 30, 2025, 12:58:32 AMBut even with a wrong URL things seem to keep working, despite the warning.
#55
Wish List / Re: need more slots in hwinfo ...
Last post by fred - March 30, 2025, 12:57:21 AMTThrottle doesn't detect any?
And HWINFO has a limit of 4?
And HWINFO has a limit of 4?
#56
Wish List / need more slots in hwinfo to r...
Last post by Joseph Stateson - March 29, 2025, 01:45:41 PMNeed additional HWINFO GPUs slots. I have six of the P104-100 (gtx-1070 equivalent) that are not recognized.
I set hwinfo32 to use 1..4 and set gpu-z to use #5 but there is no way to add the 6th.
I edited tthrottle.xml setting
<GPU_SETUP>
<nvidia_number_gpu_phys>6</nvidia_number_gpu_phys>
<GPU_SETUP>
but it did not help. GPU-z does not handle more than 1 temp. I tried running multiple gpu-z but tthrottle only saw 1 temp, not 2 on gpuz.
I moved this from BT wish list to tthrottle.
I set hwinfo32 to use 1..4 and set gpu-z to use #5 but there is no way to add the 6th.
I edited tthrottle.xml setting
<GPU_SETUP>
<nvidia_number_gpu_phys>6</nvidia_number_gpu_phys>
<GPU_SETUP>
but it did not help. GPU-z does not handle more than 1 temp. I tried running multiple gpu-z but tthrottle only saw 1 temp, not 2 on gpuz.
I moved this from BT wish list to tthrottle.
#57
Wish List / Re: Fix "exclusive application...
Last post by hucker - March 29, 2025, 01:14:28 PMNot sure how to select the app when I'm on computer 1 with boinctasks, and computer 2 is what I need to put an exclusive app for.
#58
Wish List / Re: Remember dialog box positi...
Last post by hucker - March 29, 2025, 01:11:48 PMI'm using Windows 11, have I still got 10 in some info somewhere in my profile?
#59
Wish List / Re: BOINC's project list often...
Last post by Joseph Stateson - March 25, 2025, 01:25:21 PMI ended up using OpenSSH for Win11 and the below command to transfer the updated file to my 'Shire2' PC.
I only did this as I have 12 systems and two days ago I had to scramble to log in remotely and shut down each one due to an electrical storm. After I got:
Code Select
scp C:\ProgramData\BOINC\all_projects_list.xml Shire2:C:\ProgramData\BOINC\all_projects_list.xmlI only did this as I have 12 systems and two days ago I had to scramble to log in remotely and shut down each one due to an electrical storm. After I got:
Code Select
ssh Shire2 "shutdown /s /f /t 0" to work I tried that scp command which I used to update the gpugrid URLs. #60
Questions / Some NVidia cards not being de...
Last post by Joseph Stateson - March 19, 2025, 01:29:09 PMI have 6 P102-100 cards, these are equivalent to GTX-1080Ti, but are in the $40 USD range.
They can be force installed in Win11 as P104-100 or using an unsigned driver as P102-100. They are not recognized by tthrottle except using GPUz or HWinfo32
1 - GPU-z (looking at Tthrottle display)
I ran 4 instances of GPU-z and set each instance to a different GPU. Tthrottle shows 4 GPUs in the external tab but only one temperature (the first instance) was available. Possibly there is a setting to force 4 GPUs in tthrottle.xml but I do not know how to configure it.
2 - HWinfo (looking at Tthrottle display)
HWinfo Pro shows all 4 GPU temperatures in Tthrottle but only good for 12 hours. The temperatures matched that revealed by the nvidia-smi app. I uninstalled Pro and put in HWinfo32 and there was a notice that not all items were uninstalled. TThrottle's GPU2 showed 1100c using HWinfo32. All the other temps in TThrottle were ok and matched nvidia-smi. BT reported the 4 temperatures but put in 0c for the problem 1100c temperature.
I brought up GPU-z and set instance to the GPU2 and got the correct temperature (in Tt). In Tthrottle, I was going to disable GPU2 in HWinfo and enable it for GPUz. I noticed that GPU2 in HWinfo now had the correct temperature. I closed GPUz and the temperature momentarily went back to 1100c. While looking this strange problem the temperature toggled between the correct temperature and the 1100c temp. Eventually everything in tthrottle "external" stabilized to the correct temperatures that matched nvidia-smi.
I am guessing that the left over setting from HWinfo64 Pro caused the problem in HWinfo32. If I had known the uninstall would not be clean I would have used REVO to do the uninstall.
It would be nice to avoid using GPUZ or HWinfo.
[edit] I think I found the problem with HWinfo32: While I had uninstalled HWinfo64 Pro, I had failed to close it and the uninstall did not bother terminating it. I was running both the 32 and the 64 bit version of the app at the same time. Probably was a coincidence the problem became fixed when running GPUz. I have since rebooted and all is working OK with HWinfo32
They can be force installed in Win11 as P104-100 or using an unsigned driver as P102-100. They are not recognized by tthrottle except using GPUz or HWinfo32
1 - GPU-z (looking at Tthrottle display)
I ran 4 instances of GPU-z and set each instance to a different GPU. Tthrottle shows 4 GPUs in the external tab but only one temperature (the first instance) was available. Possibly there is a setting to force 4 GPUs in tthrottle.xml but I do not know how to configure it.
2 - HWinfo (looking at Tthrottle display)
HWinfo Pro shows all 4 GPU temperatures in Tthrottle but only good for 12 hours. The temperatures matched that revealed by the nvidia-smi app. I uninstalled Pro and put in HWinfo32 and there was a notice that not all items were uninstalled. TThrottle's GPU2 showed 1100c using HWinfo32. All the other temps in TThrottle were ok and matched nvidia-smi. BT reported the 4 temperatures but put in 0c for the problem 1100c temperature.
I brought up GPU-z and set instance to the GPU2 and got the correct temperature (in Tt). In Tthrottle, I was going to disable GPU2 in HWinfo and enable it for GPUz. I noticed that GPU2 in HWinfo now had the correct temperature. I closed GPUz and the temperature momentarily went back to 1100c. While looking this strange problem the temperature toggled between the correct temperature and the 1100c temp. Eventually everything in tthrottle "external" stabilized to the correct temperatures that matched nvidia-smi.
I am guessing that the left over setting from HWinfo64 Pro caused the problem in HWinfo32. If I had known the uninstall would not be clean I would have used REVO to do the uninstall.
It would be nice to avoid using GPUZ or HWinfo.
[edit] I think I found the problem with HWinfo32: While I had uninstalled HWinfo64 Pro, I had failed to close it and the uninstall did not bother terminating it. I was running both the 32 and the 64 bit version of the app at the same time. Probably was a coincidence the problem became fixed when running GPUz. I have since rebooted and all is working OK with HWinfo32