Professional Documents
Culture Documents
Case Study Final (2022ucm23 23:31)
Case Study Final (2022ucm23 23:31)
MS DOS
(MicroSoft Disk Operating System)
Submitted by
Tanya Chhabra (2022UCM2323)
Kabir Chhabra (2022UCM2331)
MS - DOS
1) INTRODUCTION -
MS - DOS (Microsoft Disk Operating System) is an operating system that was developed
for utilization in personal computers by Microsoft. It is based on Layered structure, split
into various different layers, each layer having its own function to perform.
Its user interface is based on a command line interface (CLI) also known as text - based
interface or character - user interface. It does not have a Graphical user interface (GUI)
like many modern operating systems have, so all commands and operations have to be
performed using CLI.
In MS DOS system calls were made using software interrupts. Some common system
calls in MS - DOS were interrupt 21h, interrupt 10h, interrupt 13h, interrupt 16h, interrupt
33h; Using these interrupts softwares running on MS - DOS could access various
system functions and hardware resources.
System programs are essential for managing operating system and performing various
tasks. These system programs are typically stored in the DOS directory. Some common
system programs in MS - DOS are COMMAND.COM, CHKDSK, FORMAT, DSKCOPY,
DEFRAG etc.
MS DOS did not support preemptive multitasking, meaning it could only execute one
program at a time.When a program was launched, MS-DOS would give control to that
program until it terminated or yielded control back to the operating system. MS-DOS
provided a simple environment where one program could run at a time, and the operating
system primarily served to manage system resources and provide basic services to
running programs.
MS DOS did not have a traditional short term and long term scheduler, since it only
supported a single process at a time.
Process creation and termination was relatively very simple in MS DOS compared to
modern operating systems since it only ran a single process at a time. A process was
created whenever the user typed the name of a program in the command prompt and
then control was transferred to it. Process termination was done in two ways, either
normally by simple exit() command or abnormally (or abruptly) whenever an error was
encountered.
Since MS-DOS was primarily a single-tasking operating system, there was minimal
support for IPC mechanisms.
Shared memory was not a native feature of MS-DOS, programmers could implement
basic shared memory techniques using low-level memory management functions and
custom IPC mechanisms.
MS-DOS itself did not directly support threads or true multitasking, programmers could
simulate concurrent execution or multitasking within the constraints of the environment
using various techniques and third-party tools. Therefore it mainly only supported single
threading. Similarly multicore programming was also quite limited in MS DOS because of
it being a single tasking system, also it did support any kind of Parallelism.
4. Polling and Event flags – Processes could use polling or event flags to
coordinate their activities. For example, one process could periodically check the
status of a file or a memory location to determine if a condition was met before
proceeding. Event flags could be set or cleared by one process to signal other
processes to take specific actions.
3) Deadlocks in MS DOS –
Deadlocks are a concept that primarily applies to multitasking operating systems, where
multiple processes are running concurrently. MS-DOS was not a multitasking operating system
in its original form. It was a single-tasking operating system, meaning it could only run one
program at a time. Therefore, the concept of deadlocks doesn't directly apply to MS-DOS.
However, there were some attempts to introduce multitasking capabilities to MS-DOS through
third-party software such as task-switchers or multitasking environments like DESQview, so
some basic deadlock handling was required.
4) File System Formats – MS-DOS supported various file system formats, including
FAT12, FAT16, and later FAT32. These file systems determined how files and
directories were organized and stored on disk, as well as the maximum file size
and partition size supported.
I/O operations are imperative in all operating systems to allow communication between
internal hardware and peripheral devices. MS DOS provides a set of system calls and
interrupt services to handle such I/O operations effectively.
Here’s an overview of the key components of I/O systems in MS DOS-
a) Device Drivers: These are software modules which are loaded into memory at
boot time and are responsible for communication between internal hardware and
peripheral devices like printers, keyboards etc.
b) Interrupts: MS DOS relies mostly on interrupts for I/O operations. These are
signals generated by the hardware (internal as well as peripheral) to acquire the CPU’s
attention and communicate with other hardware devices.
c) Device I/O ports: These ports provide a means of communication between the
CPU and peripheral devices Device drivers use instructions such as IN and OUT to read
from and write to specific I/O ports, allowing them to control hardware devices directly.
d) BIOS services: MS-DOS interacts with hardware using the BIOS routines which
provide a standardized interface for accessing hardware functions. Applications running
in MS-DOS can make BIOS calls to perform I/O operations without needing to know the
specifics of the underlying hardware.
MS-DOS relies on a combination of device drivers, interrupts, BIOS services, file system
operations, and direct hardware access to manage input/output operations efficiently
and provide a platform for running applications on compatible hardware.
6) System Protection
MS DOS, which is a primitive operating system, has been primarily designed for single
user systems, hence lacks many sophisticated system protection features which can be
found in modern day operating systems.
Some basic aspects of system protection in MS DOS have been discussed below:
b) File System Security: Files and directories are accessible to all users on the
operating system. This is because MS-DOS file systems (such as FAT12, FAT16,
and FAT32) lack built-in access control mechanisms.
e) Boot Sector Protection: MS-DOS boot sectors can be susceptible to viruses and
malware. However, some versions of MS-DOS included utilities for scanning and
cleaning infected boot sectors.
2) MS-DOS Operating
SystemGeeksforGeekshttps://www.geeksforgeeks.o
rg › ms-dos-operating-syst…
4) MS-DOS Operating
SystemJavatpointhttps://www.javatpoint.com ›
ms-dos-operating-system
5) ChatGPT
—--------------------------------------------END OF DOCUMENT—------------------------------------------------