Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About flakey

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Not Telling
  1. I've made a bit of progress. I change the machine type from an EFI-only one (Apple Mac OS X) to a BIOS one (FreeBSD). Now I can boot the VM from Nawcom's boot CD and see the Snow Leopard DVD after changing mounted media and pressing F5.
  2. Is it possible?

    A retail copy of Snow Leopard can be still be obtained inexpensively; amazon.com has it for sale around the fifty-dollar mark. Don't know if Lion Disk Maker - http://blog.gete.net/lion-diskmaker-us/ - will work with a butchered pirate copy of Snow Leopard, but it might be worth trying. I've successfully used that utility with both Lion and Mountain Lion, bought from the App Store.
  3. Okey-doke. I've got questions, so I'm asking. I've tried to install Snow Leopard inside ESXi 5.1.0 (build 799733) on an N40L Microserver, but without success. I've applied Donk's unlocker v1.1.0 to ESXi. I can see darwin.vgz in /bootbank, and /bootbank/boot.cfg contains an entry near the end for darwin.vgz. I can see /darwin.vgz loading at the server console during ESXi's boot sequence. If I uninstall the unlocker, then darwin.vgz disappears from /bootbank and the entry disappears from /bootbank/boot.cfg, and /darwin.vgz no longer appears during ESXi's boot sequence. As I write this post, however, the unlocker IS installed. I downloaded Nawcom's boot CD 3.2 (filename OSX86_ModCD-032311-151021.iso) from OSX86.net, darwin_snow.iso from iFans, and also ripped an ISO (7,771,521,024 bytes) of my retail Snow Leopard DVD. All three ISO images are sitting in /vmfs/volumes/Datastore/vmimages/OSX. Using vSphere Client 5.1.0 (build 786111) on Windows 7 I created a virtual machine with the following details: * Configuration: Custom * Name: OSX * Storage: Datastore * Virtual Machine Version: 8 * Guest Operating System: Other/Apple Mac OS X 10.6 (32-bit) * CPUs: 1 socket, 1 core per socket, 1 core total * Memory size: 1GB * Network connections: 1 (the only available adapter choice is E1000) * SCSI controller: LSI Logic Parallel * Select a disk: Create a new virtual disk * Create a disk: 40GB, Thick Provision Lazy Zeroed, Store with the virtual machine * Advanced Options: Virtual Device Node SCSI (0:0), Independent mode is NOT ticked I then edited the CD/DVD drive to use the Datastore ISO file /Datastore/vmimages/OSX/OSX86_ModCD-032311-151021.iso (step 1 of your process is to use nawcom's boot CD). If I try to boot from OSX86_ModCD-032311-151021.iso all I see is "unsuccessful." in the EFI console. Similarly, if I try to boot from darwin_snow.iso I again see "unsuccessful." in the EFI console. Lastly, if I try to boot from the Snow Leopard ISO I see the Apple logo briefly before the VM crashes and reboots and the cycle repeats until I power off the VM or unmount the ISO. If I try to press F5 nothing changes; the VM constantly reboots as long as the Snow Leopard ISO is mounted. I went back to the first post in this thread for inspiration. I wanted to avoid using USB sticks or real hard disks as my Microserver is under my desk, and it's a bit awkward to scramble down there (I'm not as young and limber as I once was). The following steps were carried out on a separate computer (Intel Core 2 Duo) running Windows 7 and VMware Workstation 9.0.1 (build 894247), which has a working Mountain Lion 10.8.2 VM. * I created a second virtual SCSI hard disk of 8GB and attached it before starting the VM. * I used Disk Utility to restore from the Snow Leopard DVD to the newly-created 8GB partition. * I downloaded Nawcom's ModUSB app from OSX86.net, as blog.nawcom.com appears to be down for the time being. I ran the ModUSB application and pointed it at the 8GB MAC OS X Install volume. * I shut down the VM and detached the 8GB virtual disk. Then, from Windows, I copied the 8GB .vmdk file (OSX10_6.vmdk) via SCP to /vmfs/volumes/Datastore/OSX on ESXi, and verified the copy using MD5 checksums in Windows and ESXi. I signed into the ESXi console and used the command vmkfstools -i /vmfs/volumes/Datastore/OSX/OSX10_6.vmdk /vmfs/volumes/Datastore/OSX/OSX10_6_Install.vmdk to convert the Workstation VMDK for use with ESXi. After the conversion was complete, I returned to the vSphere client and attached the new OSX10_6_Install.vmdk file to the OSX VM, on virtual node SCSI (0:1). I started the virtual machine and held down the Alt key to get into the EFI. I chose Boot Manager and picked the new option "EFI Virtual disk (1.0)" which now appeared at the bottom of the list. Just like with the Snow Leopard ISO image, I briefly saw the Apple log before the VM reset itself and attempted to boot again. And now I'm out of ideas. I can't boot from Nawcom's boot CD, I can't boot from darwin_snow.iso, I can't boot from the Snow Leopard ISO, and I can't boot from a (virtual) hard disk created from the Snow Leopard DVD. So where did I go wrong? What do I need to do to get the Snow Leopard installer to load inside an ESXi VM on an AMD Turion II N40L-based system?
  4. Sorry for the slow response; I only just saw your reply. I don't normally use LaunchPad, as it's a gimmick to appease those weaned on touchscreens. However, I've just tried using it and can confirm that it runs abysmally slowly on my setup as well. As for audio settings, what would you like to know?
  5. On the face of it, OS X 10.8.1 appears to have installed successfully. Sound is working without any further fiddling (I don't know if that's because I upgraded from Lion with working sound, or whether a fresh install would also be fine) and all my previous settings and applications appear - so far - to have been preserved. So far, so good...
  6. First off, apologies if I've inadvertently duplicated some information already in another post; I tried searching but couldn't find anything which mentioned this: If you're going to upgrade Lion to Mountain Lion, make sure you also update the VM guest Settings so that OS X 10.8 is selected under Options -> General. Until this morning I had a working copy of Lion running inside VMware Workstation 8 on a Windows 7 host. Then I bought Mountain Lion and tried to install it. The installer did something for a few minutes and then tried to reboot the guest. After that point, the guest would no longer boot; it would constantly drop into the EFI shell after a minute or so. I tried installing VMware 9 (and the 1.1.0 unlocker again), but that wasn't enough. I tried using Lion Disk Maker - http://blog.gete.net...n-diskmaker-us/ - on my real Mac (early-2007 Mini with a C2D upgrade) to create a couple of USB sticks, one with Lion and the other with Mountain Lion. The Lion USB stick would boot inside the VM but then gave a bland "there has been an error installing Lion - please try again" message or words to that effect (I can't remember the exact text), but the Mountain Lion USB stick wouldn't boot inside the VM at all. Then I had - I think - a brainwave. I powered off the VM guest and went into the VM's settings. On the Options tab, under General, is a control to select the type and version of the guest OS. I changed it from 10.7 to 10.8. Once I made that change, the VM guest booted successfully into the expected installer. As I write this, it's installing OS X with "About 16 minutes" remaining. Once the installation is finished, I'll see if I've got any further headaches with drivers, kexts and the like before the guest runs stably.
  7. 10.6.3 Released !

    Two questions: 1) What's the significance of those two hex strings? Are they the version numbers which trigger the kernel panic? 2) What if someone (okay, me) has been a bit hasty and applied the upgrade without doing any prep. work, and is sitting here looking at a kernel panic screen? Can it be fixed in situ or am I faced with reinstalling and paying a bit more attention next time? This machine I'm using to post this message has Windows, and my Samsung NC10 (with a dead OSX install) also has Windows, Ubuntu, and Solaris on it, if booting to an alternate OS on the same disk might help. I have a couple of USB sticks with me, but my optical media and USB DVD drive are both at home, not with me.