Information for veteran users of wmseti:
=======================================
Changes since wmseti 0.3.4:
---------------------
Dan Scott has been named project maintainer because Paul is busy working
on his academic life. wmseti 0.3.6 now supports the SETI@home client 3.x,
and is even compatible with SETI@home client 2.x (not that anyone is running
it anymore).

Changes since version 0.3.0a:
----------------------------
Implemented a multiple level debugging system. Level 0 means no
debugging, level 1 information, level 2 implements more information
and level 3 produces loads of information. Information presentation
needs to be finetuned though. WARNING level 3 really produces hellish
amounts of data!

Changes since version 0.3.0:
---------------------------
A very quick and even dirtier patch to enable compatibility with the 
SETI@home 2.0 clients. This patch distroys all compatibility with the old 
SETI@home 1.x clients, so DON'T USE THIS VERSION OF WMSETI IF YOU'RE
STILL USING SETI@home 1.x!!!

Changes since version 0.2.6:
---------------------------
If the keyword flashpid is off in wmsetirc (i.e., flashpid has a value of 0),
then clicking with the middle mousebutton will flash the PID of the 
SETI@home client briefly on line 1 of the wmseti dockapp. The duration of 
this flash can be found as PID_SPAN in global.h. The value there is tested on
a Cyrix 120+ with 128 MB mem and works quite nice for this machine :)

If you want stripped binaries, you can do the installation procedure with
"make install-strip". If you're unable to do this, because you don't have the
root password, you can try "strip wmseti".

Changes since version 0.2.2:
---------------------------
In wmsetirc you can now add the keyword "flashpid". This keyword accepts
a value of 0 or 1 and only has functionality if the title "wmseti" is
being displayed somewhere in the dockapp. Because the flashrate is dependant
on a number of redrawing cycles, which take a time period dependant on machine 
characteristics, the exact value might need some fidgeting. If the value of 100
for FLASH_SPAN in "global.h" is not satisfactory, you can set set FLASH_SPAN 
to another value and recompile wmseti. The default of 100 is tested on a 
Cyrix 120+ with 128mb mem and works quite nice for that machine.
