Geez this is an old Post.

But anyhow --- I will try and explain this the best I can. There have been several ways to fix this besides java. Some have rolled back display drivers to previous version or updated them.

Some have updated the drivers on there chipsets.

Some have done routine maint. ie. defrag, disk cleanup, virus scans. etc.

Some have removed and re-installed LimeWire and Java. Some have either upgraded java or used a previous version.

Some have even had to remove and re-install there operating system.

Windows seems to be a more complex operating system when trying to figure things out. It has basicly automated most functions, which the average user seem to like.

I have been running LimeWire since version 4.2.6. Have made every upgrade, and haven't had but a few problems, which were easily fixed.

I have when I was a new user especially, but as recent as a week ago, have d/l some nasty things by them being mislabeled. That is why I have all the security features I do. Call it being paranoid or whatever. I err on the side of caution.

Other than doing routine maint. I have not had a problem with LimeWire running it in English language or in Japanese Language.

I have created problems with LW, when trying to duplicate problems that other users have had, so I might be able to assist in fixing the problem. The only time I have got this machine to freeze was when I was experimenting with java and memory usage. I lowered my VM for java to much.

See it can be a wide variety of issues when dealing with a windows operating system. There is just no quick fix for this freezing problem. If the developers can't duplicate it, how can they fix it.

Just as in my case I have not had this problem, except when I intentionaly caused it.

Hope this explained the complexity of this problem.