A little more information on what distro you are using would be helpful. Debian Live build now has proper UEFI support so you can build, or get someone to build one for you, a live image and use that to install it. Grub-efi should install, if you are using an efi capable installer and Windows is installed using efi, and you should then be able to select whatever OS you want as you would normally using Grub. On 1 January 2017 at 06:22, Felmon Davis <davisf(a)union.edu> wrote:

like Hare's exegnu version. exegnu is what I needed to know. Trinity on top of it! I think you need to find out if Windows is installed using EFI before you do anything. pretty sure, using uefi. Don't be pretty sure, be absolutely positive. uefi. presumably I would have to boot it from the 'BIOS' instead of via grub-efi. if so, not pretty but tolerable. I don't have time right now for magic surgical operations. If Windows is installed non efi (i.e. Legacy BIOS) and other OSs are installed EFI then the PC will default to EFI boot and Windows will not be a bootable option (I had this happen with my current motherboard) If Windows is installed EFI other OSs installed Legacy BIOS will not be a bootable option because Windows EFI boot takes precedence (it was MSs attempt to kill off Linux from mainstream PCs) If Windows is installed EFI and other OSs are installed EFI then Grub EFI will become the primary bootloader and should provide you with a menu that shows the EFI bootable OSs. Windows will show up in Grub EFI as long as it was installed EFI and selecting it will initiate NTbootloader and start Windows. So be absolutely positive how your system is setup and then come back and let us know so we can, if need be, walk you through the install. Just as an aside does exegnu support EFI installation? if it doesn't and that is what you want to use you will need to get an iso of Devuan, and do the required research to ensure Devuan is EFI compatible, to install it and then install TDE of top of that.

On Saturday 31 December 2016 22:29:07 Felmon Davis wrote: TDE does not always go well with KDE 4+. I personally tend to avoid putting those two together. But others will know more about this than I do. One can certainly normally install extra DEs, but this may be a case where it does not go well, both for the reason I have given and because the two (DE and OS) do appear to be rather entangled in this case. That might be simpler, so long as you are clear that Debian with Trinity is not the same thing as an OS called Trinity! It does for now. It went through a phase of having LXDE available as well. This strikes me as a good choice. Named after a rather beautiful place, too! But you are still installing an OS and a DE, and could install other additional DEs after installation if you wished. Yes. In general one can, but I fear that this may be the exception that proves the rule. :-( Anyone?? I don't know NetRunner, and had to look it up. I am always cautious about mixing any version of KDE and Trinity. To do so would certainly not muck up your mbr, but it might muck up your NetRunner! Lisi

Greg M On 12/31/2016 01:29 PM, Felmon Davis wrote: updating/installing grub might solve the lack of grub boot screen. I would use the 'dry-run' option..os-prober is the part that looks for all the other OS's installed so grub can build a multiboot scenario. Debian has no issues with uefi, at least stretch. ps multiboot is the old way, if you have the hardware, virtualization works great. I use Debian with Win7 as a guest..runs fine..caveat, I have an OEM Win7 disk., greg

Some things need to be cleared up. 1) UEFI does not use MBR (Master Boot Record), UEFI uses GPT (GUID Partition Table). 2) GPT can, and does, work in some newer BIOSs but not all. 3) I have never seen, or heard of, any instance where an OS installed in Legacy BIOS is visible on a UEFI boot. Please verify your install of Windows 7 is installed on BIOS and is an option on Grub EFI. 4) AFAIK Windows does not recognise non MS OSs in its bootloader, to have multiple options that include non MS OSs you must use a non MS bootloader as the primary bootloader (i.e. GRUB) which will then initiate the MS bootloader (NT bootloader) to boot MS OS installs. As mentioned above by someone else using os-prober will let GRUB know if there are other OSs installed. 5) Using a VM is a drain on RAM, you need enough RAM to run the host OS and then enough to run the Virtual OS inside the VM. If you are using a VM to run an MS OS most of your RAM will need to be reserved for the MS OS. In my experience unless you have alot of RAM this will negatively affect performance. There is a general move towards Hypervisors (Zen being an excellent open source option) but even these are host machines with virtualised OSs and the same RAM issues apply. On 1 January 2017 at 13:40, Felmon Davis <davisf(a)union.edu> wrote: