19. Close the 10.4.3 window in VMWare («File»->»Close»). Manually edit your VMWare guest conf file (.vmx) and add the line
If you use VMWare 5.5, you can also manually change the guest OS type to
guestOS = «darwin»
20. Open and startup the 10.4.3 VMWare guest and use «mach_kernel.sse2″ as boot option if you have installed a patched kernel. This will get you into the GUI. You can also add flags like » -v» (verbose), » -s» (single user mode) etc.
That’s it. Takes about 45 minutes to complete.
* To put files to your 10.4.3 image you have two options:
o add the 10.4.3 image file as an additional HD to your 10.4.1 Vmware guest and copy under 10.4.1 to the volume (as described above).
o use e.g. TransMac to access the HFS+ volume in the VMware image directly.
* In single-user mode you have to explicitly mount the volume as writable to modify files (as explained here). Basically, just type:
mount -uw /
* To clear and force a re-caching of the kernel extensions use the «kextcache -k» command.
* To properly shutdown your system from the system console (e.g. in single-user mode), just use shutdown -h now or reboot.
* If you use VMWare and you get this popup
* VMWare workstation internal monitor error (bug 9297) *
«The guest opearting system you are running is using Physical Address
Extension (PAE) processor option. For more information about running
PAE-enabled guest operating systems, please consult
then you forgot to add the «paevm=true» line to your VMWare config file (It’s the .vmx file, usually in the same folder with your image file).
* If you use VMWare 5.5 RC1 or RC2 and your systems reboots or you get the above popup while loading, try to downgrade to VMWare 5.0.
* The guide is based on my 1st one. You might want to read it since it explains the cause of all the troubles with the Mac OS X x86 boot loader issue.
* Java Boot Patcher (not required for this guide, but might be handy in the future); see this forum posting for usage.
* For using 10.4.3, your CPU has to at least support PAE («Physical Address Extension»). Check this first, when you try to run it in native mode.