In this episode I’ll show you how to successfully pair an Apple Wireless Magic Keyboard (first generation, MC184B/A) with Windows 10 (Version 1809). I’ve found so much conflicting information on the web, so I’m showing you what worked for me – in May 2019.
I’m using a HP Z800 Workstation here, with a no-frills Belkin F8T013 (early millennial vintage).
I love my old MacBook Pro. It does everything I want for a portable coding, writing and occasional editing device. I’ve had it since 2011 and it’s still going strong.
Apple however doesn’t want to suport it anymore. I’m stuck with macOS High Sierra, without an option to upgrade without shadowy patches. Even if I could keep up with Mojave and beyond, the hardware might just not be fast enough anymore to give me an enjoyable experience.
So I thought, perhaps I’ll put in a new hard drive that I had in another old laptop and install Windows 10 on it. Apple’s recommended way is to do all this from macOS, using their own Bootcamp setup. However, being the hacker that I am, I thought perhaps I’ll try the “Windows Only” experience.
I did this in two live streams the other night, and continued the process over the following days – and now I’ve got a (more or less working) Windows 10 installation on my MacBook Pro (early 2011 Edition). I thought I’d take some notes on how I did this step by step, and give you my opinions if this was an adventure worth undertaking.
My MacBook Pro (2011) recently developed an issue after I had tried upgrading it to the latest version of High Sierra. Some security patch came along, and after bugging me for several weeks, I finally gave in and installed it.
Sadly, after macOS tried to restart I got a message like this:
I tried restarting several times, but without luck. The message varies slightly at times, often accompanied by an error log and a more explicit message that something went wrong, but not with simple solutions on how to rectify the situation.
What worked for me to a certain extent was to start macOS with the ALT key held down, which would give me a selection of the boot drive. There are usually two drives: the “boot partition” and the “regular drive”. Clicking the latter will boot macOS without applying the update, and everything went fine again. Booting into the former would try to apply the updates, but since it failed every time, I either had to remove this behaviour or fix the underlying problem.
I looked into it and found these tips on how to proceed:
Boot with SHIFT (Safe Mode)
According to Apple’s Support Website, Safe mode can be initiated by holding down the SHIFT key while booting. This will take absolutely forever, during which time your Mac will do the following:
Verifies your startup disk and attempts to repair directory issues, if needed
Loads only required kernel extensions
Prevents startup items and login items from opening automatically
Disables user-installed fonts
Deletes font caches, kernel cache, and other system cache files
On large drives, this does take a while. Mine is a 500GB SSD and it took my MacBook Pro several hours to do this. Sadly, without fixing the problem mentioned above.
Boot with CMD+R
Another nifty trick is to bring up the Disk Repair Tool. Start your Mac and hold down CMD+R until you see the Apple Logo. At that point you can let go of those keys. This will launch something called macOS Utilities. Note that your trackpad may behave slightly differently that you’re used to (for example, tap to click will be disabled), that’s just because none of your configuration preferences have been loaded. It’s all default, and booted from another portion of your hard drive.
Once everything has loaded, select Disk Utility. Run the First Aid option and see what happens. This will attempt to repair your disk by looking through every sector and fix any mishaps that may have been caused by files not closing properly. It will either tell you that everything is fine, or that it detected issues and how fixable they were.
Check Incompatible Login Items
Another item on the agenda to check is what login items are selected. Those are processes that start after your Mac has booted into macOS. Examples include cloud service sync services like Dropbox or Creative Cloud, or things like Discord and Spotify. I’m a big believer of starting those myself if and when I need them, but over-eager installers like to sneak them in there sometimes. Some of those items may not be compatible anymore after a software update and hence interfere with both the update and the new version of macOS.
To check what’s being started with your Mac, head over to System Preferences – Users & Groups – Current User – Login Items.
Click the little lock icon at the bottom left, then select what you dislike from the list and hit the minus button below the list. This will remove said login item and – hopefully – make your Mac start as it’s supposed to.
I’m still in the middle of my investigation and have a few more items to check, but I’ll report back with what worked well for me, and what else I find. Stay tuned 🙂
Note that for either profile to work on another system, make sure all applications and their respective settings are also replicated. For example, if you’re switching OBS Studio scenes with your Stream Deck, both OBS Studio and the scenes/collections need to be configured the same was as before.
Networking sucks, particularly when Windows is involved. I’m not actually sure why, but I guess it has to do with the fact that deep down, manufacturers and software developer really don’t want us to connect arbitrary devices to suit our needs. It’s just a fact of technological survival I guess.
I’ve recently re-installed Windows on my desktop, and now my Mac cannot connect to Windows anymore. I had to set this up again from scratch. While I remember how to do it, here’s how it (once) worked for me:
Before submitting ZIP files to various third parties, I often have the need to ether remove superfluous files from my archives. Until today I’ve never had the need to add a file to such archives. Had that happened in the past, I would have probably just deleted the whole archive and crated a new one from scratch.
Today I felt adventurous and researched a way to add files to existing ZIP files and found a (not-so-obvious) solution to this puzzle, using the -r switch.
Let me show you how it works:
zip-rv YourArchive.zip NewFile.txt
According to the man page, the r switch actually replaces an existing file in the archive, so this command can be used to update files in the ZIP file too. I’ve added the v switch for convenience (it means “verbose” and can be omitted.
When ZIP up directories, particularly on macOS, some files may find their way into our ZIP archives that were never meant to be there. I’m thinking of those pesky .DS_Store and __MACOSX files, maybe even .htaccess files. For *nix based systems, * really means “everything”.
The ZIP command line tool let us remove such unwanted files from an existing archive. Here’s how:
zip-dyour-archive.zip file1 file2
The -d switch tells ZIP to hunt for and delete the unwanted files. Files whose names contain spaces can be defined in “regular quotes”, and the * asterisk can be used as usual.
For example, to remove all DS_Store files and __MACOSX files, we can use this:
To verify that such idiosyncrasies have indeed been removed from a ZIP archive before we release it into the wide, we can check with the UNZIP utility:
This will simply list the contents of your-archive.zip without actually extracting it.
Sometimes it’s easy to delete a ZIP file and create a new one – say you’ve forgotten to include a file. Just drag it into the folder to be ZIPped up and start again.
However, the clever little ZIP command line tool has a built-in ability to simply add a file to an existing archive without us having to do any manual grunt work. That can come in handy when we no longer have access to existing unZIPped content.
We can even add entire directories this way too, like so:
This will recursively add all files (indulging hidden and annoying ones) to our file.
Note that ZIP accomplishes this by temporarily extracting all files before creating a new archive for is (while deleting our original file). So in essence, the tools is doing what we’d do manually, just more conveniently and in the background without bothering us.
We all love Emojis, and it’s so super easy to insert them from an iOS keyboard. I do this frequently in messages. It stands to reason that it should be just as simple to do this on laptops and desktop Macs too – but how? Isn’t there some kind of shortcut we can use?
Well yes there is – I just keep forgetting which one it is ? so here it is:
CTRL + CMD (OPTION) + SPACE
This handy combination brings up an Emoji Picker. Find the icon you like, click on it, and the dialogue automatically closes again after it inserts your Emoji.
For a while now I’ve seen my poor Spotlight Search disappear on all my Macs disappear after typing only two or three letters. This has never been a problem since I’ve been using macOS. I have 4 systems in total, running Sierra and High Sierra, and all of them exhibit this problem.
However, my wife’s MacBook Air is still running Mavericks and – not having been updated for a while – is NOT experiencing this issue. So what’s going on there?
After some digging, I am not the only user who has an issue with Spotlight Search. Some suggest we all have to re-index Spotlight (which does take a while, multiplied by all the computers you’re using), but they report that the issue will come back sooner or later.
The most efficient way to make Spotlight Search operational again is to simply disable one of the items it’s searching when we use it – namely the Bookmarks and History option.
To access the above menu, head over to the Apple Icon and select System Preferences. From here, either click the Spotlight Logo (top right corner) or search for Spotlight. Un-tick the second box from the top, close the dialogue and – voila – Spotlight is working again!!
This thread on the Apple Forums suggests that the culprit is Safari 12 (I’m using 12.0.1 at the time of writing). Disabling Bookmarks and History means Spotlight is not accessing Safari’s (changed / faulty / updated / whatever) database and seems to work fine as a result.
Worked great for me – I hope it’ll work for you just as well 🙂