>Once upon a time, there was a Finnish guy who whined about Applixware
>being real slow on his NetBSD machine.  This guy is back!

This was a while ago .... but didn't we determine that the _root_
problem was that Applixware caused the X server to do a whole lot of
mallocs and free's, and that eventually caused the memory allocator
to take forever?  That's my hazy memory on the subject.

If this is still the case, I would suggest:

- Try using an X protocol analyzer to see what Applixware is doing.
  Do I have one?  No. Geez, someone should have _written_ one by now.
  Does anyone know of such a thing?
- Profile the X server to figure out what it is doing.
- Once you've done one of those things, generate a test program
  that reproduces this behavior (not an X program, I think the root
  cause is far underneath).

I know that in my case, I would like to help you ... but if the only
way to reproduce the problem is "run Applix", well, it makes it rather
difficult to reproduce it myself.

--Ken