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

Random updates

Browse Source
This commit is contained in:
RichardG867
2020-08-12 21:56:17 -03:00
parent 0326e043a1
commit 0caf6fd13f
6 changed files with 15 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
dev/builds.rst
View File

@@ -25,7 +25,9 @@ Optimized
Optimized builds (**86Box-Optimized**) are :ref:`standard builds <dev/builds:Standard>` which have been optimized for use with a specific CPU family on the host machine. These provide slight performance improvements, especially on older or low-end hosts; however, the aggressive optimizations employed **may result in bugs** not present on standard builds.
There are many different optimized binaries available for each build; you must download the **correct one for your host CPU**, otherwise, 86Box will run poorly or even crash. The table below lists most CPUs currently supported by optimized builds, along with the respective binaries you should use with them, as well as their codenames (as shown on an identification tool such as `CPU-Z <http://www.cpuid.com/softwares/cpu-z.html>`_):
There are many different optimized binaries available for each build, with each one corresponding to a CPU family. The table below lists most CPUs currently supported by optimized builds, along with the respective binaries you should use with them, as well as their codenames (as shown on an identification tool such as `CPU-Z <http://www.cpuid.com/softwares/cpu-z.html>`_).
.. note:: Using the wrong optimized binary for your CPU will result in poor performance and/or crashes.
.. raw:: html

4
hardware/diskimages.rst
View File

@@ -56,14 +56,14 @@ Supported formats:
+--------------------+--------------+
||86f| |.86f |
+--------------------+--------------+
|Formatted Disk Image|.fdi |
+--------------------+--------------+
|CopyQM |.cqm |
+--------------------+--------------+
|DiskDupe |.ddi |
+--------------------+--------------+
|EZ-DisKlone Plus |.fdf |
+--------------------+--------------+
|Formatted Disk Image|.fdi |
+--------------------+--------------+
|HxC MFM |.mfm |
+--------------------+--------------+
|ImageDisk |.imd |

2
hardware/ideterqua.rst
View File

@@ -16,7 +16,7 @@ The following resources are used by these additional controllers:
|Quaternary|01E8h |03EEh |11 |
+----------+-------------+---------------+---+
These controllers are not Plug and Play compliant. If the emulated machine supports ISA PnP or PCI, remember to mark the IRQ(s) as being used by a legacy ISA device in the BIOS setup utility.
These controllers are not Plug and Play compliant. If the emulated machine supports Plug and Play (through ISA, PCI or other means), remember to mark the IRQ(s) as being used by a legacy ISA device in the BIOS setup utility.
.. 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.

4
hardware/machinespecific.rst
View File

@@ -10,7 +10,7 @@ This page contains important notes related to specific machine models emulated b
.. 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.
* The IBM Personal Computer Diagnostics disks will produce a *0152 ERROR - SYSTEM BOARD* code if :ref:`time synchronization <settings/machine:Time synchronization>` is enabled, due to a lack of Y2K compliance. This code can be cleared by disabling time synchronization, then clearing the CMOS by deleting ``ibmat.nvr`` from the ``nvr`` directory.
Socket 7
--------
@@ -89,7 +89,7 @@ Footnotes
Some machines may have faulty or otherwise incomplete `Advanced Configuration and Power Interface <https://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface>`_ implementations in their BIOSes, symptoms of which include:
* Windows 2000 and higher will install the "Standard PC" HAL, which does not enable ACPI features such as soft power off and suspend to RAM;
* Windows 2000 and higher will install the "Standard PC" HAL, which does not enable ACPI features such as soft power off and sleep mode;
* Booting an existing Windows installation with the ACPI HAL will result in a STOP 0x000000A5 blue screen;
* Booting Windows Vista or 7 (which require ACPI) will also result in a STOP 0x000000A5 blue screen, or a Windows Boot Manager 0xc0000225 error.

2
hardware/network.rst
View File

@@ -50,7 +50,7 @@ The following advanced features can be accessed by directly editing the virtual
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.
All emulated network cards store their MAC address in the ``mac`` directive of their respective 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

8
settings/peripherals.rst
View File

@@ -51,10 +51,14 @@ The following information is displayed on the status bar (from left to right) wh
POST card
---------
Emulate a diagnostic POST card, which displays I/O port 80h POST code values on the status bar. The leftmost hexadecimal value is the most recent POST code reported, while the rightmost value is the second most recent code, like on a real dual-display POST card. A value of ``--`` indicates that no POST code has been reported yet.
Emulate a diagnostic POST card, which displays POST code values issued by the emulated machine's BIOS on the status bar. The leftmost hexadecimal value is the most recent POST code reported, while the rightmost value is the second most recent code, like on a real dual-display POST card. A value of ``--`` indicates that no POST code has been reported yet.
Some machines use a different I/O port for POST codes: port 0680h on Micro Channel Architecture-based machines, or port 90h on non-MCA-based IBM PS/2 machines.
The POST card will automatically use the correct diagnostic I/O port for the emulated machine:
* Port 80h on the IBM AT, clones and the XT-based Xi 8088;
* Port 84h on early Compaq machines;
* Port 0190h on IBM PS/1 and PS/2 machines not based on Micro Channel Architecture;
* Port 0680h on Micro Channel Architecture machines.
.. note:: Some guest operating systems (such as Linux before kernel 3.0) rely heavily on the first DMA extra page register, which is shared with the POST card. If you notice the POST code display is flickering and the emulation speed has decreased drastically, try disabling the POST card.