Introduction

With the step of the years one has produced a gradual evolution of the structure and capacities of the Operative systems. Nevertheless, recently there has got a certain number of new elements of design in the new Operative systems and in the new versions of the existing Operative systems. These modern Operative systems answer to new developments of the hardware and new applications. Between(among) these devices of hardware the machines are multiprocessor, enormous increases of the speed of the machine, high speed in the links of the networks(nets) of communication and increase in the size and variety of the devices of storage of memory(report). In the fields of application that have influenced the design of the Operative Sistema the applications are multimedia, the access to Internet and web pages and the execution client / servant.

The percentage of changes in the demands(lawsuits) of the Operative systems, needs not only the modifications and improvements in the already existing architectures, but new forms of organization of the Operative system. Many of the different approaches and elements of design have been proved(tried) so much in experimental as(like) commercial Operative systems, and many of them fit inside the following categories

• Architecture Microcore(Micronucleus).
• Multithreads.
• Symmetrical multiprocess.
• Distributed operative systems.
• Design Orientated to Object.

Most of the Operative systems even does a little time they were characterized by a great monolithic core(nucleus). Great part(report) of the functionality that was thought had to have an Operative system this great core(nucleus) was providing it, including planning, system of files, networks(nets), controllers of devices, management of memory(report) and many things more. Normally a monolithic core(nucleus) is implemented as the only(unique) process, with all his(her,your) components sharing the same space of directions(addresses).

The architecture microcore(micronucleus) assigns only a few essential functions to the core(nucleus), including spaces of directions(addresses), communication between(among) processes (CONSUMER PRICES INDEX) and basic planning. It(he,she) provides other services of the Operative system processes, often so called servants, who execute in way user and who the microcore(micronucleus) treats like to any other application. This approach disconnects the core(nucleus) and the servants' development. The servants can be designed for specific applications or needs of the environment. The approach of the microcore(micronucleus) simplifies the implementation, provides flexibility and adapts well for distributed environments. In essence, a microcore(micronucleus) interacts of the same form with processes local and remote servants, facilitating the construction of distributed systems.

This work tries to approach the architecture of the Operative system Windows and the services that each of his(her,your) components offers to carry out each of the categories before exposed.

General vision of the Architecture of Windows.

A serious Operative system, capable of competing on the market with others as Unix that already they have a privileged position, as for results, must have a series of characteristics that allow him(her) to gain(earn) this place him(you,them). Some of these are:

• That runs on multiple architectures of hardware and platforms.

• That is compatible with applications done in previous platforms, that is to say that were traversing the majority of the existing applications done on versions previous to the current one, we refer in this particular case to them of 16-bit of MS - TWO and Microsoft Windows 3.1.

• Assembles(Brings together,Assemble,Bring together) the governmental requirements for POSIX (Portable Operating System Interface for Unix).

• Assembles(Brings together,Assemble,Bring together) the requirements of the industry and of the government for the safety of the Operative system.

• Is(Am) easily adaptable to the global market supporting code Unicode .

• Is(Am) a system that traverses and balances the processes of parallel form in several processors simultaneously.

• Is(Am) an Operative system of virtual memory(report).

One of the most important steps that revolutionized the Operative systems of the Microsoft was the design and creation of an extensible, portable, trustworthy, adaptable, robust, Operative system sure and compatible with his(her,your) previous versions (Windows NT ).

And for it they created the following modular architecture:

 

 

 

 

 

 

 

 

 

Which(Who) is composed by a series of separated components where everyone is responsible for his(her,your) functions and they offer services to other components. Is this architecture of the type client? Servant since the programs of application are contemplated by the operative system as if they were clients to those that it is necessary to serve, and for which comes equipped with different entities servidoras .

Already created this one I design other versions that happened to him(her) to Windows NT they were taking this architecture as a base and new components were adding him.

One of the characteristics that Windows shares with the rest of the advanced Operative systems is the division of tasks of the Operative system in multiple categories, which are associated with the current manners supported by the microprocessors. These manners provide to the programs that traverse inside them different levels of privileges to accede to the hardware or to other programs that are running in the system. Windows uses a privileged way (Kernel) and a not privileged way (User).

One of the fundamental aims(lenses) of the design was to have a core(nucleus) as small as it(he,she) was possible, in that there were integrated(repaid) modules that were giving response to those calls to the system that necessarily they had to execute in privileged way (way kernel ). The rest of the calls would be expelled from the core(nucleus) towards other entities that would be executed in not privileged way (way user), and hereby the core(nucleus) would turn out to be a compact, robust and stable base.

The Way User is a less privileged way of functioning, without the direct access to the hardware. The code that runs in this way only acts in his(her,your) own(proper) space of direction(address). This one uses the APIs (System Application Program Interfaces) to ask for the services of the system.

The Way Kernel is a way very favoured of functioning, where the code has the direct access to the whole hardware and all the memory(report), even to the spaces of direction(address) of all the processes of the way user. The part of WINDOWS that runs in the way Kernel he is called An Executor of Windows, who is not any more than a set than available services to all the components of the Operative system, where every group of services is manipulated by components that are totally independent (between(among) them the Core(Nucleus)) between(among) yes and they communicate across interfaces definite well.

All the programs that do not run in Way Kernel run in Way User. The majority of the code of the Operative system User runs in Way, as well as the subsystems of environment (Win32 and POSIX that will be explained in later(posterior) chapters) and user's applications. These programs only accede to his(her,your) own(proper) space of directions(addresses) and interact with the rest of the system across messages Client / servant.

I agree on 1

Way Kernel

1.1? Cap of Abstraction of Hardware (HAL).

Known by his(her,your) initials in English HAL (Hardware Abstraction Layer) is an interfaz between(among) the hardware and the rest of the Operative system, is implemented as a library of dynamic link (dll) and is a person in charge of protecting the rest of the system of the specifications of the hardware, such as(like) control of interruption and interfaces of entry / exit. This abstraction does to the most portable system since the rest of the system does not have to worry on that platform is running. Every platform in which the system runs a specific HAL needs. The design tries(means) that when Windows is carried to a new architecture of processor, the HAL is rewritten for the new processor, but the rest of the system simply must be recompiled.

This one also gives the interfaz for the symmetrical multiprocessing (known by his(her,your) initials in English SMP ). The versions Server contain two HALs for architecture of processor ( Intel , MIPS , PowerPC and and Alpha), the first one is used to support an alone processor, whereas the second one supports up to four processors.

For every physical processor that exists in the computer the HAL represents a processor virtualizado to the microkernel . The idea is that the processor virtualizado hides the special characteristics of the own(proper) processor to the operative system, this wants to say that if for example two systems are had multiprocessors, traversing one on a processor Intel and traversing other one with one Alpha, the HALs in every system would be different, but the processors virtualizados that this one presents to the microkernel in both cases could be identical. On a system SMP (Symmetrical Multiprocessing) for every physical processor in the system the HAL represents a processor virtualizado to the microkernel .

To this alone component there can accede components of the Executor of Windows and User never calls for the programs of the Way. The HAL also tries to be the only(unique) piece of software inside the system that one communicates with the hardware, the advantage of this is that other programs cannot write information in the hardware not accidental, not intentionally and cause a fall of the system, also preventing that programs read information directly of the hardware.

Though the goal of Windows is that you relate all the calls to the hardware be across the HAL, the reality is that a small number of calls of the drivers and of the Kernel border on the HAL and interact directly with the hardware.

The cap of Abstraction of Hardware known by his(her,your) initials in English (HAL) is a library of manipulation of hardware with routines given by Microsoft or by the manufacturer of the hardware. This cap stays in the lowest level of the Executor of Windows (between(among) the hardware and the rest of the Operative system), this one hides the characteristics of the platform in order that all the platforms and architectures seem to be equal to the Operative system, this allows to the SO to traverse on different platforms with one o more processors, facilitating in addition the drivers of devices to adapt to E/S's different architectures without having to be modified to a great extent.

1.2? MicroKernel

It is the person in charge of all the actions(shares) that carry out on him(her) system and almost all the functions of the system happen(pass) across him(it).

The design of this component assigns many of the functions normally assigned to the Kernel in the traditional Operative systems to a group of programs called Executingly of Windows, of which the microkernel is a part(report), runs in the privileged way and both (the executor and the microkernel ) communicate across primitive(original) from the operative system to low level.

The principal task of this component is the planning of execution of threads (segment of code belonging to a particular process). To every thread a priority is assigned from 0 to 31, this one at the time sends threads to run in dependence of his(her,your) number of priority and allows them execute a time determined before appropriating of them and allowing that another process should run.

Here it is important to clarify that the microkernel does not plan the process execution, but it(he,she) plans the execution of threads in the environment of a process, this procedure there is the one that makes possible the multitask with preference to the being the microkernel the one that plans the execution of the whole code that runs in the system.

In a system multiprocessor, a copy of the microkernel runs in every processor. These segments of the microkernel are used to support the coherence of the resources of the system that are shared since they are acceded by the threads that run in all the processors.

This one also is responsible for the manipulation of interruptions of the system from physical devices. Normally when the system is interrupted, the microkernel appropriates of the thread that this traversing in this moment to try the interruption.

The microkernel also manipulates the exceptions of the processor, where these exceptions happen when the processor tries to do some operation that is not been allowed him(her), as the attempt of writing in a portion of memory(report) to which it(he,she) does not have access or when it(he,she) divides for zero.

The final use of the microkernel is to give a support for the recovery of the system of a fall of energy. If the system this one equipped with a supplier of energy ininterrumpible (more known by his(her,your) initials Englishman(English) UPS ) the microkernel is warned when the fall of energy is detected, then this one coordinates a closing been ordained as the system, which includes the warning to the devices of Entry / exit of the fall of the energy and to allow then to be restored consistently.

Since the Microkernel joiner is involved in the majority of the actions(shares) assumed by the Operative system, the critical portions of this sound written in language to guarantee that this one could traverse the most rapid and efficiently possible thing, which brings with it(him) that his(her,your) optimization is a critical factor of functioning when the system is carried to different architectures.

The microkernel is placed in the heart of Windows, works very narrowly with the HAL (Level of Abstraction of Hardware), this one plans the execution of threads and manipulates the interruptions and process exceptions. The paper(role) of this one is to support to the processors busy(occupied) possible mas . In general this sense he(she) takes charge of the most basic functions of the whole SO , since they are:

• Subprocess execution.

• Synchronization multiprocessor.

• Managing of the interruptions of hardware.

1.3? The Executor of Windows .

The Executor of Windows takes charge of the important tasks, which perform vital importance for the complete system, since the microkernel is too much occupied almost always to go directly.

A clear definition is that the Executor of Windows provides the foundations of the operative system that will be given to all the applications that run on the system. This one includes services as the Administration of Objects, of virtual Memory(Report), of Entry - exit and of Processes.

The Executor of Windows runs exclusively in Way Kernel and is called by the subsystems of protected environment when these need from his(her,your) services. Due to the hierarchy of Windows the applications that run in Way User cannot call segments of the Executor of Windows directly, but services of demand(lawsuit) of the subsystems of environment (explained in later(posterior) chapters), since(as,like) Win32 and POSIX those who in turn take charge calling the components of the Executor of Windows.

1.4? The Manager of Objects.

The Manager of Objects (Object Manager) is used to create, to modify and to eliminate objects (types of abstract information that are used to represent resources of the Operative system) used by all the systems that agree the Executor of Windows. This one also provides information about the condition(state) of the objects to the whole Operative system.

The objects can be concrete, such things as ports of devices, or can be more abstract as threads. When an object is created to this one there is given a name for which you programme others they him(her) can accede. When a process needs to accede to the this(this one) object it(he,she) requests a treatment of object the manager of objects. The manipulator of objects there gives a leader(pointer) who is used to locate to the object, as well as an information of control of access that he(she) says since(as,like) it is possible to accede to. This information of control of access is given by the safety subsystem (be afraid that it will be approached in near(next) topics).

This one also insures itself that the objects should not consume many resources (as a rule the memory(report)), supporting quotas for the different types of objects.

In addition the Manager of Objects takes charge cleaning orphan objects (objects that seem not to have owner), this is known as compilation of garbage. The lack of this facility in Windows 3.x was the reason of many problems, since when a program was collapsing or manipulating incorrectly the resources of the system, the resources consumed by this one were not returned to the system in order that they were returning to be available producing a mistake for lack of resources of the system. In fact this was a leak of memory(report).

Like summary the Manager of Objects takes charge creating, destroying and managing all the objects of the Executor of Windows.

1.5? The Process manager.

The Process manager (Process Manager) is the person in charge of creating, removing(taking) and modifying the conditions(states) of all the processes and threads. This one also provides information about the condition(state) of processes and threads to the rest of the system.

A process, for the definition, includes a space of virtual direction(address), one or more threads, a segment of code of the feasible program, and a set of resources of the system. A thread is a feasible object that belongs(concerns) to an alone process and contains a book-keeper of the program who points at his(her,your) current position in the segment of feasible code of the process, two batteries(sinks), and a set of values of the record.

The Process manager, as all the members of the Executor of Windows, plays a vital paper(role) in the functioning of the entire system. When an application begins his(her,your) execution, one believes as a process what asks a call from the Process manager. Since any process must have at least a thread, the Process manager is invoked again to create the thread.

The Process manager is used to handle the threads, but it(he,she) does not have his(her,your) own(proper) set of policies on how planning the execution of processes and threads. These policies are determined by the own(proper) microkernel .

The process manager (Process Manager) is the person in charge of creating, removing(taking) and modifying the conditions(states) of all the processes and threads, as well as of providing information about the condition(state) of processes and threads to the rest of the system.

1.6? The Manager of Virtual Memory(Report).

The Manager of Virtual Memory(Report) (Virtual Memory Manager or VMM ) provides the management of virtual memory(report) of the system. The virtual memory(report) is a scheme that allows to use the resources of the disc instead of the physical memory(report) of the system moving the pages to the disc when these are not being used and recovering them when they are needed. This one is an integral segment of Windows which assigns spaces of directions(addresses) of 32 bit to every process without worrying about the quantity of physical memory(report) of the system.

To every process there is assigned a space of virtual memory(report) of 4GB. Of this space, two jig bites Superiors are reserved for the use of the system, whereas others two jig bites remaining are for the use of the process. The Manager of Virtual Memory(Report) is the person in charge of translating the directions(addresses) of memory(report) of the process into the royal(real) directions(addresses) of memory(report) of the system. If the direction(address) of memory(report) of the process refers to a segment of memory(report) that has been paginated towards the disc, the Manager of Virtual Memory(Report) recovers the page of the disc.

The Manager of Virtual Memory(Report) takes charge of everything related to the politics(policy) of management of the memory(report), determines the sets of work of every process, supports a set of free pages, chooses pages that are going to pass to the royal(real) memory(report), raises and lowers pages between(among) the memory(report) RAM and the file of exchange on disc.

1.7? Services of Calls to Local Procedures.

The Service of Calls to Local Procedures (Local Procedure Call Facility or LPC ) they join to the design client / servant of Windows. East is the interfaz between(among) all the processes clients and servants who run locally in the system.

The structure of the Service of Calls to Local Procedures is very similar to that of the calls to Remote Procedures (RPC) , unless this one is optimized and only communication supports between(among) processes clients and servants locally. More specifically, the LPC is a mechanism that allows two threads in different processes to exchange information.

Remember that we said that the subsystem of Win32 is an application that User traverses in the Way and it(he,she) will run in his(her,your) own(proper) space of memory(report). When a program wants to communicate with the subsystem Win32 to request services, it(he,she) calls a function from the appropriate DLL , this function at the time uses the LPC to spend(pass) the request to the process subsystem Win32, which tries the demand(lawsuit) and realizes the asked action(share) and returns a message of accomplishment across the LPC .

The Service of Calls to Local Procedures is the module that takes charge receiving and sending the local calls of procedure between(among) the applications client and the subsystems servants.

1.8? The Monitor of Security.

The Monitor of Security (Security Reference Monitor or SRM ) is the bed of all the safety inside the system WINDOWS and is the person in charge of making fulfill all the policies of safety in the local computer.

This component works together with the subsystems of time of bullfight, process of connection to the system (known like logon process ) and control of the local safety (place security authority ). When a user tries to connect to the system his(her,your) identity it is checked, the process subsystem of connection asks for a card of safety access (known by his(her,your) initials in English SAT or security access token ) of the user. The SAT contains a list of the users' privileges and groups. East is used as key for this user during the session of connection. Providing that the user wants to do something, the SAT is presented and used to determine if the user can realize the actions(shares).

This component works narrowly with the Manager of Objects. Whenever a user tries to accede to an object the Manager of Objects creates a manipulator to accede to this one and calls the SRM to determine the level of access granted by the manipulator. The SRM uses information contained in the card of access of the user and compares it with the check list of accesses on the object to see if it(he,she) must grant the level of asked access to the user. Of this form the SRM it(he,she) has the control of the safety of access of all the objects in the system.

1.9? The Manager of Entry - exit.

The Manager of Entry - exit ( I/O Manager ) is a person in charge of managing the communication between(among) the different drivers of device, for which implements one interface definite well that allows the treatment of all the drivers of a homogeneous way, without it(he,she) controls how each one works specifically. It(he,she) has a series of subcomponents that are:

• Driver of the System of Files: this one takes charge establishing the communication with the drivers of the Systems of Files, since the system allows the coexistence of multiple Systems of Files in different logical partitions of the same physical unit.

• The servant and the redirector of network(net).

• The drivers of device of the system.

• The manager of caches (Cache Manager ): this one takes charge manipulating the cache for the whole System of Entry and Exit. This one is a method that the systems of files use to improve his(her,your) performance(yield), where instead of reading and to write on disc an used frequently this file there is stored in one cache of memory(report) and the reading and writing of these files is realized from memory(report). This component takes charge of the black magic that is often necessary to do that several devices communicate between(among) if and they should coexist together in a segment. The Manager of Entry - exit ( I/O Manager ) is a person in charge of managing the communication between(among) the different drivers of device.

I agree on 2

Way User

2.1? Subsystems of Protected Environment

Two of the aims(lenses) of WINDOWS are personality and compatibility. This has been achieved across the subsystems of protected environment.

The personality essentially means that WINDOWS exposes multiple sets of interfaces of programs of application (APIs) and can act effectively as if it was a different operative system. WINDOWS comes with a personality POSIX and OS/2 besides his(her,your) personalities WIN32, WIN16 AND TWO.

In WINDOWS, there are three subsystems of protected environment:

• The subsystem of Win32

• POSIX's subsystem

• The subsystem of OS/2

Though often the personalities prove to be WIN16 AND TWO included ones in a list of subsystems of protected environment, they really are a part(report) of the subsystem Win32.

The subsystems of protected environment User and the Executor of Windows act as the mediators between(among) the applications of the Way.

Remember that the Executor of Windows and all his(her,your) components they live in the Privileged Way or Way Kernel , whereas all the rest live in the Way User, this includes all the subsystems of environment. When an application does a call to a subsystem of environment, this one is spent(passed) across a cap of services of the Executor of Windows.

Every subsystem of environment guards fingerprint of his(her,your) own(proper) processes and works independently of other subsystems. Every application only can run in the subsystem for whom was designed. When you initiate an application in WINDOWS, it(he,she) looks at the heading represented by the file and determines in which subsystem to execute the application.

2.2? The Subsystem Win32

Win32 is the native and primary subsystem of WINDOWS. The bases for this subsystem it is the set of APIs of Win32. Many of these API are direct extensions of his(her,your) counterparts Win16.

This subsystem acts as a servant for all the other subsystems of environment supported in WINDOWS, which act as clients and translate his(her,your) calls API towards the appropriate API of Win32.

The subsystem Win32 is responsible for the whole entry and exit. This one possesses the control of the screen, the keyboard, and the mouse. When other subsystems, since(as,like) OS/2 or POSIX , needs to benefit from these devices, they ask for the services to the subsystem of Win32.

Some of the aims(lenses) that were planned to support the compatibility with the applications done in previous versions were:

• To allow that the programs done on TWO should run without modification.

• To give the aptitude to execute the majority of the applications Windows of 16 bits without modification

• To protect to the system and other applications of 32 bits of the interference of the applications of 16 bits and TWO.

• To allow to the platforms RISC (Reduced Instruction set Computer , microprocessor which number of instructions is reduced to achieve a higher frequency of work) applications to execute Windows of 16 bits and TWO.

• To give a mechanism to share information between(among) applications Windows of 32 and 16 bits .

Many persons think about Windows 3.x as an Operative system. Technically, it is not a real Operative system, but a user's interfaz that is a member of TWO, the real Operative system.

So, the step first in providing compatibility was to create an environment of TWO. The environment of TWO in WINDOWS is called the virtual machine of TWO ( Machine TWO Virtual or VDM ). The VDM is an application of way user of 32 bits which(who) requests the services of the subsystem of Win32 and in cause directly to the cap of services of the system. It is based on TWO 5.0.

WINDOWS allows to execute so many applications of TWO as one wish, where every application runs in his(her,your) own(proper) VDM . Since the VDMs are nothing more than normal processes under WINDOWS, they also are preventive multitask as other processes in the system. Consequently, it can be said that WINDOWS allows the preventive multitask of programs of TWO.

One of the additional features of the VDM is that it(he,she) gives 620 KB of "conventional" free memory(report) to the user. The miraculous thing on this is that also it(he,she) gives to the applications of TWO support of mouse, network(net), and CD-ROM .

The Subsystem Win32 is the most important, since he(she) attends not only to the native applications of Windows, but for those programs not Win32, it(he,she) recognizes his(her,your) type and throws(launches) them towards the corresponding subsystem. In case the application is MS - TWO or Windows of 16 bits (Windows 3.11 and low), which it(he,she) does is to create a new protected subsystem. This way, the application two or Win16 would execute in the context of a process called VDM (Virtual TWO Machine , virtual machine TWO), that is not any more than a malingerer than a computer working under MS - TWO . The subsystem supports a good part of the API Win32. This way, he(she) takes charge of everything related to the graphical interfaz to the user (GUI) , controlling the income of the user and exits of the application.

2.3? The Subsystem POSIX .

Microsoft gave many attention to the different standards of opened systems when Windows NT was in route of development. They recognized the value to support systems opened as a method to gain(earn) acceptance of his(her,your) new operative system advanced inside the market.

One of the standards more frequently mentioned supported by Windows is the POSIX (Interface of Portable Operative system Based on Unix), which(who) represents the interfaz of the portable Operative system and it was developed by the IEEE (Engineers' Institute in Electricity and Electronics) as a method of providing portability to the applications done on platforms UNIX. Nevertheless, POSIX has joined many systems not UNIX.

Many levels of obedience exist with POSIX . These levels represent a set of evolutions of offers, though not they all have been approved as standards.

POSIX's subsystem needs a minimum of services that are provided by WINDOWS. When POSIX's application runs in WINDOWS, the subsystem is loaded and translates the so called API of the language C, needed it to support in calls to APIs of Win32 those who are served by the subsystem Win32.

Due to the limited nature, POSIX's subsystem in WINDOWS does not give support for networking or safety system.

The Subsystem POSIX intergesticulates with the Executor of Windows. It(he,she) takes charge defining specific aspects of the Operative system UNIX, since they can be the hierarchic relations between(among) processes parents and children (which do not exist in the subsystem Win32, for example, and that consequently do not turn out to be implemented directly in the Executor of Windows).

2.4? The Subsystem OS/2.

The subsystem of OS/2 is implemented as a subsystem of protected environment, similar to the subsystem POSIX . This one translates the so called API of OS/2 in calls into APIs of Win32 that are served by the subsystem of Win32.

The subsystem and his(her,your) applications run in his(her,your) own(proper) space of memory(report) protected from 32 bits and some constitute a preventive multitask with regard to others and with regard to other applications that run in the system.

Besides a set of engines APIs of OS/2, the subsystem implements many LAN's managing APIs (Network(Net) of Local Area), including pipelines, NETBIOS and mailslots . Hereby it(he,she) differs from the subsystem POSIX since this one does not possess support for networking.

The Subsystem OS/2 like the subsystem POSIX provides an environment for applications UNIX, this subsystem gives support to the applications OS/2. It(he,she) provides the graphical interfaz and the calls to the system; the calls are served by help of the Executor of Windows.

Conclusions

Windows is a system that takes advantage of the power of the processors, has been designed to adapt to the new technologies, offers compatibility with several platforms (OS/2, Unix and versions previous to the same one), he(she) supports the symmetrical multiprocessing, good performance(yield) and conectividad , safety and on not having been classified in any standard model of Operative system has the aptitude to combine the advantages of the model client / servant, can run in addition on multiple architectures with a minimum of changes, it is allowed that several processes should be executed simultaneously in several processors and these do not appropriate of resources of the system in indefinite time, but for treatment of the system.

Consulted bibliography

• [Solo00] Solomon, David A.y Russinovich Mark? Inside Microsoft Windows 2000?. 3ra Edi . Microsoft Press . Washington. 2000.

• [Stal98] Stallings , William .? Operating Systems ?. 3ra Edi . Prentice-Hall , Inc . New Jersey. 1998.

• [Stal01] Stallings , William .? Operative Systemas ?. 4ta Edi . Pearson Edicación , S.A . Madrid. 2001.

• URL : http: // www.monografias.com/trabajos7/arso/arso2.shtml

• URL : http: // www.windowstimag.com/

• URL : http: // usuarios.lycos.es/betzweb/