mirror/86Box-docs
1
0
Fork 0
mirror of https://github.com/86Box/docs.git synced 2026-02-27 17:34:26 -07:00
Code Issues Packages Projects Releases Wiki Activity

Move hardware usage pages to their own category

Browse Source
This commit is contained in:
RichardG867
2020-08-05 20:10:06 -03:00
parent a502e7d2f5
commit 026e3c47f2
14 changed files with 95 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

106
usage/diskimages.rst
View File

@@ -1,106 +0,0 @@
Disk images
===========
86Box supports a large variety of disk image formats for the emulated drives.
Hard disk images
----------------
Supported formats:
+---------------------+--------------+
|Format |File extension|
+=====================+==============+
|**Raw image** |Many * |
+---------------------+--------------+
|Japanese FDI |.hdi |
+---------------------+--------------+
|:doc:`../formats/hdx`|.hdx |
+---------------------+--------------+
|Virtual Hard Disk |.vhd |
+---------------------+--------------+
\* Raw images come in many extensions, including: img ima
Floppy disk images
------------------
Supported formats:
+---------------------+--------------+
|Format |File extension|
+=====================+==============+
|**Raw image** |Many * |
+---------------------+--------------+
|:doc:`../formats/86f`|.86f |
+---------------------+--------------+
|Formatted Disk Image |.fdi |
+---------------------+--------------+
|CopyQM |.cqm |
+---------------------+--------------+
|DiskDupe |.ddi |
+---------------------+--------------+
|EZ-DisKlone Plus |.fdf |
+---------------------+--------------+
|HxC MFM |.mfm |
+---------------------+--------------+
|ImageDisk |.imd |
+---------------------+--------------+
|Japanese FDI |.fdi |
+---------------------+--------------+
|PCjs JSON |.json |
+---------------------+--------------+
|Teledisk |.td0 |
+---------------------+--------------+
\* Raw images come in many extensions, including: img ima flp vfd
Floppy disk detection
^^^^^^^^^^^^^^^^^^^^^
86Box determines the physical media format (sides, tracks per side, sectors per track, bytes per sector) of a floppy disk image through the following methods:
1. Image file header data - not applicable for **Raw** and **DiskDupe** formats;
2. `DOS BIOS Parameter Block <https://en.wikipedia.org/wiki/BIOS_parameter_block>`_ data within the image;
3. If all else fails, a guess is made based on the image file's size.
The BIOS Parameter Block detection method may behave incorrectly with non-DOS floppy disks. Installation floppies for UNIX and Linux are common examples of non-DOS disks. Disabling :ref:`Check BPB <settings/floppycdrom:Floppy drives>` is strongly recommended for accessing these, as an inaccurate BPB detection may result in read errors, data corruption and other issues.
.. note:: When using a **Raw** image of a non-DOS floppy with Check BPB disabled, make sure the image file is not truncated (smaller than its media size), otherwise incorrect behavior may still occur.
MO / ZIP removable disk images
------------------------------
Supported formats:
+---------------------+--------------+
|Format |File extension|
+=====================+==============+
|**Raw image** |Many * |
+---------------------+--------------+
|Japanese FDI |.mdi (MO) |
| +--------------+
| |.zdi (ZIP) |
+---------------------+--------------+
\* Raw images come in many extensions, including: img ima
CD-ROM / DVD-ROM optical disc images
------------------------------------
Supported formats:
+---------------------+--------------+
|Format |File extension|
+=====================+==============+
|Cue sheet |.cue + .bin |
+---------------------+--------------+
|ISO |.iso |
+---------------------+--------------+
CD audio
^^^^^^^^
Compact Disc Digital Audio (CDDA) is supported on **Cue sheet** images. CD audio playback is muted on all emulated CD-ROM drives by default; it can be unmuted by unchecking the *Mute* option for the respective drive on the :ref:`status bar <usage/statusbar:|cdrom| |nbsp| CD-ROM drives>` or the :ref:`Media menu <usage/menubar:Media>`.
.. note:: Only raw format (.bin) tracks are supported. Compressed or otherwise encapsulated audio tracks (.wav, .mp3, .ogg, .flac and other formats) are not supported.

76
usage/ideterqua.rst
View File

@@ -1,76 +0,0 @@
Tertiary and quaternary IDE
===========================
The additional tertiary and quaternary IDE controllers, enabled through the :ref:`settings/peripherals:Tertiary / Quaternary IDE Controller` settings, are not supported by all BIOSes and may require manual configuration of guest operating systems. The specific details are outlined on this page.
The following system resources are used by these additional controllers:
.. _table:
+----------+-------------+---------------+---+
|Channel |Main I/O port|Status I/O port|IRQ|
+==========+=============+===============+===+
|Tertiary |0168h |036Eh |10 |
+----------+-------------+---------------+---+
|Quaternary|01E8h |03EEh |11 |
+----------+-------------+---------------+---+
.. note:: While the IRQ for each channel can be changed through its respective *Settings* button on :ref:`settings/peripherals:Tertiary / Quaternary IDE Controller`, many operating systems do not allow legacy (ISA or VLB) IDE controllers to use custom IRQs.
BIOS support
------------
The tertiary and quaternary channels are both not visible and not bootable in any BIOS, with the exception of **MR BIOS version 3**, which provides full support for them, including bootability and INT 13h services.
DOS and real mode
-----------------
DOS and other real mode operating systems rely on the BIOS-provided INT 13h services to access hard disks. These are only provided for the tertiary and quaternary channels by **MR BIOS version 3**, as mentioned above.
Windows 95, 98 and Me
---------------------
The Windows 9x family will only detect and enable both additional channels during installation :ref:`if the BIOS supports them <usage/ideterqua:BIOS support>`. Each additional channel can be enabled after installation through the following procedure:
1. Go to the *Add New Hardware* control panel.
2. Add a *Standard IDE/ESDI Hard Disk Controller* from the *Hard disk controllers* category.
3. Don't restart the system when asked to.
4. Go to the *Device Manager* tab of the *System* control panel.
5. Select the newly-added *Standard IDE/ESDI Hard Disk Controller* device from the *Hard disk controllers* category and click *Properties*.
6. Go to the *Resources* tab.
7. Select *Basic configuration 4* in the *Settings based on* box.
8. Change the resource settings to match the :ref:`table above <table>`. The first *Input/Output Range* range corresponds to the **main** I/O port, the second one corresponds to the **status** I/O port, and *Interrupt Request* corresponds to the IRQ.
* The status I/O port range is off by 6 units. Select 0368 for the tertiary channel or 03E8 for the quaternary channel.
* The image below shows an example configuration for the tertiary channel.
9. If both the tertiary and quaternary channels are enabled, repeat the steps above to add the other channel.
.. image:: images/ideterqua_win98.png
:align: center
Windows NT, 2000 and XP
-----------------------
The Windows NT 4 and 5 families will automatically detect and enable both additional channels during installation, regardless of BIOS support. This auto-detection does not, however, work on machines with **Award BIOS**, except for the version which identifies itself as *Phoenix - AwardBIOS v6.00PG*, where it does work.
.. note:: If you install the system to a hard disk on one of the additional channels, it will not be bootable if the BIOS doesn't support booting from these channels.
On Windows 2000 only, the additional channels can be enabled after the system is installed through *Add New Hardware* similarly to Windows 95/98/Me above, although the I/O ports and IRQ cannot be changed. *Basic configuration 0003* corresponds to the **tertiary** channel, while *Basic configuration 0002* corresponds to the **quaternary** channel.
Windows Vista and 7
-------------------
The Windows NT 6 family does not support legacy non-Plug-and-Play IDE controllers, and therefore cannot use the additional channels as currently implemented in 86Box.
Linux
-----
On kernels 2.6.19 and newer (after the switch to ``libata``), run the ``modprobe pata_legacy probe_all=1`` command as root to enable both additional channels. Consult your distribution's documentation on how to load that module on startup.
On kernels older than 2.6.19 (before the switch to ``libata``), add the following parameters to the kernel command line to enable their respective channels:
* **Tertiary:** ``ide2=0x168,0x36e,10`` (assuming IRQ 10)
* **Quaternary:** ``ide3=0x1e8,0x3ee,11`` (assuming IRQ 11)
.. note:: Some Linux distributions may automatically detect and enable both additional channels, however, that is very rarely the case.

BIN
usage/images/ideterqua_win98.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 5.2 KiB

71
usage/machinespecific.rst
View File

@@ -1,71 +0,0 @@
Machine-specific notes
======================
This page contains important notes related to specific machine models emulated by 86Box.
80286
-----
.. rubric:: IBM AT
* The diagnostics diskette is not Y2K-compliant, and will therefore produce error codes if :ref:`settings/machine:time synchronization` is enabled. These codes can be cleared by disabling time synchronization and then using a tool such as the MS-DOS ``date`` command to set the date to before the year 2000.
Socket 7
--------
.. _p65up5:
.. rubric:: ASUS P/I-P65UP5 (C-P55T2D)
* Modular motherboard, consisting of a **P/I-P65UP5** baseboard and one of the following CPU cards:
* **C-P55T2D:** Socket 7 with Intel 430HX northbridge.
* **C-P6ND:** Socket 8 with Intel 440FX northbridge.
* **C-PKND:** Slot 1 with Intel 440FX northbridge.
* While the northbridge depends on the selected CPU card, the southbridge always remains the Intel PIIX3, as it is located on the baseboard.
* The real CPU cards support dual CPUs. As 86Box does not emulate multiprocessing, only a single CPU will be present.
* Due to a lack of I/O APIC emulation at the moment, 86Box will patch the MultiProcessor Specification tables out of RAM during boot, so that operating systems will not hang or exhibit other erratic behavior due to the missing I/O APIC.
Socket 8
--------
.. rubric:: ASUS P/I-P65UP5 (C-P6ND)
See: :ref:`p65up5`
Slot 1
------
.. rubric:: ASUS P/I-P65UP5 (C-PKND)
See: :ref:`p65up5`
.. _atc6310bxii:
.. rubric:: A-Trend ATC6310BXII
* Equipped with the SMSC Victory66 southbridge instead of the regular Intel PIIX4E.
* The Victory66 has faster IDE - up to Ultra ATA/66 as opposed to the PIIX4E's Ultra ATA/33 - and a different USB controller.
* Drivers for Windows 95, 98, Me and 2000 are available `here <http://www.attro.com/download/driver/IDE/90e66smsc.zip>`_ (TODO: mirror this). Windows XP, Vista and 7 include drivers out of the box.
Slot 2
------
.. rubric:: Gigabyte GA-6GXU
* The BIOS display will corrupt itself during the memory test if the maximum of 2048 MB RAM is selected. This is a visual glitch which does not otherwise negatively impact the machine.
Socket 370
----------
.. rubric:: A-Trend ATC7020BXII
See: :ref:`atc6310bxii`
.. rubric:: AEWIN AW-O671R
* Equipped with dual Winbond W83977EF Super I/O chips driving four serial (COM1-COM4) and two parallel (LPT1-LPT2) ports.
* The I/O ports and IRQs used by all these ports can be configured in the BIOS setup.
* ACPI is disabled by default, unlike other machines with Award v6.00PG BIOS. It can be enabled through the *ACPI function* option of the *Power Management Setup* menu on the BIOS setup.

83
usage/network.rst
View File

@@ -1,83 +0,0 @@
Networking
==========
86Box supports two connection modes for the :doc:`emulated network cards <../settings/network>`. The specific details on these connection modes and network emulation as a whole are outlined on this page.
SLiRP
-----
SLiRP creates a private network with a virtual router, allowing the emulated machine to reach the host, its network and the Internet; on the other hand, the host and other devices on its network cannot reach the emulated machine, unless :ref:`port forwarding <usage/network:SLiRP port forwarding>` is configured. This is similar to the **NAT** mode on other virtualizers.
The virtual router provides automatic IP configuration to the emulated machine through DHCP. If that is not an option, use the following static IP settings:
* **IP address:** 10.0.2.15
* **Subnet mask:** 255.255.255.0
* **Default gateway:** 10.0.2.2
* **DNS server:** 10.0.2.3
The host can be reached through IP address 10.0.2.2, while other devices on the host's network can be reached through their normal IP addresses.
.. note:: SLiRP is only capable of routing TCP and UDP traffic. Other protocols such as IPX and NetBEUI can only be used with :ref:`usage/network:PCap` networking.
PCap
----
PCap connects directly to one of the host's network adapters. The emulated machine must be configured as if it were a real machine on your network. This is similar to the **Bridge** mode on other virtualizers.
This mode requires `Npcap <https://nmap.org/npcap/>`_ (or another WinPcap-compatible driver) to be installed on the host. Only **wired Ethernet network connections** are compatible; Wi-Fi and other connections will not work at all, as they do not allow PCap to listen for packets bound to the emulated machine.
Private PCap network
^^^^^^^^^^^^^^^^^^^^
If you have an incompatible network connection (such as Wi-Fi), or if you wish to connect the emulated machine to the host without also connecting it to your network, a private network can be created with PCap in one of two ways:
* Install and configure the *Microsoft KM-TEST Loopback Adapter* included with Windows.
* Guides on how to install this adapter are available online.
* The adapter alone only provides a direct connection to the host, with no DHCP server, therefore requiring manual IP configuration on both the host and the emulated machine.
* Windows' *Internet Connection Sharing* feature can be used to connect the emulated machine to the host's network and the Internet, with DHCP for automatic IP configuration, similarly to SLiRP but with the added benefit that the host can reach the emulated machine without port forwarding.
* If VMware is installed, use one of the VMnet adapters included with it.
* VMnet1 (host-only) connects to the host only.
* VMnet8 (NAT) connects to the host, its network and the Internet.
Advanced features
-----------------
The following advanced features can be accessed by directly editing the virtual machine configuration file, which is ``86box.cfg`` by default.
MAC address
^^^^^^^^^^^
All emulated network cards store their MAC address in the ``mac`` directive of the card's configuration file section. Only the suffix (last three octets) of the MAC address is stored; the prefix (first three octets) will always be the card manufacturer's `OUI <https://en.wikipedia.org/wiki/Organizationally_unique_identifier>`_, such as 00:E0:4C for Realtek.
.. rubric:: Example: MAC address 00:E0:4C:35:F4:C2 for the Realtek RTL8029AS
.. code-block:: none
[Realtek RTL8029AS]
mac = 35:f4:c2
SLiRP port forwarding
^^^^^^^^^^^^^^^^^^^^^
Port forwarding allows the host and other devices on its network to access TCP and UDP servers running on the emulated machine. This feature is configured through the ``[SLiRP Port Forwarding]`` section of the configuration file.
Each port forward must be assigned a number, starting at 0 and counting up (skipping a number will result in all subsequent port forwards being ignored), which replaces ``X`` on the following directives:
* ``X_udp``: If this directive is missing or set to 0, forward a TCP port. If set to 1, forward an UDP port.
* ``X_from``: Port number on the host.
* ``X_to``: Port number on the emulated machine. If this directive is missing, use the same port number as the host.
The host can access forwarded ports through 127.0.0.1 or its own IP address, while other devices on the network can access them through the host's IP address.
.. rubric:: Example: forward host TCP port 8080 to guest port 80, and host UDP port 5555 to guest port 5555
.. code-block:: none
[SLiRP Port Forwarding]
0_from = 8080
0_to = 80
1_udp = 1
1_from = 5555

8
usage/statusbar.rst
View File

@@ -28,7 +28,7 @@ The status bar located at the bottom of the 86Box window provides icons related
A 3.5" or 5.25" floppy icon will appear for each configured :ref:`floppy drive <settings/floppycdrom:Floppy drives>`.
* **New image:** create a new disk image file. Opens the *New Image* window, which lets you select the image size and where to save the file.
* **Existing image:** insert a :ref:`disk image file <usage/diskimages:Floppy disk images>` into this drive.
* **Existing image:** insert a :ref:`disk image file <hardware/diskimages:Floppy disk images>` into this drive.
* **Existing image (Write-protected):** insert a disk image file into this drive as a read-only disk.
* **Export to 86F:** convert the currently-inserted disk image file to 86Box's :doc:`../formats/86f` surface image format. You will be asked where to save the converted file.
* **Eject:** remove the currently-inserted disk from this drive.
@@ -38,10 +38,10 @@ A 3.5" or 5.25" floppy icon will appear for each configured :ref:`floppy drive <
A CD icon will appear for each configured :ref:`CD-ROM drive <settings/floppycdrom:CD-ROM drives>`.
* **Mute:** mute any :ref:`usage/diskimages:CD audio` played through this drive. **CD audio is muted by default on all drives.**
* **Mute:** mute any :ref:`hardware/diskimages:CD audio` played through this drive. **CD audio is muted by default on all drives.**
* **Empty:** remove any disc inserted into this drive.
* **Reload previous image:** reinsert the last disc image file selected through the *Image* option.
* **Image:** insert a :ref:`CD-ROM or DVD-ROM disc image file <usage/diskimages:CD-ROM / DVD-ROM optical disc images>` into this drive.
* **Image:** insert a :ref:`CD-ROM or DVD-ROM disc image file <hardware/diskimages:CD-ROM / DVD-ROM optical disc images>` into this drive.
|zip| |mo| |nbsp| ZIP and MO drives
-----------------------------------
@@ -49,7 +49,7 @@ A CD icon will appear for each configured :ref:`CD-ROM drive <settings/floppycdr
A ZIP or MO icon will appear for each configured :doc:`additional removable storage drive <../settings/removable>`.
* **New image:** create a new disk image file. Opens the *New Image* window, which lets you select the image size and where to save the file.
* **Existing image:** insert a :ref:`disk image file <usage/diskimages:MO / ZIP removable disk images>` into this drive.
* **Existing image:** insert a :ref:`disk image file <hardware/diskimages:MO / ZIP removable disk images>` into this drive.
* **Existing image (Write-protected):** insert a disk image file into this drive as a read-only disk.
* **Eject:** remove the currently-inserted disk from this drive.
* **Reload previous image:** reinsert the last disk image file selected through the *Existing image* options.