Mark reserved keywords and trademarks
This commit is contained in:
parent
787b2f9931
commit
b739163dc3
@ -11,11 +11,11 @@ that enables kernel level components to be upgraded without a need to recompile
|
|||||||
|
|
||||||
## XT Architecture
|
## XT Architecture
|
||||||
ExectOS is a preemptive, reentrant multitasking operating system that implements the XT architecture which derives from
|
ExectOS is a preemptive, reentrant multitasking operating system that implements the XT architecture which derives from
|
||||||
NT architecture. It is modular, and consists of two main layers: microkernel and user modes. Its' kernel mode has full
|
NT™ architecture. It is modular, and consists of two main layers: microkernel and user modes. Its' kernel mode has
|
||||||
access to the hardware and system resources and runs code in a protected memory area. It consists of executive services,
|
full access to the hardware and system resources and runs code in a protected memory area. It consists of executive
|
||||||
which is itself made up on many modules that do specific tasks, a kernel and drivers. Unlike the NT, system does not
|
services, which is itself made up on many modules that do specific tasks, a kernel and drivers. Unlike the NT™, system
|
||||||
feature a separate Hardware Abstraction Layer (HAL) between the physical hardware and the rest of the OS. Instead, XT
|
does not feature a separate Hardware Abstraction Layer (HAL) between the physical hardware and the rest of the OS. Instead,
|
||||||
architecture integrates a hardware specific code with the kernel. The user mode is made up of subsystems and it has been
|
XT architecture integrates a hardware specific code with the kernel. The user mode is made up of subsystems and it has been
|
||||||
designed to run applications written for many different types of operating systems. This allows us to implement any
|
designed to run applications written for many different types of operating systems. This allows us to implement any
|
||||||
environment subsystem to support applications that are strictly written to the corresponding standard (eg. DOS, or POSIX).
|
environment subsystem to support applications that are strictly written to the corresponding standard (eg. DOS, or POSIX).
|
||||||
Thanks to that ExectOS will allow to run existing software, including Win32 applications.
|
Thanks to that ExectOS will allow to run existing software, including Win32 applications.
|
||||||
@ -28,19 +28,19 @@ Thanks to that ExectOS will allow to run existing software, including Win32 appl
|
|||||||
ExectOS. The majority of code is original, not forked.
|
ExectOS. The majority of code is original, not forked.
|
||||||
* Modular design for better compatibility with existing software and drivers, enabling binaries to remain compatible even
|
* Modular design for better compatibility with existing software and drivers, enabling binaries to remain compatible even
|
||||||
when the core system is updated.
|
when the core system is updated.
|
||||||
* Own, XT drivers for commonly used devices as well as NT drivers compatibility layer for better hardware support.
|
* Own, XT drivers for commonly used devices as well as NT™ drivers compatibility layer for better hardware support.
|
||||||
* Technical support directly from the architects and developers of the system.
|
* Technical support directly from the architects and developers of the system.
|
||||||
|
|
||||||
## Why
|
## Why
|
||||||
* We believe, there is no ideal Operating System on the market. During ExectOS development, we try to bring most useful
|
* We believe, there is no ideal Operating System on the market. During ExectOS development, we try to bring most useful
|
||||||
features known from existing solutions, while keeping compatibility with NT architecture at desired level.
|
features known from existing solutions, while keeping compatibility with NT™ architecture at desired level.
|
||||||
* Some of our ideas differ greatly from other projects and it is much easier if we do not have to fight legacy code and
|
* Some of our ideas differ greatly from other projects and it is much easier if we do not have to fight legacy code and
|
||||||
ideas.
|
ideas.
|
||||||
* We need the freedom to break things when necessary.
|
* We need the freedom to break things when necessary.
|
||||||
|
|
||||||
## Goals
|
## Goals
|
||||||
* Keep the greatest advantages of the NT architecture, while implementing new features and technologies known from other
|
* Keep the greatest advantages of the NT™ architecture, while implementing new features and technologies known from
|
||||||
Operating Systems.
|
other Operating Systems.
|
||||||
* Flexibility where it makes sense to provide flexibility.
|
* Flexibility where it makes sense to provide flexibility.
|
||||||
* Be able to deliver features that other non-commercial Operating Systems consider too ambitious.
|
* Be able to deliver features that other non-commercial Operating Systems consider too ambitious.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user