I've had intermittent problems with this, too.
In my case, it occurs during lengthy sessions without a reboot,
and is cured by a reboot, so I theorize there is a memory leak
somewhere in the software.

For those not familiar with the term, a "memory leak" occurs
when a program asks the system for permission to use some bit
of dynamically-allocated memory, then "forgets" to give it back.

It's a programming error, and quite common, even in released
software these days.  Rebooting, of course, resets everything,
effectively giving back all the dynamically-allocated memory.

Sometimes, just terminating the offending program and restarting
it will do the same thing, but often times it will not, whereas
a reboot is always successful.

Hope it helps,
Henry Bibb
Windows sufferer

                         PCSOFT's List Owner's:
                      Bob Wright<[log in to unmask]>
                       Drew Dunn<[log in to unmask]>