>this additional user guide</a>.
</p>
</div><!-- answer -->
+<button>I’m working on Windows‑XP,
+but the MinGW compiler doesn’t seem to recognize this;
+is this a bug?
+</button>
+<div class="answer">
+<p>No, it is <em>not</em>  a bug.
+The version of Windows, on which you are working,
+is <em>fundamentally irrelevant</em> ;
+what <em>is</em>  important is the extent to which
+you would like your application to run on older versions of Windows,
+and, in line with MinGW.OSDN’s legacy platform support policy,
+the MinGW compiler sets its <em>default level</em>  of API
+support <em>very</em>  conservatively,
+to ensure support for <em>all</em>  versions of Windows,
+from Windows‑NT4 (or Windows‑95) onwards.
+</p>
+<p>Of course,
+you may wish to take advantage of some newer API capabilities,
+which are not supported on these legacy versions of Windows,
+and you are willing to sacrifice legacy support in order to do so.
+In this respect,
+MinGW and Microsoft’s compilers exhibit similar behaviour,
+(although newer versions of Microsoft’s SDK may set a less
+conservative level of legacy support);
+if you wish to support any API function,
+which is not supported by the compiler’s default Windows version,
+then the onus is on <em>you</em>  to enable support for the
+newer API version,
+as stipulated in <a target="_blank" rel="noopener noreferrer"
+ href="https://docs.microsoft.com/en-gb/cpp/porting/modifying-winver-and-win32-winnt"
+>this Microsoft documentation</a>,
+(but note that,
+whereas Microsoft no longer offer support for Windows‑2000,
+or earlier, nor any version of Windows‑9x,
+MinGW <em>does</em>  endeavour to support these legacy Windows versions,
+by setting <code>WINVER</code> and
+<code>_WIN32_WINNT</code> — and
+<code>_WIN32_WINDOWS</code> for
+Windows‑9x — to
+appropriate values,
+as defined in the MinGW version of <code><sdkddkver.h></code> ).
+</p>
+</div><!-- answer -->
<button>Why does the MinGW linker
persistently report “undefined reference” errors,
when I have specified all of the libraries