Correspondence; 1958-1989; Bulk

Total Page:16

File Type:pdf, Size:1020Kb

Correspondence; 1958-1989; Bulk Honeywell Interoffice Correspondence Date: 19 79 January 19 RECEIVED To: L. W. Beers JAN 2 2 1979 From: R. W. Bemer l. W. (ROY) BEERS Location: Subject: Introducing a New Major Operating System 1. Around 1966, Univac introduced EXEC8 to supplant EXEC2. It was a superior design, fabricated by better software production methods than are currently in use here at Phoenix. Customers went 4 full years more with EXEC 2 before EXEC8 was sufficiently workable to be accepted. 2. GCOS 66 has been talked for several years. Many actions were deferred on the assumption of its availability. It is still not released for general test. 3. The design of GCOS 66 is superior to that of GCOS 3, just as EXEC8 was a better design than EXEC2. But customers for the first few years of its life will be unable to discern any substantial superiority over GCOS 3. Therefore, they will stay with the familiar, which in many cases contains their own modifications, and avoid the retraining problem. My conclusion: There is no safe way to sidestep continuous upgrading of GCOS 3 for competitive position in the field. 25 (4-78 ) !! RECEIVED [ Honeywell Interoffice Correspondence <711 NOV 3 Ib/e phr&' L W. (ROY) BEERS 41^ Date: November 1, 1978 cc: ^L. W. Beers C. Clingen To: E. R. Vance R. A. Forzani I H*- e, W. P. Frink From: R. R. Douglas G. A. Gillette S. G. Jerritts Location: LISD S. Klee J5 D. F. Manzer yn'"^3i J. Ring Subject: A Basic Software Operating PhilosophyPfiilosbnhv ' ' P. N. Stoughton I. M. Wyman Having had an opportunity to spend a considerable amount of time on reviewing our Software Development organization, I would like to now describe my thoughts about what needs to be done from an organization and operating standpoint within LISD's software groups. Ideally, I would like to be able to preserve the marketing benefits of three focused operating systems, but it is patently clear to me that we do not have sufficient resources to support three major operating systems on an independent basis. We are not generating sufficient revenues and bottom line results to permit us to enjoy this luxury unless we can become more effective in our development activity. We already see ourselves under terrific pressure across all fronts to provide greater levels of function­ ality and use which frustrate us in terms of maintaining a state- of-the-art situation for any of our systems. Correspondingly, working closely with Roy Beers and Dewey Manzer's organization, I want you to put the following into operation immediately: 1. You must focus the development of our three operating system functionalities (GCOS, Multics, and CP-6) on very specific market targets. I do not see the neces­ sity of having Multics look like GCOS, GCOS look like CP-6 and CP-6 look like Multics. Each of the three systems has its own design points with unique strengths and weaknesses. Your approach should be to focus future developments of these three operating systems on market targets which exploit the strengths that we have in each of the systems. For example, the market thrust for GCOS might be in the batch, database, and transaction processing world with multi-dimensional capabilities in timesharing and remote batch. We should exploit Multics' strength in interactive terminal management, security, integrated communication services, relational database capability and its good user interface. We should not only look upon CP-6 as a migration vehicle for the Sigma base to a Level 66 hardware base, but also look at it from the standpoint of its applicability as a high-performance timesharing product offering, employing the same underlying CF 25 (4-78) f HONEYWELL INTEROFFICE CORRESPONDENCE E. R. Vance November 1, 1978 Page two set of engines as GCOS. In all cases, market targets should be selected which hopefully will reduce market­ ing costs as an objective. We cannot afford to go in and do too many hard conversions. We need to be very selective in the choice of market targets such as time­ sharing, publications management, the universal front-end, etc., and attempt to minimize the amount of marketing investment to secure new-name accounts. I would like you to immediately convene a group of your people, along with Marketing, Systems Engineering and Product Planning, to address this area. I am going to look for a resolution of this matter by December 1, 1978, so I can present it to the management group on December 11, 1978. It may not be final by that point in time, but sufficient work should be done such that we have a direction. 2. Recognizing the fact that we have three operating systems, it is incumbent upon us to cut down the overall costs associated with the development, maintenance and support of three operating systems. This implies a strategy whereby we develop dependent components in a high level language and rehost them under our three operating systems. I recognize that this is not easy, but it has to be done if we are going to keep going in the direc­ tion we are proceeding. Unfortunately, we tend to be locked in based on past marketing strategies and programs, and we need to evolve our whole long-term software stra­ tegy in a more evolutionary fashion. The implication of this strategy implies that you develop single centers of expertise. To my way of thinking, the benefits that we would derive from this are the best use of our resources at the lowest overall cost, the development of high levels of expertise in dependent component areas, a uniformity of user interface, reduced documentation costs within LISD, Marketing and FED, reduced cost in Marketing Support and FED as a result of reduced training requirements and sup­ port requirements, and a singular support of a DSE strategy. The implications of this are many. It does not imply, how­ ever, that it all needs to be done in Phoenix. This concept has implications in the area of the control of file systems, language compilers, a job control language, a database management system, an end-user facility, utilities, and our overall networking strategies. I would like a recom­ mendation from you by November 15 on the form this would take from an organizational standpoint so that we can get on with it. I recognize that it isn't going to be easy to do, but it has to be done to support the three operating systems strategy. If we are unable to make this organization CF 25-1 " HONEYWELL INTEROFFICE CORRESPONDENCE E. R. Vance November 1, 1978 Page three and development strategy work, then most likely we are going to be faced with the reality of having to cancel a major operating system. My thought process runs along the lines that we need a COBOL 79 center of expertise, a file system center of expertise, a FORTRAN center of expertise, a database management system center of expertise, an end-user facility center of expertise, etc. Last, but not least, you need to develop a programming standards and methodology function that will improve portability and productivity. 3. I think that you should adopt a subcontract strategy of a magnitude of 5 to 10% of our total outlay. This will give us a ride-over capability in case we encounter an economic downturn which would force some reduction in expense levels in R&D. I would prefer to take the reduction in outside contracting rather than do it against permanent staff. Further, if you are clever, the contracting can be done on completion dates on six-month intervals so that you have the capacity to adjust in a current year given sufficient lead time. 9. As a major subset of number 2, I think we need to develop a file processing strategy. We need to determine what is it, how are we going to do it, and what is involved in making it happen. One of our problems in the entire Engineering and Product Planning structure within LISD is that we endlessly debate doing things, and hence, nothing seems to get done. This is a critical area that I want to follow-up on with you shortly after you've had an opportunity to do some work on it. 5. You need to develop a common remote maintenance strategy with Product Planning and Systems Engineering, whose objective is to provide increased availability and respon­ siveness while removing FED costs. This is a high impact program, and it is one that must be accomplished quickly. I think your organization has been far too passive on this. 6. Along with Product Planning and Marketing, you need to give very serious consideration to what options we have and what programs we need to put in place to improve our ability to convert from foreign systems. This has too long been neglected in software development. CF 25-1 HONEYWELL INTEROFFICE CORRESPONDENCE E. R. Vance November 1, 1978 Page four 7. I feel very strongly that your organization, if con­ structed in the fashion above, needs to speak to the competitiveness of the products which are being developed in it. I want your COBOL people to be able to tell me why the COBOL they have is the best in the business. For the market target selected, I want the operating system people to be able to tell me why it's the best operating system around. The same applies to all of the dependent components that we produce. This has to be forced into your organization, and I intend to follow-up with key managers on very specific dates in the future to determine their understanding of how competitive their product really is in the marketplace.
Recommended publications
  • Standards for Computer Aided Manufacturing
    //? VCr ~ / Ct & AFML-TR-77-145 )R^ yc ' )f f.3 Standards for Computer Aided Manufacturing Office of Developmental Automation and Control Technology Institute for Computer Sciences and Technology National Bureau of Standards Washington, D.C. 20234 January 1977 Final Technical Report, March— December 1977 Distribution limited to U.S. Government agencies only; Test and Evaluation Data; Statement applied November 1976. Other requests for this document must be referred to AFML/LTC, Wright-Patterson AFB, Ohio 45433 Manufacturing Technology Division Air Force Materials Laboratory Wright-Patterson Air Force Base, Ohio 45433 . NOTICES When Government drawings, specifications, or other data are used for any purpose other than in connection with a definitely related Government procurement opera- tion, the United States Government thereby incurs no responsibility nor any obligation whatsoever; and the fact that the Government may have formulated, furnished, or in any way supplied the said drawing, specification, or other data, is not to be regarded by implication or otherwise as in any manner licensing the holder or any person or corporation, or conveying any rights or permission to manufacture, use, or sell any patented invention that may in any way be related thereto Copies of this report should not be returned unless return is required by security considerations, contractual obligations, or notice on a specified document This final report was submitted by the National Bureau of Standards under military interdepartmental procurement request FY1457-76 -00369 , "Manufacturing Methods Project on Standards for Computer Aided Manufacturing." This technical report has been reviewed and is approved for publication. FOR THE COMMANDER: DtiWJNlb L.
    [Show full text]
  • Čestné Prohlášení
    VYSOKÉ UČENÍ TECHNICKÉ V BRNĚ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA STROJNÍHO INŢENÝRSTVÍ ÚSTAV STROJÍRENSKÉ TECHNOLOGIE FACULTY OF MECHANICAL ENGINEERING INSTITUTE OF MANUFACTURING TECHNOLOGY VÝROBA PLYNOVÝCH VENTILŮ NA AUTOMATICKÉ LINCE PRODUCTION OF GAS VALVES ON THE AUTOMATIC LINE DIPLOMOVÁ PRÁCE DIPLOMA THESIS AUTOR PRÁCE BC. MILAN PEŠL AUTHOR VEDOUCÍ PRÁCE ING. MAREK ŠTRONER, PH.D. SUPERVISOR BRNO 2011 Vysoké učení technické v Brně, Fakulta strojního inženýrství Ústav strojírenské technologie Akademický rok: 2010/2011 ZADÁNÍ DIPLOMOVÉ PRÁCE student(ka): Bc. Milan Pešl který/která studuje v magisterském navazujícím studijním programu obor: Strojírenská technologie a průmyslový management (2303T005) Ředitel ústavu Vám v souladu se zákonem č.111/1998 o vysokých školách a se Studijním a zkušebním řádem VUT v Brně určuje následující téma diplomové práce: Výroba plynových ventilů na automatické lince v anglickém jazyce: Production of gas valves on the automatic line Stručná charakteristika problematiky úkolu: Na základě poznatků při výrobě plynových ventilů na automatické lince ve firmě Honeywell bude řešena problematika automatizace a manipulace, chodu automatické linky, testování ventilů, akce na snížení počtu vadných kusů při výrobě a implementace kamerového systému na detekci chyb šroubování. Cíle diplomové práce: Seznámení s automatizovanou výrobní linkou na plynové ventily a její rozložení. Popis principu práce linky a typy ventilů, které se na ní výrábějí. Testy používané ke kontrole funkčnosti ventilů. Statisté zhodnocení výroby a kamerový systém pro kontrolu šroubů. Seznam odborné literatury: 1. DRAŽAN, František., JEŘÁBEK, Karel. Manipulace s materiálem. 1. vyd. Praha : SNTL, 1989. 456 s. ISBN 04-220-79. 2. HLAVENKA, Bohumil. Manipulace s materiálem. 4. vyd. Brno : VUT, 2001. 164 s. ISBN 80-214-0068-4.
    [Show full text]
  • Standards for Computer Aided Manufacturing
    NBSIR 76-1094 (R) Standards for Computer Aided Manufacturing John M. Evans, Jr., Ph.D., Project Manager Joseph T. O'Neill John L. Little James S. Albus, Ph.D. Anthony J. Barbera, Ph.D. Dennis W. Fife, Ph.D. Elizabeth N. Fong David E. Gilsinn, Ph.D. Frances E. Holberton Brian G. Lucas, Ph.D. Gordon E. Lyon, Ph.D. Beatrice A. S. Marron Albercht J. Neumann Mabel V. Vickers Justin C. Walker Office of Developmental Automation and Control Technology Institute for Computer Sciences and Technology National Bureau of Standards Washington, D. C. 20234 Second Interim Report October, 1976 Prepared for Manufacturing Technology Division Air Force Materials Laboratory Wright-Patterson Air Force Base, Ohio 45433 NBSIR 76-1094 (R) STANDARDS FOR COMPUTER AIDED MANUFACTURING John M. Evans, Jr., Ph D., Project Manager Joseph T. O'Neill John L. Little James S. Albus, Ph D. Anthony J. Barbera, Ph.D. Dennis W. Fife, Ph.D. Elizabeth N. Fong David E. Gilsinn, Ph D. Frances E. Holberton Brian G. Lucas, Ph D Gordon E. Lyon, Ph D. Beatrice A. S. Marron Albercht J. Neumann Mabel V. Vickers Justin C. Walker Office of Developmental Automation and Control Technology Institute for Computer Sciences and Technology National Bureau of Standards Washington, D. C. 20234 Second Interim Report October, 1976 Prepared for Manufacturing Technology Division Air Force Materials Laboratory Wright-Patterson Air Force Base, Ohio 45433 U.S. DEPARTMENT OF COMMERCE. Elliot L. Richardson, Secretary Edward O. Vetter, Under Secretary Dr. Betsy Ancker-Johnson, Assistant Secretary for Science and Technology NATIONAL BUREAU OF STANDARDS, Ernest Ambler.
    [Show full text]
  • Creativity – Success – Obscurity
    Author Gerry Pickering CREATIVITY – SUCCESS – OBSCURITY UNIVAC, WHAT HAPPENED? A fellow retiree posed the question of what happened. How did the company that invented the computer snatch defeat from the jaws of victory? The question piqued my interest, thus I tried to draw on my 32 years of experiences in the company and the myriad of information available on the Internet to answer the question for myself and hopefully others that may still be interested 60+ years after the invention and delivery of the first computers. Computers plural, as there were more than one computer and more than one organization from which UNIVAC descended. J. Presper Eckert and John Mauchly, located in Philadelphia PA are credited with inventing the first general purpose computer under a contract with the U.S. Army. But our heritage also traces back to a second group of people in St. Paul MN who developed several computers about the same time under contract with the U.S. Navy. This is the story of how these two companies started separately, merged to become one company, how that merged company named UNIVAC (Universal Automatic Computers) grew to become a main rival of IBM (International Business Machines), then how UNIVAC was swallowed by another company to end up in near obscurity compared to IBM and a changing industry. Admittedly it is a biased story, as I observed the industry from my perspective as an employee of UNIVAC. It is also biased in that I personally observed only a fraction of the events as they unfolded within UNIVAC. This story concludes with a detailed account of my work assignments within UNIVAC.
    [Show full text]
  • NLJAN2013.Pdf
    1 2 WHO WE ARE: ABB is a global leader in power and automation technologies. Based in Zurich, Switzerland, the company employs 145,000 people and operates in approximately 100 countries. The firm’s shares are traded on the stock exchanges of Zurich, Stockholm and New York. ABB’s business is comprised of five divisions that are in turn organized in relation to the customers and industries we serve. The company in its current form was created in 1988, but its history spans over 120 years. ABB’s success has been driven particularly by a strong focus on research and development. The company maintains seven corporate research centres around the world and has continued to invest in R&D through all market conditions. The result has been a long track record of innovation. Many of the technologies that underlie our modern society, from high-voltage DC power transmission to a revolutionary approach to ship propulsion, were developed or commercialized by ABB. Today, ABB stands as the largest supplier of industrial motors and drives, the largest provider of generators to the wind industry, and the largest supplier of power grids worldwide. HISTORY OF THE COMPANY RECRUITMENT STEPS: APTITUDE 1883 GROUP DISSCUSIONS Ludvig Fredholm establishes Elektriska Aktiebolaget in Stockholm as TECHNICAL manufacturers of electrical lighting and generators INTERVIEW HR INTERVIEW 1933 BBC obtains the patent for turbine rotors constructed from individual steel disks that are welded 3 1942 CURRENT STATUS: ASEA builds the world's first 120 MVA, 220 kV transformer in the Stockholm Elverks Värtanstation JOBS AVAILABLE=1336 1952 JOBEMPLOYERS =165K ASEA designs and installs the first 400 kV AC cable – a 70 m low TECHNOLOGIES=8000 pressure oil-filled (LPOF) cable connecting an underground power station (built to withstand an atomic bomb) to the Swedish grid.
    [Show full text]
  • Honeywell International Inc
    UNITED STATES SECURITIES AND EXCHANGE COMMISSION WASHINGTON, D.C. 20549 Form 10-K ☒ ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended December 31, 2020 OR ☐ TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the transition period from to Commission file number 1-8974 Honeywell International Inc. (Exact name of registrant as specified in its charter) Delaware 22-2640650 (State or other jurisdiction of (I.R.S. Employer incorporation or organization) Identification No.) 300 South Tryon Street Charlotte, North Carolina 28202 (Address of principal executive offices) (Zip Code) Registrant’s telephone number, including area code (704) 627-6200 Securities registered pursuant to Section 12(b) of the Act: Title of Each Class Trading Symbols Name of each exchange on which registered Common Stock, par value $1 per share* HON The New York Stock Exchange 1.300% Senior Notes due 2023 HON 23A The New York Stock Exchange 0.000% Senior Notes due 2024 HON 24A The New York Stock Exchange 2.250% Senior Notes due 2028 HON 28A The New York Stock Exchange 0.750% Senior Notes due 2032 HON 32 The New York Stock Exchange * The common stock is also listed on the London Stock Exchange. Securities registered pursuant to Section 12(g) of the Act: None Indicate by check mark if the Registrant is a well-known seasoned issuer, as defined in Rule 405 of the Securities Act. Yes ☒ No ☐ Indicate by check mark if the Registrant is not required to file reports pursuant to Section 13 or Section 15(d) of the Exchange Act.
    [Show full text]
  • Directory of Educational Programs in Information Science 1971-1972
    DOCUMENT RESUME ED 056 728 LT 003 272 AUTHOR Wilkie, Lorna C., Ed. TITLE Directory of Educational Programsin Information Science 1971-1972. Science, Washington, INSTITUTION American Society for Information D.C. SPONS AGENCY American Society for InformationScience, Washington, D.C. Special Interest Group onEducation for Information Science.; ERICClearinghouse on Library and Information Sciences,Washington, D.C. PUB DATE Nov 71 NOTE 1109.;(3 References) AVAILABLE FROM American Societyfor Information Science, 1140 Connecticut Ave., Suite 804,Washington, D.C. 20038 (HC Members $4.50Non-members 55.00) EDRS PRICE mr-$0.65 HC Not Available fromEDRS. DESCRIPTORS Directories; *Education;Information centers; Information Processing;*Information Science; *Information Scientists;*Information Systems; *Information Theory ABSTRACT For the purposes of thisDirectory, information science includes the followingsubjects: library and information systems, library automation andnetworks, systems analysis, manacrement information systems,information needs and uses, abstracting and indexing, advancedclassification theory, non-traditional techniques oforganizing knowledge, managementof reprography, computational technical information centers, theory. The linguist s, man-machineinteraction, and information Directory includes an introduction, atable of contents, a compilation of entries arrangedby school and department or program, and four indexes. Separateentries are made for eachdepartment or program even though someof them are at the sameuniversity. The "Index of EducationalInstitutions by State and Province"is an alphabetical list of the statesin the United States andprovinces in Canada. The other threeindexes are: "Index of DegreesOffered," "Index of Information ScienceCourses Offered," and "Indexof Faculty Members Interested in InformationScience." This first edition ofthe Directory describes only thosegraduate programs with primary emphasis on information sciencerather than on its two major applications, namely computer scienceand library science.
    [Show full text]
  • Application for Renewal of Honeywell Metropolis Works
    Honeywell Specialty Materials Honeywell P.O. Box 430 Highway 45 North Metropolis, IL 62960 618 524-2111 618 524-6239 Fax May 27, 2005 U.S. Nuclear Regulatory Commission (UPS: 301-415-6334) Attention: Michael Raddatz Fuel Cycle Licensing Branch, Mail Stop T-8A33 Two White Flint North, 11545 Rockville Pike Rockville, MD 20852-2738 Subject: Renewal of USNRC Source Materials License Re: Docket No. 40-3392 License No. SUB-526 Dear Sirs, Please find enclosed the Honeywell International Inc. application for renewal of USNRC Source Materials License SUB-526 for Honeywell's Metropolis, Illinois Uranium Conversion Facility (Docket No. 40-3392). This application has been prepared in accordance with the requirements of 10 CFR 40. The content and format of the application and supporting materials are generally consistent with the guidance provided in USNRC Regulatory Guide 3.55, "Standard Format and Content for the Health and Safety Section of License Renewal Applications for Uranium Hexafluoride Production." We have incorporated certain variations from this guidance consistent with our April 26, 2005 discussions with the NRC staff. Enclosed are the following: * One original and 7 copies of the Metropolis Works USNRC Source Materials License Application (Regulatory Guide 3.55 Chapters 1 through 7), including USNRC Form 313 * One original and 7 copies of the revised Metropolis Works Emergency Response Plan * One original and 7 copies of the Metropolis Works Safety Demonstration Report (Regulatory Guide 3.55 Chapters 8 through 14), including related drawings and appendices * One original and 7 copies of the Metropolis Works Environmental Report * One compact disc containing the text files for each of the above in pdf format Attached to this letter, please find a summary of the significant changes to the License Application and Safety Demonstration Report.
    [Show full text]
  • An Interview With
    An Interview with W. EARL BOEBERT OH 460 Conducted by Jeffrey R. Yost on 28 April 2015 Computer Security History Project Albuquerque, New Mexico Charles Babbage Institute Center for the History of Information Technology University of Minnesota, Minneapolis Copyright, Charles Babbage Institute W. Earl Boebert Interview 28 April 2015 Oral History 460 Abstract Computer security pioneer Earl Boebert discusses his education at Stanford University before the bulk of the interview focuses on his work within the Air Force and at Honeywell. Among the topics he discusses are the Air Force Undergraduate Navigator Training System, efforts to save and market Multics (and the inherent challenges given GE’s existing systems and the economics of the mainframe business), PSOS, Sidewinder, the formation of Secure Computing Corporation. Also discussed is his role in the broader computer security research community including serving on many National Research Council committees, including the one producing the influential 1991 Computers at Risk. This material is based upon work supported by the National Science Foundation under Grant No. 1116862, “Building an Infrastructure for Computer Security History.” 2 Yost: My name is Jeffrey Yost from the Charles Babbage Institute at the University of Minnesota, and I’m here this afternoon on April 28, 2015 with Earl Boebert in Albuquerque, New Mexico. This is for CBI’s NSF-funded study “Building an Infrastructure for Computer Security History.” Earl, can you begin by just giving me some basic biographical information, where and when you were born? Boebert: I was born in Elko, Nevada in 1939. My father was a railroad policeman. I’m an only child.
    [Show full text]
  • Pergamon Titles of Interest Journals Computer Languages Computers
    Pergamon Titles of Interest Journals Computer Languages Computers & Data Bases Computers & Education Computer & Graphics Computers & Human Concern Computers & the Humanities Computers & Urban Society Books Author-Subject Index to Computers and the Humanities 11 Computer-Assisted Research IN THE r^/^^/^e/ A Directory of Scholars Active Edited by Joseph Raben Queens College City University of New York PERGAMON PRESS New York / Toronto / Oxford / Sydney / Frankfurt / Paris Pergamon Press Offices: U.S.A. Pergamon Press Inc., Maxwell House, Fairview Park, Elmsford, New York 10523, U.S.A. U.K. Pergamon Press Ltd., Headington Hill Hall, Oxford 0X3, OBW, England CANADA Pergamon of Canada, Ltd., 207 Queen's Quay West, Toronto 1, Canada AUSTRALIA Pergamon Press (Aust) Pty. Ltd., 19a Boundary Street, Rushcutters Bay, N.S.W. 2011, Australia FRANCE Pergamon Press SARL, 24 rue des Ecoles, 75240 Paris, Cedex 05, France WEST GERMANY Pergamon Press GmbH, 6242 Kronberg/Taunus, Frankfurt-am-Main, West Germany Copyright © 1977 Pergamon Press Inc. Library of Congress Cataloging in Publication Data Main entry under title: Computer-assisted research in the humanities. Includes index. 1. Humanities - Data processing -- Directories. I. Raben, Joseph. AS8.C63 001.3'028'54 75-16447 ISBN 0-08-019870-8 All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means: electronic, electrostatic, magnetic tape, mechanical, photocopying, recording or otherwise, without permission in writing from the publishers. Printed in the United States of America Preface This book is a response to a frequently expressed need for a single reference work describing the great variety of computer-assisted research in the humanities and the related social sciences.
    [Show full text]
  • Highlights from Digital Computer Museum Report 1/1982
    file:////cray/Shared/COLLECTIONS/Curator/mondo_museum_report.htm Return to List of Reports Highlights from Digital Computer Museum Report 1/1982 Contents of Highlights ● Back of Front Cover ● The Director's Letter ● Unusual Photos ● LECTURE SERIES Back of Front Cover The Digital Computer Museum is an independent, non-profit, charitable foundation. It is the world's only institution dedicated to the industry-wide preservation of information processing devices and documentation. It interprets computer history through exhibits, publications, videotapes, lectures, educational programs, excursions, and special events. Hours and Services The Digital Computer Museum is open to the public Sunday through Friday, 1:00 pm to 6:00 pm. There is no charge for admission. The Digital Computer Museum Lecture Series Lectures focus on benchmarks in computing history and are held six times a year. All lectures are videotaped and archived for scholarly use. Gallery talks by computer historians, staff members and docents are offered every Wednesday at 4:00 and Sunday at 3:00. Guided group tours are available by appointment only. Books, posters, postcards, and other items related to the history of computing are available for sale at the Museum Store. The Museum's lecture hall and reception facilities are available for rent on a prearranged basis. For information call 617-467-4443. BOARD OF DIRECTORS Charles Bachman C. Gordon Bell Gwen Bell Harvey C. Cragon Robert Everett C. Lester Hogan Theodore G. Johnson Andrew C. Knowles, III John Lacey Pat McGovern George Michael Robert N. Noyce Kenneth H. Olsen Brian Randell Edward A. Schwartz Michael Spock Erwin O. Tomash Senator Paul E.
    [Show full text]
  • Virtual Machine
    Virtual machine A virtual machine (VM) is a software implementation of a machine (i.e. a computer) that executes programs like a physical machine. Definitions A virtual machine was originally defined by Popek and Goldberg as "an efficient, isolated duplicate of a real machine". Current use includes virtual machines which have no direct correspondence to any real hardware.[1] Virtual machines are separated into two major categories, based on their use and degree of correspondence to any real machine. A system virtual machine provides a complete system platform which supports the execution of a complete operating system (OS). In contrast, a process virtual machine is designed to run a single program, which means that it supports a single process. An essential characteristic of a virtual machine is that the software running inside is limited to the resources and abstractions provided by the virtual machine²it cannot break out of its virtual world. Example: A program written in Java receives services from the Java Runtime Environment (JRE) software by issuing commands to, and receiving the expected results from, the Java software. By providing these services to the program, the Java software is acting as a "virtual machine", taking the place of the operating system or hardware for which the program would ordinarily be tailored. System virtual machines See also: Platform virtualization and Comparison of platform virtual machines System virtual machines (sometimes called hardware virtual machines) allow the sharing of the underlying physical machine resources between different virtual machines, each running its own operating system. The software layer providing the virtualization is called a virtual machine monitor or hypervisor.
    [Show full text]