You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2022-01-07-pcem-migration-guide.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,22 +20,22 @@ One aspect commonly used to compare PCem and 86Box is the emulation performance.
20
20
21
21
PCem v15 introduced a rewritten dynamic recompiler, which was primarily aimed at improving emulation performance in games; however, it also caused minor to severe performance regressions in other applications. One example of a regressed application is the (ironically related to a game) **MapEdit** level editor for Wolfenstein 3D, which we measured to lose as much as **85%** emulation speed with the new recompiler on a relatively sensible Pentium 75 setup.
22
22
23
-
On **x86 host systems**, 86Box uses the **previous recompiler** from PCem versions before v15, with optimizations performed by us, as we have determined that the new one causes too many regressions to be adopted as a sensible default. There is a way for you to try out the new recompiler on 86Box, though: go to our [Jenkins](https://ci.86box.net/job/86Box/), find whatever build number you're using ([here's 6130](https://ci.86box.net/job/86Box/6130/artifact/), the release build for v4.2.1) and download the **New Recompiler (beta)** variant that's right for your host operating system.
23
+
On **x86 host systems**, 86Box uses the **previous recompiler** from PCem versions before v15, with optimizations performed by us, as we have determined that the new one causes too many regressions to be adopted as a sensible default. There is a way for you to try out the new recompiler on 86Box, though: go to our [experimental builds page](/builds), find whatever build number you're using ([here's 7600](/builds#7600), the release build for v5.0) and download the **New Recompiler (beta)** variant that's right for your host operating system.
24
24
25
25
On the other hand, **ARM host systems** always use the new recompiler, as the old one has not received an ARM version. It's worth noting both recompiler variants for macOS are **universal binaries**; the old recompiler one automatically switches over to the new recompiler when running on Apple Silicon.
26
26
27
27
### Accuracy is slow
28
28
29
29
PCem's emulation of some core system components, such as the Programmable Interval Timer (PIT), takes a few shortcuts to improve performance. These shortcuts are perfectly fine for games, which is what PCem targets; although, they have caused issues with the software preservation side of things, as we found out with **Microsoft Word 1.0**, the **MR BIOS** and other old pieces of software.
30
30
31
-
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.
31
+
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 handle CPU cache, 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 BIOS cache test errors on some machines")\), but we try to follow what's possible.
32
32
{: #cache}
33
33
34
34
---
35
35
36
-
## Bring your own manager
36
+
## Machine manager
37
37
38
-
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 [**Avalonia 86**](https://github.com/notBald/Avalonia86) or other manager applications developed by the community.
38
+
After years of requests, 86Box v5.0 finally brings a preview for a built-in manager, which allows you to keep and run multiple emulated machine configurations from one place. As with PCem, open 86Box directly to start the manager. You can also use [**Avalonia 86**](https://github.com/notBald/Avalonia86) or other manager applications developed by the community.
39
39
40
40
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.
41
41
@@ -73,7 +73,7 @@ There is **no migration path** for configuration files, as the format is too dif
|[Super 7] FIC VA-503+ | Super Socket 7:<br />[VIA MVP3] FIC VA-503+ | Not to be confused with the FIC VA-503**A**, which has a different southbridge. |
142
+
|[Super 7] FIC VA-503+ | Super Socket 7:<br />[VIA MVP3] FIC VA-503+ | Not to be confused with the FIC VA-503**A**, which is a very different board. |
@@ -182,8 +182,8 @@ The 86Box settings interface is designed to be easy to navigate, though you shou
182
182
183
183
### Sound
184
184
185
-
* There are regular and PnP variants of the **Sound Blaster 16** and **AWE32** cards. You should stick to the regular variants with manual settings, unless you feel like messing with ISA Plug and ~~Pray~~ Play.
186
-
* The **MIDI out device** option is sound card independent; it's located right below the sound card selection box. 86Box also supports MIDI input.
185
+
* There are regular and PnP variants of the **Sound Blaster 16** and **AWE32** cards. When migrating an existing machine, sticking to the regular variants with manual settings is recommended.
186
+
* The **MIDI out device** option is sound card independent; it's located right below the sound card selection boxes. 86Box also supports MIDI input.
187
187
* The **OPL emulator** option is named **FM synth driver**, with a selection of NukedOPL for accuracy or YMFM for performance.
188
188
* The **LPT device** option is in the **Ports (COM & LPT)** page, as 86Box supports more devices (such as printers) connected to up to 4 parallel ports.
189
189
@@ -193,17 +193,17 @@ The 86Box settings interface is designed to be easy to navigate, though you shou
193
193
* Floppy drives in the **Floppy & CD-ROM drives** page;
194
194
* Hard drives in the **Hard disks** page;
195
195
* CD-ROM drives in the **Floppy & CD-ROM drives** page;
196
-
* Iomega Zip drives (86Box adds Zip 250 support) in the **Other removable devices** page;
196
+
* Iomega Zip drives (86Box adds Zip 250 support) as removable disks in the **Other removable devices** page;
197
197
* 86Box adds magneto-optical drives also in the **Other removable devices** page.
198
198
* IDE drives are represented by a channel:device index, instead of a drive index or location like "Primary Master". See [our documentation](https://86box.readthedocs.io/en/v5.0/settings/hdd.html#adding-a-new-disk) for more information.
199
-
* IDE channels 2 and 3 correspond to [tertiary and quaternary IDE controllers](https://86box.readthedocs.io/en/v5.0/hardware/ideterqua.html), which can be added through the **Storage controllers** page. PnP Sound Blaster cards also claim the quaternary channel for their integrated IDE.
199
+
* IDE channels 2 and 3 correspond to [tertiary and quaternary IDE controllers](https://86box.readthedocs.io/en/v5.0/hardware/ideterqua.html), which can be added through the **Storage controllers** page. PnP Sound Blaster cards with IDE capability also claim the quaternary channel.
200
200
* 86Box supports using IDE and SCSI simultaneously. IDE is automatically enabled on machines with it, and up to 4 SCSI controllers can be installed through the **Storage controllers** page.
201
201
* The **CD Model** and **CD Speed** options are configurable for each individual drive in the **Floppy & CD-ROM drives** page, as **Type** and **Speed** respectively.
202
202
203
203
### Input
204
204
205
205
* 86Box can emulate serial and PS/2 mice with **three buttons** or a **scroll wheel**. This functionality can be enabled through the **Configure** button next to the mouse selection box.
206
-
* The **4-axis 4-button** joystick allows for a more modern control scheme (if supported by the emulated software), which takes advantage of all 4 axes and 4 buttons that the game port provides.
206
+
* The **4-axis 4-button** joystick allows for a more modern control scheme (if supported by the emulated software), which takes advantage of all 4 axes and 4 buttons that the game port provides. More joystick models are also available.
207
207
208
208
### Network
209
209
@@ -216,7 +216,7 @@ The 86Box settings interface is designed to be easy to navigate, though you shou
216
216
217
217
## User interface
218
218
219
-
The 86Box user interface should look familiar to PCem users, with two main differences: the menu layout and the status bar. The [menu bar](https://86box.readthedocs.io/en/v5.0/usage/menubar.html)had some options moved to the **Settings** window, and media controls moved to the **Media menu**. The [status bar](https://86box.readthedocs.io/en/v5.0/usage/statusbar.html) contains activity indicators, with the same controls as the Media menu also being accessible by clicking the icons. While we don't have the **Machine** window, most of what it provides on PCem is accessible through the title bar, menu bar and status bar on 86Box.
219
+
The 86Box user interface has a lot more going on. The [menu bar](https://86box.readthedocs.io/en/v5.0/usage/menubar.html)contains some options, while others are in the **Settings** window, and media controls are found in the **Media menu**. The [toolbar](https://86box.readthedocs.io/en/v5.0/usage/toolbar.html) contains shortcuts for common actions and the emulation speed indicator. The [status bar](https://86box.readthedocs.io/en/v5.0/usage/statusbar.html) contains indicators for activity, keyboard lock lights and display refresh rate, with the same controls as the Media menu also being accessible by clicking the media icons. While we don't have the **Machine** window, a lot of what it provides is accessible through other means on 86Box.
220
220
221
221
{% include image.html url="/assets/images/pcem-migration/media.png" description="Media controls through the Media menu and status bar." %}
222
222
@@ -226,17 +226,17 @@ As of 86Box v5.0, the key combination to release mouse capture is the same **Ctr
226
226
227
227
## Media
228
228
229
-
86Box is quite a bit different in the media department as well. More disk image formats are supported, including our own [**86F**](https://86box.readthedocs.io/en/v5.0/dev/formats/86f.html) format for floppy bitstream images. Unlimited hard drives (the controllers are the limit) and up to 4 removable drives of **each type** (floppy, CD-ROM, Zip, MO) can be installed, with each removable drive getting its own entry on the **Media menu** and **status bar**.
229
+
86Box is quite a bit different in the media department as well. More disk image formats are supported, including our own [**86F**](https://86box.readthedocs.io/en/v5.0/dev/formats/86f.html) format for floppy bitstream images. Unlimited hard drives (the controllers are the limit) and up to 4 removable drives of **each type** (floppy, CD-ROM, removable disk, MO) can be installed, with each removable drive getting its own entry on the **Media menu** and **status bar**.
230
230
231
231
### Limited host CD-ROM passthrough
232
232
233
233
86Box currently supports the use of a host CD-ROM drive on **Windows hosts only**, with more platforms coming soon.
234
234
235
-
For other platforms, we recommend ripping your discs to `.cue` + `.bin`, as that format preserves the sector mode, audio tracks and other information that `.iso` doesn't. 86Box also supports `.cue` images with audio tracks in `.wav`, `.mp3` and other encapsulated or compressed formats.
235
+
For other platforms, we recommend ripping your discs to `.cue` + `.bin` or **unencrypted**`.mds` + `.mdf`, as those formats preserve the sector mode, audio tracks and other information that `.iso` doesn't. 86Box also supports `.cue` images with audio tracks in `.wav`, `.mp3` and other encapsulated or compressed formats.
236
236
237
-
### Zip 250 and MO
237
+
### Removable disks and MO
238
238
239
-
86Box supports **Iomega Zip 250** disks, which require Zip 250 support to be enabled at a drive level in the **Other removable devices** settings page. **Magneto-optical** (MO) is also supported, as another removable medium which provides more storage than Zip disks: up to 1.3 GB per cartridge.
239
+
On top of the Iomega Zip 100, 86Box supports **Zip 250**and **generic removable disks**, which can be set as removable disk drive models in the **Other removable devices** settings page. **Magneto-optical** (MO) is also supported, as another removable medium which provides more storage than Zip disks: up to 1.3 GB per cartridge.
0 commit comments