BoincTasks TrayIcon doesn't show

[Mellowman]

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?

Anthony.

[Beyond]

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.

[Mellowman]

It starts immediatly on my system, except that it won't close. I  just did a uninstall/install to see if that helped as I've been testing whole afternoon. It still won't close normally. I'll do a reboot as soon as my TV-recording is done, which is now I see. Hopefully that'll work.

[Beyond]

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 

[Mellowman]

I'm still having connecting problems. Fred and I thoughed we solved it this afternoon, but we didn't actually. After my reboot it couldn't connect to 1 of my 2 clients on the same computer. I run a separate client for my old GF8600GT card which can only run Collatz. My other card is a GTX-500Ti. If I use them both with 1 client GPU-projects that can't use the 8600GT will still try to resulting in errors. And I didn't want to disable my 8600GT.

Now it won't connect to my main Boinc client, but if I start BoincManager en then start BT it does connect to both of them  . BT still won't shutdown properly though. I still have to kill it in TaskManager.

Anthony.

[Pepo]

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 in agreement with my observation of BT 1.26's delayed start.
Possibly the kill was indeed not necessary, but more than a couple of seconds is (or at least was) highly unusual for starting BT.

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?

[fred]

The 1.27 test version has a build in timeout as old files are deleted.
There is also some additional logging in the startup log.

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

[Beyond]

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.   

[fred]

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.

[Mellowman]

He means your startuplog:

C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\log\BoincTasks Startup.log

Put your username where mine (Anthony) is.

[Beyond]

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.

[Beyond]

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 

[fred]

Here it is,

Also a nice log but not the one I wanted.
See Anthony's link and replace the username.....

[Beyond]

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

[Beyond]

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.