Ok. I know what you’re probably thinking… It’s now 2018, so why are you still rocking a 13″ MacBook Pro from early 2011? Well, the simple reason is that for the most part, it still does what I need it to do. It’s got a Core i7, 8GB of RAM, and an SSD drive. Another reason is that I just simply don’t have the funds to plop down on a newer model MacBook Pro. It has become clear, however, that the internal graphics card is starting to become one of its weakest components.
Earlier this year, I upgraded from MacOS Sierra 10.12.6 to High Sierra 10.13.2. Even before the update, I noticed a few websites that utilized the WebGL API said that WebGL wasn’t enabled on my browser. From what I’ve researched, it appears that WebGL was disabled in my browser because the Intel HD Graphics 3000 card isn’t supported. (See WebGL Browser Report over at https://browserleaks.com/webgl).
Continue reading “MacOS 10.13 Graphics Issue with Early 2011 MacBook Pro”
Let’s say you want to build a new VMware Fusion virtual machine using the newer UEFI firmware instead of the traditional BIOS. How is that done in VMware Fusion? Unlike VMware Workstation and ESXi, there’s no GUI-based option to choose EFI over BIOS (at least as of this writing). So, I decided to put this post together to walk you through the process. I should also point out that this needs to be done before an operating system is installed to the VM.
If you’re not sure what the differences are between UEFI and BIOS, How-To-Geek has two great articles that explain how newer UEFI firmware differs from traditional BIOS; “What Is UEFI, and How Is It Different from BIOS?” and “What You Need to Know About Using UEFI Instead of the BIOS.”
Continue reading “Creating a UEFI-Enabled VM in VMware Fusion”
In this blog post, we’ll take a look at how to setup and install a brand-new virtual machine using VMware Fusion. For this post, I’ll be installing a fresh copy of Microsoft Windows to use as an example, but these same steps should apply to just about any operating system. Let’s get started!
Continue reading “Building a New Virtual Machine in VMware Fusion”
Now, I know I said this blog was going to focus mostly on virtualization and all, but every once in a while, you stumble across a tech-related issue and a fix or workaround that’s just worth sharing. This, in my opinion, is one of those times.
Occasionally, my Mac would wake itself up from sleep mode every now and again. At first, it didn’t seem like much of an issue, but I recently noticed that it seemed to be recurring at regular intervals, almost on a schedule of sorts. So, I took to the web to see if I could figure out the issue and here’s what I found:
Check the logs using Terminal
What do these “Wake Reason” codes mean?
Ok, so my system is waking from sleep on a regular basis due to a RTC code, but what does that actually mean? Well, I found a blog post over at www.osxdaily.com that explains the codes in more detail:
- OHC: Open Host Controller (usually a USB or Firewire device). If you see OHC1 or OHC2 it is probably an external USB keyboard or mouse that has woken up the machine.
- EHC: Enhanced Host Controller is another USB interface, but can also be wireless devices and bluetooth since they are also on the USB bus of a Mac.
- USB: a USB device woke the machine up
- LID0: this is literally the lid of your MacBook portable, when you open the lid the machine wakes up from sleep
- PWRB: Power Button, which is the physical power button on your Mac
- RTC: Real Time Clock Alarm, is generally from wake-on-demand services like when you schedule sleep and wake on a Mac via the Energy Saver preference pane. It can also be from a launched setting, user applications, backups, and other scheduled events.
As you can see from my Terminal screenshot, I had a RTC code kicking off every two hours. Because of the RTC codes, I decided to check my settings in the Energy Saver system preferences. I also had a few UHC and EHC codes mixed in there, which was probably me (or someone in my family) clicking the mouse or keyboard to wake the system from sleep.
See if “Wake for network access” is set
- Open System Preferences > Energy Saver
- Uncheck: Wake for network access
See if a Schedule is set
- While still in the System Preferences > Energy Saver window, click Schedule…
- Ensure that Startup or wake is unchecked (unless, of course, you actually want your system to startup or sleep at a specific time).
As it turns out, my particular situation was indeed the result of “Wake for network access” being checked in the Energy Saver preference pane. After unchecking this setting, my system is no longer waking from sleep every two hours! Hopefully this post helps you to resolve your Mac’s “Wake from Sleep” woes. As always, thanks for stopping by!