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
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,28 +35,28 @@ In addition to taking fewer shortcuts, 86Box also tries to follow the specificat
35
35
36
36
## Bring your own 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 our [**86Box Manager**](https://github.com/86Box/86BoxManager) or other manager applications developed by the community, which provide at least basic configuration management.
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.
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
42
42
---
43
43
44
44
## Machine list
45
45
46
-
86Box has most of the machines PCem emulates, though we have removed, renamed and/or recategorized some of them for various reasons. The table below (make sure to scroll down) provides a reference for **v4.2**.
46
+
86Box has most of the machines PCem emulates, though we have removed, renamed and/or recategorized some of them for various reasons. The table below (make sure to scroll down) provides a reference for **v5.0**.
47
47
48
48
<divclass="scroll td2nowrap"markdown="block">
49
49
50
50
| PCem name | 86Box category and name | Notes |
51
51
|-----------|-------------------------|-------|
52
52
|[8088] AMI XT clone | 8088:<br />[8088] AMI XT clone ||
53
-
|[8088] Atari PC3 |- | Not implemented due to its undocumented Atari ST-based bus mouse. |
53
+
|[8088] Atari PC3 |8088:<br />[8088] Atari PC 3 | As with PCem, the Atari bus mouse and other on-board devices are not emulated. |
54
54
|[8088] Compaq Portable Plus | 8088:<br />[8088] Compaq Portable ||
|[8088] IBM PC | 8088:<br />[8088] IBM PC (1981/1982) | The 1981 and 1982 variants have [different BIOS versions and memory size limits](https://86box.readthedocs.io/en/v4.2/hardware/machinespecific.html#ibmpc). |
57
+
|[8088] IBM PC | 8088:<br />[8088] IBM PC (1981/1982) | The 1981 and 1982 variants have [different BIOS versions and memory size limits](https://86box.readthedocs.io/en/v5.0/hardware/machinespecific.html#ibmpc). |
58
58
|[8088] IBM PCjr | 8088:<br />[8088] IBM PCjr ||
59
-
|[8088] IBM XT | 8088:<br />[8088] IBM XT (1982/1986) | The 1982 and 1986 variants have [different BIOS versions and memory size limits](https://86box.readthedocs.io/en/v4.2/hardware/machinespecific.html#ibmxt). |
59
+
|[8088] IBM XT | 8088:<br />[8088] IBM XT (1982/1986) | The 1982 and 1986 variants have [different BIOS versions and memory size limits](https://86box.readthedocs.io/en/v5.0/hardware/machinespecific.html#ibmxt). |
60
60
|[8088] Juko XT clone | 8088:<br />[8088] Juko ST ||
61
61
|[8088] Leading Edge Model M | - | Not implemented yet. |
62
62
|[8088] NCR PC4i | 8088:<br />[8088] NCR PC4i | 86Box emulates the NCR Graphics Adapter (NGA) that went with this machine. |
@@ -66,7 +66,7 @@ There is **no migration path** for configuration files, as the format is too dif
|[386DX] IBM PS/2 Model 70 (type 3) | i386DX: [MCA] IBM PS/2<br />model 70 (type 3) ||
@@ -195,8 +195,8 @@ The 86Box settings interface is designed to be easy to navigate, though you shou
195
195
* CD-ROM drives in the **Floppy & CD-ROM drives** page;
196
196
* Iomega Zip drives (86Box adds Zip 250 support) in the **Other removable devices** page;
197
197
* 86Box adds magneto-optical drives also in the **Other removable devices** page.
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/v4.2/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/v4.2/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.
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.
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
@@ -207,7 +207,7 @@ The 86Box settings interface is designed to be easy to navigate, though you shou
207
207
208
208
### Network
209
209
210
-
* 86Box supports three networking modes, detailed in [our documentation](https://86box.readthedocs.io/en/v4.2/hardware/network.html):
210
+
* 86Box supports three networking modes, detailed in [our documentation](https://86box.readthedocs.io/en/v5.0/hardware/network.html):
211
211
***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).
212
212
***SLiRP** behaves just like PCem's private network, with **port forwarding** available as an added advanced feature.
213
213
***VDE** (not available on Windows) can create a virtual network connecting 86Box instances, other emulators and real network interfaces.
@@ -216,17 +216,17 @@ 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/v4.2/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/v4.2/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 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.
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
223
-
Note that the key combination to release mouse capture on 86Box is**F8+F12** on Windows hosts, 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](#input) is configured.
223
+
As of 86Box v5.0, the key combination to release mouse capture is the same**Ctrl+End**as PCem on all host operating systems; previous 86Box versions used F8+F12 on Windows hosts. You can also use the middle mouse button to release capture (unless a [three-button or wheel mouse](#input) is configured) and even [customize the keyboard shortcuts](https://86box.readthedocs.io/en/v5.0/settings/input.html#key-bindings) for mouse release and several other emulator functions.
224
224
225
225
---
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/v4.2/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, Zip, MO) can be installed, with each removable drive getting its own entry on the **Media menu** and **status bar**.
0 commit comments