mirror/86box.github.io
1
0
Fork 0
mirror of https://github.com/86Box/86box.github.io.git synced 2026-02-21 09:05:35 -07:00
Code Issues Packages Projects Releases Wiki Activity

Minor revisions to old changelogs

Browse Source
This commit is contained in:
RichardG867
2025-12-20 18:10:20 -03:00
parent 5f1d5eb600
commit 0dca770297
7 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
_posts/2022-02-16-86box-v3-2.md
View File

@@ -18,11 +18,11 @@ This Linux version was made possible by the massive work put in by contributors
Linux builds are distributed as [**AppImage**](https://appimage.org) binaries for maximum compatibility. We've tested these on distributions as old as **Ubuntu 16.04** and as new as **Manjaro 21.2.2**, but if you run into issues on your specific distro, [please let us know](/#social). Binaries for **x86_64**, **ARM32** and **ARM64** architectures are available; 32-bit x86 is currently not available due to a [packaging issue](https://github.com/AppImageCrafters/AppRun/issues/37). Of course, building 86Box from source and running it with system libraries is still an option, and there's a [community-maintained Arch Linux AUR package](https://aur.archlinux.org/packages/86box) which does just that.
**IMPORTANT UPDATE:** On Linux, you should place the `roms/` directory (containing the ROM set) in the **same directory** as the `.AppImage` file ([example](/assets/images/v3.2/roms.png)\). A global ROM path and a manager interface will be added in a future release. For now, you can manage emulated machines through one of the following methods:
**IMPORTANT UPDATE:** On Linux, you should place the `roms` folder (containing the ROM set) in the **same folder** as the `.AppImage` file ([example](/assets/images/v3.2/roms.png)\). A global ROM path and a manager interface will be added in a future release. For now, you can manage emulated machines through one of the following methods:
* Keeping multiple copies (or symlinks) of the 86Box `.AppImage` and the `roms/` directory.
* Running the 86Box `.AppImage` with the `-P /path/to/machine/directory` switch, which **does not require** copying `roms/` over to the emulated machine's directory.
* Running the 86Box `.AppImage` from a different working directory, which also **does not require** copying `roms/` over.
* Keeping multiple copies (or symlinks) of the 86Box `.AppImage` and the `roms` folder.
* Running the 86Box `.AppImage` with the `-P /path/to/machine/folder` switch, which **does not require** copying `roms` over to the emulated machine's folder.
* Running the 86Box `.AppImage` from a different working folder, which also **does not require** copying `roms` over.
**IMPORTANT UPDATE #2:** Still on Linux, **86Box v3.2.1** (link above, [changelog below](#v3-2-1)\) should fix the issue with mouse capture dropping the emulation speed down to 0%.

2
_posts/2022-04-20-86box-v3-4.md
View File

@@ -16,7 +16,7 @@ This is the April 2022 update to 86Box, bringing **macOS support**, bugfixes and
Continuing on the cross-platform development effort started during [v3.0]({% post_url 2021-12-01-86box-v3-0 %}#one-more-thing-linux-is-coming) and first released for Linux on [v3.2]({% post_url 2022-02-16-86box-v3-2 %}#now-with-linux), we now provide **Intel macOS** builds of 86Box. These should work on macOS High Sierra 10.13 and newer, natively on Intel Macs and through Rosetta 2 on Apple Silicon Macs. [dob205](https://github.com/dob205) was our main macOS tester, while [**jgilje**](https://github.com/jgilje), [**Cacodemon345**](https://github.com/Cacodemon345) and other contributors did the OS integration work.
As with Linux, there is currently no 86Box manager for macOS, but you can manage emulated machines by **making copies** of `86Box.app` on different places (just dragging it to `/Applications` is currently not recommended); the `roms/` directory (containing the ROM set) must be placed next to the .app ([example](/assets/images/v3.4/roms.png)\), and the emulated machine's files will be saved next to the .app as well.
As with Linux, there is currently no 86Box manager for macOS, but you can manage emulated machines by **making copies** of `86Box.app` on different places (just dragging it to `/Applications` is currently not recommended); the `roms` folder (containing the ROM set) must be placed next to the .app ([example](/assets/images/v3.4/roms.png)\), and the emulated machine's files will be saved next to the .app as well.
### But where's Apple Silicon?

4
_posts/2022-07-31-86box-v3-7.md
View File

@@ -49,8 +49,8 @@ With the significant improvement to emulation performance consistency afforded b
### User interface
* Added global preference to fix the starting directory for **file prompts on macOS**
* Fixed **Settings section list** being too narrow on some host machines
* Added global preference to fix the starting folder for **file prompts on macOS**
* Fixed **Settings section list** being too narrow on some hosts
* Fixed incorrect button order on the **hard reset confirmation** message
* Fixed incorrect **icons** on some warning and error messages
* Fixed incorrect warning message shown when **Ghostscript** is missing

2
_posts/2023-10-16-86box-v4-0-1.md
View File

@@ -22,7 +22,7 @@ Despite this being a minor bugfix release, the **ROM set was also updated** to r
### MSI MS-5119 BIOS update
After updating the ROM set, the MS-5119 BIOS update to fix PS/2 mouse issues is **not applied automatically to existing emulated machines** using that board. Apply it by deleting `ms5119.bin` from the machine's `nvr` directory, then start the machine and check if the BIOS version displayed below the American Megatrends logo is `A37EB` instead of the previous `A37E`.
After updating the ROM set, the MS-5119 BIOS update to fix PS/2 mouse issues is **not applied automatically to existing emulated machines** using that board. Apply it by deleting `ms5119.bin` from the machine's `nvr` folder, then start the machine and check if the BIOS version displayed below the American Megatrends logo is `A37EB` instead of the previous `A37E`.
### Tertiary and quaternary IDE

2
_posts/2025-08-24-86box-v5-0.md
View File

@@ -336,7 +336,7 @@ Inserting **DVD-ROM discs** (or folders larger than 1 GB) now requires [setting
* **Ports**
* Added **bidirectional**, **ECP** and **EPP** parallel port modes on supported machines
* Added **named pipe client** mode to serial passthrough on Windows hosts
* Fixed **ESC/P printer** not printing text when using a system-wide or custom ROM directory
* Fixed **ESC/P printer** not printing text when using a system-wide or custom ROM folder
* **Storage**
* Added **Panasonic/MKE** CD-ROM interface and drive
* Added **Alcohol 120% MDS** CD-ROM image support

2
_posts/2025-09-14-86box-v5-1.md
View File

@@ -32,7 +32,7 @@ As noted in the [v5.0 release announcement]({% post_url 2025-08-24-86box-v5-0 %}
* Added **input scaling** options to the OpenGL 3.0 Core renderer
* Added saving of **full screen mode** after exiting the emulator
* Added **portable mode** enabled by placing an empty `86box_global.cfg` file next to the Windows executable, macOS app bundle or Linux AppImage
* Added **portable mode** enabled by placing an empty `86box_global.cfg` file next to the Windows executable, Linux AppImage or macOS app bundle
* Fixed keyboard shortcuts with **numpad keys** in full screen mode
* Fixed **command line options** not applying to machines started from the manager
* Fixed `--clear` command line option in its long form

6
_posts/2025-10-26-86box-v5-2.md
View File

@@ -36,7 +36,7 @@ The **IBM PCjr** no longer has a floppy drive controller by default. PCjr setups
Continuing the work [started in v5.1]({% post_url 2025-09-14-86box-v5-1 %}#merged-machines), **3 OEM machines** (listed in the 686 category [below](#machines)) have moved and are now BIOS variant options for their respective base motherboards. As before, configuration and CMOS data is **migrated automatically** upon upgrading to v5.2, and if the machine no longer boots, make sure the **ROM set** is up to date.
On top of that, 5 other machines (listed in the 586 and 686 categories [below](#machines)) have received BIOS updates; however, existing emulated setups will remain on the previous BIOS until an NVRAM wipe is performed, either [through the manager's right-click menu](https://86box.readthedocs.io/en/v5.2/usage/manager.html#machine-list) or by deleting the respective `.bin` file in the machine's `nvr` directory.
On top of that, 5 other machines (listed in the 586 and 686 categories [below](#machines)) have received BIOS updates; however, existing emulated setups will remain on the previous BIOS until an NVRAM wipe is performed, either [through the manager's right-click menu](https://86box.readthedocs.io/en/v5.2/usage/manager.html#machine-list) or by deleting the respective `.bin` file in the machine's `nvr` folder.
### Host system deprecations
@@ -51,7 +51,7 @@ macOS **High Sierra 10.13** and **Mojave 10.14** support is still on track to be
### Emulator
* Slightly improved emulator startup speed through ROM scanning optimizations
* Fixed **OpenGL shader** loading errors and black screens on some host systems
* Fixed **OpenGL shader** loading errors and black screens on some hosts
* Fixed **OpenGL renderer** producing invisible or transparent screenshots
* Fixed compilation from source on hosts with **Qt 6.10**
@@ -119,7 +119,7 @@ macOS **High Sierra 10.13** and **Mojave 10.14** support is still on track to be
* Renamed **HP Vectra VL 5 Series 4** to **Vectra VL 5/xxx Series 4**
* Renamed **Packard Bell PB520R** to **Robin LC**
* Renamed **Packard Bell PB640** to **Thousand Oaks**
* Renamed **Packard Bell Multimedia C110** to **Orlando/2D/2D/MMX**
* Renamed **Packard Bell Multimedia C110** to **Orlando/2D/3D/MMX**
* Renamed **Packard Bell Multimedia M415** to **PB810/820**
* Renamed **Packard Bell Bora Pro** to **Bora/Bora Pro**
* Renamed **Sony Vaio PCV-90** to **PCV-70/90/100/120**