@IceWolf does grub even support anything windowsy? I thought it only worked for linux
-F

@Felthry It looks like we can tell it to chainload to any arbitrary EFI program!

@Felthry @IceWolf i've definitely used grub for windows

@Felthry @IceWolf the common advice has always been ime "if you're going to dual boot windows and linux, install windows first. if you install linux first, the windows bootloader clobbers grub. if you install windows first, grub gets installed over the windows bootloader, but it can boot either so you don't lose anything"

@monorail @IceWolf how would you go about adding windwos as a boot option to a linux machine then?
-F

@Felthry @IceWolf every time i've tried it just, does it

@Felthry @monorail @IceWolf it auto-detects it usually

@monorail @Felthry @IceWolf grub won't replace the windows bootloader, it just starts first, you need the windows bootloader to boot windows

@noiob @Felthry @IceWolf sorry not the bootloader, what am i thinking of

the windows "what do you want to boot to" menu

@monorail you have multiple versions of Windows installed?

@noiob no but i've seen the menu for if you do

@monorail ah okay

the only machine I got that on dualboots Windows ME and XP :3

@noiob my assumption was that whatever shows you the menu still runs, but if there's only one option it doesn't show the menu

@monorail @Felthry Hah. We had Windows and installed Linux and installing Linux broke Windows.

@monorail @Felthry ... This MAY be due to the fact that when we used the Mac's "Boot Camp" thing to install Windows, it did some really wonky hybrid-MBR install-Windows-in-BIOS-mode thing.

Why, I don't know. But it's annoying!

@IceWolf @monorail oh you're just chaining bootloader after bootloader there
-F

@Felthry @monorail Huh?

@IceWolf @monorail i think the mac thing uses its own bootloader that would then chain to the windows bootloader and then *that* would chain to grub presumably -F

@Felthry @monorail Ohh!

Nah, when we installed grub it did a normal EFI installation.

... it actually doesn't show up in the firmware's boot list at all so it only works when it's set to boot by default.

@Felthry @monorail [/That/ is a thing with the firmware, I don't think it has anything to do with how grub is installed.]

@monorail @Felthry @IceWolf yeah that's how you dualboot Windows and Linux

or just use the UEFI selector

@noiob @monorail @Felthry We um,

our UEFI selector is wonky and often doesn't show stuff...

and also we're trying to boot the Windows /installer/ bootloader which is on an NTFS partition right now because the installer had a >4GB file that wouldn't fit on FAT. >,,>

@IceWolf @monorail @Felthry yeah some uefi implementations suck

@noiob @monorail @Felthry [Our regular Windows installation's bootloader is currently broken for some reason.]