@Ghot @jimbo45 @cereberus 'Morning, boys. If there's any sparring to be done, I'm your huckleberry. It's Monday, the new time is fecked (as our near and dear
@Edwin would say), I had only 3 hours sleep before the therapist came, and I'VE HAD ONLY 2 CUPS OF COFFEE. !%$!&!%! so any side of the bed was the wrong one for me.
The big problem here is the ambiguity of the original post which we all read differently. I was wrong since I assumed he had the ability to connect the drive secondary to his Windows OS. Linux or not, we can all agree it all boils down to changing his boot order and then he has a multitude of options available
as long as his boot media is UEFI and secure boot disabled. Right???
I love the reference to Tombstone there, as well as your use of feck lol. My sister went to Ireland about 1.5 years ago, so naturally she educated me on that word.
Not to sound like an arse, here, but ambiguity is solved by first ascertaining what the problem is. No matter what, the Problem Solving guides and Troubleshooting manuals throughout the world, and especially in fthe digital world and remote troubleshooting, all say "Ask any pertinent questions and repeat the issue back to the user to verify that you are, in fact, on the same page and understand what hte actual issue is", or something along those lines.
Not picking on you,
@glasskuter, individually or solely, because it is something that happens a lot here and in many other forums the world over - someone posts something and someone else posts 'an answer' which turns out is not really an answer because it doesn't address the user's actual problem. And, no, I'm not trying to be a pariah, either, nor elevate myself into some sort of lofty 'holier than thou' position - I've done it plenty of times myself. Sometimes, when words are written in a certain manner, it's easy to forget that "Well, maybe what I'm reading into this is not what the author had in mind to convey to us". I've done it myself, as I said, even taking benign comments from other users out of context and taking offense where none was intended.
Regardless, no need to apologize - in many cases your answer would have been sufficient.
As for his system - can't assume that he has UEFI either - BIOS systems also allowed users to limit which devie(s) they can boot from. I do that regularly on my systems, restrict all devices from allowing boot except my actual system drive, no CDs, no USB Flash devices, nothing. After POST, the firmware knows exactly where to look, nothing to poll for.But it is also a security issue - leaving USB boot enabled means anyone could come by, slap in a bootable USB, hit the reset button, and off they go. And I did the exact same thing for the exact same reason on my previous mobo too, an X58-based mobo that had only BIOS, no UEFI. And if it has no UEFI, then it doesn't have secure boot, either
