jbreak has problems: [1] It can not be triggered by J's window interface. This means that it either requires screen real-estate even when you are not using J, or that it needs to be found when your system is heavily burdened by some infinite loop in J.
[2] It is implemented in J in such a fashion that it can interrupt itself. And since it generally needs to be used when the system is under heavy load, and since it requires spinning up several processes, and since you typically need to run it twice, this quirk comes up more than occasionally. This does not make it unusable, but I keep wishing that the service handler for J's window could have a pair of checkboxes in the title bar, or something, that together accomplish the same thing as two successful invocations of jbreak. But perhaps there's some robustness constraint that prevents that approach? -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
