Hello!
(Incidentally all of you are getting this because Google Mail delights
in sending things out as reply-all.)
I'm currently an observer in this set of circumstances but as it
happens Stefan you are very right. My older laptop used a BIOS that
was more suited to an earlier and even uglier release of Windows(!)
and this one is using EFI and behaves strangely  sometimes.

Oh and I was able to run Windows 8 and Windows 8.1 for a while on the
older one. Slowly of course but those versions ran.

Let's see what does work..
-----
Gregg C Levine [email protected]
"This signature fought the Time Wars, time and again."

On Tue, Jun 11, 2019 at 6:53 PM Stefan Reinauer
<[email protected]> wrote:
>
> * ron minnich <[email protected]> [190611 07:13]:
> > if you boot windows 12 would you need tianocore?
>
> Need is a harsh word, but the simple answer to a simple question is yes,
> you do.
>
> You can use SeaBIOS, but Windows does not officially support legacy BIOS
> since at least Windows 7, so whatever works today might stop working
> tomorrow.
>
> >
> > On Mon, Jun 10, 2019 at 1:44 PM Nico Huber <[email protected]> wrote:
> > >
> > > On 09.06.19 20:53, Matt B wrote:
> > > > It is possible through u-root support for multiboot images [1] to 
> > > > chainload
> > > > grub?
> > >
> > > Yes, I would think so. But in case we are still on topic: It won't
> > > help you to boot Windows (unless you also implement UEFI services
> > > in your LinuxBoot and use a UEFI GRUB).
> > >
> > > To chainload something for Windows I would currently go either one of
> > > these ways:
> > >
> > >     coreboot -> LinuxBoot -> SeaBIOS   -> Windows loader
> > >     coreboot -> LinuxBoot -> tianocore -> Windows loader
> > >
> > > I think SeaBIOS already has an option to build a multiboot image. In
> > > either case you could also (in theory) pack either into a bzImage and
> > > feed that to kexec.
> > >
> > > Nico
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to