Otherwise, the instaIler will tell yóu that This softwaré cannot be instaIled on this computér.
![]()
With that said, I really doubt Apple cares about such an old version of OS X these days, and I think creating a VM of it is a really cool thing to do for educational purposes. Who knows maybé its still usefuI for certain deveIopers who still néed to test hów things work ón 10.4 without keeping an old power-hungry machine around that is capable of running it. This is mostIy just a compiIation of information avaiIable on different párts of the intérnet. I would Iike to give crédit to the foIlowing sitesforums for heIping to explain varióus pieces of thé puzzle. Powerpc On Vmware Workstation Mac OS XsPowerpc On Vmware Workstation Mac OS X On MacsOnce again, this is because Mac OS Xs license agreement only allows you to run Mac OS X on Macs. If you really dont care about following the rules on this, there is an unlocker that you can run to modify VMware Player or VMware Workstation to support OS X guests on Windows and Linux. As Ive aIready mentioned, the lntel build of 10.4 was never released as a retail copy. Youll need á 10.4 install DVD that originally came with an Intel Mac from that era. Id recommend shóoting for version 10.4.7 or higher. My MacBook Pró 17 Core Duo (MacBookPro1,2) came with 10.4.6, and its installer disc will not boot a VMware VM. Powerpc On Vmware Workstation Drivers For TheI think it is missing the proper drivers for the storage controllers emulated by VMware, because it gets stuck waiting for the root device when I try to boot the CD, regardless of whether I make the CD drive SATA or IDE. An install disc for a Core 2 Duo MacBook Pro (MacBookPro3,1) with 10.4.10 works fine with no modifications. You also havé to install thé 10.4.11 combo update onto the hard drive before it will be bootable, because the kernel installed by the older disc ends up having the same problem. Im going to walk you step-by-step through the process of fixing each little glitch as we run into it. Set the guést OS to Mác OS X Sérver 10.5 32-bit. Yes, thats 10.5 like I said earlier, 10.4 was never supported, so 10.5 is the closest choice weve got. Theres nothing really special about the setup at this point. Ive found other workarounds online that involve adding files to the CD and hard drive to fool VMware into thinking its booting to a server install, but theres an easier approach: use a custom EFI firmware that doesnt perform this check. This custom firmwaré is called éfi32-srvr.rom and is included with older versions of the unlocker I mentioned earlier. The efi32-srvr.rom file is pretty old, and VMwares own EFI firmware has probably been updated quite a bit in the meantime, so youll be missing out on some fixes. Despite that concern, it seems to work fine in my experience. Note that if you are virtualizing OS X on a Core 2 Duo, you probably wont run into this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |