Change static post URL references to post_url

richardg867 · richardg867 · commit 3ec2c6ead941 · 2024-11-08T22:32:57.000-03:00
diff --git a/_posts/2022-03-21-why-not-p3.md b/_posts/2022-03-21-why-not-p3.md
@@ -46,7 +46,7 @@ After numerous disagreements with that contributor, including but not limited to
 
 ### Stick to the Windows that's best
 
-It is widely known (and even shown in the cover of our [v3.0 release post](/2021/12/01/86box-v3-0.html)\) that with a new enough Super Socket 7 or Pentium II setup, you can actually run Windows 7 on 86Box. But "running" is a **massive overstatement**: Windows versions beyond XP were originally designed for much newer hardware than 86Box can emulate at full speed on modern computers, even if you take Microsoft's official minimum requirements into account. Windows Vista and 7 were never meant to even boot on Pentium 1 systems, but Microsoft was pandering to the [embedded computing industry](https://www.google.com/search?q=%22Vortex86%22+%22Windows+7%22 "Vortex86 is a Pentium 1-class CPU from the Windows 7 era") at the time by avoiding intentionally breaking support for these old CPUs, and [sometimes even fixing it in updates](http://web.archive.org/web/20110814164028/http://support.microsoft.com/kb/980358 "KB980358 fixes a BSOD when booting Windows 7 RTM on a Pentium 1"). This changed with Windows 8, which required a late model Pentium 4 with the SSE2 instruction set and NX bit feature at a bare minimum; Windows 7 also eventually received updates which required a Pentium III with SSE at a minimum.
+It is widely known (and even shown in the cover of our [v3.0 release post]({% post_url 2021-12-01-86box-v3-0 %})\) that with a new enough Super Socket 7 or Pentium II setup, you can actually run Windows 7 on 86Box. But "running" is a **massive overstatement**: Windows versions beyond XP were originally designed for much newer hardware than 86Box can emulate at full speed on modern computers, even if you take Microsoft's official minimum requirements into account. Windows Vista and 7 were never meant to even boot on Pentium 1 systems, but Microsoft was pandering to the [embedded computing industry](https://www.google.com/search?q=%22Vortex86%22+%22Windows+7%22 "Vortex86 is a Pentium 1-class CPU from the Windows 7 era") at the time by avoiding intentionally breaking support for these old CPUs, and [sometimes even fixing it in updates](http://web.archive.org/web/20110814164028/http://support.microsoft.com/kb/980358 "KB980358 fixes a BSOD when booting Windows 7 RTM on a Pentium 1"). This changed with Windows 8, which required a late model Pentium 4 with the SSE2 instruction set and NX bit feature at a bare minimum; Windows 7 also eventually received updates which required a Pentium III with SSE at a minimum.
 
 As a result of this, we've been getting many requests to emulate newer CPUs so that 86Box can "run Windows 8 and 10". Even if such CPUs were to be implemented, the user experience would be **extremely painful**; as outlined earlier, there is no host system in existence which can consistently keep up with the fastest CPUs we already emulate, let alone faster ones. Running newer versions of Windows on 86Box is just as much of a questionable endeavor as it is on an equivalent real system: it's a fun experiment maybe worth making a [YouTube video](https://www.youtube.com/watch?v=Zs8-rQKvptM) about, and nothing more. Everything will be so slow you won't even want to open a web browser (if they run at all due to CPU requirements). Just stick to Windows 98, maybe 2000 or XP if your host system is capable; for newer versions, **virtualizers exist**, you know.
 
diff --git a/_posts/2023-08-26-86box-v4-0.md b/_posts/2023-08-26-86box-v4-0.md
@@ -10,7 +10,7 @@ image: "/assets/images/v4.0/hero.png"
 
 This is the August 2023 update to 86Box, bringing many improvements, bugfixes (especially for non-Windows users) and some new hardware.
 
-It's certainly been a while since [our last update](/2022/11/26/86box-v3-11.html). Needless to say, despite the bumpy ride to this release, **we're still alive** and working on making 86Box great. We have some **exciting new features** currently being worked on for future updates, and from now on, we'll be sharing work-in-progress builds of new features with our [**Patreon supporters**](https://www.patreon.com/86box), with no impact to our regular release schedule; the first WIP build is already available to supporters, so go check it out.
+It's certainly been a while since [our last update]({% post_url 2022-11-26-86box-v3-11 %}). Needless to say, despite the bumpy ride to this release, **we're still alive** and working on making 86Box great. We have some **exciting new features** currently being worked on for future updates, and from now on, we'll be sharing work-in-progress builds of new features with our [**Patreon supporters**](https://www.patreon.com/86box), with no impact to our regular release schedule; the first WIP build is already available to supporters, so go check it out.
 
 <hr />
 
diff --git a/_posts/2023-10-16-86box-v4-0-1.md b/_posts/2023-10-16-86box-v4-0-1.md
@@ -8,7 +8,7 @@ image: "/assets/images/v4.0.1/hero.png"
 
 {% include imageheading.html url="/assets/images/v4.0.1/hero.png" separator=" " %}
 
-This is the October 2023 update to 86Box, bringing bugfixes over [the original v4.0 release](/2023/08/26/86box-v4-0.html), as well as a few new features.
+This is the October 2023 update to 86Box, bringing bugfixes over [the original v4.0 release]({% post_url 2023-08-26-86box-v4-0 %}), as well as a few new features.
 
 The work-in-progress build currently available to our [**Patreon supporters**](https://www.patreon.com/86box) will be receiving a v4.0.1 update as well. This WIP build contains a new **Local Switch** feature for connecting 86Box machines locally or across a network in a plug-and-play, cross-platform way, without relying on PCap or VDE.
 
diff --git a/_posts/2024-03-20-86box-v4-1-1.md b/_posts/2024-03-20-86box-v4-1-1.md
@@ -8,7 +8,7 @@ image: "/assets/images/v4.1.1/hero.png"
 
 {% include imageheading.html url="/assets/images/v4.1.1/hero.png" separator=" " %}
 
-This is the March 2024 update to 86Box, bringing bugfixes over [the original v4.1 release](/2024/02/21/86box-v4-1.html) and some new hardware.
+This is the March 2024 update to 86Box, bringing bugfixes over [the original v4.1 release]({% post_url 2024-02-21-86box-v4-1 %}) and some new hardware.
 
 As always, the work-in-progress build currently available to our [**Patreon supporters**](https://www.patreon.com/86box) will be updated accordingly.
 
diff --git a/_posts/2024-07-26-86box-v4-2.md b/_posts/2024-07-26-86box-v4-2.md
@@ -30,7 +30,7 @@ The [**Media Vision Pro AudioSpectrum**](https://en.wikipedia.org/wiki/Media_Vis
 
 The **Ensoniq AudioPCI** emulation was also expanded with Sound Blaster PCI cards based on the **ES1373** and **CT5880** chips. These were far more common than the previous ES1371 chip, which is better known through VMware's emulation than real cards. The newer chips are functionally equivalent and allow you to use later Creative drivers for Windows without running into [issues stemming from an incompatibility with the ES1371](https://messaroundery.net/2023/09/19/ensoniq-es1371-driver-bug "Ensoniq AudioPCI ES1371 and the driver bug nobody found"); though be careful with older ES1371-specific drivers, which may recognize the ES1373 but end up in crashes and other misbehavior.
 
-**Small but important note:** similarly to the [AWE64 in v4.1.1](/2024/03/20/86box-v4-1-1.html#rom-set-update), users of the **Sound Blaster 16 PnP** and **Crystal CS4236B** should update the ROM set, as accurate Plug and Play ROMs were located. If this update is not present, these cards will **disappear from emulated machines** and the sound card selector until the ROM set is updated.
+**Small but important note:** similarly to the [AWE64 in v4.1.1]({% post_url 2024-03-20-86box-v4-1-1 %}#rom-set-update), users of the **Sound Blaster 16 PnP** and **Crystal CS4236B** should update the ROM set, as accurate Plug and Play ROMs were located. If this update is not present, these cards will **disappear from emulated machines** and the sound card selector until the ROM set is updated.
 
 ### Modem
 
diff --git a/_posts/2024-09-01-86box-v4-2-1.md b/_posts/2024-09-01-86box-v4-2-1.md
@@ -8,7 +8,7 @@ image: "/assets/images/v4.2.1/hero.png"
 
 {% include imageheading.html url="/assets/images/v4.2.1/hero.png" separator=" " %}
 
-This is the September 2024 update to 86Box, bringing in the results of a month-long bugfix marathon started right after [the original v4.2 release](/2024/07/26/86box-v4-2.html).
+This is the September 2024 update to 86Box, bringing in the results of a month-long bugfix marathon started right after [the original v4.2 release]({% post_url 2024-07-26-86box-v4-2 %}).
 
 The removal of 32-bit builds and the release of a new Patreon feature preview, both outlined in the v4.2 post, are still on track for the next full release.
 
@@ -27,7 +27,7 @@ We are lacking contributors in various areas of expertise, including but not lim
 * **Linux host interfacing**, for fixing mouse input, keyboard shortcuts and other recurring issues that our Linux users face.
 * **Qt on C++**, to address our user interface code's many loose ends from being modeled after the old Win32 interface.
 * **Dynamic recompilers**, to help close the performance gap between our emulation and full virtualization, analyzing potential optimizations on known pain points such as the complex and well-utilized x86 MMU.
-* **ARM assembly**, for diagnosing a dynamic recompiler issue with MMX acceleration that has stumped us, and potentially bringing the ARM recompiler to parity with our [tried-and-true x86 one](/2022/01/07/pcem-migration-guide.html#the-new-recompiler).
+* **ARM assembly**, for diagnosing a dynamic recompiler issue with MMX acceleration that has stumped us, and potentially bringing the ARM recompiler to parity with our [tried-and-true x86 one]({% post_url 2022-01-07-pcem-migration-guide %}#the-new-recompiler).
 
 Our [GitHub](https://github.com/86Box/86Box) and [Discord](https://discord.gg/v5fCgFw) are always open to pull requests and code contribution discussions, respectively; we will follow development and provide constructive feedback if needed. The [codebase documentation](https://86box.readthedocs.io/en/latest/dev/api/index.html) is currently lacking in details about the emulator's inner workings, but this is something we are looking into correcting in the future.
 
