1 / 16

Case Study: Windows 2000 Part I

Case Study: Windows 2000 Part I. Will Richards CPSC 550 Spring 2001. Windows 2000 Part I. History Overview Design Micro Kernel Plug and Play (PnP) NT File System (NTFS). History. 1981 MS-DOS 1.0 1986 Windows 1.03 1993 MS-Windows 3.11 (Windows for Workgroups) 1993 Windows NT

kendall-sutton
Télécharger la présentation

Case Study: Windows 2000 Part I

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. Case Study: Windows 2000 Part I Will Richards CPSC 550 Spring 2001

  2. Windows 2000 Part I • History • Overview • Design • Micro Kernel • Plug and Play (PnP) • NT File System (NTFS)

  3. History • 1981 MS-DOS 1.0 • 1986 Windows 1.03 • 1993 MS-Windows 3.11 (Windows for Workgroups) • 1993 Windows NT • 1995 Windows 95 • 1996 Windows NT 4.0 • 1998 Windows 98 • 2000 Windows 2000

  4. Overview • Windows 2000 Professional • Replaces NT Workstation • Can Handle 2 CPU’s and 4 Gig of ram • Requires 1 Gig of disk space • Windows 2000 Server • Replaces the NT Server • Can Handle 4 CPU’s and 4 Gig of Memory

  5. Overview 2 • Windows 2000 Advanced Server • Provides support for distributed computing, clusters and load balancing • Can Handle 8 CPU’s and up to 8 Gig of Ram • Windows 2000 Datacenter Server • Can Handle 32 CPU’s and up to 64 Gig of Ram

  6. Design Goals • Kernel API: • minimize the need for parameters and flags when programming. • Better documentation and support • Better Handling of errors • Posix and C2 Compliance

  7. Formal Design • Simple, well documented, using common coding standards • Major portions designed as subsystems • Subsystem design allows additional subsystems • Every subsystem coded for security features • Validation of arguments by subsystem called

  8. Kernel Mode Overview • System uses a layered format • Kernel Layers • The Executive • Device Drivers • Hardware Abstraction Layer (HAL)

  9. PnP manager Executive See page 296 fig 12.3 of the text System Layers PnP manager Setup Applications User Mode Kernel Mode Object Manager Process and Thread Manager Device Drivers HAL

  10. The Executive • Object Manager • Process and Thread Manager • Security Reference Monitor • Local Procedure Call (LPC) Facility • Virtual Memory Manager • I/O Manager

  11. The Executive 2 • Systems within the Executive are responsible for error handling • All arguments passed in a system call are checked by the called system • Calls made by other kernel processes are assumed correct • Calls made from outside the Kernel are thoroughly checked • Exceptions raised when needed

  12. Plug and Play • New to NT and thus Win2K • Improved over Win 9x • User knows at installation, if drivers are certified by Microsoft for use. • Increased reliability of the system • Responsible for Win2k reaching 99.99% reliability

  13. NT File System (NTFS) • Supports all MS file formats including: • FAT (floppies), FAT-32 (Win 98), CDFS (CD-ROMs), and UDF (DVD’s) • Provides a means to interchange files between different systems • Uses ACL, Reparse Points and Storage Management

  14. Access Control Lists (ACL) • NTFS employs ACL to maintain a database of security protection for the files. • ACL is maintained locally on each shared volume • Similar to Unix permissions settings. • Also controls User disk space quotas

  15. Storage Management • Single Instance storage • Identifies duplicate data streams and replaces them with a reference to a single instance. Reducing disk space usage. • Remote Storage • Similar to a caching scheme • Allows user to see remotely stored data as though it was stored locally. • Invisible to the user • When the data is in use, it is pulled from remote storage and stored locally in a cache • When the data has not been actively used, it is placed back in remote storage.

  16. Reparse Points • Allows the system to determine how to handle a file at the time is it being accessed • Contained in the files reference. • Indicates the file type.(Win9X, NTFS, third party etc) • Indicates actual location • Allows Win2K to operate w/ third party file system filters, allowing customized storage management

More Related