Switch horizontal rules from HTML to proper markdown

richardg867 · richardg867 · commit 28785ff8dfce · 2024-11-17T22:16:04.000-03:00
diff --git a/_posts/2021-12-23-86box-v3-1.md b/_posts/2021-12-23-86box-v3-1.md
@@ -7,7 +7,7 @@ authors: ["richardg867"]
 
 Happy holidays. We hope you're enjoying the season. As a gift, we're releasing [**86Box v3.1**](https://github.com/86Box/86Box/releases/tag/v3.1), a bugfix update fixing many of the issues reported after the release of v3.0 earlier this month.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2022-01-07-pcem-migration-guide.md b/_posts/2022-01-07-pcem-migration-guide.md
@@ -10,7 +10,7 @@ image: "/assets/images/pcem-migration/hero.png"
 
 PCem users sometimes ask us about migrating their emulated setups to 86Box. While it is true that 86Box started out as a fork of PCem, we have since rewritten many components and made many additions, outgrowing our "fork" status. This post details all the differences between the two emulators that you have to keep in mind when migrating your setups to 86Box.
 
-<hr />
+---
 
 ## <a name="performance" />Performance will be different
 
@@ -28,15 +28,15 @@ PCem's emulation of some core system components, such as the Programmable Interv
 
 <a name="cache" />In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. Generally speaking, the more accurate a component's emulation is made, the more host CPU horsepower it will require. There are certain limits to what's attainable to emulate (as an example, we don't do CPU caches, as that is too complex [even for other non-PC emulators](https://dolphin-emu.org/blog/2017/02/01/dolphin-progress-report-january-2017/#50-2204-hack-to-protect-lower-mem1-from-malicious-game-code-by-booto "Our issues involved cache test errors on some BIOSes")\), but we try to follow what's possible.
 
-<hr />
+---
 
 ## Bring your own manager
 
 PCem has a built-in manager, which allows you to keep and run multiple emulated machine configurations from one place. 86Box does not have such a manager, though one is planned for the future. For now, you can use our [**86Box Manager**](https://github.com/86Box/86BoxManager) application, which provides basic configuration management; or, even better, use the community-developed [**WinBox for 86Box**](https://github.com/86Box/WinBox-for-86Box), which has an user-friendly interface resembling PC virtualizers, as well as presets, screenshot and printed document management, and other cool features.
 
 There is **no migration path** for configuration files, as the format is too different. You will have to reconfigure your emulated machine on 86Box, but that's a nice opportunity to double-check your configuration while also checking out our features. More on the differences between PCem and 86Box in the configuration department later.
 
-<hr />
+---
 
 ## <a name="machines" />Machine list
 
@@ -159,7 +159,7 @@ PCem's implementation of the Intel 430HX, 430VX and 440FX chipsets uses the **PI
 
 If you run into this issue, one option is to reinstall the operating system. Another option is to boot the operating system on PCem, uninstall the PIIX IDE driver (on Windows 2000/XP, use **Device Manager** to replace the 82371FB IDE controller driver with the Standard Dual Channel one), then switch to 86Box.
 
-<hr />
+---
 
 ## Settings differences
 
@@ -208,7 +208,7 @@ The 86Box settings interface is designed to be easy to navigate, though you shou
 
 * 86Box supports two networking modes: **PCap** allows for a bridged connection to a wired Ethernet adapter on the host through `pcap` libraries (such as [Npcap](https://nmap.org/npcap/) on Windows), while **SLiRP** behaves just like PCem's private network, with **port forwarding** available as an added advanced feature. See [our documentation](https://86box.readthedocs.io/en/v3.0/hardware/network.html) for more information.
 
-<hr />
+---
 
 ## User interface
 
@@ -218,7 +218,7 @@ The 86Box user interface should look familiar to PCem users, with two main diffe
 
 Note that the key combination to release mouse capture on 86Box is **F8+F12**, as we've found PCem's Ctrl+End to conflict with some applications. You can also use the middle mouse button to release capture, unless a [three-button or wheel mouse](#mousebtns) is configured.
 
-<hr />
+---
 
 ## Media
 
@@ -238,7 +238,7 @@ We recommend ripping your discs to `.cue` + `.bin` before using them in 86Box, a
 
 PCem's IBM cassette emulation uses the `.pzx` format, originally designed for ZX Spectrum tapes. 86Box supports the `.cas` format developed as part of [PCE/ibmpc](http://www.hampa.ch/pce/), as well as audio recordings in `.wav` or `.pcm` format. The `pzx2wav` tool in [PZX tools](http://zxds.raxoft.cz/pzx.html) can potentially convert `.pzx` tapes to `.wav` for 86Box, though we haven't tested that.
 
-<hr />
+---
 
 ## Conclusion
 
diff --git a/_posts/2022-02-16-86box-v3-2.md b/_posts/2022-02-16-86box-v3-2.md
@@ -10,7 +10,7 @@ image: "/assets/images/v3.2/hero.png"
 
 This is the February 2022 update to 86Box, and it's one we know many of you have been looking forward to, as it finally brings in **Linux support**, after many requests over the course of many years. As always, you can [download 86Box v3.2 from GitHub](https://github.com/86Box/86Box/releases/tag/v3.2.1).
 
-<hr />
+---
 
 ## Now with Linux
 
@@ -28,7 +28,7 @@ Linux builds are distributed as [**AppImage**](https://appimage.org) binaries fo
 
 The **Windows version** will remain on the existing Win32 user interface for now, as [**jriwanek**](https://github.com/jriwanek) has stepped up to maintain it, at least while we work on some Windows-specific odds and ends of the Qt interface. All UI points in the changelog below apply to both interfaces.
 
-<hr />
+---
 
 ## Changelog for v3.2
 
@@ -104,7 +104,7 @@ The **Windows version** will remain on the existing Win32 user interface for now
   * Fixed **ISA memory expansion** detection on the IBM PC, XT and clones
   * Fixed **ISA RTC cards** crashing on machines with integrated RTC
 
-<hr />
+---
 
 ## <a name="v3-2-1" />Changelog for v3.2.1
 
diff --git a/_posts/2022-03-18-86box-v3-3.md b/_posts/2022-03-18-86box-v3-3.md
@@ -12,7 +12,7 @@ This is the March 2022 update to 86Box, bringing overall bugfixes and some new h
 
 This release also brings a **major change to the Windows version**: it now uses the same Qt user interface as the Linux and (future - don't worry, we're still working on it) macOS versions. As previously stated in the [v3.2 post]({% post_url 2022-02-16-86box-v3-2 %}#now-with-linux), this new interface should look and feel just like the old Windows one, though there are some minor changes.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2022-03-21-why-not-p3.md b/_posts/2022-03-21-why-not-p3.md
@@ -10,7 +10,7 @@ image: "/assets/images/whynotp3/hero.png"
 
 Word is out there that an individual is trying to develop **Pentium III** emulation as part of a fork of 86Box, regardless of how slow it is, in the name of "hardware preservation". But why didn't **we** do it in the first place? Why did we, developers of a PC emulator clearly aimed at the preservation of hardware and software, limit ourselves to the Pentium II and an underperforming competitor (the VIA Cyrix III), and why did we do these two knowing they're already pretty slow to emulate? It's story time.
 
-<hr />
+---
 
 ## Backstory: Orphans of Virtual PC
 
@@ -28,7 +28,7 @@ If we had any goal early on (before taking on the 86Box name), it was to make a
 
 This Pentium II emulation was eventually shelved as generational improvements to single-thread performance stagnated (and even regressed with Ryzen at first), and also due to a very mysterious bug triggered by Windows XP's use of the Pentium II's `SYSENTER`/`SYSEXIT` feature; as AMD delivered a return to significant generational improvements in x86 and (ironically) PCem's author found a fix to the aforementioned bug while independently developing their own Pentium II emulation, we took our version off the shelf in 2020 as part of **86Box v2.10**, which would later become **v3.0** released in late 2021.
 
-<hr />
+---
 
 ## Drawing the line
 
@@ -52,7 +52,7 @@ As a result of this, we've been getting many requests to emulate newer CPUs so t
 
 While we have fixed emulation bugs explicitly related to newer Windows versions (`STI` interrupt blocking during `SYSENTER`/`SYSEXIT`, incrementing of `RDTSC` in dynamic recompiler mode, etc.), it was all done on **principle**: there might be another older operating system or application out there which runs into the same bug. Theoretically, you don't need to be running Windows XP to stumble upon incorrect `STI` behavior, or Windows 7 to hit a division by zero caused by `RDTSC` returning the same value twice.
 
-<hr />
+---
 
 ## This is fine, we're just telling our side
 
diff --git a/_posts/2022-04-20-86box-v3-4.md b/_posts/2022-04-20-86box-v3-4.md
@@ -10,7 +10,7 @@ image: "/assets/images/v3.4/hero.png"
 
 This is the April 2022 update to 86Box, bringing **macOS support**, bugfixes and other behind-the-scenes work. As always, you can [download 86Box v3.4 from GitHub](https://github.com/86Box/86Box/releases/tag/v3.4.1).
 
-<hr />
+---
 
 ## Now with macOS
 
@@ -26,7 +26,7 @@ As it turns out, a cross-platform project like 86Box is **nearly impossible** to
 
 Apple hardware is expensive. While their chips provide good performance for the money, the machines are still costly upfront, and **we can't afford them**. Renting a Mac Mini from a hosting company also costs more than our entire hosting bill, and while there is one such company out there providing free M1 hardware to open source projects, their offering is **not available to us**. If you want native 86Box on Apple Silicon to become a reality, consider [making a donation](https://paypal.me/86Box) or [joining our Patreon](https://www.patreon.com/86box); contributing will help us get our hands on that hardware in one way or another.
 
-<hr />
+---
 
 ## Changelog for v3.4
 
@@ -65,7 +65,7 @@ Apple hardware is expensive. While their chips provide good performance for the
 * The host mouse cursor may **escape the 86Box window** when using the aforementioned workaround
 * While mouse movement through **Remote Desktop** on Windows hosts was fixed, it still isn't perfect
 
-<hr />
+---
 
 ## <a name="v3-4-1" />Changelog for v3.4.1
 
diff --git a/_posts/2022-05-23-86box-v3-5.md b/_posts/2022-05-23-86box-v3-5.md
@@ -10,7 +10,7 @@ image: "/assets/images/v3.5/hero.png"
 
 This is the May 2022 update to 86Box, bringing bugfixes as well as the long-awaited **native Apple Silicon support** for macOS thanks to a very generous hardware contribution to our project. As always, you can [download 86Box v3.5 from GitHub](https://github.com/86Box/86Box/releases/tag/v3.5).
 
-<hr />
+---
 
 ## Enter Apple Silicon
 
@@ -25,7 +25,7 @@ Note that 86Box builds for macOS are **not signed by Apple**, since signing woul
   * You probably want to keep copies of [**the 86Box app and the ROM set**](/assets/images/v3.4/roms.png) on different folders anyway, as a way of managing multiple emulated machines while there is no 86Box manager app for macOS.
   * Alternatively, you can copy just the 86Box app and use the **system-wide ROM set** feature introduced in v3.4, which is now [documented](https://86box.readthedocs.io/en/v3.5/usage/roms.html); the ROMs should be located on `~/Library/Application Support/net.86box.86Box/roms` in that case ([example](/assets/images/v3.5/appsupport.png)\).
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2022-06-30-86box-v3-6.md b/_posts/2022-06-30-86box-v3-6.md
@@ -10,7 +10,7 @@ image: "/assets/images/v3.6/hero.png"
 
 This is the June 2022 update to 86Box, bringing bugfixes and some new features mostly in the IBM PS/2 department. As always, you can [download 86Box v3.6 from GitHub](https://github.com/86Box/86Box/releases/tag/v3.6).
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2022-07-31-86box-v3-7.md b/_posts/2022-07-31-86box-v3-7.md
@@ -10,7 +10,7 @@ image: "/assets/images/v3.7/hero.png"
 
 This is the July 2022 update to 86Box, bringing initial suport for dual monitors, performance improvements and bugfixes. As always, you can [download 86Box v3.7 from GitHub](https://github.com/86Box/86Box/releases/tag/v3.7.1).
 
-<hr />
+---
 
 ## Dual monitors: color and monochrome
 
@@ -23,7 +23,7 @@ This is the July 2022 update to 86Box, bringing initial suport for dual monitors
 
 As for newer emulated setups running operating systems such as Windows 98, we have plans to extend this feature to **PCI VGA cards** in the future, since many of those have hardware and software support for multi-monitor operation using multiple cards.
 
-<hr />
+---
 
 ## Improving performance by slowing hard disks (no, really)
 
@@ -33,7 +33,7 @@ But wait, there's more! It turns out throttling disk speeds has a positive side
 
 With the significant improvement to emulation performance consistency afforded by disk throttling, we've opted to set **[1997] 5400 RPM** as the default IDE and ESDI speed profiles when migrating an emulated machine from a previous version of 86Box to v3.7. As a result of this change, **you will see a difference** in your setup's operating system speed and responsiveness if it uses IDE or ESDI hard disks, especially if their images are stored in an SSD, but that's a worthy sacrifice in the name of consistent performance, especially while running games. **You can always restore the old behavior without downgrading 86Box** by switching all IDE/ESDI hard disks to the aforementioned **RAM Disk** speed profile.
 
-<hr />
+---
 
 ## Changelog for v3.7
 
@@ -114,7 +114,7 @@ With the significant improvement to emulation performance consistency afforded b
   * Fixed emulator crash with a `Write_MULTIPLE` message when exiting DOS mode on Windows 3.1 with an IDE hard disk
   * Fixed emulator crash with a `Hard disk image` message when a host I/O error occurs on a **VHD image**
 
-<hr />
+---
 
 ## Changelog for v3.7.1
 
diff --git a/_posts/2022-11-26-86box-v3-11.md b/_posts/2022-11-26-86box-v3-11.md
@@ -10,7 +10,7 @@ image: "/assets/images/v3.11/hero.png"
 
 This is the November 2022 update to 86Box, bringing folder mounting through CD-ROMs, new hardware, bugfixes across the board, and big improvements to network emulation ~~truly making this the 86Box for Workgroups release~~. As always, you can [download 86Box v3.11 from GitHub](https://github.com/86Box/86Box/releases/tag/v3.11).
 
-<hr />
+---
 
 ## Folders as CDs
 
@@ -34,7 +34,7 @@ It turns out emulating a writable filesystem is a significantly more difficult j
 
 While there are common methods to create freely-writable optical discs, such as [DVD-RAM](https://www.youtube.com/watch?v=ecH3OU0R4ls "Also check out his other videos on optical discs") and [Packet Writing](https://en.wikipedia.org/wiki/Packet_writing "Writing to optical media a block at a time, instead of a session or disc at a time") (the latter relates to the Windows "what do you want to do with this disc?" prompt that anyone old enough to have used recordable CDs or DVDs will remember), these methods run on top of two features we don't implement, but are in our ever so large "maybe do it one day" list: CD/DVD writing and the UDF filesystem. Even then, the aforementioned complexities in keeping track of a writable filesystem come into play, and they would only be avoidable by limiting ourselves to Packet Writing on a CD-R or DVD-R.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2023-08-26-86box-v4-0.md b/_posts/2023-08-26-86box-v4-0.md
@@ -12,7 +12,7 @@ This is the August 2023 update to 86Box, bringing many improvements, bugfixes (e
 
 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 />
+---
 
 ## Main features
 
@@ -32,7 +32,7 @@ The [**Mach8 and Mach32**](https://en.wikipedia.org/wiki/ATI_Mach_series) were c
 
 A nasty emulator crash when **PCap** fails to initialize was fixed, and the **SLiRP** library was updated to its full version on Windows and macOS hosts for potential performance improvements.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2023-10-16-86box-v4-0-1.md b/_posts/2023-10-16-86box-v4-0-1.md
@@ -12,7 +12,7 @@ This is the October 2023 update to 86Box, bringing bugfixes over [the original v
 
 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.
 
-<hr />
+---
 
 ## Important notes
 
@@ -28,7 +28,7 @@ After updating the ROM set, the MS-5119 BIOS update to fix PS/2 mouse issues is
 
 Due to a longstanding oversight, previous versions of 86Box had the tertiary and quaternary IDE controllers **switch places**, using the incorrect I/O port and IRQ resources for their respective channels. This swap has now been fixed; additionally, the tertiary channel provided by **Plug and Play Sound Blaster cards** is now a quaternary channel. If you use these additional IDE channels, make sure any drives connected to them are placed correctly after updating.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2024-02-21-86box-v4-1.md b/_posts/2024-02-21-86box-v4-1.md
@@ -12,7 +12,7 @@ This is the February 2024 update to 86Box, bringing new emulated machines, new h
 
 The work-in-progress build currently available to our [**Patreon supporters**](https://www.patreon.com/86box) will be updated accordingly. We hope to have its **Local Switch** feature for easy plug-and-play networking between emulated machines ready for public release soon.
 
-<hr />
+---
 
 ## Main features
 
@@ -30,7 +30,7 @@ This release also brings several PCI network cards from **Digital Equipment Corp
 
 Generic compatible variants of the **NE1000** and **NE2000** are now available, addressing a common pitfall when setting up a Windows machine, where the network drivers provide different options on Novell and compatible cards. The **D-Link DE-220P** was also added as a second ISA Plug and Play NE2000 clone.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2024-03-20-86box-v4-1-1.md b/_posts/2024-03-20-86box-v4-1-1.md
@@ -12,7 +12,7 @@ This is the March 2024 update to 86Box, bringing bugfixes over [the original v4.
 
 As always, the work-in-progress build currently available to our [**Patreon supporters**](https://www.patreon.com/86box) will be updated accordingly.
 
-<hr />
+---
 
 ## Important notes
 
@@ -22,7 +22,7 @@ A minor change was made to the ROM set. Users of the base **Sound Blaster AWE64*
 
 The newly-added machines also require an updated ROM set, otherwise they will not be listed in the machine selector.
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2024-07-26-86box-v4-2.md b/_posts/2024-07-26-86box-v4-2.md
@@ -18,7 +18,7 @@ v4.2 is the final release of 86Box for which **32-bit builds** will be provided,
 
 We believe that any host hardware old enough to be incapable of running 64-bit operating systems will not provide a satisfactory emulation experience. Should you have such hardware, the ability to [**compile 86Box from source**](https://86box.readthedocs.io/en/latest/dev/buildguide.html) for unsupported architectures is not going anywhere, but we cannot guarantee that the dynamic recompiler will remain functional on them.
 
-<hr />
+---
 
 ## Main features
 
@@ -38,7 +38,7 @@ A **serial modem** is now available as a network card option. This standard Haye
 
 As with any hardware of this era, there are many potential gotchas to account for when configuring the modem, all described in the [documentation](https://86box.readthedocs.io/en/v4.2/hardware/network.html#modem).
 
-<hr />
+---
 
 ## Changelog
 
diff --git a/_posts/2024-09-01-86box-v4-2-1.md b/_posts/2024-09-01-86box-v4-2-1.md
@@ -12,7 +12,7 @@ This is the September 2024 update to 86Box, bringing in the results of a month-l
 
 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.
 
-<hr />
+---
 
 ## Important notes
 
@@ -43,7 +43,7 @@ A minor change was made to the ROM set. Users of the **Diamond Stealth 3D 4000**
 
 Updating the ROM set will also change the **Phoenix XT clone** machine to a newer BIOS revision which was also located.
 
-<hr />
+---
 
 ## Changelog
 
