xt-sys/website
xt-sys/website
2
1
Fork 1
Code Issues Pull Requests Actions Activity

Update FAQ

Browse Source
This commit is contained in:
Rafal Kupiec 2024-06-17 16:29:34 +02:00
parent b739163dc3
commit 544d0815d0
Signed by: belliash
GPG Key ID: 4E829243E0CFE6B4
1 changed files with 24 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
content/faq.md
View File

@ -20,6 +20,15 @@ symbolize dynamism, progress, and forward motion. The smooth curves suggest a se
colors represent diversity and adaptability. All of this convey a message of innovation, user-friendliness, and
adaptability. It invites users to explore a new operating system that promises a seamless computing experience.
#### What is the difference between XTOS and ExectOS?
XTOS is a common name of the Operating System standard based on the XT architecture. ExectOS is a name of the specific
project, that is a reference XTOS implementation, that implements all requirements from a corresponding specification.
#### What does XT mean?
XT is a name of XTOS architecture of an Operating System, that consists of two main components, user mode and kernel
mode. It derives mostly from NT™ architecture, as well as uses a couple of ideas from other open source projects.
XT is a short for "neXTgen" architecture, but you can also call it "eXTendable".
#### What architectures does ExectOS support?
ExectOS supports the x86_64 (sometimes called AMD64 or EM64T), as well as i686 CPU architectures. However, it requires
a modern EFI enabled hardware, thus it is not possible currently to boot ExectOS on a legacy BIOS.
@ -31,16 +40,16 @@ corresponding standard (eg. DOS, or POSIX). This means that running Windows appl
some time. However development is mostly focused on providing system core at the moment.
#### Is ExectOS another Unix based OS?
No. ExectOS implements the XT architecture which derives from NT architecture. It is modular, and consists of two main
layers: microkernel and user mode. Its' kernel mode has full access to the hardware and system resources and runs code
in a protected memory area. It consists of executive services, which is itself made up on many modules that do specific
tasks, a kernel and drivers. Unlike the NT, system does not feature a separate Hardware Abstraction Layer (HAL) between
the physical hardware and the rest of the OS. Instead, XT architecture integrates a hardware specific code with the
kernel.
No. ExectOS implements the XT architecture which derives from NT™ architecture. It is modular, and consists of
two main layers: microkernel and user mode. Its' kernel mode has full access to the hardware and system resources and
runs code in a protected memory area. It consists of executive services, which is itself made up on many modules that
do specific tasks, a kernel and drivers. Unlike the NT™, system does not feature a separate Hardware Abstraction
Layer (HAL) between the physical hardware and the rest of the OS. Instead, XT architecture integrates a hardware specific
code with the kernel.
#### Does ExectOS allow to use Windows drivers?
This is one of our goals. Thanks to the NT drivers compatibility layer provided by ExectOS, you should be able to install
and use the same drivers as you can on Windows.
This is one of our goals. Thanks to the NT™ drivers compatibility layer provided by ExectOS, you should be able to
install and use the same drivers as you can on Windows®.
#### Can I install ExectOS on a pendrive / USB stick?
Yes. This is how it is tested on a bare metal (real hardware).
@ -75,16 +84,16 @@ Because GCC is a crap.
We don't need tests. If it compiles, it is good enough; if it boots up, then it is perfect.
#### Why don't you help Wine?
Wine implements Win32Api only, while ExectOS is a featureful Operating System, that implements a compatibility layer with NT.
This means, ExectOS will be able to run NT drivers as well, not only Windows software. However, thanks to its modular design,
it will be possible to implement Win32 subsystem as well at some point, based on Wine.
Wine implements Win32Api only, while ExectOS is a featureful Operating System, that implements a compatibility layer with
NT™. This means, ExectOS will be able to run NT™ drivers as well, not only Windows® software. However, thanks
to its modular design, it will be possible to implement Win32 subsystem as well at some point, based on Wine.
#### Why don't you help ReactOS?
ExectOS goals are very different from ReactOS, and contrast the project's core philosophy as being quite on different paths.
While ReactOS aims to replicate Windows NT, ExectOS is a completely new Operating System implementing the XT architecture
which derives from NT. Although both projects share the goal of being NT compatible, they intend to achieve it in different
ways. What ReactOS tries to replicate, ExectOS only implements as a compatibility layer. Thanks to that, ExectOS does not
need to strictly follow NT architecture and is capable of providing modern features.
While ReactOS aims to replicate Windows® NT™, ExectOS is a completely new Operating System implementing the XT
architecture which derives from NT™. Although both projects share the goal of being NT™ compatible, they intend
to achieve it in different ways. What ReactOS tries to replicate, ExectOS only implements as a compatibility layer. Thanks
to that, ExectOS does not need to strictly follow NT™ architecture and is capable of providing modern features.
#### Do you intend to cooperate with ReactOS to achieve common goals?
No. We share Wine's opinion on the inappropriate reverse-engineering methods used in the ReactOS project, as well as its