Recent content by tucano2000

I am glad to hear that you were able to achieve your goal. I'm having some problems with where to store the ISOs. But yes, I'll try to create some Google Drive accounts to make them available.

I don't know what actually happened during the entire process. Which ISO image of which macOS version you're trying to install, or even if I missed a step. But VMWare could also be the real cause of the problem. Perhaps trying all the steps on another machine could shed some light on what's...

Try another install. Delete this volume and try create another volume SATA... I think that the issue appears with macos volume install.

Are you using Hackintosh on a VMware virtual machine? There doesn't seem to be any error on the screen you posted. Please provide more details about the problem and what you are doing.

It is usually the incorrect number of CPU cores. Check in VMWare if it is configured according to the file you downloaded and enter the correct number of cores: macOS_Opencore_1.0.4_4_cores.vmdk put 4 cores macOS_Opencore_1.0.4_8_cores.vmdk put 8 cores macOS_Opencore_1.0.4_16_cores.vmdk put...

I was referring to the link to download the VMware patch tool to unlock, which was previously not working and has now been fixed and which is also done by running win-install.cmd in the Windows command prompt as an administrator. Another member of the channel commented about broken link and I...

Good news!!! Tahoe is now working on VMWare!!! I finally got Tahoe working on VMWare, and if you want to download and test it too, here are the necessary files: Tahoe.iso The first file is a WinRAR executable to automatically extract all files. You do not need to have WinRAR installed...

Thanks for letting me know. I fixed it in the tutorial at this link.

redo the virtual machine again from scratch without any changes to the .vmx file. I don't know if you're using a different configuration from what is written in the tutorial so I recommend that you do all the steps again correctly.

the .vmx file should remain intact and you should not modify it. These changes you made to fake the processor are only used when there is no Opencore on boot to load the system. It is precisely Opencore that makes the patch to work with AMD.

I believe so, considering that if you try Sequoia use the new vmdk that contains opencore 1.04 updated with vmhide.kext that allows you to use Apple Login Services.

yes, you need to keep opencore as the first drive or if you have the appropriate knowledge then create an EFI partition on the other drive and copy the files from the opencore EFI partition to this new partition. That way the hard drive containing opencore will no longer be needed. There are...

Which vmware disk image file are you using? What number of cpu cores have you configured? Could you post the vmx file of your virtual machine?

Can you post your .vmx file for your virtual machine? Usually this is an incorrect setting of the cpu color number for the vmdk boot image file you are using.

In Windows using VMWare or Virtualbox it is not possible to use the host graphics card because none of them have made or are making drivers to allow this support. Mainly because the emulated hardware doesn't currently support many recent graphics features and there's no intention of doing so...