as i also said some months ago,
this same bug exists not only with mxj-files but also at loading
another thing, i found out in the meanwhile is, that the problem was
fixed on one machine after switching from runtime to developer-max.
Hi Charlie - just wanted to let you know that I was able to reproduce
your problems by uninstalling Jitter (which initializes Java at
program startup.) Thanks for your persistence in reporting this weird