Spring Cleaning and CrashPlan Woes
April 9, 2013 by Christopher Silvertooth
So I spent the entire weekend re-building my Macbook Pro since it was totally fubar’ed. Here are the things that occurred to me during this rebuild.
1. I am my own worst enemy.
2. Spending the extra time to build out a test platform is worth its weight in gold. Solves #1
3. I did find some cool new software and performed my digital spring cleaning.
A little explanation is needed here. I am my own worst enemy because I am constantly creating and testing the various scripts and other tweaks for OS X. Unfortunately, I always test these on my Macbook Pro (i.e. my companion) even though I know better. In fairness, I didn’t have any other devices to test with as I haven’t figured out how to create computers out of thin air nor grow money on trees. That said, I finally was able to procure a Mac Mini which I turned into a VMware ESX host, a topic for another day. Now that I have my ESX server up and running with multiple vm’s to test with I can stop being a guinea pig on my work laptop. So now for my CrashPlan woes….
Like I said before I completely re-built my laptop this weekend. I backed up my data with my trusty companion – Carbon Copy Cloner and then proceeded to low level format, re-install OS X, apps, etc.
So now that Java from Apple is effectively dead on OS X I didn’t bother getting the crappy Java SE 6 version from Apple but rather downloaded Java JDK 7 from Oracle. I then installed CrashPlan, which as of version 3.5.2 supports Java 7, and fired up the app. But, then, what!!! It wants me to install Java SE 6?
WTF!!! I thought they said CrashPlan worked with Java 7? Maybe I am misinterpreting the following from the CrashPlan web site.
“Oracle’s Java 7 is now fully supported as well.”
Hmmm…Well crap. So I do a bunch of research, try a few things I find on the web but all to no avail. Alas, I do find a way to launch the app until Code 42 fixes their bug.
To launch CrashPlan.app with only Java 7 installed open the terminal and type or paste the following.
If that isn’t very much fun you can create an alias by doing the following.
1. Go to your Applications folder and ctrl-click on CrashPlan. Choose “Show Package Contents”.
2. Now go to the following folder. Contents/MacOS. In that folder you will find a file called CrashPlan.
3. Ctrl-click the CrashPlan file and choose “Make Alias” and drag that to your desktop.
Voilà!!! You can now double click that alias to launch CrashPlan. Below is my screencapture showing the annoying message from a failed attempt with the CrashPlan app running in the background 🙂
Be the first to write a comment.