Messages

The gadget stated something like

Running=0
Connected=0

where I would have expected it to state 'Connected=x'. It was easy enough for me to physically check all machines to ensure that they were all running and connected to the network because all machines are located in my house. I am thinking more of others who might not have all machines locted in the same building.

As for the messages tab, I think I will have to recreate the scenario to give an more accuate report.

One concern with "Display active tasks" - if it is set and there are no more active tasks, the Tasks tab is empty. It is then not possible to open the tasks' context menu and display the inactive ones - context menu is the only way the control it...

A few days ago, my ISP went down for approx 24 hours during which time my cache was totally cleaned out and I therefore had no WUS to process. What you are are reporting was also showing me in Tasks tab and the gadget that I appeared to have no machines connected to BT.

My point being that all machines were still connected yet not processing any data. I think it is disconcerting to get a report that no machines are connected when in fact they are. Wouldn't it make more sense to still report that they are connected even if they are not doing any work? After all, it should still be useful to be able to go to the messages tab to confirm that attempts are still being made to connect to the server.

Installed and running. The crash of 1.22 appears to have been resolved.

Note to other users: initially on starting the process, BT appears to hang but opens up within 60 seconds.

Thanks for the quick fix, fred.

Thanks. BTW 1.12 was a typo, I'm using 1.21

OK. BT uninstalled this time using the official way and 1.21 installed without any problem. Nice to see that even though the program is deinstalled, it reinstalls with old settings retained

Attempted to update to 1.22 but once again, program continues to crash along with Fatal error of BoincTasks_ENU.btlang. Eventually, reached 'more than 10 crashes in last 12 hours message'.

I'd love to do more to help with this version, but for me it is unusable, so it's back to 1.12 for me.

Same problem here. I got a message that I had had 12 crashes in last 12 hours and that if I removed them from AppData/eFMer/BoincTasks/crash, BT would run again. All 12 dmps are from today and are 0 bytes. All 12 removed but BT continues to crash (although seen to be running in Task Manager).

I then reinstalled 1.21 and attempted to run. Now get a new error message about fatal error in language file: BoincTasks_ENU.btlang. Unsure if this is going to be of any use, but here are the contents of that file:

Open file:C:\Program Files\eFMer\BoincTasks\lang\BoincTasks_ENU.btlang
Group: <GroupMenuMain> string header in pos 177, <ShowHistoryLong> not found
Group: <GroupMenuMain> string header in pos 178, <ShowHistoryLongS> not found
Group: <GroupDialogSettings> string header in pos 375, <HistoryMoveLong> not found
Group begin not found: <groupdialoghistorylong>

I was wondering if you agreed that it might be useful to add an option to send an e-mail/alert on certain conditions being met.

Now that I appear to have Webserver running, I don't see a way select a computer in order to view messages on that particular machine. The page lacks a 'select computer' option in the page.

Is this planned for a future update or left for the user to create?

Apologies for the delay in replying. I had previously enabled BOTH.

So now I have 'Enable Webserver on port:' set to the default 38000 and 'Enable WWW update' DISABLED. It's here that I have to apolgise to you. For some reason on the machine that I did the test with, IE8 is the only instance in which I cannot effectively scroll down the page because of constant refreshing.

All other machines are not giving me the problem, so once again, please accept my apologies.

I have never looked at this thread before, but one question I have is about

All members that have never logged in. (within a week).

What about people on vacation? Isn't a week rather severe and perhaps adding more work for you than neccessary?

I have noticed that if one of my connected machines is rebooted, BT seems to be unable to connect to it once that machine restarts. In the computer selection sidebar there is no icon to show that BT has lost connection to the machine.

If I close BT and reopen it, the other machine is automatically detected again.

NOTE: I don't know if it makes a difference, but before I reboot a machine, I always suspend running tasks after they reach checkpoint. By the reboot stage, all tasks (including 'Ready to start' tasks on that machine are all in 'Suspended' mode

I looked at this again in the light of a new day and realise that the 'LEFT CTRL+dbl-click' is more powerful than I first of all realised. Let's take this scenario:

1 WU1 type is suspended and WU2 type is ready to start. Both types are filtered. I wish to micromanage these WU types to (for example) give priority to resends.

2 I had asked for a way to a quick method to unfilter both types so that I could easily see the WUs that I wished to run in priority. We already know that LEFT CTRL+dbl-click cannot open a second WU type whilst retaining the first type in an unfiltered view.

3 THIS IS MY WORKAROUND.
i   Change the suspended type to 'ready to start' (now both WU types are in the same state)
ii  LEFT CTRL+dbl-click and BOTH WU types become unfiltered
iii  Now suspend the ones you don't want to run. Your selected WUs for priority will now be in 'ready to start' state.
iv  Once you are done, LEFT CTRL+dbl click to return to filtered view.

NOTE: I have realised that if you do LEFT CTRL dbl click on WUs from another machine, those WUs too will become unfiltered. I now realise that my mistake was that I thought LEFT CTRL+dbl click was meant to be a second process. Now I realise that if you use it as an alternative to simply dbl-clicking, its true potential can be realised.

It's a bit of a half-way house, I think. If I need the kind of info it shows, I think it is easier to go 'all the way' and open BT itself and make any required changes. I find it useful to just rest mouse over the icon and be reassured that all machines are up and running.

The fix to show the total amount of machines reporting to BT is clean and easy to be seen. When I want to micromanage, I can open the main program.

e.g. I just finished building a new machine yesterday and set it to process BOINC. The popup message kept showing me that the machine wasn't connecting to BT which was enough to prompt me to go check and realise that I hadn't changed from the default Power Management setting to 'always on and running'.

With this fix, I don't even have to work out if a machine is down. The 'total' shows me this immediately!

There are users with 5000+ tasks and for every tasks BT has to check a couple of different unrelated things. It will take too much additional time.

That puts my request into perspective. I create templates for and work on a program called TViXiE, and when I get requests for features from users, what may appear to be a simple request can often entail a lot of background work so I fully understand what you are saying.

Changed: Added sum to icon message, like 2,4,3,6 =15.

Thanks for the bug fix. Much more user-friendly now