Currently Being ModeratedApr 27, 2011 4:26 PM (in response to axe_grinder68)Re: RE: Java Exception error
Tne first thing I'd suggest trying is to re-install Java for OSX 10.6.7. Here's a direct link to Apple's page for that installer: http://support.apple.com/kb/DL1360
Next, after installing Java, I'd open up Disk Utility (it's located in Applications/Utilities). Select your local HD on the left and click "Repair Disk Permissions" on the bottom.
Restart your Mac when finished. Then, try launching Line 6 Edit 3.04 again when it boots back up and let us know your results.
Currently Being ModeratedApr 29, 2011 11:14 AM (in response to axe_grinder68)Re: RE: Java Exception error
Is there a chance that you used Apple/Mac OSX "Time Machine" or the "Mac Migration Utility" program to transfer files from a different Mac computer installation? We've found (and other software manufacturers have mentioned this, too) that the Migration Utility scheme doesn't always provide a good solution, particularly with OSX-related filesystem permissions. However, I'm not sure if you've used this Mac OSX feature, but it definitely could be the root cause of your specific Mac's issue.
I installed Line 6 Edit on our department's MacBook Pro with 10.6.7. We actually just wiped the hard drive and installed a clean copy of OSX 10.6.7 last week on it.
Safari is on this machine, as is Firefox.
Line 6 Edit for Mac OSX 3.04 downloaded and installed. When I ran it, it got me to a setup screen to Add a Device. I did not experience any Java related error messages.
Just for extra measure, I installed Line 6 Edit 3.04 on my personal MacBook Pro at home last night. It opened up and I connected a PODxt Live successfully and started editing patches; no java related issues when trying to run the program.
The Line 6 Edit 3.04 program works fine. I really do believe you have a filesystem/OSX library dependent issue. There's probably a file that OSX is looking for when launching our software that isn't present on your particular installation of OSX 10.6.7, and OSX is throwing you that message.