Messages

Thank you so much for BoincTasks; during the winter, I cannot imagine running BOINC without it. The workunit history is its best feature, and I refer to it all the time.  You certainly deserve more and larger donations, but right now money is a problem.  Let me just say, if I get some, so will you. 

I am testing a video card using BOINC, Einstei@Home, and BoincTasks, even though I don't need them for the heat.
The left-most pane below the ribbon of the BoincTasks main window has a list of computers, each having an indication of whether or not the computer is connected.  On BoincTasks Beta 1.95 this pane is not docked, and so it must be created every time the BoincTasks UI is displayed.  Moreover, when the UI is dismissed to the tray, the left-most pane still exists on the Desktop and must be destroyed separately.

BoincTasks sent me a notice suggesting that I download BoincTasks 1.95, but I cannot find a download link anywhere.   

Thank you in advance for your kind attention to these matters.

Charles Elliott

PS: Platform:
OS Name:      Microsoft Windows 11 Pro Version 10.0.26100 Build 26100.4061
Processor:      AMD Ryzen 7 5700X 8-Core Processor, 3401 Mhz, 8 Core(s), 16 Logical Processor(s)
BaseBoard Product: ASUS TUF GAMING X570-PLUS (WI-FI)
BIOS:              AMI 5021 9/29/24
RAM:               64 GB DDR4 1800 MHz G.Skill P/N: F4-3600C18-16GTZN
 

Thanks for all your help.

The history *.cvsN files are using a different computer name.  The NetBIOS name of the computer is Luke.  The Control Panel/System computer name is Luke.local.celliott.us, and that was the name used by BoincTasks when the BoincTasks folder was on C:.  But now that it is on G:, BoincTasks is using just Luke in the file names.  I rebooted the computer at about 9 this morning.  The History tab now contains all the work units completed after 9:11:30 AM.

If I stop BoincTasks and edit the files to transfer the entries from the files with the Luke.local.celliott.us name to the files with just the Luke name, will it cause any problems?

What about the log folder?  It has hundreds of entries from Oct 2015 and before, but nothing recent.  How can I fix that?

Thanks for making it possible to move BoincTasks data files away from an SSD.  The first time I tried it, it worked well, but now I have a problem.

I had to install a new SSD due to a crash and burn.  Last evening, after a month of operation, I got around to moving the BoincTasks directory to a hard drive. I changed "C:\Users\CElliott\AppData\Roaming\eFMer\BoincTasks" to "G:\Users\CElliott\AppData\Roaming\eFMer\BoincTasks,' where there were some old files from October 2015.  Now only the old work units will display on the History tab.  All the cvsN files seem to have been updated correctly; workunits completed after 8:30 PM last night are in the files, but the History tab is not updating.  This morning, BoincTasks was frozen when I clicked on the tray icon; I had to stop it with TaskMgr and restart it.  The first time I tried moving the default BoincTasks folder, it worked great, but not now.  Perhaps it is the old files BoincTasks found in the new destination directory that is causing the problem.

Do you know some way I can make the History tab display current information?  I copied the BoincTasks directory before I moved it.

We need a way to store the BoincTasks history and other data files on a different drive than C:.  C: is an SSD, and it is waste to wear it out storing files that could easily be placed elsewhere.

Not much changed in 1.59.
I run Win 8.1 so that's not the issue.
Look at the BoincTasks log it shows a line like this:
08 May 2014 - 10:00:26 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
Can you give me your line.

I looked thru all the logs and could not find one that mentioned version 1.59.  When tried to re-create the problem by installing 1.59 again, it installed w/o problems.  That was several days ago, and it has run w/o issues since.

The latest version of BoincTasks (1.59 May 2014) will not install on Windows 8; it says there is an error in a language file, Butang, I believe.

Version 1.58 runs fine on Windows 8, though.