how to multi-boot: separate uefi drives, win10+win7+linux+hackintosh

dataguy

Distinguished
Feb 16, 2010
5
0
18,510
A salvage shop combined with aging personal inventory yields the opportunity, I hope, to build a fairly capable and flexible desktop work station with PLEX home network media server system within a minimalist budget. (It may not be the latest-greatest architecture, but neither am I.). It includes a Gigabyte GA-Q77M-D2H LGA1155 socket motherboard; an Intel Core i5 3470 quad-core CPU; 16 gb DDR3 RAM; >12 tb storage (3 or 4 SSD's, several internal and external HDD's), NVIDIA Quadro K620 GPU. BIOS is updated, set to UEFI; USB 3.0 works.

Goal: multi-boot system; Win7 Pro, Win10 Pro, Mac High Sierra, Linux Mint. (PLEX will run on Windows, my everyday OS.) Getting there needs to be an evolving staged development over months, as time becomes available while maintaining everyday usability.

SSD1 contains W7 OS partition C: with some programs, partition D: with most of programs; (this dinged-up configuration is muddled and corrupted over the years, but contains several hundred programs, many I will install fresh on W10). SSD2 contains clean/activated W10, gained from MS upgrade program, based on OEM tag from motherboard. SSD3 will contain High Sierra; SSD4, Mint (unless I decide to add it to an existing SSD).

My question is how to make all these OS's on separate SSD's boot correctly while maintaining a common identification among the various logical drives. (I tried EasyBCD, but haven't got it quite working, yet.) My reading suggests that a boot manager like rEFInd might be my easiest option, but I'm looking here for experienced counsel for best software and configuration process to make this all purr smoothly.

So far I get SSD1 and SSD2 to boot independently, but they don't always like to be connected at the same time. They were each initially installed solo, with no other drives attached. I'm using W7 as my current everyday, but I'd like to get both W7 and W10 dual-booting and coexisting, so I can access and copy files from one drive to the other as I gradually develop/transition to my W10 system. One problem I remember is that both of these independent installs see their OS on logical drive C: Do I just change the labels within the two configurations to avoid conflict? Perhaps label W10's C: to E: while running off W7's C: & D:, and label W7's C: to F: when running off W10's C:? Or is there a way to change W10's registry, et. al. from C: to reference E: all the time?

While I have backups of both drives, I'd like to avoid any reinstalls of W7 or W10. W7 over the years is so jury-rigged, I'm lucky it still works, and I need it to remain dependable until I'm totally transitioned to W10. My W10 was installed from the MS upgrade program (which has now expired), so it doesn't have a stand-alone DVD--or is there a way around this?)

I'm thinking it's wise to get W7 and W10 to coexist first, before proceeding to Sierra and Mint. Can I use the same multi-boot manager for just those two (as I will for the four)? Can each additional OS simply be added to its configuration, one-at-a-time, or does the boot manager need to be uninstalled and reinstalled each time? Does the boot manager software get installed on only one drive or in each OS? What other advice is important for this project?

My apologies for my naiveté. I've built numerous single OS Windows machines over the years, but this is certainly a new level of challenge. I've studied tons of web articles and forums on multi-booting with these OS's, including tonymacx86, but couldn't answer these particular questions. Your considerate guidance is appreciated.
 
Solution
One problem I remember is that both of these independent installs see their OS on logical drive C: Do I just change the labels within the two configurations to avoid conflict? Perhaps label W10's C: to E: while running off W7's C: & D:, and label W7's C: to F: when running off W10's C:? Or is there a way to change W10's registry, et. al. from C: to reference E: all the time?

Each Windows OS sees itself as the C drive. Boot up Win 10, that drive is the C.
Boot up Win 7 from a whole different drive, that drive is the C, within the context of that running OS.
All other drives are other drive letters. And not necessarily stable across each running OS.
Reboot back into Win 10, and that physical drive is again its own "C drive"...
Tonymacx86 has guides for this in their forums. You'll get better help there. There are many more users experienced with this. As I understand it. The forum rules also limit how much help can be provided here for hackintoshes. Beyond generalities.

Setting the mac drive as the boot drive in the BIOS and using Clover as the bootloader is the way to go. Some extra work is required to get Linux recognized. Other bootloaders don't play nice with OS X. I think rEFit and rEFind have to be used on real Macs. Clover is based on rEFind.

Way back when I was interested in fiddling with Mac on PC. I used Chameleon, it was reliable. Clover has replaced Chameleon. Now I'm happy just running OS X on my Macbook and iMac. Windows on everything else. Every once in a while I try various Linux distributions. Each time I remember how much I dislike Linux. Although Elementary OS looks promising. I've always owned Macs. It was just interesting to learn how to do. Taught me a lot about Mac OS X diagnostics I'd never have learned in normal use.
 

dataguy

Distinguished
Feb 16, 2010
5
0
18,510
Thanks, velocityg4. Will try to delve in more @ tonymacx86, but its emphases (and bias) seemed to be almost all hackintosh, while providing less than satisfactory detail about Windows (and Linux). I posted on TH because of its much larger/broader audience and stronger attention to Windows.

I had been trying to get W7 and W10 to coexist smoothly before installing hackintosh. Do you recommend trying to add high sierra with its MultiBeast bootloader right away, hoping that resolves the multi-boot configuration? Can I add Linux later?

Windows is my everyday choice for my primary machine, simply because I have so much $ invested in software, and its 99% of my experience with computers. I'm transitioning my 3 other home network machines to Linux because its a totally free avenue to PLEX client and browsing, pretty much their only tasks (might also add KODI). Would run Linux on my primary machine only for convenience when developing changes for my other machines. I like how PLEX does all its transcoding on my powerful server, so client machines require less resources.

Hackintosh is something I've dreamed about because its historical reputation suggested Mac was generally more simplistically elegant, and more facile in its treatment of video media (but some recent critical reviews of editing software propose that recent W10 versions equal or beat Mac).

I've also been wondering about running virtualization (e.g., VirtualBox, VMware) on Windows instead of hackintosh, as my expected use of MacOS is limited (unless I become smitten after learning it). Maybe run both Mac and Linux via virtualization on W10 instead? Advantage: no stoppage of access for my PLEX system. Q1: does physical installation of multi-boot Mac & Linux provide better stability and easier permanent configuration settings than virtualization? Q2: does my hardware have enough horsepower to run virtualization without impairing PLEX performance?

What do you think?
 
I'll just step in with this gentle reminder:

Since MacOS is only licensed to owners of Apple branded hardware, all discussion centered around installing/configuring/running MacOS on standard PC's is prohibited here. However, since a Mac is just a glorified PC you may discuss the hardware (only) to your heart's content.
 


Since the the Clover bootloader is open source. Is discussion of it permitted? As in my earlier post.
 

Math Geek

Titan
Ambassador
i actually have win 7, 10, OS 10 and android running one one pc. after a ton of false starts i managed it by getting OS 10 running first. then i start adding hdd's and getting windows and such going.

at that point it's pretty much like running boot camp on a mac and installing windows and so on. i wanted to add it to my windows pc's but just could not get it working.

that's about all i can get into here since as bubblehead noted, the hardware discussion is fine but we avoid the software side of it here. see tonymac for how to get OS10 running and then start adding windows and it should be ok. i assume you've already checked the hardware side of it to be sure what you have is compatible. if not tonymac has a ton of info on that as well.
 

As the Clover bootloader is a generic booter, yes, discussion is permitted, right up to the point that the discussion turns to MacOS. At that point you cross the line.

 

dataguy

Distinguished
Feb 16, 2010
5
0
18,510
My apologies for not knowing the fine print in this forum's protocol. I've read plenty of posts when researching my own questions, but have little experience in submitting my own posts, that would acquaint me with policy details. Being inexperienced, I defer to judgement by administrators and moderators.

Nevertheless, I'm motivated to appreciate velocityg4's perspective re open source tools. And honestly, it's pretty confusing when a http://www.tomshardware.com/forum/all.html?refine=hackintosh search results in 1406 threads in the forum (many with extensive discussion).

If it helps, the target of my questions is on multi-boot or virtualization strategies, tactics, and resources--particularly as they relate to separate uefi SSD hardware pre-configured with particular OS's. So if answers could be seen from "generic" perspective, maybe that would be acceptable (especially given the 1406 thread history). Or, if you prefer, PM me. Thanks for everyone's help, and again, I do respect policy.
 

USAFRet

Titan
Moderator
One problem I remember is that both of these independent installs see their OS on logical drive C: Do I just change the labels within the two configurations to avoid conflict? Perhaps label W10's C: to E: while running off W7's C: & D:, and label W7's C: to F: when running off W10's C:? Or is there a way to change W10's registry, et. al. from C: to reference E: all the time?

Each Windows OS sees itself as the C drive. Boot up Win 10, that drive is the C.
Boot up Win 7 from a whole different drive, that drive is the C, within the context of that running OS.
All other drives are other drive letters. And not necessarily stable across each running OS.
Reboot back into Win 10, and that physical drive is again its own "C drive"

And do NOT attempt to go into the Reg and change a running OS drive letter to something else. You WILL kill that OS.
 
Solution

TRENDING THREADS