Microsoft really want you to upgrade. Not content with ‘accidentally‘ forcing upgrades on some Windows 7 and 8 users that hadn’t upgraded yet, apparently they have an old equipment trade in program if you buy a new PC running Windows 10. You can get upto $200 for an old laptop, but for a MacBook you can get $300. Really? Microsoft values old Macs more than old PCs. You’d have to give me far more than $300 to trade in even an older MacBook. How about buy me a new MacBook Pro, throw in the Windows Sourface for free, and then when I’m convinced I really don’t like Windows then I still have a new MBP. That sounds like an awesome deal.
Installing command line dev tools on Mac OS X 10.11
After upgrading to El Capitan (10.11) last night, I lost my XCode command line build tools. You can reinstall by doing:
xcode-select –install
and then following the prompts to download and install.
More info here.
Reminder to self: MySql on Mac OS X is installed to /usr/local/mysql[version]
Apparently it’s been a while since I started up mysqld on my Mac for development (as I’ve been using MongoDB for a lot of my local dev). Anyway, apparently also I had already written a short article over a year ago to remind myself that the default location for the Mac install of MySQL is to /usr/local/.
Reminder to self again: remember to search your previous posts to remind yourself where MySQL is installed.
Windows 10 Activation Issues on Mac Parallels 9 and 10 for Bootcamp VMs
Parallels has a neat feature to allow you to create a VM from a bare metal install of Windows in the Bootcamp partition (rather than having it installed to a file representing a virtual disk on the host). This allows you to either natively boot straight from the Bootcamp partition, or boot in a VM running on a Mac OS X host.
For Windows 8.x, this worked fine even though Windows Activation saw the bare metal install and when running in the VM as two different installs. Previously one would activate as normal, and the other would require a call to the Microsoft number to get a new activation code. Once you had activated both, then you could boot either and both would be activated from one license.
On Windows 10 however, it looks like which ever you boot second, it sees the activation code already used on one of your Windows 10 devices, and then refuses to activate. This is discussed in this Parallels forum post here. So far it seems if you leave Windows 10 booted for ‘long enough’ eventually it will activate itself? I’m having this issue, so leaving my unactivated native boot up and running for a while to see whether it activates or not.