The workaround is to use JEmplode

There's no need for a workaround. emplode isn't actually using that CPU-time -it's essentially sitting in a wait-loop, but it's yielding immediately at the start of each slice. However, since it's the only thing ready it immediately gets scheduled again.

If you want to run something else, it'll get timesliced properly, and the other application will get almost all of the CPU available.

The only reason that it could be a problem is if you're using a laptop, and the CPU isn't getting a chance to sleep -- thus wasting battery.

Anyway, as pointed out, it was fixed recently, but (disk corruption) problems with the XP USB driver have prevented us from releasing it more widely. The USB driver has now been fixed, and another release should be forthcoming fairly shortly, I hope.