1 / 16

CMPE003 – Personal Computer Concepts

CMPE003 – Personal Computer Concepts. Hardware and Software Winter 2004 Instructor: Scott Cooper scooper@soe.ucsc.edu. Lab sections. Monday 1-3pm Tuesday 10am-12pm Thursday 2-4pm All sections in Oakes 205. Chapter 3: Operating Systems. Software in the Background. The bad old days.

jens
Download Presentation

CMPE003 – Personal Computer Concepts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CMPE003 – Personal Computer Concepts Hardware and Software Winter 2004 Instructor: Scott Cooper scooper@soe.ucsc.edu

  2. Lab sections • Monday 1-3pm • Tuesday 10am-12pm • Thursday 2-4pm All sections in Oakes 205

  3. Chapter 3: Operating Systems Software in the Background

  4. The bad old days • Command line (text) input: wp /p epson c:\templates\equipment.doc • Invokes the program wp on the named file with an option switch (/p) and parameter (epson)

  5. The Mac is born “Obviously it was true that … it would be a good thing to make computers more accessible to a less technical audience – if not for altruistic reasons, then because those sorts of people constituted an incomparably vaster market.” Neal Stephenson, In the Beginning… There Was The Command Line

  6. Layers GUI Command Interpreter Operating System

  7. GUIs • Graphical User Interface created at XEROX PARC • Sometimes called WIMP (Windows, Icons, Mouse, and Pointing) • Unleashed on the world by Apple in 1984 • Two steps back: Windows 3.x released in 1990

  8. Shared resources • Memory • CPU • Storage • Printer • Network • Other devices and peripherals

  9. OS initiates transfer of program code Word.exe Starting applications • What happens when you start a program? Storage Memory Input Processing Output OS

  10. Memory allocation • OS wouldn’t leave a hole, but… unused Operating System Word.exe Solitaire IE • Storage (memory, disk) becomes fragmented over time

  11. Virtual memory • What if it doesn’t all fit? • Treat disk like an extension of memory and move stuff back and forth as needed • Slows processing down • Excessive transfer between memory and the disk is called thrashing You can never be too rich or too thin, or have too much RAM.

  12. File types • How does the OS know which application to open your file with? • Windows uses a 3-letter extension

  13. One thing at a time • CPU can’t do two things at once • Multiprogramming or multitasking makes it look like it by switching rapidly • Who runs next? • For how long? The OS schedules the CPU amongst running programs.

  14. File systems • OS maintains a hierarchy of directories on each disk • Can contain files as well as other directories • Shown as folders in the GUI c:\documents\nicole party music pictures rock dance Invite.doc shins

  15. Device drivers • Programs cannot support every manufacturer’s hardware • Driver models abstract different types of hardware • Manufacturers provide the driver code to implement the model • Programs can treat all models of printers, or removable storage, etc. as if they worked exactly the same

  16. The short version • An operating system allows programs to act as though they have exclusive access to machine resources, while actually sharing them among many programs

More Related