On 30/12/2020 18:59, Dave Plowman (News) wrote:
In article ,
John Rumm wrote:
On 30/12/2020 14:18, Dave Plowman (News) wrote:
In article ,
John Rumm wrote:
On 29/12/2020 14:41, Dave Plowman (News) wrote:
In article ,
Andy Burns wrote:
Dave Plowman wrote:

Setting it to Other OS makes no difference. If I set it to boot from
the Win7 SSD, I get the same error as Bert.

Was the win7 installed when the UEFI setting was set for secure boot? if
so it won't boot when secure boot is turned off.

No. The Win7 SSD was on the ancient MB - that wouldn't work with Win10.
Don't think UEFI existed when it was new.

EasyBCD does have quite a bit to say about dual booting Win10. It
worked perfectly with Win7 and the other OS I have. But it looks
pretty involved to dual boot Win10 - and the desire to do so
diminishes every day. ;-)

One of the reasons we suggested sticking one OS inside a VM on the other!

Yes. IMHO, it's likely my new MB which is the culprit.

One of the difficulties you can run into a new hardware is the modern
UEFI supports secure boot, and if that is turned on it makes it
difficult to dual boot machines since it replaces the traditional BIOS
boot capabilities.

You normally need to turn that off in the BIOS setup screen when
installing multiple OSs

Tried that from the start. I can remove everything from the MB apart from
the SSD containing Win7 - which worked with the old MB. And set it to
'other OS' Still won't boot.

Are all the drives formatted the same way (i.e. GPT / MBR), and which
partitions have the active flag set?

You may find that you are using the Win 7 SSD as the only active
partition on a MBR drive.


--
Cheers,

John.

/================================================== ===============\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\================================================= ================/