BoincTasks TrayIcon doesn't show

Started by Mellowman, November 07, 2011, 04:10:39 PM

Previous topic - Next topic

0 Members and 4 Guests are viewing this topic.

Mellowman

Startup log:

11/10/2011, 16:58:07 -- Startup: BoincTasks Version: 1.27
11/10/2011, 16:58:07 -- Set exeption handler
11/10/2011, 16:58:07 -- Read arg:
11/10/2011, 16:58:07 -- Language detection
11/10/2011, 16:58:07 -- Language registry: 0
11/10/2011, 16:58:07 -- Language selected: 0
11/10/2011, 16:58:07 -- Read translation
11/10/2011, 16:58:07 -- Close translation, OK
11/10/2011, 16:58:07 -- Started logging
11/10/2011, 16:58:07 -- Open translation override
11/10/2011, 16:58:07 -- Close translation override, OK
11/10/2011, 16:58:07 -- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
11/10/2011, 16:58:07 -- Mutex is not set
11/10/2011, 16:58:07 -- DeleteFiles in folders:C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\crash\*.*
11/10/2011, 16:58:07 -- Deleted crash files
11/10/2011, 16:58:07 -- DeleteFiles in folders:C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\history\backup\*.*
11/10/2011, 16:58:07 -- Deleted history files
11/10/2011, 16:58:07 -- DeleteFiles in folders:C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\log\*.*
11/10/2011, 16:58:07 -- Deleted logging files
11/10/2011, 16:58:07 -- WSAStartup OK
11/10/2011, 16:58:07 -- Menu translations done
11/10/2011, 16:58:07 -- Created main window
11/10/2011, 16:58:08 -- computers.xml IP: localhost
11/10/2011, 16:58:08 -- computers.xml IP: localhost
11/10/2011, 16:58:08 -- computers.xml IP: 169.254.0.2
11/10/2011, 16:58:08 -- Connect to BOINC clients
11/10/2011, 16:58:08 -- Startup finished

Daily log:

Start logging

10 November 2011 - 16:58:07 BoincTasks version: 1.27
10 November 2011 - 16:58:07 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
10 November 2011 - 16:58:08 Maximum number of computers: Unlimited
10 November 2011 - 16:58:08 Computers ---- localhost get local password: (C:\ProgramData\BOINC\\gui_rpc_auth.cfg) 124a4ce72617dcb839f17ea33a5020af
10 November 2011 - 16:58:08 Computers ---- Windows-7-PC , localhost
10 November 2011 - 16:58:08 Computers ---- Windows-7-PC Collatz , localhost2
10 November 2011 - 16:58:08 Computers ---- Labtop , 169.254.0.2
10 November 2011 - 16:58:08 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:08 Connect ---- Try to connect to: Host: localhost2, Windows-7-PC Collatz, Port: 31418, Thread ID: 7496
10 November 2011 - 16:58:08 Connect ---- Try to connect to: Host: 169.254.0.2, Labtop, Port: 31416, Thread ID: 4656
10 November 2011 - 16:58:08 Connect ---- Connected to: Host: localhost2, Windows-7-PC Collatz, Port: 31418, BOINC Version: 6.12.34
10 November 2011 - 16:58:08 Connect ---- Connected to: Host: 169.254.0.2, Labtop, Port: 31416, BOINC Version: 6.12.34
10 November 2011 - 16:58:09 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:11 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:12 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:14 Connect ---- Connected to: Host: 169.254.0.2, Labtop,Port: 31417, TThrottle Version: 5.10
10 November 2011 - 16:58:14 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:15 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:17 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:18 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:20 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:21 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:23 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:24 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:26 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:27 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:29 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:30 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:32 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:33 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:35 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:36 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:37 Memory ----
   PageFaultCount      : 0x00002181   8K
   PeakWorkingSetSize   : 0x01F4A000   32808K
   WorkingSetSize      : 0x01F4A000   32808K
   QuotaPeakPagedPool   : 0x00071BE8   465K
   QuotaPagedPool      : 0x00070C88   461K
   QuotaPeakNonPagedPool   : 0x00008028   32K
   QuotaNonPagedPool   : 0x00007858   30K
   Pagefile         : 0x01055000   17125K
   PeakPagefile      : 0x011FD000   18862K

10 November 2011 - 16:58:38 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:39 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:39 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:40 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:41 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:42 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:44 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:45 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:59:09 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:59:10 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:59:39 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:59:40 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error


Anthony.

Beyond

Quote from: Mellowman on November 10, 2011, 03:09:52 PM
The 8600GT still can crunch a mini-collatz in ~2hours. All my Collatz credits from last month are from that card.
Just to give you a reference, even the HD4770 will do a full size Collatz WU in ~1 hour, so is about 16x faster than the 8600.  You should be able to get one for under $50 used.  The HD5770 will do about 43 minutes/large WU for a 23x improvement..  You would also get rid of your Collatz problems:  "I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors."

Mellowman

#62
QuoteYou would also get rid of your Collatz problems:  "I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors."

I don't have a lot of computation erorrs. Where did I say that? You can check it here.

And I only run Collatz because that's the only project I know that will run on my 8600GT 256MB, and I want to use that card too. Otherwise I wouldn't even have signed up for the project.

Anthony.

Beyond

Quote from: Mellowman on November 10, 2011, 04:14:55 PM
QuoteYou would also get rid of your Collatz problems:  "I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors."

I don't have a lot of computation erorrs. Where did I say that? You can check it here.

Here's your thread on Collatz:

lot of videodriver crashes and WU-errors on GF8600GT

http://boinc.thesonntags.com/collatz/forum_thread.php?id=796

Your first post on the subject:

"Hi, I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors. I got those even without my GTX-550OC added to the system. I can't even suspend a collatz task as it will result in a displaydriver crash and a computation error. I also use my GF8600GT as my main display output to my TV. Display on the GTX550OC is totally disabled as I want that card fully dedicated for crunching other non collatz tasks as collatz is the only project that seems to run on my GF8600GT 256MB card. I use the latest nvidia driver 280.26."

How soon we forget...   :)

Mellowman

Did you read the next post too. It happened to be a driver problem, so I wasn't the only one with a lot of computation errors. Since I updated the driver I've hadn't had any problem except for the driver crashes when I suspend Collatz or exit the Collatz boinc client, but no computation errors. But I wrote to Nvidia about the driver crash problem. It isn't that big of a problem as I only suspend Collatz when I want to watch (recorded) TV. And lately I havent watched much (but still kept recording so I should watch because I'm running out of space on my 1.5 TB total drive space on this system).

So after 2.5-3 week I totally forgot about that post. Can you blame me, I might have other things on my mind, then to remember something that's been solved for 3 weeks and has been on my mind that oktober 23rd for maybe less than an hour.

I f*cked up my brain already with 23.5 years of smoking marihuana (I quit smoking it since the 2nd half of July this year after having not smoked it the first half year of this year when I was in a psychiatric hospital/clinic because I have a deathwish.

I still take tranqelizers to calm me down and those aren't that good for your memory either. So I'm sorry I forgot something that wasn't an issue anymore.

Anthony.

Beyond

Sorry Anthony, was just trying to offer a helpful alternative.  Think I forgot something once too, but can't remember what it was at the moment  ;)

Mellowman

But the alternative doesn't work for me. It would mean I have to throw a perfectly good card (old but still good enough for some stuff) in the bin as I can't sell it as it isn't worth anything. And if I buy an ATI card which project that I run can I use it for. I need an ATI double precision card then, so I could use it for MilkyWay. What will those cost me? And are those 2 projects the only projects where I can use ATI cards (from the projects I run)?

Going to bed now as it's 4:42 AM overhere.

Anthony.

Pepo

Quote from: Pepo on November 09, 2011, 09:41:36 PM
My ...\history\backup folder (on one machine with a very small number of tasks being processed) contains 10.4 MB in 250 files, spanning 25.10.-9.11. - possibly because of History's "keep 12 days + 0 hours" preference? The startup times are short now (2-3 seconds, full CPU use).
On another machine (with a bit more tasks) there were 800 files using up 400 MB, spanning 25.10.-11.11. Short-term history is set to keep 5d+23h.

Actually neither of the files (on both machines), nor the backup folders were set to read-only.
Peter

fred

Quote from: Pepo on November 11, 2011, 02:00:44 PM
Quote from: Pepo on November 09, 2011, 09:41:36 PM
My ...\history\backup folder (on one machine with a very small number of tasks being processed) contains 10.4 MB in 250 files, spanning 25.10.-9.11. - possibly because of History's "keep 12 days + 0 hours" preference? The startup times are short now (2-3 seconds, full CPU use).
On another machine (with a bit more tasks) there were 800 files using up 400 MB, spanning 25.10.-11.11. Short-term history is set to keep 5d+23h.

Actually neither of the files (on both machines), nor the backup folders were set to read-only.
Wait for 1.27, I made a lot of changes, that should fix all these problems, including a read only problem. The last one shouldn't be there in the first place.

Pepo

Quote from: fred on November 11, 2011, 03:29:13 PM
Wait for 1.27, I made a lot of changes, that should fix all these problems, including a read only problem.
Will it be able to install over the "temporary" 1.27? Or better some 1.27.1?
Peter

fred

Quote from: Pepo on November 11, 2011, 04:34:55 PM
Will it be able to install over the "temporary" 1.27? Or better some 1.27.1?
It should install over the test version as the file itself is 1.271.

Pepo

Quote from: fred on November 11, 2011, 06:18:09 PM
Quote from: Pepo on November 11, 2011, 04:34:55 PM
Will it be able to install over the "temporary" 1.27? Or better some 1.27.1?
It should install over the test version as the file itself is 1.271.
:) That's exactly what I've meant.
Peter