1.)I thought this item has been fix: "BOINC Settings: Try to write back only changed items". It doesn't write back only the changed items.
Its not on the todo list anymore.
2. )Another issue: BOINC settings >- textbox for "only after computer has been idle for"
should be grayed out if both are checked:
-while computer ....
-use gpu ....
3.) still has garbage in log if connection is lost.
Quote from: glennaxl on May 13, 2010, 08:39:39 AM
1.)I thought this item has been fix: "BOINC Settings: Try to write back only changed items". It doesn't write back only the changed items.
Its not on the todo list anymore.
2. )Another issue: BOINC settings >- textbox for "only after computer has been idle for"
should be grayed out if both are checked:
-while computer ....
-use gpu ....
3.) still has garbage in log if connection is lost.
1) There is nothing that I can do about that, as far as I know. Probably the default setting is used of the Internet profile.
2) There still is no release version with that option, but I noted the request.
3) Strange, but noted.
I do have a report that BT gets sluggish after a connection is lost.
Anyone notice anything.
Quote from: fred on May 13, 2010, 09:53:07 AM
I do have a report that BT gets sluggish after a connection is lost.
Anyone notice anything.
Yes a bit sluggish, either reconnect is on or off. Not only in this version but (i think) all previous versions.
Once it start (making it slow), I just deselect that computer and all systems are go.
Hello,
have there been changes in supported operating systems? I'm back to 0.50 (the version I downloaded before 0.55), because W2K tells me "...not a valid 32bit-application"!? Or do I have a damaged installer?
Quote from: borsti67 on May 14, 2010, 07:42:12 AM
Hello,
have there been changes in supported operating systems? I'm back to 0.50 (the version I downloaded before 0.55), because W2K tells me "...not a valid 32bit-application"!? Or do I have a damaged installer?
Check in C:\Program Files\eFMer\BoincTasks if you have the 32 bit version installed. (boinctasks.exe) without the 64 in the name.
But what I fear it that some functions I need are no longer W2K compatible.
Otherwise remove the boinctasks.exe from the C:\Program Files\eFMer\BoincTasks and try installing: http://www.efmer.eu/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_0_5_3.exe (http://www.efmer.eu/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_0_5_3.exe)
Try if that one is working, than I know something more. That's the last one before I switched compiler.
Quote from: glennaxl on May 14, 2010, 02:32:56 AM
Quote from: fred on May 13, 2010, 09:53:07 AM
I do have a report that BT gets sluggish after a connection is lost.
Anyone notice anything.
Yes a bit sluggish, either reconnect is on or off. Not only in this version but (i think) all previous versions.
Once it start (making it slow), I just deselect that computer and all systems are go.
But that's probably because you have a lot of computers.. and it just takes time for BOINC to respond.
Hi all, (please bear with me if I'll repeat something already mentioned, I've got 3 pages of unread threads,)
after starting setup_32_64_boinc_tasks_0_5_5.exe it says "This will install BT 32+64 by eFMer V 0.54 on your computer", the installed BT is indeed 0.55.
After a double-click on any task's line (meant for (un)packing filtered tasks) the otherwise colorful toolbar with task/project tool buttons gets sluggishly (0.3-2.0 seconds (OK, later noticed this delay happens just while running a GPU task)) redrawn with grayed icons. (Why at all this gray?) Another click on any task's line immediately recolors the toolbar.
Am I right that each double-click causes a new communication with clients?
(Win7 Home Premium x64, 2 clients defined, 1 local connected and active. I've been using BT v0.53 for a week or two here.)
-----
While trying the double-clicks to see, whether the communication from/to BT will rise (1-2 double-clicks/second during a minute or two), BT crashed. I've attached a debugger to it to get the reason and stack frame:
Unhandled exception at 0x000000013f668d48 in boinctasks64.exe: 0xC0000005: Access violation reading location 0x0000000000000050.
> boinctasks64.exe!000000013f668d48()
[Frames below may be incorrect and/or missing, no symbols loaded for boinctasks64.exe]
boinctasks64.exe!000000013f6c89d2()
boinctasks64.exe!000000013f6c26ac()
boinctasks64.exe!000000013f6c6534()
boinctasks64.exe!000000013f6c65ec()
user32.dll!000000007751c3c1()
user32.dll!000000007751c60a()
boinctasks64.exe!000000013f6bef4e()
boinctasks64.exe!000000013f6beb27()
boinctasks64.exe!000000013f82fd0f()
boinctasks64.exe!000000013f8160c8()
kernel32.dll!000000007761f56d()
ntdll.dll!0000000077753281()
Launched once more, the first double-click into white area under the lowest task crashed BT again.
OK, third time - it is indeed the white area underneath.
Quote from: Pepo on May 14, 2010, 08:33:31 AM
Hi all, (please bear with me if I'll repeat something already mentioned, I've got 3 pages of unread threads,)
after starting setup_32_64_boinc_tasks_0_5_5.exe it says "This will install BT 32+64 by eFMer V 0.54 on your computer", the installed BT is indeed 0.55.
After a double-click on any task's line (meant for (un)packing filtered tasks) the otherwise colorful toolbar with task/project tool buttons gets sluggishly (0.3-2.0 seconds (OK, later noticed this delay happens just while running a GPU task)) redrawn with grayed icons. (Why at all this gray?) Another click on any task's line immediately recolors the toolbar.
Am I right that each double-click causes a new communication with clients?
(Win7 Home Premium x64, 2 clients defined, 1 local connected and active. I've been using BT v0.53 for a week or two here.)
-----
While trying the double-clicks to see, whether the communication from/to BT will rise (1-2 double-clicks/second during a minute or two), BT crashed. I've attached a debugger to it to get the reason and stack frame:
Unhandled exception at 0x000000013f668d48 in boinctasks64.exe: 0xC0000005: Access violation reading location 0x0000000000000050.
> boinctasks64.exe!000000013f668d48()
[Frames below may be incorrect and/or missing, no symbols loaded for boinctasks64.exe]
boinctasks64.exe!000000013f6c89d2()
boinctasks64.exe!000000013f6c26ac()
boinctasks64.exe!000000013f6c6534()
boinctasks64.exe!000000013f6c65ec()
user32.dll!000000007751c3c1()
user32.dll!000000007751c60a()
boinctasks64.exe!000000013f6bef4e()
boinctasks64.exe!000000013f6beb27()
boinctasks64.exe!000000013f82fd0f()
boinctasks64.exe!000000013f8160c8()
kernel32.dll!000000007761f56d()
ntdll.dll!0000000077753281()
Forgot to change the number in the installer... oeps.
Launched once more, the first double-click into white area under the lowest task crashed BT again.
OK, third time - it is indeed the white area underneath.
Welcome back!
The icons are gray when not active, e.g. when you didn't select any task.
Double click does an update, so that may take some time.
The GPU tasks tend to slow things a bit down, my own "fast" computer sometimes freezes for a second or 2. And Win 7 has a lot more of these than other versions.
For debugging I need something more:
http://www.efmer.eu/forum_tt/index.php?topic=338.0 (http://www.efmer.eu/forum_tt/index.php?topic=338.0)
I will try to add an automatic dump in the next version.
Quote from: fred on May 13, 2010, 09:53:07 AM
I do have a report that BT gets sluggish after a connection is lost.
Anyone notice anything.
still sluggish after connection lost from one machine with this last version too (x32 & x64)
I have set-up reconnect time as 120.
long time to refresh, with message please wait or updating.
long time if program want to be closed and sometimes the message of BT has done one ...
and need closing, do you want to report it??
but for the rest is going really well. :)
Hi Fred,
Quote from: fred on May 14, 2010, 07:51:04 AM
Quote from: borsti67 on May 14, 2010, 07:42:12 AM
have there been changes in supported operating systems?
Check in C:\Program Files\eFMer\BoincTasks if you have the 32 bit version installed. (boinctasks.exe) without the 64 in the name.
The version is ok.
Quote(0.5.3)
Try if that one is working, than I know something more. That's the last one before I switched compiler.
This one ist working!
So no more W2K, yes? :(
Quote from: borsti67 on May 14, 2010, 11:31:55 AM
Hi Fred,
Quote from: fred on May 14, 2010, 07:51:04 AM
Quote from: borsti67 on May 14, 2010, 07:42:12 AM
have there been changes in supported operating systems?
Check in C:\Program Files\eFMer\BoincTasks if you have the 32 bit version installed. (boinctasks.exe) without the 64 in the name.
The version is ok.
Quote(0.5.3)
Try if that one is working, than I know something more. That's the last one before I switched compiler.
This one ist working!
So no more W2K, yes? :(
The problem is Microsoft stopped supporting W2k and some things I really need are in XP and up.
And I don't have any test machines win W2K anymore.
Quote from: Corsair on May 14, 2010, 10:43:15 AM
Quote from: fred on May 13, 2010, 09:53:07 AM
I do have a report that BT gets sluggish after a connection is lost.
Anyone notice anything.
still sluggish after connection lost from one machine with this last version too (x32 & x64)
I have set-up reconnect time as 120.
long time to refresh, with message please wait or updating.
long time if program want to be closed and sometimes the message of BT has done one ...
and need closing, do you want to report it??
but for the rest is going really well. :)
But.. What I really need to know has 0.54 the same problem. Or is the problem introduced in V 0.55.
Quote from: Pepo on May 14, 2010, 08:33:31 AM
Am I right that each double-click causes a new communication with clients?
(Win7 Home Premium x64, 2 clients defined, 1 local connected and active. I've been using BT v0.53 for a week or two here.)
-----
While trying the double-clicks to see, whether the communication from/to BT will rise (1-2 double-clicks/second during a minute or two), BT crashed. I've attached a debugger to it to get the reason and stack frame:
Unhandled exception at 0x000000013f668d48 in boinctasks64.exe: 0xC0000005: Access violation reading location 0x0000000000000050.
> boinctasks64.exe!000000013f668d48()
[Frames below may be incorrect and/or missing, no symbols loaded for boinctasks64.exe]
boinctasks64.exe!000000013f6c89d2()
boinctasks64.exe!000000013f6c26ac()
boinctasks64.exe!000000013f6c6534()
boinctasks64.exe!000000013f6c65ec()
user32.dll!000000007751c3c1()
user32.dll!000000007751c60a()
boinctasks64.exe!000000013f6bef4e()
boinctasks64.exe!000000013f6beb27()
boinctasks64.exe!000000013f82fd0f()
boinctasks64.exe!000000013f8160c8()
kernel32.dll!000000007761f56d()
ntdll.dll!0000000077753281()
Launched once more, the first double-click into white area under the lowest task crashed BT again.
OK, third time - it is indeed the white area underneath.
Ok the logs you send me gave me some great info.
The problem is indeed in the double click part, so don't double click in this version. ;D
Now that I know exactly what happened, all the 6 times you send me, gave the same result.
I should be able to fix it. One night sleep. ;D
Quote from: fred on May 14, 2010, 01:58:44 PM
Ok the logs you send me gave me some great info.
The problem is indeed in the double click part, so don't double click in this version. ;D
I'll not anymore :) (at least under the task lines)
QuoteNow that I know exactly what happened, all the 6 times you send me, gave the same result.
I should be able to fix it. One night sleep. ;D
OK, until you get then asleep, one more info: as soon as TThrottle ceases to communicate or terminates, BT continues to display the last known temperatures and throttle level, as if it were the actual values. I'd prefer to let them disappeared as it is until the two start to communicate. (Say after maybe 10 times the usual connect interval or so.)
Quote from: Pepo on May 14, 2010, 02:23:36 PM
Quote from: fred on May 14, 2010, 01:58:44 PM
Ok the logs you send me gave me some great info.
The problem is indeed in the double click part, so don't double click in this version. ;D
I'll not anymore :) (at least under the task lines)
QuoteNow that I know exactly what happened, all the 6 times you send me, gave the same result.
I should be able to fix it. One night sleep. ;D
OK, until you get then asleep, one more info: as soon as TThrottle ceases to communicate or terminates, BT continues to display the last known temperatures and throttle level, as if it were the actual values. I'd prefer to let them disappeared as it is until the two start to communicate. (Say after maybe 10 times the usual connect interval or so.)
Noted.
A currently running (in high prio mode) GPUGrid task (0.04C +1NV) is not highlighted and I'm not able to find any reason - 3 days 1 hour till deadline, 13:45 hours to go, CPU%=3.06, deadline warning is 1d8h, so neither deadline warning nor computing ration should apply, a running GPU color is defined. But the task's line is still not colored.
Quote from: Pepo on May 17, 2010, 07:51:40 AM
A currently running (in high prio mode) GPUGrid task (0.04C +1NV) is not highlighted and I'm not able to find any reason - 3 days 1 hour till deadline, 13:45 hours to go, CPU%=3.06, deadline warning is 1d8h, so neither deadline warning nor computing ration should apply, a running GPU color is defined. But the task's line is still not colored.
The HP color is set ok?
A picture?
Quote from: fred on May 17, 2010, 10:05:58 AM
Quote from: Pepo on May 17, 2010, 07:51:40 AM
A currently running (in high prio mode) GPUGrid task (0.04C +1NV) is not highlighted and I'm not able to find any reason - 3 days 1 hour till deadline, 13:45 hours to go, CPU%=3.06, deadline warning is 1d8h, so neither deadline warning nor computing ration should apply, a running GPU color is defined. But the task's line is still not colored.
The HP color is set ok?
No ::)
(solved, sorry)
Quote from: fred on May 14, 2010, 04:31:51 PM
Quote from: Pepo on May 14, 2010, 02:23:36 PM
OK, [...] one more info: as soon as TThrottle ceases to communicate or terminates, BT continues to display the last known temperatures and throttle level, as if it were the actual values. I'd prefer to let them disappeared as it is until the two start to communicate. (Say after maybe 10 times the usual connect interval or so.)
Noted.
Today during my TThrottle's 1.76->1.80 update, the 1.76 was a couple (10-25?) of minutes stopped. I've noticed that BT does not display the temperatures anymore.
So maybe BT already behaves deterministically like this, just the delay is somehow longer.