Messages

Part of the delay may be here:

11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\history\backup\*.*
11/09/2011, 11:44:18 -- Timeout

BTW, the above directory has 6007 files using in excess of 6GB of disk space.

I edited my previous reply and replaced it with the correct log hopefully.

To answer your questions, I don't know what you mean by "Which client is it connected to?"  The CPU usage is high until BT pops up on the desktop and the BT taskbar icon simultaneously appears, then the CPU usage immediately drops to well under 1%.  There is no way to see the Messages or Tasks tab until the BT

Startup file? So I can see where the 90 seconds go.

Nope, those were my answers to Pepo's questions 

I like to see the startup log: "BoincTasks Startup.log", that should show what BT is doing, time wise.

11/09/2011, 11:43:57 -- Startup: BoincTasks Version: 1.27
11/09/2011, 11:43:57 -- Set exeption handler
11/09/2011, 11:43:57 -- Read arg:
11/09/2011, 11:43:57 -- Language detection
11/09/2011, 11:43:57 -- Language registry: 1033
11/09/2011, 11:43:57 -- Language selected: 1033
11/09/2011, 11:43:57 -- Read translation
11/09/2011, 11:43:57 -- Close translation, OK
11/09/2011, 11:43:57 -- Started logging
11/09/2011, 11:43:57 -- Open translation override
11/09/2011, 11:43:57 -- Close translation override, OK
11/09/2011, 11:43:57 -- User: 1033 (ENU), System: 1033 (ENU), Selected: 1033 (ENU) Used: 1033 (ENU)
11/09/2011, 11:43:57 -- Mutex is not set
11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\crash\*.*
11/09/2011, 11:43:57 -- Deleted crash files
11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\history\backup\*.*
11/09/2011, 11:44:18 -- Timeout
11/09/2011, 11:44:18 -- Deleted history files
11/09/2011, 11:44:18 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\log\*.*
11/09/2011, 11:44:18 -- Deleted logging files
11/09/2011, 11:44:18 -- WSAStartup OK
11/09/2011, 11:44:18 -- Menu translations done
11/09/2011, 11:44:18 -- Created main window
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.7
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.4
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.11
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.9
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.8
11/09/2011, 11:44:18 -- computers.xml IP: localhost
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.6
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.3
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.15
11/09/2011, 11:44:18 -- Connect to BOINC clients
11/09/2011, 11:45:40 -- Startup finished

So far the localhost TT temp seems to be reporting most of the time, a nice improvement.

Tried it a 3rd time, exited immediately.  Took 90 seconds when I restarted it.  Watched the process in Process Lasso, BT grabbed a whole CPU core for the 90 seconds that it took for the main window and icon to appear.  Then it returned to its normal low CPU usage.  The long start period always makes me a little nervous because of the BT start problems I've had post 1.21 

Which client is it connected to? While the CPU usage is high, what does the Messages tab look like? Is the Tasks tab correct?

Tried exiting and restarting 4 more times (8 in all so far), watching in Process Lasso.  The exit is always immediate.  The start always takes about 90 seconds (80-85 seconds CPU time).  I was trying to get the darn toolbar icons all to stay on one line, no luck there until I disabled 2 of them that I never use anyway.

To answer your questions, I don't know what you mean by "Which client is it connected to?"  The CPU usage is high until BT pops up on the desktop and the BT taskbar icon simultaneously appears, then the CPU usage immediately drops to well under 1%.  There is no way to see the Messages or Tasks tab until the BT program window pops up after ~90 seconds.

So far the 1.27 test version is the first one that worked at all properly here since 1.21.  A very nice improvement IMO.   

Tried it a 3rd time, exited immediately.  Took 90 seconds when I restarted it.  Watched the process in Process Lasso, BT grabbed a whole CPU core for the 90 seconds that it took for the main window and icon to appear.  Then it returned to its normal low CPU usage.  The long start period always makes me a little nervous because of the BT start problems I've had post 1.21 

On my system it works too except that it won't close and I have to kill it in TaskManager. Can you check that on your system?

It exited properly the 2 times I tried it, takes about 90 seconds to start though every time.

Test version: 1.27 TEST  http://www.efmer.com/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_1_2_7_TEST.exe

BT 1.24 & 1.25 started erratically here too.  Often the icon would not appear and the program would also not appear (set not to minimize on start) but the BT task would be in Task Manager with about .4 seconds of CPU time.  I could get 1.25 to start by rebooting.  1.26 would not start at all.  Tried 1.27 test version above and it started after about 90 seconds.  Seems to be working well and for some reason now the localhost TT temp is showing in BT.  In 1.25 the TT temp showed up about 1% of the time if that.

Calibration, Temperature: 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34
Calibration, Temperature: 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34
Calibration, Temperature: 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34
Retry: 60 Delta: 161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616
CoreDelta: 16.500000, 16, Valid core readings: 60
Calibration, Cores using: 6, Core step 3
Calibration, End

Still finds 2 sensors on an X6.

Can you give me the calibration log of V 5.43, lets see what going on.

Start logging

Calibration, Start
Calibration, Temperature: 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24
Calibration, Temperature: 29 29 29 29 29 29 29 29 29 29 29 29 29 29 29 29

Calibration, Temperature: 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34
Retry: 60 Delta: 161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616161616
CoreDelta: 16.500000, 16, Valid core readings: 60

continued below...

Fixed: If there is only one temperature sensor, the calibration takes a long time and sometimes detects 2 sensors.
Fixed: Installation: Failed to place the desktop icon.

Still finds 2 sensors on an X6.  The only way I've found to get back to 1 sensor is to uninstall 5.43, then regedit and remove TThrottle calibration section, then reinstall 4.3 and let it do the calibration, then reinstall 5.43 over it without recalibrating.

I found that by completely uninstalling 5.42 and then installing 4.30, TT recalibrated and found 1 CPU temp sensor.  Then reinstalled 5.42 over 4.30 without recalibrating and now that machine still shows 1 temp sensor.  A question is, how many temp sensors does an x6 really have?

My human eye shows only 1 core. So I have to check the program, why it calls the reading invalid, as it's clearly valid.
Should be easy to fix.

I can't find any info about AMD, only that it has one sensor.

4.30 finds 1 core, 5.30 finds 2, 5.42 finds 2.  So uninstalling 5.42, running regedit and deleting the TT settings, then installing 4.30 and letting it run calibration, then installing 5.42 over it gets things back to normal.  Sometimes regedit has to be used, sometimes not...

I found that by completely uninstalling 5.42 and then installing 4.30, TT recalibrated and found 1 CPU temp sensor.  Then reinstalled 5.42 over 4.30 without recalibrating and now that machine still shows 1 temp sensor.  A question is, how many temp sensors does an x6 really have?

Calibration, Temperature: 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45
Calibration, Temperature: 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45
Calibration, Temperature: 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45
Retry: 60 Delta: -1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1
CoreDelta: 0.000000, 16, Valid core readings: 0
Calibration, Cores using: 6, Core step 3
Calibration, End

I cut out a lot of the middle part of this file but it's still way too long to post.  It's 94k and the one on the other machine I recalibrated is 444k.

The 2 that show 2 temp sensors are the one's that recalibrated when loading 5.42.  Stopping BOINC and recalibrating causes TT to show 2 temp sensors  for an x6.

Calibration is logged to the logging file: C:\Users\username\AppData\Roaming\eFMer\TThrottle\log
Look for Calibration start and end. I like to see everything in between.

Calibration, Start
Calibration, Temperature: 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44
CoreDelta: 0.000000, 16, Valid core readings: 0
Reset.

continued below...