Messages

There is a file dated 13/07/13 which is just over 100MB would that be any use? I've opened it with notepad but cannot make any sense of it.

Happy to send if required.

No. The folder is empty

We will probably never know what caused the problem.

I guess not, but will keep an eye on it.

One question arising from this is what causes TThrottle to close without any user input? I see this quite often (perhaps 1-2 machines out of 12 closing every day or so). It isn't the case of the icon disappearing from the system tray, they are not showing in Task Manager Processes either.

If this is going to prove to require more info, I will do so in the TThrottle thread.

I have found another issue which I have never seen before (but only on one machine)

Using the TThrottle module of BT, I am looking at one machine in particular. It is telling me that the number of matching Programs (Processes) is 2 and lists them. However, this machine is being reported in BT as running 4 (and that is alsothe case when physically checking the machine).

I have never examined the PID info before, but in the TThrottle module, it is different to what is reported in TThrottle and Task Manager on the actual machine. Is there any logs info that I could add to this?

Did BoincTasks generate a crash report? For 1.52
C:\Users\username\AppData\Roaming\eFMer\BoincTasks\crash

No. The folder is empty

I may have found a bug in 1.52. BoincTasks Credit Graphic was showing graphed results in Average mode, but when I switched to Total, the window went blank (i.e. nothing at all not even gridlines). Switching back to Average now gave the same result. Closing the graphic and reopening did not fix it.

Whilst typing this report, the graphics window closed itself and reopened with no Computers or Projects highlighted. Enabling Computers and Projects again now shows the plot with gridlines and legend. So it appears that BT fixed the problem itself but I thought I would report this because I have never seen it before.

Apologies. I look at this again and conclude that it is a user error. All machines are now reporting running temperatures.

re your reply, if IP had changed, surely no data at all would have been reported to BT?

Hi Fred. I'm not sure if this post would be better suited to the general TThrottle thread but I noticed today that although TThrottle is running on all machines, it is not being reported in Boinctasks for any machine.

I had to reboot one machine and instantly TThrottle results for that machine were shown in BoincTasks which is what drew my attention to this.

So why is it that all other machines are no longer showing results? (This is not the first time that I have noticed this, but I have never seen so many not being shown at once)

Thanks for the reply. As soon as I read 'first column' I realised that the reboot has somehow caused corruption in TThrottle.

Looking at it again, it looked like the old format of presenting the data even though the window title was TThrottle V7.01. All processes were running and data was being passed to BT.

Re-installing v7.01 appears to have fixed the problem and I now have it displaying the data in the new style. 

Hi Fred, since b7.01 has fixed the problem with drivers, it might be worthwhile to change the red warning message at the top of the page to advise to change to v7.01 instead of v7 Beta which it still says.

One thing I have noticed is that after rebooting the Vista x64 machine for the first time since I upgraded to 7.01, the processes in the Programs tab are no longer highlighted in green. The data in that screen appears to be correct (and the window title still says TThrottle V7.01).

Is the green highlight merely cosmetic (in which case, I don't mind), or does the green highlight indicate something?

[474C40CD64806E66EBD3E0B9F8F2ADC371A5B1B3]

Not a problem

I'm more intrigued by the difference in the hash values so I have done an online calculation here which confirms that the SHA-1 value is 474C40CD64806E66EBD3E0B9F8F2ADC371A5B1B3

I suppose that does the job, but what I was thinking of was being able to show more than one machine at a time and plotting ONLY the values that TThrottle uses to decide whether to throttle or not.

I would then be able to see at a glance if any machine was constantly running at high temps and being throttled. I would thus be able to see if any machine required a better thermal management. Not such a big problem  in colder months but invaluable in the summer.

By having all machines on the same graph, I could compare how well temps are being managed just like I can compare efficiency in the Statistics graph. Does that make more sense?

[i.e. not H474C40CD64806E66EBD3E0B9F8F2ADC371A5B1B3 as you have posted]

Congrats on these important changes and for adding the SHA-1 hash to the download page. I have a question about the SHA-1 value you have given. My check lists SHA-1 value as 474C40CD64806E66EBD3E0B9F8F2ADC371A5B1B3

i.e. not H474C40CD64806E66EBD3E0B9F8F2ADC371A5B1B3 as you have posted

I will do some test installs and let you know the outcome:

Win 7 x64: 7.0.0.2 TO 7.01 SUCCESS
Vista x64: 6.5 TO 7.01: SUCCESS Congratulations!
Vista x86: 7.0.0.2 TO 7.01: SUCCESS
XP x86: 7.0.0.2 TO 7.01 SUCCESS

SUCCESS = Installed and runs with NO problems.

P.S. I see my name didn't make it to the 'About' screen 
Don't worry, I am more grateful that the Vista x64 problem had been fixed

I will continue to monitor performance and keep you informed

Hi Fred, I wonder if it would be possible to add a new chart similar to the credits graph to record temperatures of machines (using the value that TThrottle uses when deciding whether to throttle or not). Getting values even on an hour by hour basis, it should help decide which machines are in need of better thermal management.

I would be interested to hear your thoughts on this...

Yes, TThrottle in any of the v7 versions shows that tasks are running, but | Show | TThrottle | in BT 1.50 seems to require the latest beta for running tasks to be shown. Otherwise BT 1.50 reports 0 tasks running.

It's all the fun of beta testing and great sport for rainy days!

OK. The reason I said 'left behind' is because of your previous reply,

This is probably the best test version on this side.

This probably means that 2.4 is the last < W7 driver.

so I naturally assume that Win7 x64 will be stuck with TThrottle 6.50