Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Install windows then Virtualization or vice versa
- Thread starter ramw5p
- Start date
- Sort by reaction score
Thanks..to clarify
I dont want boot camp and a virtual program..thinking just a virtualization program, but i didnt know if i used the program to install windows, or installed widows FIRST using bootcamp partition etc, then installed the virtualization program [parrallels].
I dont want boot camp and a virtual program..thinking just a virtualization program, but i didnt know if i used the program to install windows, or installed widows FIRST using bootcamp partition etc, then installed the virtualization program [parrallels].
Thanks Tom
So......parallels or VM install 1ST...THEN install windows. Got it. Do i use VM or Parallels to install windows???? is it just intuitive? I thought i had to partition the HDD or somehting before windows, is VM doing this for me? Thanks
So......parallels or VM install 1ST...THEN install windows. Got it. Do i use VM or Parallels to install windows???? is it just intuitive? I thought i had to partition the HDD or somehting before windows, is VM doing this for me? Thanks
You are confusing what boot camp or parallels do.
If all you want is the occasional use of Windows, and don't care if it runs a bit slower, then Parallels is a great way to go. You load Parallels and then it does all the work to install Windows. It does not create a separate partition, it keeps everything on the Mac OSX disk.
The downside of the Parallels first and no boot camp approach is that if you decide you want to go to boot camp, it's not trivial to move everything.
If you do a boot camp partition - the way you can boot to Windows and run it without OSX - it takes more time and effort on your part. The instructions must be followed exactly if you want it to work (and to ensure you don't do something dumb to destroy your OSX install. If youy can print out directions and follow them, it will be fine. After you get Windows up and running via boot camp, you can easily install Parallels and tell it to use your boot camp install. You then have the option of running Windows natively (booting to it) or running it by simply opening a Parallels VM from in OSX. Windows runs faster natively than in a VM. My gut is about 25% slower in the VM, but I've done no real tests.
I run using Parallels on occasion (now on V7 but started with V3 years ago) but most often I find I boot to Windows and run it via boot camp. If you do run via boot camp, you'll want to consider adding Tuxera NTFS to allow OSX to write to your Windows (NTFS) formatted disk and something like MacDrive to allow Windows to read/write to your OSX (HFS+) disk. With Parallels (no boot camp), you don't need either of these as it takes care of it for you.
If all you want is the occasional use of Windows, and don't care if it runs a bit slower, then Parallels is a great way to go. You load Parallels and then it does all the work to install Windows. It does not create a separate partition, it keeps everything on the Mac OSX disk.
The downside of the Parallels first and no boot camp approach is that if you decide you want to go to boot camp, it's not trivial to move everything.
If you do a boot camp partition - the way you can boot to Windows and run it without OSX - it takes more time and effort on your part. The instructions must be followed exactly if you want it to work (and to ensure you don't do something dumb to destroy your OSX install. If youy can print out directions and follow them, it will be fine. After you get Windows up and running via boot camp, you can easily install Parallels and tell it to use your boot camp install. You then have the option of running Windows natively (booting to it) or running it by simply opening a Parallels VM from in OSX. Windows runs faster natively than in a VM. My gut is about 25% slower in the VM, but I've done no real tests.
I run using Parallels on occasion (now on V7 but started with V3 years ago) but most often I find I boot to Windows and run it via boot camp. If you do run via boot camp, you'll want to consider adding Tuxera NTFS to allow OSX to write to your Windows (NTFS) formatted disk and something like MacDrive to allow Windows to read/write to your OSX (HFS+) disk. With Parallels (no boot camp), you don't need either of these as it takes care of it for you.
Boot camp - allows you to run windows as if you have a PC, it runs natively, you reboot your Mac leaving OSX.
Parallels/Fusion - allows you to run windows inside OSX. Downside is performance and no direct access to hardware. Generally ok for most tasks and the user prefers OSX over windows
Both Parallels/Fusion can use your bootcamp partition instead of creating a proprietary virtual file. This gives you the ability to run windows inside OSX or if you want reboot and start windows natively.
I personally don't use bootcamp as my needs are such that VMware fusion satisfies them.
Parallels/Fusion - allows you to run windows inside OSX. Downside is performance and no direct access to hardware. Generally ok for most tasks and the user prefers OSX over windows
Both Parallels/Fusion can use your bootcamp partition instead of creating a proprietary virtual file. This gives you the ability to run windows inside OSX or if you want reboot and start windows natively.
I personally don't use bootcamp as my needs are such that VMware fusion satisfies them.