Zum Hauptinhalt wechseln
Hilfe

Aktuelle Version von: S W ,

Text:

TonyMacX86[https://www.tonymacx86.com/|TonyMacX86] is a great resource and other solutions.
TonyMacX86[https://www.tonymacx86.com/|TonyMacX86] is a great resource and other solutions.
They like to use "multibeast" instead of Clover.
 
In a VM, everything is virtualized into signals or files in respect to physical hardware and signals on a tangible computer. In a physical machine, a hard drive is a 3.5" or 2.5" rectangular box with platters (or SSD) inside.
 
On Virtualbox, a .vmdk is the file that represents a physical hard drive, since nothing is physical.
 
It sounds like you straight downloaded a premade 'hackintosh' or virualbox VM image for a Mac.
 
You may in that case need to edit the VM and tweak various settings in the VM settings to make it work better in respect to your Windows HOST computer (i.e. increase RAM?).
 
On both Mac and PCs (modern), the boot order is the following:
 
• user turns on the computer providing power
 
• BIOS (or EFI) checks for security, hardware confirmation, and starts to load the OS from the hard drive (or USB or CD/DVD)
 
The only difference in PC or a MAC is the EFI. Mac's being Apple, they are particular in the instructions and look for specific things. What Clover EFI does is mimick what Apple wants to see.
 
So simply put, the boot order on the VM is the following:
 
• user turns on the VM
 
• BIOS/EFI in the VM looks for boot device
 
• Boot device has Clover --> Clover fakes a Mac --> OS X starts thinking its a mac
 
I'm not sure how your .vmdk is set up or where it came from so I can't really help you from that step.
 
What I can tell you, is if you do have a working Mac with installers of anything except High Sierra (haven't figured that one out yet because of a mandatory FW upgrade), you can create your own VM and start from scratch and you can figure out and learn what exactly is going on.
 
• Create an installer via normal OS X instructions on the Mac
 
• Follow this to make it PC bootable https://www.tonymacx86.com/threads/test-drive-how-to-create-a-clover-usb.127134/
 
• With this you should be able to create a blank VM and install OS X from scratch like a normal Mac

Status:

open

Bearbeitet von: S W ,

Text:

TonyMacX86 is a great resource and other solutions.
They like to use "multibeast" instead of Clover.
 
In a VM, everything is virtualized into signals or files in respect to physical hardware and signals on a tangible computer. In a physical machine, a hard drive is a 3.5" or 2.5" rectangular box with platters (or SSD) inside.
 
On Virtualbox, a .vmdk is the file that represents a physical hard drive, since nothing is physical.
 
It sounds like you straight downloaded a premade 'hackintosh' or virualbox VM image for a Mac.
 
You may in that case need to edit the VM and tweak various settings in the VM settings to make it work better in respect to your Windows HOST computer (i.e. increase RAM?).
 
On both Mac and PCs (modern), the boot order is the following:
 
• user turns on the computer providing power
 
• BIOS (or EFI) checks for security, hardware confirmation, and starts to load the OS from the hard drive (or USB or CD/DVD)
 
The only difference in PC or a MAC is the EFI. Mac's being Apple, they are particular in the instructions and look for specific things. What Clover EFI does is mimick what Apple wants to see.
 
So simply put, the boot order on the VM is the following:
 
• user turns on the VM
 
• BIOS/EFI in the VM looks for boot device
 
• Boot device has Clover --> Clover fakes a Mac --> OS X starts thinking its a mac
 
I'm not sure how your .vmdk is set up or where it came from so I can't really help you from that step.
 
What I can tell you, is if you do have a working Mac with installers of anything except High Sierra (haven't figured that one out yet because of a mandatory FW upgrade), you can create your own VM and start from scratch and you can figure out and learn what exactly is going on.
 
• Create an installer via normal OS X instructions on the Mac
 
• Follow this to make it PC bootable https://www.tonymacx86.com/threads/test-drive-how-to-create-a-clover-usb.127134/
 
• With this you should be able to create a blank VM and install OS X from scratch like a normal Mac

Status:

open

Ursprünglicher Beitrag von: S W ,

Text:

In a VM, everything is virtualized into signals or files in respect to physical hardware and signals on a tangible computer.  In a physical machine, a hard drive is a 3.5" or 2.5" rectangular box with platters (or SSD) inside.

On Virtualbox, a .vmdk is the file that represents a physical hard drive, since nothing is physical.

It sounds like you straight downloaded a premade 'hackintosh' or virualbox VM image for a Mac.

You may in that case need to edit the VM and tweak various settings in the VM settings to make it work better in respect to your Windows HOST computer (i.e. increase RAM?).

On both Mac and PCs (modern), the boot order is the following:

• user turns on the computer providing power

• BIOS (or EFI) checks for security, hardware confirmation, and starts to load the OS from the hard drive (or USB or CD/DVD)

The only difference in PC or a MAC is the EFI.  Mac's being Apple, they are particular in the instructions and look for specific things.  What Clover EFI does is mimick what Apple wants to see.

So simply put, the boot order on the VM is the following:

• user turns on the VM

• BIOS/EFI in the VM looks for boot device

• Boot device has Clover --> Clover fakes a Mac --> OS X starts thinking its a mac

I'm not sure how your .vmdk is set up or where it came from so I can't really help you from that step.

What I can tell you, is if you do have a working Mac with installers of anything except High Sierra (haven't figured that one out yet because of a mandatory FW upgrade), you can create your own VM and start from scratch and you can figure out and learn what exactly is going on.

• Create an installer via normal OS X instructions on the Mac

• Follow this to make it PC bootable https://www.tonymacx86.com/threads/test-drive-how-to-create-a-clover-usb.127134/

• With this you should be able to create a blank VM and install OS X from scratch like a normal Mac

Status:

open