|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
As a coil moves past a magnet, an emf is produced due to the qv * B force produced. Even if the coil is the stationary object and the magnet is being moved, the same induced electric field is produced. Because of this occurrence, the electrons are not being moved by the magnetic force, which means that this occurs because of some other effect. The effect is caused by an induced electric field being produced when a magnetic field changes with time. The induced electric field lines that are produced are circular and run perpendicular to the changing magnetic field that produced them. The magnitude of the induced electric field is calculated by the equation, Faraday's Law: - 1 CS450 Misc - 1.1 John's website - - 2 Operating System 08/20/03 - 2.1 intermediary between users and resources of computer system - 2.2 one type of a system's program - 2.3 manages hardware - 2.4 controls interactions between user and hardware - 2.5 promotes convenient and efficient sharing of system resources - 3 Computing system - 3.1 physical resources - 3.1.1 harware - 3.1.2 provides basic computing functionality of system - 3.1.3 eg. processors, memory, I/O devices, disks - 3.2 logical resources - 3.2.1 collections of information such as data or programs - 3.2.2 stored within physical resources - 3.2.3 eg. files, processes, jobs or sessions, application and system programs processes - program in execution jobs - complete unit of work application program - product software for a user to accomplish system program - provide system related services to both users and application programs - 3.3 user/program interfaces - 3.3.1 provides application usage and functionality of system - 3.4 hardware interface - 3.4.1 provides device management and device drivers - 4 User interface - 4.1 command interpreter - 4.2 application interface - 4.3 most visible portion of the OS - 5 Process management - 5.1 involves scheduling of processes scheduling - deciding which process gets CPU usage - 5.2 interleaved execution - 5.2.1 multiple processes having short use of CPU sharing - 5.3 multiprogramming - 5.3.1 allows multiple processes to share CPU - 6 Job and session management job - complete unit of work; in batch processing session - series of commands executed to OS on behalf of a specific user; unit of work - 7 Device management - 7.1 involves all aspects of controlling I/O and devices - 7.2 responding to errors - 7.3 deciding which process receives each device - 8 Time management - 8.1 involves control and manipulation of internal devices called clocks - 8.2 controlling time slices - 9 Memory management - 9.1 involves a set of tasks that involve controlling and allocating main memory - 9.2 swapping process into and out of memory - 10 File management - 10.1 reading, writing, organizing files - 11 Semester Project 08/22/03 - 11.1 construct a basic operating system - 11.2 MPX - 11.2.1 multiprogramming executive - 11.3 For every module - 11.3.1 main C file - 11.3.2 header file - 11.3.2.1 defined constants, data types, global variable - 11.3.3 source file - 11.3.3.1 function bodies - 12 Types of computers 08/25/03 - 12.1 mainframes - 12.2 mini-computer - 12.3 micro-computer - 13 Range of OS's, for above three - 13.1 no OS - 13.2 single user OS - 13.3 multi-programming - 14 OS generations There is never an abrupt change in generations due to large investment of money - 14.1 Generation Zero - 1940-50 - 14.1.1 time before OS - 14.1.2 enormous and expensive - 14.1.3 single user machines - 14.1.4 one program at a time - 14.1.5 written in machine language - 14.1.6 biggest problem - 14.1.6.1 CPU IDLE TIME If a person is stuck with a problem, the CPU isn't being used - 14.1.7 simple I/O devices Data and programs could be prepared ahead of time on cards or tape to save time instead of one instruction at a time -> more people can use machine -> increased CPU usage - 14.1.7.1 paper tape - 14.1.7.2 punched cards - 14.1.7.3 printers - 14.1.7.4 special piece of software needed -> loader Used with the card reader - 14.1.8 assembler language - 14.1.8.1 special program called assembler is required - 14.1.8.2 steps to running a program - 14.1.8.2.1 load the loader - 14.1.8.2.2 load the assembler - 14.1.8.2.3 read the program - 14.1.8.2.3.1 re-read the program - 14.1.8.2.4 create the object deck - 14.1.8.2.5 re-load the loader - 14.1.8.2.6 load the linker - 14.1.8.2.7 read the object deck - 14.1.8.2.8 read system libraries - 14.1.8.2.9 punch the loadable (executable) image - 14.1.8.2.10 load the loader - 14.1.8.2.11 load MY program - 14.1.8.2.12 run the program - 14.1.9 big innovations - 14.1.9.1 high-level language - 14.1.9.2 magnetic tapes - 14.1.9.2.1 faster - 14.1.9.2.2 output from steps is sent to tape rather than cards - 14.1.9.2.3 separate smaller computer manages job input - 14.1.9.3 employment of professional operators - 14.1.9.3.1 load, execute, and run programs - 14.1.9.3.2 leads to programmer losing control - 14.1.9.3.2.1 debugging is harder - 14.1.9.3.3 manually batched jobs - 14.1.9.3.3.1 ran jobs that needed similar resources one after another - 14.2 Generation One - Mid 1950's - Supervisors and I/O Systems - 14.2.1 goals - 14.2.1.1 make computing more convenient - 14.2.1.2 automate some of the operator's tasks - 14.2.1.3 make jobs fast as possible, still only one at a time - 14.2.1.4 programs had to contain device specific code - 14.2.2 1953 - 14.2.2.1 Herb Grosch - 14.2.2.1.1 GM released the input/output system for the IBM 701 - 14.2.2.1.1.1 early OS - 14.2.2.1.1.2 always loaded into memory - 14.2.2.1.1.3 provided a common set of procedures to do I/O - 14.2.3 Share IBM users group - 14.2.3.1 created OS for IBM 704 - 14.2.3.1.1 internal support for assembly language programming - 14.2.3.1.2 buffered I/O management - 14.2.3.1.3 supervisory control (most important aspect) - 14.2.3.1.3.1 automated loading, switching of jobs, etc.
Approximate Word count = 1416
Approximate Pages = 5.7
(250 words per page double spaced)
|
|
|
|
|
|