Lines Matching full:windows

24 but where Linux was installed to replace the original OS (Windows or OSX).
26 The larger group is the systems tested to run only Windows.  Not only that,
27 but many were tested to run with just one specific version of Windows.
28 So even though the BIOS may use _OSI to query what version of Windows is running,
33 with all versions of Windows.
35 But Linux isn't actually compatible with Windows, and the Linux community
37 Windows to its list of _OSI strings.  So it is possible that additional strings
41 What should an OEM do if they want to support Linux and Windows
43 for Linux to deal with how Linux is different from Windows.
73 Windows 98, SE: "Microsoft Windows"
74 Windows ME: "Microsoft WindowsME:Millennium Edition"
75 Windows NT: "Microsoft Windows NT"
90 _OS "Microsoft Windows NT", though it seems somewhat far-fetched
94 Linux answers "Microsoft Windows NT" to please that BIOS idiom.
95 That is the *only* viable strategy, as that is what modern Windows does,
110 were to agree on a string of the form such as "Windows-interface_name".
112 But two bad things happened.  First, the Windows ecosystem used _OSI
116 in example code using _OSI("Windows 2001").
120 Linux had no choice but to also return TRUE to _OSI("Windows 2001")
125 the latest version of Windows, and sometimes it takes more than a year
129 to _OSI("Linux").  Doing so is even worse than the Windows misuse
141 ACPI BIOS that are tested on Windows machines.  There is a real risk
150 to support Linux and Windows differences in the same BIOS.
155 Modern Windows returns _REV = 2.  Linux used ACPI_CA_SUPPORT_LEVEL,
172 Like Linux's _OSI("*Windows*") strategy, Linux defaults to
175 Just like on Windows-tested platforms, this strategy has risks.
180 disabled all _OSI("*Windows*") to keep poorly written Mac BIOS