Larry Portner, Bob Puffer. Andy Knowles Was Important, Particularly in the Way We Worked, There Was Enormous Stress Between Marketing and Engineering
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Windows XP History and Versions
Lecture 23: Windows XP History and Versions n Mid-80ies Microsoft and IBM cooperated to develop OS/2 n Windows XP is produced by Microsoft Co. n 1988 - Microsoft started to develop its own new technology (NT) OS n XP is multi-user, multi-process, preemptive multitasking OS, 30M lines of source code capable of running OS/2, Windows and Unix apps. Hired Dave Cutler - architect of DEC VAX/VMS to head the design n It is developed to support multiple platforms and targeted towards enterprise workstations and server market as well as n NT v. 3.1 first released commercially July 1993 desktops n NT v 4.0 adopted Windows 95 user interface, graphics code moved into kernel to improve performance n In today’s lecture n 2000 – improved networking and laptop support, support for plug-and- u XP’s predecessors, the history of XP design, XP versions play devices, support for more processors (up to 8) and memory, u design principles becomes true multi-user through terminal server u components n XP (released Oct 2001) – update for 2000 replacement for 95/98 F hardware abstraction layer u simplifies user interface, improved reliability, performance F executive improvements, partial 64-bit support F environmental subsystems n versions F file system u desktop: XP personal – 95/98 replacement, professional – advanced features like POSIX support, some network features 1 u server: .NET – support for web/print service, clusters, large memory2 and multiple processors Design goals Components n XP is microkernel-based, modular n security – NT was C-2 certified (US -
Unifying the User and Kernel Environments
Unifying the User and Kernel Environments Richard P. Draves Scott M. Cutshall March 12, 1997 Technical Report MSR-TR-97-10 Microsoft Research Microsoft Corporation One Microsoft Way Redmond, WA 98052 Unifying the User and Kernel Environments Richard P. Draves and Scott M. Cutshall Microsoft Research One Microsoft Way Redmond, WA 98052 http://www.research.microsoft.com Abstract Vendors of commercial operating systems today invest resources in two very different environments—one for user- level (application or server) programming and one for kernel-level (device driver or subsystem) programming. The kernel environment is typically more restrictive, with completely different interfaces and programming conventions. Based on our experience developing and deploying an operating system for an interactive TV system, we believe that it is desirable to unify the user and kernel environments. We structured our operating system to provide common programming and run-time environments for user-level code and kernel-level code. For example, modules loaded into the kernel did not have any restrictions on their use of shared libraries or stack space. We found that unifying the user and kernel environments with common interfaces and run-time requirements, common documentation, and a common debugger produced significant software-engineering benefits. In addition, we could transparently collocate trusted server code in the kernel to reduce memory usage and improve performance. 1. Introduction We advocate structuring operating systems to unify the user and kernel environments. The operating system should present a single environment, with common interfaces or APIs, common run-time characteristics for scheduling, paging, stack usage, and shared libraries, common debugger and development tools, etc. -
Roadmap for Section 1.2
Unit OS1: Overview of Operating Systems 1.2. The Evolution of Operating Systems Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze Roadmap for Section 1.2. History of Operating Systems Tasks of an Operating System OS as extension of the hardware Main concepts: processes, files, system calls Operating system structuring 3 1 Operating Systems Concepts System software manages resources OS hides complexity of underlying hardware Layered architectures Banking Airline Web browser Application programs system reservation Command Compilers Editors interpreter System programs Operating system Machine language Microprogramming Hardware Physical devices 4 History of operating systems Batch processing The elements of the basic IBM 1401 system are the 1401 Processing Unit, 1402 Card Read-Punch, and 1403 Printer. Punching cards Multiprocessing programming Job 3 Job 2 Memory Job 1 partitions OS 5 2 The Evolution of Operating System Functionality Batch Job Processing Linkage of library routines to programs Management of files, I/O devices, secondary storage Multiprogramming Resource managment and sharing for multiple programs Quasi-simultaneous program execution Single user Multiuser/Timesharing Systems Management of multiple simultaneous users interconnected via terminals Fair resource management: CPU scheduling, spooling, mutual exclusion Real-Time Systems (process control systems) Management of time-critical processes High requirements with respect to reliability and availability 6 Tasks of an Operating -
What We Learned from the PDP-11
ABSTRACT Gordon Bell, William Il. Strecker November 8, 1975 COMPUTER STRUCTURES: WHAT HAVE WE LEARNED FROM THE PDP-ll? Over the FDP-11’S six year life behave in a particular way? about 20,000 specimens have been Where does it get inputs? HOW built based on 10 species (models). does it formulate and solve Al though range was a design goal, problems? it was unquantified; the actual range has exceeded expectations 3. The rest of the DEC (5OO:l in memory size and system organization--this includes price]. The range has stressed the applications groups assoc ia ted baa ic mini (mall computer with market groups # sales, architecture along all dimensions. service and manufacturing. The marn PM.5 structure, i.e. the UNIBUS, has been adopted as a de 4. The user, who receives the facto standard of interconnection final OUtQUt. for many micro and minicomputer systems. The architectural Note, that if we assume that a experience gained in the design and QrOduc t is done sequentially, and use of the PDP-11 will be described each stage has a gestation time of in terms Of its environment about two years, it takes roughly (initial goals and constraints, eight years for an idea from basic technology, and the organization research to finally appear at the that designs, builds and user’s site. Other organizations distributes the machine). ala0 affect the design : competitors (they establish a deaign level and determine the product life): and government IsI 1.0 TNTRODUCTTON and standards. There are an ever increasing number Although one might think that of groups who feel compel led to computer architecture is the sole control all products bringing them determinant of a machine, it is all common norm : the merely the focal point for a government (“5) , testing groups such specification. -
VAX VMS at 20
1977–1997... and beyond Nothing Stops It! Of all the winning attributes of the OpenVMS operating system, perhaps its key success factor is its evolutionary spirit. Some would say OpenVMS was revolutionary. But I would prefer to call it evolutionary because its transition has been peaceful and constructive. Over a 20-year period, OpenVMS has experienced evolution in five arenas. First, it evolved from a system running on some 20 printed circuit boards to a single chip. Second, it evolved from being proprietary to open. Third, it evolved from running on CISC-based VAX to RISC-based Alpha systems. Fourth, VMS evolved from being primarily a technical oper- ating system, to a commercial operat- ing system, to a high availability mission-critical commercial operating system. And fifth, VMS evolved from time-sharing to a workstation environment, to a client/server computing style environment. The hardware has experienced a similar evolution. Just as the 16-bit PDP systems laid the groundwork for the VAX platform, VAX laid the groundwork for Alpha—the industry’s leading 64-bit systems. While the platforms have grown and changed, the success continues. Today, OpenVMS is the most flexible and adaptable operating system on the planet. What start- ed out as the concept of ‘Starlet’ in 1975 is moving into ‘Galaxy’ for the 21st century. And like the universe, there is no end in sight. —Jesse Lipcon Vice President of UNIX and OpenVMS Systems Business Unit TABLE OF CONTENTS CHAPTER I Changing the Face of Computing 4 CHAPTER II Setting the Stage 6 CHAPTER -
Gordon's Personal View of Personal Computing: Before the PC
Gordon’s Personal View of Personal Computing: before the PC Vintage Computer Society 27 September 1998 Gordon Bell [email protected] http://www.research.microsoft.com/~gbell Apple II First personal computer Micral In the beginning: Manchester “Baby” ran the first program 22 June 1948 English Electric Deuce Console 1955 Whirlwind c1953 … 1st generation, 16-bit word; 4 KB memory; 8 K drum Whirlwind begot TX-O/TX-2 begot DEC PDP-1 Real time, first compiler, ECAD, text editor Whirlwind console, drum, 1 Kw core SAGE Control Room c 1962. Whirlwind used for first experiments. SAGE (Semi-Automatic Ground Environment) Operator Console TX-0 Console c1959… one of the first transistorized personal computers Speech, handwriting recognition, neuro data analysis, etc. Interactive editors, debuggers, etc. MIT Speech group with TX-0, c1959. DEC Computer before PDP-11 1957 1961 1963 DEC PDP-1 c1961 Wes Clark & LINC c1962: Personal computers for bio-medical research PDP-5 c1964: PDP-8 predecessor Process control, real time experiments. Fortran ran in 4 K, 12 bit words Gbell with LINC and PDP-8 c1965 PDP-8: first mini First OEM computer. OS/8 (from timesharing) begot RT-11 begot CPM PDP-8 Modules PDP-8/E PDP-8 and Linc Family Tree PDP-8 12 bit word price (t) PDP-8 prices (t) Timesharing: given everyone their own, low cost, personal computer PDP-6 c1965 : First commercial time shared computer. Gbell & Alan Kotok PDP-6 Development team c1965 PDP-6/10/ DECsystem 10/20 family tree TThheerree iiss nnoo rreeaassoonn aannyyoonnee wwoouulldd wwaanntt aa ccoommppuutteerr iinn tthheeiirr hhoommee. -
MICROSOFT WINDOWS Early Versions Main Articles: Windows 1.0
MICROSOFT WINDOWS Early versions Main articles: Windows 1.0, Windows 2.0, and Windows 2.1x Windows 1.0, the first version, released in 1985 The history of Windows dates back to September 1981, when Chase Bishop, a computer scientist, designed the first model of an electronic device and project "Interface Manager" was started. It was announced in November 1983 (after the Apple Lisa, but before the Macintosh) under the name "Windows", but Windows 1.0 was not released until November 1985.[5] Windows 1.0 achieved little popularity and was to compete with Apple's own operating system. Windows 1.0 is not a complete operating system; rather, it extends MS-DOS. The shell of Windows 1.0 is a program known as the MS- DOS Executive. Components included Calculator, Calendar, Cardfile, Clipboard viewer, Clock, Control Panel, Notepad, Paint, Reversi, Terminal and Write. Windows 1.0 does not allow overlapping windows. Instead all windows are tiled. Only modal dialog boxes may appear over other windows. Windows 2.0 was released in December 1987 and was more popular than its predecessor. It features several improvements to the user interface and memory management.[citation needed] Windows 2.03 changed the OS from tiled windows to overlapping windows. The result of this change led to Apple Computer filing a suit against Microsoft alleging infringement on Apple's copyrights.[6][7] Windows 2.0 also introduced more sophisticated keyboard shortcuts and could make use of expanded memory. Windows 2.1 was released in two different versions: Windows/286 and Windows/386. Windows/386 uses the virtual 8086 mode of Intel 80386 to multitask several DOS programs and the paged memory model to emulate expanded memory using available extended memory. -
Thesis May Never Have Been Completed
UvA-DARE (Digital Academic Repository) Digital Equipment Corporation (DEC): A case study of indecision, innovation and company failure Goodwin, D.T. Publication date 2016 Document Version Final published version Link to publication Citation for published version (APA): Goodwin, D. T. (2016). Digital Equipment Corporation (DEC): A case study of indecision, innovation and company failure. General rights It is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), other than for strictly personal, individual use, unless the work is under an open content license (like Creative Commons). Disclaimer/Complaints regulations If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons. In case of a legitimate complaint, the Library will make the material inaccessible and/or remove it from the website. Please Ask the Library: https://uba.uva.nl/en/contact, or a letter to: Library of the University of Amsterdam, Secretariat, Singel 425, 1012 WP Amsterdam, The Netherlands. You will be contacted as soon as possible. UvA-DARE is a service provided by the library of the University of Amsterdam (https://dare.uva.nl) Download date:26 Sep 2021 Digital Equipment Corporation (DEC) (DEC) Corporation Digital Equipment David Thomas David Goodwin Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure David Thomas Goodwin Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure David Thomas Goodwin 1 Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure ACADEMISCH PROEFSCHRIFT ter verkrijging van de graad van doctor aan de Universiteit van Amsterdam op gezag van de Rector Magnificus prof. -
Bell's Law of Computer Classes
Bell’s Law; P,M,S Structures; Rules of thumb; and Taxonomies 1957-1998. 41 yrs. 4 generations: Tubes > transistors > ICs, VLSI (micros) > clusters - winner take all How computer classes form, evolve …and die (according to economically based laws) Gordon Bell Microsoft Research, Silicon Valley Laboratory References Moore’s Law http://www.computerhistory.org/semiconductor/timeline/1965-Moore.html Bell’s Law: http://research.microsoft.com/research/pubs/view.aspx?0rc=p&type=technical +report&id=1389 Bell, C. G., R. Chen and S. Rege, "The Effect of Technology on Near Term Computer Structures," Computer 2 (5) 29-38 (March/April 1972). IEEE History Center's Global History Network: http://ieeeghn.org/wiki/index.php/STARS:Rise_and_Fall_of_Minicomputers In retrospect…by 1971, the next 50 years of computing was established 1. Moore’s Law (1965) transistors/die double every 18 mos. 2. Intel 4004, Processor-on-a-chip (1971) Clearly, by 1978 16-bit processor-on-a-chip 3. Bell et al 1971 observation...computer evolution 1. Computers evolve at constant price (Moore’s Law) 2. Computer clases form every decade (Bell’s Law) New technology, manufacturers, uses and markets How I think about computers • P,M,S describes architectures i.e. the components and how they are interconnected and interact – Reveals structure (size, cost, performance, power, etc.) – Parallelism, bottlenecks, and rules of thumb – Functional evolution to compete with larger computers • Bell’s Law determines classes birth & death • Rules of thumb determine goodness • Taxonomies enumerate alternatives A Walk-Through Computer Architectures from The Largest & Fastest to the Digestible Computers have evolved from a bi-furcation of: • calculating (P) aka scientific and record keeping (M) aka commerce to • control (K), • interfacing (T/Transduction) including GUIs, NUI, and • Communication (L), switching (S) and networking (N) Every information carrier from greeting cards to phones is an embedded computer. -
2.5 Win-History [Read-Only]
Unit OS2: Operating System Principles 2.5. History of the Windows NT/2000/XP/2004 OS Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze Copyright Notice © 2000-2005 David A. Solomon and Mark Russinovich These materials are part of the Windows Operating System Internals Curriculum Development Kit, developed by David A. Solomon and Mark E. Russinovich with Andreas Polze Microsoft has licensed these materials from David Solomon Expert Seminars, Inc. for distribution to academic organizations solely for use in academic environments (and not for commercial use) Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 2 1 Roadmap for Section 2.5. History of NT Windows Release History and Versions New features in Windows XP/2003 Original Windows Design Goals/Culture How Development Processes evolved throughout Windows NT 3.1 Development and Windows 2000 Development Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 3 NT Timeline first 10 years 2/89 Coding Begins 7/93 NT 3.1 Ships 9/94 NT 3.5 Ships 5/95 NT 3.51 Ships 7/96 NT 4.0 Ships 12/99 NT 5.0 a.k.a. Windows 2000 ships Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 4 2 Unix Timeline first 20 years ’69 Coding Begins ’71 First Edition – PDP 11/20 ’73 Fourth Edition – Rewritten in C ’75 Fifth Edition – Leaves Bell Labs, basis for BSD 1.x ’79 Seventh Edition – One of the best ’82 System III ’84 4.2 BSD ’89 SVR4 Unification of Xenix, BSD, System V NT development begins Windows Operating System Internals - by David A. -
Oral History Interview with Joseph F. Traub
An Interview with JOSEPH F. TRAUB OH 94 Conducted by William Aspray on 29 March 1985 Columbia University (New York, NY) Charles Babbage Institute The Center for the History of Information Processing University of Minnesota, Minneapolis Copyright, Charles Babbage Institute 1 Joseph F. Traub Interview 29 March 1985 Abstract The main topic is institutions in computing. Traub begins by discussing why computer science has developed as a discipline at some institutions but not others. Institutions that are highlighted include Stanford, Berkeley, University of Pennsylvania, MIT, and Carnegie-Mellon. Traub discusses his experiences as chairman of the computer science departments at Carnegie-Mellon and later Columbia. Other topics include: industrial and government funding of computer science departments (in particular the role of the Advanced Research Projects Agency of the Defense Department); the relationships between academic centers, such as M.I.T., Stanford, Columbia, and Carnegie-Mellon; and the importance of educational institutions to regional centers of industrial computing. At the end of the interview Traub returns to a topic of his earlier interviews, his experiences at Bell and Watson Laboratories. 2 JOSEPH F. TRAUB INTERVIEW DATE: 29 March 1985 INTERVIEWER: William Aspray LOCATION: Columbia University (New York, NY) ASPRAY: This is a session on the 29th of March, 1985, with Joseph Traub in his office at Columbia University. It is the third in a series of interviews, and the main topic in this session is institutions in computing. Why don't we start by talking about why certain universities - Pennsylvania, Harvard, Columbia, which had strong early activities in computing - didn't develop into first-rate research and teaching centers in computer science? TRAUB: It seems to me that in each of the institutions, that have become the major centers one can usually identify one or two people who were responsible. -
Computing History: a Personal and Industry View
or attempted designs; seven reaIly suc- ceeded, about 20 are still trying, and a COMPUTING HISTORY: A whoIt flock are no longer with us. including American Computet, Atron, BIT, and Viatron. With some under- PERSONAL AND INDUSTRY standing of the historic generational patterns my goal was to get DEC into VIEW/GORDON BELL large scale integrated circuits and to establish the YAX line as a new stan- lis. and Herbert Simon wrote a letter to dard. And ironically, this year 20 years Science and identified computer sci- after the first PDP-8 was built, sales of ence. The next steps, what we now call the machine were higher than ever “the third and fourth generations’’ weren’t at all clear. At Carnegie, Allen Newel1 and I collected materials and years objects from past machines to build Ironically, his year 20 theories. This resulted in a book en- 1 der he fint PDP$ was titled Computer Srructuras that in- fluenced at least two generations of built des of the muchine computer architects. The concepts of the DEC Unibus and general registers were higher hnever. came from this work. Other Carnegie alumni extended and implemented thae ideas in subsequent (and future) since it is implemented on a single chip DEC computers. These developments and embedded in a word processor. came from a deep knowIedgc of past Now one of my goals is to con- computers, and how they were used sider not just the development of a sin- and gave some insights about the fu- gle company, but of the entire industry ture trajectory of computer evolution.