There are two ways I know to run Windows on a Mac.
One uses Mac’s built in boot manager “Bootcamp.” This involves installing MacOS and Windows OS in two different partitions and dual booting the computer to switch between the two systems. You either boot into MacOS or into Windows. It means you can only run one OS at a time and must reboot the computer to run the other OS.
That can be inconvenient if, in the course of your business, you do your Internet transactions on the Mac, but must use a Windows-specific program regularly at the same time.
The other way to run Windows on a Mac is in a virtual machine or VM. in this case the OS that runs the computer (host) is the MacOS. The Windows OS (guest) is installed and operates in a large file (think bubble) on the host machine. Both operating systems coexist and can run at the same time without reboot. The MacOS (host) actually runs the machine and the associated hardware. The Windows OS runs in the VM (guest/bubble) and “borrows” the host’s hardware.
How does that come about?
Well, you need several prerequisites.
First, you need a machine capable of the task. In essence, it has to be able to run two computers at once.
The processor function for this is called virtualization. This will be listed When you look up the specs on the processor.
Each of the operating systems has a minimum hardware specification – minimum RAM, hard drive space, etc. The computer must meet, at the very minimum, the sum of these requirements. For example, if Win7 requires a minimum of 1GB RAM and the Mac OS requires 4GM RAM, the computer must have at least 5GB (but we know minimum specs are often WAY WAY to low).
Secondly, you need virtualization software. I use Patallels Desktop for Mac. VMWare Fusion for Mac is another application for this purpose.
The virtualization software takes the Windows installer (ISO, DVD, flash drive), creates the virtual machine on the host (file, or “bubble,” if you will), and installs the Windows OS in it. It provides the drivers so the Windows OS can communicate with and use the Mac’s hardware and peripherals, sets the guest OS specs such as number of processor cores, hard drive space and RAM dedicated to the VM, and defines how the guest interacts with the host OS otherwise.
I have to add here, that the Windows OS installed in a VM needs to be a valid licensed copy of the software.
Once the VM is set up, you can make the choice of how the two OSs interact. My references here are to Parallels Desktop installed on a Mac.
Most of the time, I like the VM to run in “full screen” mode. I can switch between the Mac desktop and the Windows desktop with a three-finger sideways swipe. Whatever is running in each of the full screen VMs continues running even when it is not the focus. Yesterday evening I was moderating the AskWoody website and playing solitaire on the Mac desktop while I downloaded and installed the Win10 Cumulative Update in a VM.
Another possible combination is running Windows in a window on the Mac desktop – you choose the size of window. I use this setup when running the legacy Access application in the XP VM because I need simultaneous access to e-mail and the Internet (NOT using XP on the Internet!)
You can also just run a Windows application directly on the Mac desktop using coherence. The Windows OS runs in the background unseen and the icon for the Windows application sits in the dock on the Mac desktop.
Because there is not always a Mac equivalent for a Windows program (and visa versa) dual booting and virtualization are ways to have the best of both worlds.