Jump to content


  • Content count

  • Joined

  • Last visited

About wurst001

  • Rank
    InsanelyMac Protégé
  1. Status of Unlocker 2.0

    @Donk: thanks for your efforts. It's good that you're trying to unlock Snow Leopard, as I need it as a build machine.
  2. If you manage to somehow package the unlocker such that it doesn't require an external python on windows, then I have no problem with python at all. I assume, the Linux version will come as python source?
  3. I'm using Linux most of the time. Python is installed and wouldn't be a problem. On Windows however, I usually don't have python and installing it for something tiny as the unlocker would be a major pain in the butt. Well, I usually do have cygwin installed, so if the unlocker would run under cygwin that would be a plus (cygwin doesn't come with python by default, however).
  4. So I guess VMWare Player 7 isn't working either ... (It has been released yesterday)
  5. And are you sure that the bootable image was created successfully? It sounds like the packages have not been copied over.
  6. I can't see your problem. What happens if you chose "Reinstall OS X" from the list and click continue? Can you post a screenshot? Also, you don't need to do a sudo.
  7. The new version doesn't seem to be able to make DVD images anymore, which is a pity. As I wrote, the InstallESD.dmg used to be a bootable dmg. Not anymore. So the question is why they made it more complicated is pretty legitimate! To save space maybe? I wasn't able to get a copy of that tool, so I couldn't try it. Is it capable of creating bootable DVDs?
  8. OK, Donk's script is very similar. The way Don't script computes the size of the dmg looks a bit funny. However, thanks for the link.
  9. For some reason, Apple decided that the InstallESD.dmg that comes with the Mavericks Install as downloaded from the App Store shouldn't be a bootable DVD image anymore. In earlier times, all you needed to do was to convert that InstallESD.dmg into an ISO and you could install OS X in VMWare from scratch. Starting with OS X Mavericks, you need to do a more complicated procesdure. Find a shell script below. It's an enhanced version of the script found at http://forums.appleinsider.com/t/159955/howto-create-bootable-mavericks-iso #!/bin/bash ESD=$1 TMP=$2 if [ -z "$ESD" ] || [ -z "$TMP" ]; then echo usage: "'$0' /path/to/esd /path/to/tmpdir" exit 1 fi if ! [ -e "$ESD" ]; then echo "file '$ESD' does not exist" exit 1 fi if ! [ -e "$TMP" ]; then echo "dir '$TMP' does not exist" exit 1 fi MPAPP=/Volumes/install_app MPIMG=/Volumes/install_img IMGSPARSE=$TMP/install.sparseimage IMGDVD=$TMP/install.cdr detach_all() { if [ -d "$MPAPP" ]; then hdiutil detach "$MPAPP"; fi if [ -d "$MPIMG" ]; then hdiutil detach "$MPIMG"; fi } exit_all() { echo +++ Command returned with error, aborting ... exit 2 } trap detach_all EXIT trap exit_all ERR echo +++ Trying to unmount anything from previous run detach_all echo +++ Mount the installer image hdiutil attach "$ESD" -noverify -nobrowse -readonly -mountpoint "$MPAPP" echo +++ Convert the boot image to a sparse bundle rm -f "$IMGSPARSE" hdiutil convert "$MPAPP"/BaseSystem.dmg -format UDSP -o "$IMGSPARSE" echo +++ Increase the sparse bundle capacity to accommodate the packages hdiutil resize -size 6g "$IMGSPARSE" echo +++ Mount the sparse bundle for package addition hdiutil attach "$IMGSPARSE" -noverify -nobrowse -readwrite -mountpoint "$MPIMG" echo +++ Remove Package link and replace with actual files rm -f "$MPIMG"/System/Installation/Packages cp -rp "$MPAPP"/Packages "$MPIMG"/System/Installation/ echo +++ Unmount the installer image hdiutil detach "$MPAPP" echo +++ Unmount the sparse bundle hdiutil detach "$MPIMG" echo +++ Resize the partition in the sparse bundle to remove any free space hdiutil resize -sectors min "$IMGSPARSE" echo +++ Convert the sparse bundle to ISO/CD master rm -f "$IMGDVD" hdiutil convert "$IMGSPARSE" -format UDTO -o "$IMGDVD" echo +++ Remove the sparse bundle rm "$IMGSPARSE" echo "Done" echo "Find your DVD at '$IMGDVD'" The first parameter to the script is the path to InstallESD.dmg which is part of the Mavericks Installer if you downloaded it from the App Store. The second parameter is the path to a directory (such as /tmp) with at least 16GB space.
  10. Yes of course it's all virtualized. But even in virtualization, it is an advantage if the guest OS can send multiple I/O request to the virtual harddisk (and thus to the host OS) without waiting for the previous ones to complete. This feature is available only with SATA and maybe SCSI - but not IDE. I'm pretty sure there is an equivalent of the queue depth for SCSI drives. But I couldn't find out if it's larger or smaller than the one for the SATA drives. Since SATA is the new default, I hoped SATA would be the best choice performance wise. Removing anything ide.* related from the VMX file doesn't really solve the problem. The IDE controller still appears in lspci. Nevermind, it's not a big issue.
  11. I upgraded to VMWare Player 6.0, unlocked with unlocker 1.2.0. I recreated the virtual machines and added the images of the SCSI harddisk as SATA disks (SATA is now the default for OS X guests). OS X booted without a hassle. Then I edited the VMX files and disabled the SCSI controller. The virtual SATA harddisks have a queue depth of 32. I couldn't find anything out about the queue depth of the SCSI disks. Also, I wasn't able to disable the IDE controller. So far all my OS X guests run very solid.
  12. I just discovered, that there's no problem with using DMG images directly without converting them to ISO first. This is at least true for vmware player 5.0.2 on Linux. There's just one small issue with the GUI, namely that the file chooser doesn't show *.dmg files by default. So if the unlocker could enable that as well, that would be perfect!
  13. It's good to hear you're working on it. Enjoy your holiday.
  14. ESXi 5 Mac OS X Unlocker

    VMWare has started releasing Fusion 6.0, Player 6.0, etc. Unlocker 1.1.1 seems to works somewhat - however, patching vmwarebase.dll fails since no matches are found.