Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
amot

Need help OS X 10.8 on VMWare 9

8 posts in this topic

Recommended Posts

Morning Guys,

 

I have VMware.Workstation.9.0.1 (i used unlock-all-v110 to get Apple OSX to show up on VMWare9) and i am trying to install OS X 10.8 Mountain Lion Retail VMware Image on it but i keep running into...

 

"EFI VMware Virtual IDE CDROM Drive (IDE 1:0) ... unsuccessful"

 

How do I fix this? let me know if you need more info from me.

Share this post


Link to post
Share on other sites
Advertisement

Read again then...

 

I am new to all this so none of it makes sense to me.... Blah, thanks for trying to help though. Wish someone can make it much easier to understand.

Share this post


Link to post
Share on other sites

I am new to all this so none of it makes sense to me.... Blah, thanks for trying to help though. Wish someone can make it much easier to understand.

 

No silver platter, you need to invest a bit of your own time to learn.

Which bit is too difficult to understand:

 

One CDROM is IDE & the second one is SCSI Legacy emulation

 

Boot to EFI Shell, change to IDE CDROM, run boot -v npci=0x2000

 

VM will boot from IDE, but then mount SCSI CDROM & carry on with installation

Share this post


Link to post
Share on other sites

The ISO image file contains a pre-built VM for vmWare - simply mount it in your host OS and drag-and-drop everything to where you want it.

 

In the example I am giving, I already have Windows x64 (it can be Vista, 7, or 8) and vmWare Workstation (8.x or 9.x) installed and unlocked (the ISO image also includes the vmWare Workstation unlocker - both 8.x and 9.x use the same unlocker script). In my case, I dragged and dropped the pre-built VM to C:/Users/User Name/My Documents/Virtual Machines. In vmWare, I selected File->Open->C:/Users/User Name/My Documents/Virtual Machines/OS X Mountain Lion/OS X Mountain Lion.vmx.

 

The *only* changes you should need to make before starting the VM are to the RAM and number of CPU cores. The RAM should be set to no more than half your physical RAM (2048k if you have 4 GB) - the number of CPU cores should match your CPU (2 for dual-core CPUs, 4 for quad-core, etc.; since I have a Q6600, I selected 4 - the same setting would apply to any i5 or i7). Once you have those settings in place, start your VM. The rest of the settings are the same as starting any real Mac or "Hack".

 

It works just fine - I am posting this from the VM (Windows 8 Pro host/OS X 10.8.3 guest).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • Hello! In my signature system the program does not show the life of the hard drives but only that of the ssd.   High Sierra 10.13.4
    • hello   try this one   DSDT.aml.zip   for graphics and backlight are needed ssdt files   good hack
    • Non ti ho messo io quelle impostazioni I sul config.. Poi aggiorna i kext.. 
    • So, i am thinking about pubblishing the stable release of tinu 2.0, just with a few minor chenges from the last pre-release, and to focus my work on the next one, i have just chenged a couple of UI things for the stable release and add a warning message if you try to use a time machine disk as a target drive to create the macOS install media, for the release that will come after the stable 2.0 release (and maybe also after a bug fix release for the 2.0 if needed) i am trying to use the system apis to manage the tasks which needs special priviladges to be executed, instead of the "sudo" based system which i am using now, this will make the application more secure and reliable, and also you will have to do the authentication only one time, when creating an install media, and using this system maybe i can also pubblish the application on the app store (obviusly just a limited version for mac users, but a version with all the features unlocked will be always available outside the app store and will have all the hackintosh-friendly features as well). But to do that i need to re-write a large amount of code into the app, because all the tasks which needs special permitions needs to be re-implemented differently, so that's why i do not want to use this in the 2.0 release, so because i am going to finish with tinu 2.0 tell me every complain or problem you are having with the latest pre-release or the latest release of tinu, so i can work on that before releaseing the stable 2.0 version
    • here it is,
      https://drive.google.com/file/d/1_FwNFczk4CdIfiIQ-T1pX_LY1takRuny/view?usp=sharing


×