I had a bit of a hic-up with the 3.51 update for Unity that I believe directly relates to my poor decision to build my Win7 Pro system on a 40 GB SSD drive.
So today is rebuilding my system day.
Which generally starts with the apprehensive backing up everything important period.
The Unity stuff is pretty easy. I’ve located most of that in it’s own section on my HDD so it’s not going to be too hard to dig it all up and make sure it’s saved to a remote drive. And it’s a good time to clean out some of the tutorial projects that I’ve completed and no longer referance.
It’s the documentation of other things, that I tend to take for granted, that’s going to be harder.
License keys, user accounts, etc.
I am horrible at saving that stuff responsibly. Generally, I can figure out user accounts through trial and error, but license keys are a horrible mess. Most of the software that I’ve purchased over the last couple of years has been digital. Office, Norton, and what have you, so it’s pretty important that I keep those licenses in a safe spot. So, of course, I have not.
Thus rebuild day is starting out with frantically trying to remember all of the my digital purchases that don’t have some sort of built in license storing mechanism (THANK YOU, btw, to Steam, Origin, and Stardock) so that I can store those keys on a file such that they don’t disappear when I format my system.
Then there’s all of my login names for crap. Thanks to Blizzard, I have a period where the email that I have used in the past had to transition to a new email. So I have some things that I log in with, or have registered an account with, the pre-Blizzard gave away my email email, and I have things that I log into with the new email account. You would not think that would not be much of a huge issue. However it does tend to be, when alot of sites have a lost password mechanic that doesn’t bother to let you know if you’re trying to get a password sent to an email that they don’t use. How hard is that, really?
Anyhow.
The issue that I had with Unity was that the update kept bombing out after everything was installed but before the MonoDevelop install completed. So while Unity seemed to work fine, MonoDevelop didn’t. No big dealio, I figured. I’d just download and install MonoDevelop on it’s own and just tell Unity to open with that install rather then the built-in one.
It’s not the same thing. I got use to the differences, but when I do have a scripting error, I can’t double click on the error message in teh log and have the highlighted line open up in MonoDevelop. I’m sure I could have figured out how to get that to work, but this amounted to the last straw regarding that SSD space issues, and today I rebuild.
I would guess that over the course of a 13 year career in IT (prefaced by 10 years or so as a hobbiest), I’ve probably re/installed an OS two hundredish times. Not even counting the thousands of times I’ve pushed out a new OS with SCCM. But still, it’s aways a little tense when I’m doing it on the system that is responsible for so much of my leasure time.
Wish me luck.
Hope to type at you again, soon.
-dr