DOCSLIB.ORG

Design of OS/2 by Michael S. Kogan, Harvey M. Deitel Outline 1.1 Introduction 1.2 DOS History 1.3 DOS Limitations 1.3.1 Memory M

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Design of OS/2 by Michael S. Kogan, Harvey M. Deitel Outline 1.1 Introduction 1.2 DOS History 1.3 DOS Limitations 1.3.1 Memory M Design of OS/2 by Michael S. Kogan, Harvey M. Deitel Outline 1.1 Introduction 1.2 DOS History 1.3 DOS Limitations 1.3.1 Memory Management 1.3.2 I/O Management 1.3.3 Multitasking 1.3.4 System Extendibility 1.3.5 Graphical User Interface OS/2 History 1.4.1 IBM–Microsoft Joint Development 1.4.2 Multisite Development 1.4.3 OS/2 1.0 1.4.4 OS/2 1.1 1.4 The Evolving Market 1.5.1 Microsoft Windows 1.5.2 DOS Expanded Memory 1.5.3 DOS Extended Memory 1.5.4 DOS Extenders 1.5.5 Intel 80386 1.5.6 DOS Multitaskers 1.6 OS/2 1.2 1.7 OS/2 1.3 1.8 Windows 3.0 1.9 OS/2 2.0 1.10 The 1990s Summary 1.1 INTRODUCTION This chapter reviews the history of personal computers and operating systems. It traces the evolution of personal computer hardware from the original IBM Personal Computer to the latest IBM PS/2, and examines how this process has affected the content and design of DOS and OS/2. Before 1980 most computers were mainframes and minicomputers, large computing resources that were mainly job- and transaction-processing systems. Operating system technology had evolved from its early simplistic control program stages to sophisticated multiprogrammed virtual memory systems such as VM, MVS, and later versions of UNIX. In the era of large, centralized computing resources, computer time was expensive, learning was time consuming, assistance was difficult to obtain, and computing resources were scarce. Users rarely had opportunities to interact privately with a local computing resource. The advent of the microprocessor and of inexpensive, off-the-shelf computer components enabled the creation of the first microcomputer systems. The Altair, a primitive computer kit based on the Intel 8080, was one of the most popular early systems. The Altair was surpassed by the Apple I and II computers created by Steve Jobs and Steve Wozniak. The Apples used the MOS Technology 6502 chip and included a keyboard and display. Also gaining acceptance were microcomputer systems configured with the Intel 8080 and Zilog Z80 processors. Besides the Apple, which had its own proprietary operating system, the Intel and Zilog systems principally ran the CP/M operating system. CP/M was primarily designed for 8-bit single-user microcomputers that had floppy-disk drives. At this point, during the late 1970s, IBM decided to spin off an independent business unit (IBU) to investigate the potential of an IBM microcomputer system. In the late 1970s, IBM used IBUs to respond rapidly to new opportunities, and granted them considerable freedom within IBM’s business processes. An IBU is similar to a venture capital operation that attempts to exploit evolving technologies. The IBU ultimately became the current Entry Systems Division (ESD) of the IBM Corporation, which is responsible for personal computer hardware and operating system development. 1.2 DOS HISTORY The DOS era of microcomputer operating system technology began when the first IBM Personal Computer (PC) was designed. The first IBM PC went beyond the current 8-bit technology available and used the then-new 16-bit Intel 8088 processor. This choice was made because the current 8-bit systems were being eclipsed by the newer 16-bit systems, and the 16-bit system architecture provided a base for more robust software. The 8088 and 8086 processors are functionally identical, but the 8088 was used in the IBM PC since it was cheaper to configure in hardware. The 8088 processor could address up to 1MB of memory; few designers could envision using all that memory in a desktop personal computer in 1979. IBM also chose the 8088 microprocessor because porting software from existing 8080-based systems to the 8088 would be relatively straightforward. With the hardware for the first PC under development, IBM sought to adapt existing software for the system. Developing a new operating system and software tools would have taken too long. IBM contracted Microsoft, at the time a new company, to provide a BASIC interpreter, assembler, and link editor for the machine. IBM chose Microsoft because of Bill Gates’s experience in writing the most popular BASIC interpreter to date for the Altair systems. Since many CP/M-based programs were available, IBM initially attempted to interest Digital Research, Inc. (DRI) in providing a 16-bit version of the CP/M operating system for the IBM PC. However, DRI did not foresee the success of the 8088 microprocessor and declined to participate in the venture. IBM then approached Microsoft and, after explaining the requirements, asked Microsoft whether it was interested in providing the operating system software as well as the tools. The main concern of both IBM and Microsoft at the time was whether Microsoft had the resources to develop both the software tools and the operating system in the time required. Realizing that writing a new system was not feasible due to the schedules, Microsoft acquired from Seattle Computing Products a CP/M clone called SCP- DOS. With the SCP-DOS technology as a base, Microsoft predicted that it could complete the operating system, and the original operating system agreement between IBM and Microsoft was established. In 1981, the first version of the DOS operating system, 1.0, was shipped for IBM PCs. The system supported PCs with up to 256KB RAM, two 180KB floppy-disk drives, and included a Basic Input Output System (BIOS) built into the system ROM. DOS 1.0 was similar to CP/M in the way it managed the diskette devices and files, and it provided the base platform for the first 8088 DOS applications. Since the primary data structure used by the DOS file system to map file blocks to diskette addresses was the file allocation table (FAT), the DOS file system became known as the FAT file system. Figure 1.1 illustrates the DOS system structure. In 1982, IBM began shipping PCs with 360KB floppy disk drives. Since the new diskette medium had a format different from that of the 180KB diskettes, DOS had to be updated. IBM shipped DOS 1.1 when the new diskette drives became available in 1982. IBM next enhanced its PC line in 1983 with the addition of the IBM PC/XT. The PC/XT had a hard disk that could store far more data than could traditional floppy diskettes. This development illustrates how mainframe technology was becoming less expensive and more widely available in the PC market. The IBM PC/XT also included a new system board that allowed 640KB of memory to be installed. At this point, a trend emerged that continues to this day in the computer industry: The hardware drives the software. The addition of a hard disk to the PC was a problem for DOS 1.1, since the FAT file system was written for floppy-disk systems in which a single 360KB diskette could contain a maximum of 64 files. This limitation had to be removed; even the smallest hard disks could hold 10MB of data. Responding to this requirement, the DOS team at Microsoft explored different hard-disk and file- allocation strategies to select one that would enable DOS software to exploit future improvements in storage technology. Merely extending the limit of 64 files per disk would yield too many files to manage in a single file space, so the Microsoft team chose a hierarchical file-management approach similar to the one found in UNIX. They implemented this approach to support both diskettes and hard drives. Another requirement for the next version of DOS was an architecture for extending the system to support different peripheral devices. This support took the form of device drivers, user-installable program modules that interface the DOS system and applications to devices. The version of DOS that included the hierarchical FAT file system, support for hard disks, and a device-driver model for extending the system was shipped as DOS 2.0 in 1983. IBM’s next PC enhancements involved providing faster systems with larger hard disks. The Intel 80286 chip was selected for the next-generation IBM PC, the PC/AT. The 80286 has two modes of operation called real mode and protected mode. In real mode, the 80286 functions as a fast 8088. In protected mode, the 80286 allows up to 16MB of memory to be addressed and provides features that support a protected multitasking environment. These protection features allow an operating system to separate the memory spaces associated with different programs. However, since the 80286 was not designed to allow existing DOS applications to run in protected mode, they could neither be executed concurrently, nor use more than 1MB of memory. Therefore, DOS applications used the 80286 as a fast 8088. Other operating systems—such as Intel’s RMX or Microsoft’s XENIX—used the protected mode of the 80286, but neither of these systems was considered to be a mainstream desktop system due to a lack of applications compared to the number of DOS applications. The PC/AT was also the first PC to use 1.2MB 5.25-inch diskette drives. Since several modifications to DOS 2.0 were necessary for the PC/AT hardware, DOS 3.0 was not released until August 1984. DOS 3.1 was released in 1985 to provide support for PC local-area networks (LANs). Another update to the system (DOS 3.2) was made for supporting 3.5-inch diskettes in 1986. Table 1.1 shows the evolution of the DOS operating system. 1.3 DOS LIMITATIONS Between 1983 and 1985, IBM, Microsoft, and most application developers began to be aware of certain limitations of DOS and the 8088 environment.
Load more

Recommended publications
  • A Microkernel API for Fine-Grained Decomposition
    A Microkernel API for Fine-Grained Decomposition Sebastian Reichelt Jan Stoess Frank Bellosa System Architecture Group, University of Karlsruhe, Germany freichelt,stoess,[email protected] ABSTRACT from the microkernel APIs in existence. The need, for in- Microkernel-based operating systems typically require spe- stance, to explicitly pass messages between servers, or the cial attention to issues that otherwise arise only in dis- need to set up threads and address spaces in every server for tributed systems. The resulting extra code degrades per- parallelism or protection require OS developers to adopt the formance and increases development effort, severely limiting mindset of a distributed-system programmer rather than to decomposition granularity. take advantage of their knowledge on traditional OS design. We present a new microkernel design that enables OS devel- Distributed-system paradigms, though well-understood and opers to decompose systems into very fine-grained servers. suited for physically (and, thus, coarsely) partitioned sys- We avoid the typical obstacles by defining servers as light- tems, present obstacles to the fine-grained decomposition weight, passive objects. We replace complex IPC mecha- required to exploit the benefits of microkernels: First, a nisms by a simple function-call approach, and our passive, lot of development effort must be spent into matching the module-like server model obviates the need to create threads OS structure to the architecture of the selected microkernel, in every server. Server code is compiled into small self- which also hinders porting existing code from monolithic sys- contained files, which can be loaded into the same address tems. Second, the more servers exist | a desired property space (for speed) or different address spaces (for safety).
    [Show full text]
  • Openvms Record Management Services Reference Manual
    OpenVMS Record Management Services Reference Manual Order Number: AA-PV6RD-TK April 2001 This reference manual contains general information intended for use in any OpenVMS programming language, as well as specific information on writing programs that use OpenVMS Record Management Services (OpenVMS RMS). Revision/Update Information: This manual supersedes the OpenVMS Record Management Services Reference Manual, OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, PATHWORKS, DECnet, DEC, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
    [Show full text]
  • Kontron / ICS Advent SB586P(V) Manual (Pdf)
    Full-service, independent repair center -~ ARTISAN® with experienced engineers and technicians on staff. TECHNOLOGY GROUP ~I We buy your excess, underutilized, and idle equipment along with credit for buybacks and trade-ins. Custom engineering Your definitive source so your equipment works exactly as you specify. for quality pre-owned • Critical and expedited services • Leasing / Rentals/ Demos equipment. • In stock/ Ready-to-ship • !TAR-certified secure asset solutions Expert team I Trust guarantee I 100% satisfaction Artisan Technology Group (217) 352-9330 | [email protected] | artisantg.com All trademarks, brand names, and brands appearing herein are the property o f their respective owners. Find the Kontron / ICS Advent SB586PV at our website: Click HERE Model SB586P(V) Product Manual MANUAL NUMBER : 00431-027-3C Page - ii FOREWORD This product manual provides information to install, operate and or program the referenced product(s) manufactured or distributed by ICS Advent. The following pages contain information regarding the war- ranty and repair policies. Technical assistance is available at: 800-480-0044. Manual Errors, Omissions and Bugs: A "Bug Sheet" is included as the last page of this manual. Please use the "Bug Sheet" if you experience any problems with the manual that requires correction. The information in this document is provided for reference only. ICS Advent does not assume any liability arising from the application or use of the information or products described herein. This document may contain or reference information and products protected by copyrights or patents and does not convey any license under the patent rights of ICS Advent, nor the rights of others.
    [Show full text]
  • Assessing the Quality of Mobile Graphical User Interfaces Using Multi-Objective Optimization
    Noname manuscript No. (will be inserted by the editor) Assessing the Quality of Mobile Graphical User Interfaces using Multi-objective Optimization Makram Soui · Mabrouka Chouchane · Mohamed Wiem Mkaouer · Marouane Kessentini · Khaled Ghedira the date of receipt and acceptance should be inserted later Abstract Aesthetic defects are a violation of quality attributes that are symp-toms of bad interface design programming decisions. They lead to deteriorating the perceived usability of mobile user interfaces and negatively impact the Users eXperience (UX) with the mobile app. Most existing studies relied on a subjective evaluation of aesthetic defects depending on end-users feedback, which makes the manual evaluation of mobile user interfaces human-centric, time-consuming, and error-prone. Therefore, recent studies have dedicated their effort to focus on the definition of mathematical formulas that each targets a specific structural quality of the interface. As the UX is tightly dependent on the user profile, the combi-nation and calibration of quality attributes, formulas, and users characteristics, when defining a defect, is not straightforward. In this context, we propose a fully automated framework which combines literature quality attributes with the users profile to identify aesthetic defects of MUI. More precisely, we consider the mobile user interface evaluation as a multi-objective optimization problem where the goal is to maximize the number of detected violations while minimizing the detection complexity of detection rules and enhancing the interfaces overall quality in means M. Soui College of Computing and Informatics Saudi Electronic University, Saudi Arabia E-mail: [email protected] Mabrouka Chouchane School of computer science of Manouba, Tunisia E-mail: [email protected] Mohamed Wiem Mkaouer Rochester Institute of Technology E-mail: [email protected] Marouane Kessentini University of Michigan E-mail: [email protected] Khaled Ghedira Honoris United Universities E-mail: [email protected] 2 Makram Soui et al.
    [Show full text]
  • Introduction to MS-DOS
    1.Introduction to MS-DOS : MS-DOS (Microsoft Disk Operating System) was the Microsoft-marketed version of the first widely-installed operating system in personal computers. It was essentially the same operating system that (Bill Gates's) young company developed for IBM as Personal Computer - Disk Operating System in 1981. Most users of either DOS system simply referred to their system as Disk Operating System. Like PC-DOS, MS-DOS was (and still is) a non-graphical line-oriented command- driven operating system, with a relatively simple interface but not overly "friendly" user interface. Its prompt to enter a command looks like this: C:\> MS-DOS does not care about anything called an icon, wallpaper or screen saver. Rather than being considered as a Graphical User Interface (GUI) MS-DOS is what is known as a command-line interface. You type commands on what is called the command line. MS-DOS is a single-user, single-tasking computer operating system. In spite of its very small size and relative simplicity, it is one of the most successful operating systems that has been developed to date. In DOS, a file name consists of eight character followed by a 3 character file extension. The size of a file is restricted to a 4 byte file descriptor, which limits a file’s maximum size to approximately 4 billion characters. The first release of DOS could not read or write to disk drives so users could only read and write to a floppy disc. DOS was not a state of the art operating system, even for its time.
    [Show full text]
  • SOS Internals
    Understanding a Simple Operating System SOS is a Simple Operating System designed for the 32-bit x86 architecture. Its purpose is to understand basic concepts of operating system design. These notes are meant to help you recall the class discussions. Chapter 1 : Starting Up SOS 3 Registers in the IA-32 x86 Architecture BIOS (Basic Input/Ouput System) Routines Real Mode Addressing Organization of SOS on Disk and Memory Master Boot Record SOS Startup A20 Line 32-bit Protected Mode Addressing Privilege Level Global Descriptor Table (GDT) More on Privilege Levels The GDT Setup Enabling Protected Mode Calling main() Chapter 2 : SOS Initializations 10 In main() Disk Initialization Display Initialization Setting Up Interrupt Handlers Interrupt Descriptor Table (IDT) A Default Interrupt Handler Load IDT The Programmable Interrupt Controller (PIC) The Keyboard Interrupt Handler Starting the Console Putting It All Together Chapter 3: SOS1 – Single-tasking SOS 16 Running User Programs GDT Entries Default Exception Handler User Programs Executable Format System Calls Creating User Programs The run Command Understanding a Simple Operating System The DUMB Memory Manager Program Address Space Process Control Block Switching to a User Program Kernel-Mode Stack Chapter 4 : SOS2 – Multi-tasking SOS 24 Running Multiple User Programs NAÏVE Memory Manager Programmable Interval Timer (PIT) Process States Timer Interrupt Handler Sleep System Call The run Command Process Queue The Scheduler The Complete Picture ps Command Chapter 5 : SOS3 – Paging in SOS 31
    [Show full text]
  • Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11
    Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11 Application Note Joshua Folks April 3, 2015 Abstract: Software Application programming involves the concept of human-computer interaction and in this area of the program, a graphical user interface is very important. Visual widgets such as checkboxes and buttons are used to manipulate information to simulate interactions with the program. A well-designed GUI gives a flexible structure where the interface is independent from, but directly connected to the application functionality. This quality is directly proportional to the user friendliness of the application. This note will briefly explain how to properly create a Graphical User Interface (GUI) while ensuring that the user friendliness and the functionality of the application are maintained at a high standard. 1 | P a g e Table of Contents Abstract…………..…………………………………………………………………………………………………………………………1 Introduction….……………………………………………………………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Visual Studio Methods.…..…………………………….……………………………………………………………………………4 Interface Types………….…..…………………………….……………………………………………………………………………6 Understanding Variables..…………………………….……………………………………………………………………………7 Final Forms…………………....…………………………….……………………………………………………………………………7 Conclusion.…………………....…………………………….……………………………………………………………………………8 2 | P a g e Key Words: Interface, GUI, IDE Introduction: Establishing a connection between
    [Show full text]
  • Chapter 3 System Calls, Exceptions, and Interrupts
    DRAFT as of September 29, 2009: Copyright 2009 Cox, Kaashoek, Morris Chapter 3 System calls, exceptions, and interrupts An operating system must handle system calls, exceptions, and interrupts. With a system call a user program can ask for an operating system service, as we saw at the end of the last chapter. Exceptions are illegal program actions that generate an inter- rupt. Examples of illegal programs actions include divide by zero, attempt to access memory outside segment bounds, and so on. Interrupts are generated by hardware de- vices that need attention of the operating system. For example, a clock chip may gen- erate an interrupt every 100 msec to allow the kernel to implement time sharing. As another example, when the disk has read a block from disk, it generates an interrupt to alert the operating system that the block is ready to be retrieved. In all three cases, the operating system design must range for the following to happen. The system must save user state for future transparent resume. The system must be set up for continued execution in the kernel. The system must chose a place for the kernel to start executing. The kernel must be able to retrieve information about the event, including arguments. It must all be done securely; the system must main- tain isolation of user processes and the kernel. To achieve this goal the operating system must be aware of the details of how the hardware handles system calls, exceptions, and interrupts. In most processors these three events are handled by a single hardware mechanism.
    [Show full text]
  • DOS Virtualized in the Linux Kernel
    DOS Virtualized in the Linux Kernel Robert T. Johnson, III Abstract Due to the heavy dominance of Microsoft Windows® in the desktop market, some members of the software industry believe that new operating systems must be able to run Windows® applications to compete in the marketplace. However, running applications not native to the operating system generally causes their performance to degrade significantly. When the application and the operating system were written to run on the same machine architecture, all of the instructions in the application can still be directly executed under the new operating system. Some will only need to be interpreted differently to provide the required functionality. This paper investigates the feasibility and potential to speed up the performance of such applications by including the support needed to run them directly in the kernel. In order to avoid the impact to the kernel when these applications are not running, the needed support was built as a loadable kernel module. 1 Introduction New operating systems face significant challenges in gaining consumer acceptance in the desktop marketplace. One of the first realizations that must be made is that the majority of this market consists of non-technical users who are unlikely to either understand or have the desire to understand various technical details about why the new operating system is “better” than a competitor’s. This means that such details are extremely unlikely to sway a large amount of users towards the operating system by themselves. The incentive for a consumer to continue using their existing operating system or only upgrade to one that is backwards compatible is also very strong due to the importance of application software.
    [Show full text]
  • Computing :: Operatingsystems :: DOS Beyond 640K 2Nd
    DOS® Beyond 640K 2nd Edition DOS® Beyond 640K 2nd Edition James S. Forney Windcrest®/McGraw-Hill SECOND EDITION FIRST PRINTING © 1992 by James S. Forney. First Edition © 1989 by James S. Forney. Published by Windcrest Books, an imprint of TAB Books. TAB Books is a division of McGraw-Hill, Inc. The name "Windcrest" is a registered trademark of TAB Books. Printed in the United States of America. All rights reserved. The publisher takes no responsibility for the use of any of the materials or methods described in this book, nor for the products thereof. Library of Congress Cataloging-in-Publication Data Forney, James. DOS beyond 640K / by James S. Forney. - 2nd ed. p. cm. Rev. ed. of: MS-DOS beyond 640K. Includes index. ISBN 0-8306-9717-9 ISBN 0-8306-3744-3 (pbk.) 1. Operating systems (Computers) 2. MS-DOS (Computer file) 3. PC -DOS (Computer file) 4. Random access memory. I. Forney, James. MS-DOS beyond 640K. II. Title. QA76.76.063F644 1991 0058.4'3--dc20 91-24629 CIP TAB Books offers software for sale. For information and a catalog, please contact TAB Software Department, Blue Ridge Summit, PA 17294-0850. Acquisitions Editor: Stephen Moore Production: Katherine G. Brown Book Design: Jaclyn J. Boone Cover: Sandra Blair Design, Harrisburg, PA WTl To Sheila Contents Preface Xlll Acknowledgments xv Introduction xvii Chapter 1. The unexpanded system 1 Physical limits of the system 2 The physical machine 5 Life beyond 640K 7 The operating system 10 Evolution: a two-way street 12 What else is in there? 13 Out of hiding 13 Chapter 2.
    [Show full text]
  • Open WATCOM Programmer's Guide
    this document downloaded from... Use of this document the wings of subject to the terms and conditions as flight in an age stated on the website. of adventure for more downloads visit our other sites Positive Infinity and vulcanhammer.net chet-aero.com Watcom FORTRAN 77 Programmer's Guide Version 1.8 Notice of Copyright Copyright 2002-2008 the Open Watcom Contributors. Portions Copyright 1984-2002 Sybase, Inc. and its subsidiaries. All rights reserved. Any part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of anyone. For more information please visit http://www.openwatcom.org/ Portions of this manual are reprinted with permission from Tenberry Software, Inc. ii Preface The Watcom FORTRAN 77 Programmer's Guide includes the following major components: · DOS Programming Guide · The DOS/4GW DOS Extender · Windows 3.x Programming Guide · Windows NT Programming Guide · OS/2 Programming Guide · Novell NLM Programming Guide · Mixed Language Programming · Common Problems Acknowledgements This book was produced with the Watcom GML electronic publishing system, a software tool developed by WATCOM. In this system, writers use an ASCII text editor to create source files containing text annotated with tags. These tags label the structural elements of the document, such as chapters, sections, paragraphs, and lists. The Watcom GML software, which runs on a variety of operating systems, interprets the tags to format the text into a form such as you see here. Writers can produce output for a variety of printers, including laser printers, using separately specified layout directives for such things as font selection, column width and height, number of columns, etc.
    [Show full text]
  • Operating System
    OPERATING SYSTEM INDEX LESSON 1: INTRODUCTION TO OPERATING SYSTEM LESSON 2: FILE SYSTEM – I LESSON 3: FILE SYSTEM – II LESSON 4: CPU SCHEDULING LESSON 5: MEMORY MANAGEMENT – I LESSON 6: MEMORY MANAGEMENT – II LESSON 7: DISK SCHEDULING LESSON 8: PROCESS MANAGEMENT LESSON 9: DEADLOCKS LESSON 10: CASE STUDY OF UNIX LESSON 11: CASE STUDY OF MS-DOS LESSON 12: CASE STUDY OF MS-WINDOWS NT Lesson No. 1 Intro. to Operating System 1 Lesson Number: 1 Writer: Dr. Rakesh Kumar Introduction to Operating System Vetter: Prof. Dharminder Kr. 1.0 OBJECTIVE The objective of this lesson is to make the students familiar with the basics of operating system. After studying this lesson they will be familiar with: 1. What is an operating system? 2. Important functions performed by an operating system. 3. Different types of operating systems. 1. 1 INTRODUCTION Operating system (OS) is a program or set of programs, which acts as an interface between a user of the computer & the computer hardware. The main purpose of an OS is to provide an environment in which we can execute programs. The main goals of the OS are (i) To make the computer system convenient to use, (ii) To make the use of computer hardware in efficient way. Operating System is system software, which may be viewed as collection of software consisting of procedures for operating the computer & providing an environment for execution of programs. It’s an interface between user & computer. So an OS makes everything in the computer to work together smoothly & efficiently. Figure 1: The relationship between application & system software Lesson No.
    [Show full text]