![]() This caused other problems with VirtualBox 4.0.x which seem to be worked around by booting into the 32-bit kernel. Also, the new MacBook Pros boot into a 64-bit kernel - the older ones booted into a 32-bit kernel (even though they had 64-bit CPUs, and either way allows 64-bit apps). The processor is listed in About This Mac under the Apple menu.ĮDIT TWO: Perhaps VirtualBox's CPU detection code incorrectly identifies the Sandy Bridge (2nd generation) i7. To confuse things further, after "Core 2", Intel dropped the "2" and used "i"-something: This also means this Mac cannot run OS X Lion (a requirement of the current beta which seems likely to persist to release). VirtualBox does allow 64-bit guests on hosts running a 32-bit OS, but still requires a 64-bit processor ( with hardware virtualization support). Mac OS X is not Linux - they are cousins.ĮDIT: Apparently you have one of the early Intel Macs, which had "Core Solo" and "Core Duo" - not "Core 2 Solo" and "Core 2 Duo" - processors. Navigate to Finder and locate the restored drive and goto folder System > Installation and there you will see Packages. Format the USB drive as Mac OS Extended (Journaled). Plug your 8gb USB drive and Open Disk Utility. Unix is a common ancestor of both Mac OS X and Linux. In the Terminal, Type the following: open /Volumes/Mac\ OS \ X\ Install\ ESD/BaseSystem.dmg. (Intel tried an earlier 64-bit processor named Itanium, but it didn't catch on, so they adopted AMD's approach.) When we execute this, it will modify some VMware binary files and unlock VMware application to support macOS guest versions on Windows host.Ĭlose the VMware program completely, then open the command prompt as administrator and execute the windows.bat file (or, even you can right-click on the windows.Longer answer: "AMD64" applies to both AMD and Intel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |