So if you’ve read any of my past computing posts, you’ll know that I triple boot between Linux, OS X, and Windows 10 on my Macbook, and that I circumvented idiotic BootCamp to do it...I’ve always wondered why the MacBook’s performance was a little “off”. That is, until I discovered something I had somehow missed or overlooked.

Last week, I was checking my MacBook 3,1 (Late 2007, Santa Rosa) System specs. For whatever reason, a few of my games (a couple of which came out a few years BEFORE the MacBook was made) didn’t play very well despite the fact that my system specs were well above and beyond the minimum reqs. And thinking about it, Windows did run a little clunky too. My initial thought was “oh crap, maybe a RAM stick failed?”

Advertisement

I could have sworn that I had 3GB of RAM installed, but it was only indicating 2.5GB. Turns out I was wrong (there’s a 2GB paired with a 512MB). But while I was checking those specs, I discovered something alarming!!! I had somehow installed a 32-Bit Windows 10 onto a system with 64-bit hardware! How could this be?

Looking back, I now remember what happened. When I popped in my Windows installation disk a year or so ago, it warned me that my system was incompatible with that version of Windows. So I popped in a 32-bit of the same version of Windows and it installed easy peasy. From that moment forward, I had simply assumed that I had a 32-bit MacBook.

Fast forward to last week. I see Windows claiming that I had 64-bit hardware. I also Googled it and sure enough, the Santa Rosa MacBooks have 64-bit hardware, confirmed by Apple. So, I facepalmed myself, then decided to pop one of my very many 64-bit Windows recovery DVDs (I have several copies of 7, 8.1, and 10 lol) into the MacBook. It didn’t like that...I instead was greeted with a fun “Select CD ROM Boot Type:” message...a message that also seems to disable the keyboard and any external keyboards, effectively making it impossible to choose one of the two (blank) choices. Goddammit, what the hell is going on here? None of the DVDs worked, and the MacBook decided it didn’t even want to read a bootable USB with a 64-bit system on it. I thought my system was going to run this no problem?

Such isn’t true. Apparently while the computer has 64-bit hardware, Apple paired it up with an EFI that does not meet the ISO 9660 standard...effectively rendering all 64-bit OS from installing. Nearly 9 years after my MacBook (and similarly, other early Intel Macs) was released, Apple offers no 64-bit EFI support. Ugh, so what now?

Advertisement

I checked guides on the net, and let’s be honest here, they all were pretty darn hard, and all were unsuccessful.

So, I created my own and MUCH easier way to get around Apple’s idiotic EFI. Following one of the previous guides, I had used a script to modify the Windows bootloader to work with the MacBook, then created a new ISO and saved it to a DVD...a method that lots of people claimed worked. Welllllll...I wasn’t that lucky. It NEVER worked for me. Pop disc in, boots to 32-bit Windows 10 and ignores the DVD...K

Advertisement

That’s when I thought about my old friend, rEFIt. Now, I know that the boot utility doesn’t claim to fix this issue (in fact, it seems nobody has even thought to use it), but at this point, I was willing to try anything.

So...I installed rEFIt (I had it installed before, but on another HDD) and popped in my DVD...

Advertisement

Holy shite, it worked!!! And it only took me a week of cursing my Mac to accomplish!!!! :D

Advertisement

First impressions are that the computer is definitely more stable, like, it’s incredibly smooth!!! But I will need to up the RAM to make use of the 64-bits of joy.

64-Bits! YAY!

Advertisement

Have this GIF of a not-Mustang nearly crashing into people for your time. :)