PC 102 A Operating Systems - PowerPoint PPT Presentation

1 / 31
About This Presentation
Title:

PC 102 A Operating Systems

Description:

Some material excerpted without permission from Microsoft, Oracle courseware ... Jumpers. Presented by Phillip Schein for ComputerEd Institute, 2002 ... – PowerPoint PPT presentation

Number of Views:26
Avg rating:3.0/5.0
Slides: 32
Provided by: 4re
Category:

less

Transcript and Presenter's Notes

Title: PC 102 A Operating Systems


1
PC 102A Operating Systems
  • Methodology Revisited

2
MOTD
Work from the top down
3
  • What are the 3 components of any project plan
    that were discussed in class?
  • 1.
  • 2.
  • 3.

4
  • What are the 3 components of any project plan
    that were discussed in class?
  • Scope
  • Resources
  • Schedule

5
  • Name the 5 functional management areas that are
    part of the NOS/DOS operating systems we have
    discussed in class?
  • 1.
  • 2.
  • 3.
  • 4.
  • 5.

6
  • Name the 5 functional management areas that are
    part of the NOS/DOS operating systems we have
    discussed in class?
  • Configuration
  • Performance
  • Fault
  • Security
  • Auditing

7
  • People
  • Process
  • Property

Security (Authentication/Authorization/Auditing)
Performance Fault Configuration
8
  • Write an inventory list of at least 8 hardware
    components that are part of a generic motherboard
    as discussed in class.
  • 1.
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.
  • 8.

9
  • Write an inventory list of at least 9 hardware
    components that are part of a generic motherboard
    as discussed in class.
  • Processor (socket or slot)
  • (system bus)
  • Memory Module(s)
  • (expansion bus)
  • EIDE controllers
  • FDD controller
  • ISA/PCI expansion slots
  • ROM Bios
  • CMOS Setup (chip)
  • Battery
  • AGP port
  • I/O Ports
  • Jumpers

10
Object/Entity Relationships
Functional
Physical / Logical
  • Input/Output
  • Processor
  • Storage

Primary Secondary Component Configuration
11
Methodology
  • Use Scenarios (Cases)
  • People (Actors) / Needs (Required/Optional)
  • Scope, Resources, Schedule
  • Block Diagrams Reference Models
  • System Architecture / Inventory
  • Installation / Process Flows
  • Linear / Layered
  • Data Flow Diagramming
  • PseudoEnglish scripting/programming

12
  • Name the 7 functional components of a Windows 95
    operating system. Use the diagram that was
    discussed in class and included in your class
    handout.
  • 1.
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.

13
  • Name the 7 functional components of a Windows 95
    operating system. Use the diagram that was
    discussed in class and included in your class
    handout.
  • Physical (substrate)
  • VM (virtual memory manager)
  • IFS (installable file system manager)
  • Config (configuration manager)
  • UI (user interface)
  • Registry
  • Application

14
Windows 98 Architecture
User Interface - 32 bit shell
Windows 98 Core
VMMngr
IFSMngr
ConfigMngr
WDM Driver Mngr
Device Drivers
Basic Input Output System
Hardware Substrate
15
  • You have been provided with a bootup diskette.
    List the steps necessary to install MS DOS 6.22
    and make a hard drive bootable. These steps must
    be in the correct sequence and provide the proper
    command line syntax.
  • 1.
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.

16
  • You have been provided with a bootup diskette.
    List the steps necessary to install MS DOS 6.22
    and make a hard drive bootable. These steps must
    be in the correct sequence and provide the proper
    command line syntax.
  • Boot from bootup diskette.
  • Delpart existing partitions
  • Fdisk
  • Format c /s
  • Remove bootup diskette
  • Reboot
  • At command prompt type VER

17
NT4 Installation Sequence
  • Power on and boot
  • NTLDR in MBR seeks activated partition
  • NTLDR runs NTDETECT
  • NTLDR runs NTOSKRNL
  • NTOSKRNL assumes control of bootup
  • Specific system components are loaded
  • System launches services
  • Security Attention Sequence (SAS) is provided
  • User logs onto running system to access services

18
Virtual Memory Management in NT4
MS-DosVirtualMachine
MS-DosVirtualMachine
Ring 3
Ring 3
Ring 3
Win32
Win32
Win32
Kernel386, GDI, USER
Ring 0
Kernel32, GDI32, USER32
19
Generic Microsoft NOS Architecture
Win32 Apps
User Mode
CSS
Kernel Mode
20
A Block view of Windows 2K
User Mode Process Space
Win32
Win32
NTVDM
NTVDM
Win16
MS DOS app
WOW
Win16
Win32 SubsystemClient Services
Kernel Mode Process Space
Executive Services
I/O
VM
SM
OM
Video
OS Kernel
Hardware Abstraction Layer
Hardware Substrate
21
HowTosFeature Comparisons
  • Inventory operating system features
  • Recognize functional, physical, logical areas
  • Outline linear/layered installation flows
  • Diagram functional management areas
  • Recognize relationships between these object
    entities
  • Compose scripts for unattended operations
  • Automate specific processes to achieve specific
    objectives/goals
  • Determine scope, tasks, resources, scheduling
    issues

22
Contemporary OS Issues
  • Win 2K
  • HAL with PnP
  • Multiprocessor (either x86 or Alpha
  • Runs in protected mode
  • Separate 16-bit memory
  • Multi-threaded OS
  • NTFS, FAT, or FAT32
  • File and resource rights
  • User-level security
  • Win 9x
  • PnP
  • x86 support only
  • Protected and real
  • Shared 16-bit memory
  • Single threaded
  • FAT or FAT32
  • No rights
  • Limited password security

23
Comparing Business Issues
  • Administration TCO / ROI
  • Applications and System Software, Hardware
  • Security AAA, confidentiality, integrity,
    non-repudiation
  • User Management
  • Support, Maintenance, Training
  • Resource Management
  • Support, Maintenance
  • Scalability Expandability/Extensibility
  • OS Interconnectivity/Interoperability

24
What to ask your client / boss?
  • Determine scope, tasks, resources, schedule

She tells you this
You identify these
She tells you this
When your behavior is goal directed, Every job
you do is a mini project!!!
25
An OS Definition
  • Depending on NOS/DOS -
  • A linear list of goal-directed tasks
  • or ToDos
  • that tells hardware
  • what to do

Who, Where, What, and When
26
A Troubleshooting Punchlist
  • Follow the logical flow
  • System (at the bottom!)
  • Application
  • Data (at the top!)
  • Follow the physical bus
  • Power (at the bottom!)
  • Data/address
  • Control (at the top!)

27
To Be Continued
28
Legacy Single Domain Models
29
Multiple Domain Models
Resource
Resource
Resource
Resource
30
NT 4 Object Authentication
Logon
Logon Dialog Box CtrlAltDelete
Security Subsystem
User Mode
Kernel Mode
ACL
SAM
Access Token
31
Generic Domain Relationships
Trusted Domain
User/Group Account
Trusting Domain
Token
Validation Request
ACL
Write a Comment
User Comments (0)
About PowerShow.com