The bootstrap process on EFI systems

Posted Feb 18, 2015 11:16 UTC (Wed) by etienne (guest, #25256)
In reply to: The bootstrap process on EFI systems by marcH
Parent article: The bootstrap process on EFI systems

> ... x86 EFI implementations ...
> How many of these bugs affect Windows, requiring Microsoft to have similar workarounds in place?

Maybe Windows has same problems (for instance waking up from power saving modes on some hardware), but Windows users have a different definition of "working" - they expect to pay to have a fix - so they do not complain too much.

The bootstrap process on EFI systems

Posted Feb 23, 2015 21:11 UTC (Mon) by poruid (guest, #15924) [Link] (1 responses)

It's simpler than that: many if not most EFI implementation are for computers that will delivered with MS Windows pre-installed. For that reason the developers will find their implementation working once it boots the targeted MS Windows versions.

A nasty consequence of this circumstance can be that errors in the MS Window boot code, may cause those EFI developers to adjust their code in order to have MS Windows boot properly.

The bootstrap process on EFI systems

Posted Feb 24, 2015 11:35 UTC (Tue) by etienne (guest, #25256) [Link]

> most EFI implementation are for computers that will delivered with MS Windows pre-installed

I can give you an example of a pre-installed Windows 7 on a branded portable PC which is not working(1) when waking from hibernation.
No update for the BIOS are present after 2 years.

(1) not working: In the Unix/Linux sense, meaning it sometimes fails.
Windows users would call it "working" because on a good day, you can try to close the lid for few seconds so the screen re-enter power saving mode - then re-open the lid - and you may get back your screen.
Windows user have learned to carry lucky things and put them on the top left side of the screen when using their computers. Me, I am not superstitious, that brings bad luck...