{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiedhjgynbomsv4vovlhf4vtfgig3yq6hpk4syf73wre3uqiewp24i",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmcjl2xunao2"
  },
  "path": "/viewtopic.php?t=33248&p=274417#p274417",
  "publishedAt": "2026-05-20T18:12:05.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Problem is, targeting 7 SP0 will make the binaries’s minimum subsystem version NT 6.1 to run, meaning I’d either:\n>\n> A) have to modify the binaries to make the minimum subsystem version NT 6.0 (hacky)\n> B) make an app that spoofs Vista as NT 6.1 (even more hacky)\n\nWell, actually the subsystem version is controlled by the linker, not the SDK target.\n\nSo you can do...\n\n_WIN32_WINNT=0x0601\n\nTo expose Windows 7 APIs in the SDK.\n\nAnd then link with:\n\n/SUBSYSTEM:WINDOWS,6.00\n\nBasically, you can target the Windows 7 APIs and still link the binaries in such a way that the subsystem version is valid for Vista, if you really want to.\n\nI did tell you this was complex.  If you ship it the way you have it, Vista users will be locked out of DirectX 11 even if they have it, and might actually be a worse situation than Vista users were in with binaries that just target Windows 7.\n\nI mean, in the end, I guess you're free to do it the way you're doing it... but doing it that way locks you into supporting old, unpatched Vista and missing out on features that later Vista did support.\n\n* * *",
  "title": "Other Applications • Re: Dactyloidae Browser (Basilisk fork)",
  "updatedAt": "2026-05-20T18:12:05.000Z"
}