I received a report about a failed logging process on a Samba network share. This problem is related to the new code that converts old log files to the new format. Check out the Help forum on the project page for a workaround.

This is a good opportunity to do a bit advertising for the services offered at the SourceForge project page. At the left you see a list with several links. Their purpose are explained here:

	Public Forums: There are two forums, one for general discussions and feature requests, the other for general help. Currently, you need to be a member of the SourceForge developer community to post messages (registration and all services are free).
	Bug Tracking: Report any bugs you find in Ksetiwatch here.
	Tech Support: If you need specific help (maybe in case you have problems installing Ksetiwatch on your computer) use this service. AFAIK, you don't need to be a SourceForge member for tech support.
	Doc Manager: If you like to have something added to the documentation of Ksetiwatch, post your contribution here.
	Patch Manager: If you like to contribute via patches (bug fixes, new features, etc.), post it here. Each patch will be reviewed, and merged into the source code if it is useful.
	Task Manager: This service allows to coordinate tasks between different developers. Since I'm currently the only developer, there's not much need for it at the moment.
	CVS Repository: Here you can view all changes to the source code, and check out a working copy of the source code. There's no guarantee, however, that the code compiles or works properly.
	Anonymous FTP: Anonymous FTP space. Not used right now. I might use it for the release of unofficial versions.

I had some problems when switching from the latest beta of KDE2 to RC2. Every time I clicked on the dock icon, Ksetiwatch crashed. After recompiling the package, everything is working normally again. I'm not sure whether this is related to any binary incompatibility between the KDE versions, or my installation of KDE is crappy. If you found any similar irregularities, please drop me a note.

The updated KDE-2 version is now available. Ksetiwatch 2.0.1 now works happily together with the S@h 3.0 client. Here is the complete list of changes:

• Ksetiwatch didn't display any data when using the 3.0 client. This bug appeared because the author of this program had some problems counting higher than two. After taking an extra math lesson, this bug could easily be fixed. :-)

• I added two more columns to the Analysis tab; one for the `Strongest Pulse' and the other for the `Strongest Triplet'.

• When logging a completed WU, Ksetiwatch automatically converts the log file (SETILog.csv) into an extended format, so that pulse and triplet data can be logged as well. The old log file will be written to SETILog.old. Note that this feature has not been tested with network directories, so be prepared for unexpected behaviour.

• The Completed Work Units tab now displays the pulse and triplet data for all the logged WUs in the usual fashion.

• 3.0 clients require more floating point operations (2.65 TeraFlops on average) to complete a work unit. I adjusted the MFlops calculation to this value, if a 3.0 client is used. However, the total number of Flops depends on the work unit, so a more precise calculation needs to be done in the future.

• I finally figured out how to draw grid lines in list views. This should improve readability, especially for complex lists. If you don't like it you can switch it off in the Options tab.

• As long as no Gaussian (pulse, triplet) is found, the corresponding entries in the Analysis and Completed WU lists remain empty (again for better readability).

• The tooltip of the dock icon didn't show up reliably. While the origin of this problem seems to be in the KDE libs, I managed to apply a workaround that (mostly) works.

Here comes a service release for the KDE-1.1.x version of Ksetiwatch. Version 0.5.4 offers now basic support for the SETI@home 3.0 client. Pulse and triplet data are displayed in the 'Analysis' tab. When logging a completed WU, Ksetiwatch automatically converts the log file (SETILog.csv) into an extended format, so that pulse and triplet data can be logged as well. The old log file will be written to SETILog.old. Note that this feature has not been tested with network directories, so be prepared for unexpected behaviour. Although all information is logged, the 'Completed WU' tab does not display pulse and triplet data. This feature will exclusively be implemented in the KDE-2 version, which should follow soon.

Major changes ahead. Version 3 of the SETI@home client will be officially available in the near future. Unfortunately, the current versions of Ksetiwatch don't work quite well with the new client. While this specific problem has already been fixed, I'm working hard to add at least basic support for the new features in the S@h client. I think a new version will be ready in the next days. In the mean time, experienced users are encouraged to check out an updated working copy from the CVS repository.

Enough testing. Ksetiwatch is ready for KDE2. No new features, but great care has been taken to ensure that everything is functioning as expected. The only noticeable difference is that Gaussian graphs are now saved in the PNG file format, thereby saving precious space on your harddisk. As you can see, the version number mysteriously jumped to 2.0.0. This is to make a clear distinction to the previous releases for KDE 1.1.x, and -as a side effect- to be in line with KDE 2.x. Needless to say that this version does not work with KDE 1.1.x any more.

In case you need help, or you have comments or feature requests, I'd like to direct you to the discussion forums on the Ksetiwatch project page (see the links at the left). If you find a bug, please use the bug tracker which can also be found on the project page. Otherwise, keep on crunching...