Diah

Hmm, well if you've ruled out Java then I'm probably not qualified to help (java's my only non-food-related skill). My only suggestion is to post a log from the most recent launcher (looks like you backed up to 1.0.2.0), and using Java 6. That'd help the guys smarter than me to rule out the big things first. If it helps, when I was fiddling with it I renamed my techniclauncher folder each time so I'd have fresh logs and bins.

Looks like you're using Java 7, which is known to be involved in the problem. The most often recommended solution is to use Java 6. You can easily downgrade Java, but that's really the nuclear option, since you lose the benefits of having Java 7 around. Another option is to use a script to switch Java on the fly, but it's a little involved. Since you're Terminal-averse, the ideal GUI solution would be to track down a copy of the now-defunct Java Preferences application (try googling it). That'd let you switch between Java 6 and 7 using convenient tick-boxes.

It's been pointed out to me that the script I posted above doesn't work if technic-launcher.jar is in a folder with certain characters in the filename (like spaces). I've updated the post above with a version that should. Good thinking, I added this too.

You can force the use of Java 6 just for the Technic Launcher, if you have it installed. I use the following script (saved as a .command file) to get it running: #!/bin/zsh cd "${0:h}" export JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home java -jar ./technic-launcher.jar Paste the script into a plain text document (in Textedit, use shift-command-T to enter plain text mode) and save it with the extension ".command". Put it in the same folder as technic-launcher.jar. You need to mark it as executable first using Terminal: chmod +x /path/to/script.command Then you can double-click it to start the Launcher. So far, using Java 6 is the only solution that's worked for me.