From af19a1524ed0cea37eabfece7d6ce4722a4b7dd9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Hrdli=C4=8Dka?= Date: Tue, 10 Jul 2018 19:35:47 +0200 Subject: [PATCH] Update FAQ --- faq.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/faq.md b/faq.md index 8eacd18..85c57ff 100644 --- a/faq.md +++ b/faq.md @@ -2,6 +2,8 @@ Frequently asked questions ========================== _Please note that this page is a work in progress._ -> Which came first: the chicken or the egg? +> How is 86Box different from applications like VirtualBox or Virtual PC? -The egg. \ No newline at end of file +VirtualBox, Virtual PC and similar applications are _virtualizers_. They monitor running virtual machines and only modify running instructions when it is required to enforce the separation of a virtual machine from the rest of the system. They also implement peripherals that are custom designed to let the guest take full potential of the virtualizer as long as appropriate drivers, which are distributed with the provided _additions_, are installed. Because of the way virtualizers work, they are tied to a specific CPU architecture. + +On the other side, 86Box is an _low-level emulator_. It implements a whole system in software, which includes the CPU, chipset and additional cards, if any. Emulators interpret every single instruction running in the virtual machine, which allows them to run on incompatible CPU architectures. Furthermore, 86Box emulates peripherals that have actually existed, which makes it possible to use drivers that are already available. On the other side, these components haven't been designed to work in virtual environment, therefore it is not possible to offer advanced features such as mouse pointer integration or shared folders without custom drivers. \ No newline at end of file