Maximum length: 7 pages Time alloted: 30 minutes



Download 35.41 Kb.
Date31.07.2017
Size35.41 Kb.
#25687
Maximum length: 7 pages

Time alloted: 30 minutes

Windows 95 case study


  1. Background ( people involved , history and progress )

  2. Motives or goals

  3. Architecture

  4. Features

  5. Problems faced

  6. Evolution

  7. Outcomes

I.Background :


Journey of os started with dos which is a command line interface , developed by ibm , but then its copyright was taken by microsoft. Dos is a cli. By cli we mean, an interface which is fully handled by using commands. It takes less memory space but we need to remember commands .




II.Developed by : microsoft


Place : chicago

Released : august 24, 1995.

Kernal type: monolithic

III.Motives and goals:




  • Windows 95 is the first gui (graphical user interface) which is user friendly also. It is so because it introduces the concepts of icons, mouse cursor, etc. Hence, its hardware requirement and cost also increases.



  • It introduces system tools, control panel, icons, menu bar, etc. It also has greater compatibility with softwares.


IV.Architecture:




  1. Hardware: it is a 32 bit system for application robustness.

  2. Device driver:

    1. Windows 95/98 uses a universal driver/mini-driver architecture.

    2. The actual system interface to the hardware (or some software parts) is through a virtual device driver (vxd).

    3. These keep track of the state of the device for each application and ensure that the device is in the correct state whenever an application continues.

    4. This allows for multitasking programming and also for multi-access for a single device.





examples:

      1. Msmouse.vxd ms mouse

      2. Serial.vxd serial port

      3. Unimodem.vxd modem

      4. Wsock.vxd winsock

      5. Javasup.vxd javascript

      6. Pppmac.vxd ppp connection






  1. Configuration manager:

    1. Windows 3.x and dos is did not automate pc configuration. For this purpose, windows 95/98 has a configuration manager.





I) the left-hand side of shows how it integrates into the system.

Ii)the right side of figure an example device connection of a pc.



B) aim : monitor the pc for any changes to the number of devices connected and also the device types. If it detects any changes then it manages the reconfiguration of the devices.

    1. Operations performed:

      1. The configuration manager communicates with each of the bus enumerators and asks them to identify all the devices on the buses and their respective resource requirements.



      1. The bus enumerator locates and gathers information from either the device drivers or the bios services for that particular device type.



      1. Each of the drivers is then loaded and wait for the configuration manager to assign their specific resources.



      1. Configuration manager calls on resource arbitrators to allocate resources for each device.



      1. Resource arbitrators identify any devices which are conflicting and tries to resolve them.



      1. The configuration manager informs all device drivers of their device configuration.

this process is repeated when the bios or one of the other bus enumerators informs configuration manager about a system configuration change.

  1. Ifs: installable file systems.

    1. Windows 95/98/nt supports a layered file system architecture that directly supports multiple file systems (such as, fat and cdfs).





    1. the above diagram is explained as follows:

      1. Ifs manager : this is the arbiter for the access to different file system components. On ms-dos and windows 3.x it was provided by interrupt 21h.



      1. File system drivers:



      1. Input/output supervisor (ios). This component provides for an interface between the file systems and drivers.



      1. Port driver. This component is a 32-bit, protected-mode driver.



      1. Scsi layer: it is used for communicating with scsi devices.



      1. Miniport driver: it used for writing device-specific code.



  1. Vmm: virtual machine manager



    1. In windows 95/98 the virtual machine manager (vmm) provides each application with the system resources when it needs them.

    2. It creates and maintains the virtual machine environments in which applications and system processes run.

    3. The vmm is responsible for three areas.

      1. Memory paging.

      2. Ms-dos mode support.



  1. Registry: in windows 95/98/nt use a central database called the registry which stores user specific and configuration-specific information at a single location….. An important role for the registry is to store hardware-specific information which can be used by hardware detection and plug-and-play programs.



  1. Windows 95/98 core: windows 95 has 3 main core components as follows:



User

Kernal

Gdi







(graphical device interface)

  • Provides input and output to and from the user interface



  • Input is form the keyboard, mouse, and any other input device and the output is to the user interface.



  • Manages interaction with the sound driver, timer, and communications ports.



  • Use an asynchronous input model for system input




  • File i/o services





  • Virtul memory management



  • Task scheduling



  • Provides services to both 16-bit and 32-bit applications by using a thunking process






  • Manages information that appears on the screen.



  • Draws graphic and manipulates bitmaps.



  • Uses a 32- bit graphics engine known as dib (device-independent bitmaps)



  • Support for deferred printing



  • Support for bi-directional communication .



  • Plug-and-play.






  1. Ui tools:

  2. Application:

V.Windows 95 features :




  1. A new user interface

  2. Plug and play

  3. Long filenames

  4. Improved system performance

  5. True preemptive multitasking

  6. Scalable performance

  7. Built-in fax and electronic messaging

  8. The microsoft network online service

  9. Access to the internet

  10. Support for 32-bit applications

  11. Mobile computing anywhere

  12. Increased robustness

  13. Less frustrating the whole computing experience

  14. Better, faster games(15.16.17. Better graphics)

  15. Compatibility with existing ms-dos–based and windows–based applications(13.15)

  16. Functionality is more discoverable

  17. Remote performance monitoring and configuration editing tools

  18. Can restore crashed system to working state

  19. Run windows 95 locally or from a server

  20. Multiple users can share a single system and get different configurations

  21. Enable people to work on multiple things at once

  22. Make information easier to access

  23. Enable new, more productive applications and systems

  24. Reliable, and most thoroughly tested product in history

  25. Built-in transition tools for windows 3.1 users


VI.Evaluation:


evaluation is done on the basis of :



  1. Ease of use

  2. Performance

  3. Compatibility of device and application support

  4. Support for networking and connectivity

  5. Support for manageability and administration

  6. Support for communications and messaging

  7. Support for mobile services and remote access



Ease of use

Performance

Compatibility

Manageability

  • Evaluate on the basis of of both novice and experienced users.

  • How the operating system performs overall while performing multiple tasks simultaneously

  • Whether the replaced os can run with the existing hardware and software.

  • It must support management mechanisms that adhere to existing standards or its infrastructure must be designed for adaptability to a new standards.

  • Is the operating system easy to learn and use.

  • Can users discover new features

  • Is it flexible, speedy, and powerfull.

  • Is it working well with different hardware and software.

  • How well it completes benchmark tests.

  • Is it working well with networked environments.

  • Are devices easily recognized, installed, and configured by the operating system?

  • Does the new os allows you to run the applications of previous os

  • Does it provides services like multimedia,

Remote access and other communication programs.

  • Does the os provide the tools for supporting management mechanisms

  • Does the os provide tools and mechanisms to customize and control the functionality on the desktop?

  • Does the os provide support for managing desktop pcs remotely over a network?
















Networking

Remote access




Communications

  • Operating system must be able to provide network support for a broad base of clients

  • To realize seamless mobility, users must be able to easily communicate whether they are in the office, at a customer site, or at home.



Increased demand of internet allowing users to discover new communications and messaging possibilities

  • Is the operating system an open, layered networking architecture.

  • Does the operating system have built-in, native support for popular networks?

  • Does the operating system natively support a wide range of network protocols such as tcp/ip

  • Does the operating system support remote access to the key services or information you need on your corporate network?

  • Does the operating system have robust support for the dynamic nature of mobile hardware, such as pcmcia, power management, and docking stations?



  • Does the os support high-speed communications and related hardware

  • Does the os provide messaging capabilities, such as faxing, dial-up access and online information services, etc.



VII.Outcomes:




  • Windows 95 is the first gui in true sense. It is because it introduces the concepts of icons, menubars and buttons, etc. We have experienced new features and graphical improvements in windows 95



  • Previous systems were16-bit os ,but windows 95 is a 32 bit os that results in its robustness also.



  • It supports long file names, multiple file formats and plug and play concept. Most importantly, it supports internet connectivity.



  • Performance



  • So we conclude that windows 95 gives the experience and difference in technology, compatability and stability.


Download 35.41 Kb.

Share with your friends:




The database is protected by copyright ©ininet.org 2024
send message

    Main page