David T. C~Ai9 736 Edgewater [M J Wichita, Kansas 67230 (USA)
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Ucsd-Psystem-Fs UCSD P-System Filesystem Reference Manual
ucsd-psystem-fs UCSD p-System Filesystem Reference Manual Peter Miller [email protected] . This document describes ucsd-psystem-fs version 1.22 and was prepared 21 July 2013. This document describing the ucsd-psystem-fs package, and the ucsd-psystem-fs utility pro- grams, are Copyright © 2006, 2007, 2008, 2010, 2011, 2012, 2013 Peter Miller This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) anylater version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without eventhe implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. See the GNU General Public License for more details. Youshould have receivedacopyofthe GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. 0 Table of Contents(ucsd-psystem-fs) Table of Contents(ucsd-psystem-fs) The README file . ................. 1 Release Notes ................... 2 Howtobuild ucsd-psystem-fs .............. 6 ucsdpsys_disk(1) manipulate files on a UCSD p-System filesystem image ...... 10 ucsdpsys_fsck(1) verify and repair UCSD p-System filesystem images ....... 13 ucsdpsys_fs_license(1) GNU General Public License ............... 14 ucsdpsys_interleave(1) decode interleavedUCSD p-System filesystem image ....... 23 ucsdpsys_mkfs(1) create newUCSD p-System filesystem disk images ........ 25 ucsdpsys_mount(1) mount aUCSD p-System filesystem . ........... 27 ucsdpsys_rt11(1) extract files from RT-11 disk images ............ 29 ucsdpsys_text(1) translate UCSD p-System text files . ............ 30 ucsdpsys_umount(1) unmount UCSD p-System filesystems . -
Implementing the UCSD PASCAL System on the MODCOMP Computer
TDA Progress Report 42-60 September and October 1960 Implementing the UCSD PASCAL System on the MODCOMP Computer T. Wolfe DSN Data Systems Section This article describes the UCSD PASCAL system developed by the University of California, San Diego, now available on the MODCOMP computer. The system includes a Pascal compiler and many useful utility programs. A BASIC compiler and a FORTRAN 77 compiler are also avatkble. There is currently a large amount of software availabie written in UCSD PASCAL, including a data base system, word processing systems and a MODULA compiler. I. Introduction Assembly language subroutines thus produced may also be called from either Pascal or FORTRAN. Currently the assem- The UCSD PASCAL* System is a complete interactive bler has not been modified to produce MODCOMP machine software development system consisting of an operating sys- code. A system library program may be used to build libraries tem, compilers (Pascal, BASIC, FORTRAN 77) two text of useful subroutines and the system linker used to link them editors (screen editor and line-oriented editor), a linker and to user programs. many useful utility programs. The system is written and main- tained in Pascal. The compiler generates code for an idealized processor known as the “pseudo-machine.” The “pseudo- Interpreters currently exist for Z80/8080, PDP 11 /LSI-1 1, code” (p-code) generated by the compiler is interpreted at 6800, 9900 and 6502 computers and are being developed for runtime by a program (known as the interpreter) which emu- other computers. Thus, software could be developed on an lates the pseudo-machine. -
Oral History Interview with John Brackett and Doug Ross
An Interview with JOHN BRACKETT AND DOUG ROSS OH 392 Conducted by Mike Mahoney on 7 May 2004 Needham, Massachusetts Charles Babbage Institute Center for the History of Information Processing University of Minnesota, Minneapolis Copyright, Charles Babbage Institute John Brackett and Doug Ross Interview 7 May 2004 Oral History 392 Abstract Doug Ross and John Brackett focus on the background of SofTech and then its entry into the microcomputer software marketplace. They describe their original contact with the University of California at San Diego (UCSD) and licensing the p-System which had been developed there. They discuss the effort required to bring the program to production status and the difficulties in marketing it to the sets of customers. They talk about the transition from 8 bit to 16 bit machines and how that affected their market opportunities. They conclude with a review of the negotiations with IBM and their failure to get p-System to become a primary operating environment. That, and the high performance of Lotus 1-2-3, brought about the demise of the p- System. [John Brackett requested that the following information from Wikipedia, the free encyclopedia, be provided as an introduction to this oral history interview: “UCSD p-System or UCSD Pascal System was a portable, highly machine independent operating system based upon UCSD Pascal. The University of California, San Diego Institute for Information Systems developed it in 1978 to provide students with a common operating system that could run on any of the then available microcomputers as well as campus DEC PDP-11 minicomputers. UCSD p- System was one of three operating systems (along with PC-DOS and CP/M-86) that IBM offered for its original IBM PC. -
BULLETIN I of AVAILABLE TERAK SOFTWARE (Tugboats) the Terak User's Group Library Is a Clearing House Only; It Does Not Sell, Generate Or Test Prograns
Vol. 2, Issue 1 01·Jan.·82 BULLETIN i OF AVAILABLE TERAK SOFTWARE (Tugboats) The Terak User's Group Library Is a clearing house only; It does not sell, generate or test prograns. All prograns and information are provided "AS IS". Terak User's Group and contributors of software disclaim all warranties on the prograns, Including without I Imitation, all Impl led warranties of merchantabtl ity and fitness. The description, service charges, and ayallabll tty of software available for the Terak User's Group Library are subject to change without notice. Copyright (C) 1982, Terak User's Group; Scottsdale, Arizona DEC, DECUS, RT-l1, PDP-l1 are all trademarks of DIgItal EquIpment CorporatIon. UCSD Pascal Is a trademark of the UnIversIty of CalIfornIa Board of Regents. Terak Is a trademark of the Terak CorporatIon. TABLE OF CONTENTS PAGE TOflCS Introduction •••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 1-1 TUGBOATS Updates •••••••••••••••••••••••••••••••••••••••••••••••••••••• 1-1 Ordering User Group Library Software •••••••••••••••••••••••••••••••••• 1-2 1. RT-ll Operating System •••••••••••••••••••••••••••••••••••••••••••••• 1-1 1.1 Languages •••••••••••••••••••••••••••••••••••••••••••••••••••••••• 1-1 1.2 Editors •••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 1-2 1.3 Device Handlers •••••••••••••••••••••••••••••••••••••••••••••••••• 1-3 1.4 Statistical Routines ••••••••••••••••••••••••••••••••••••••••••••• 1-4 1.5 Disk FormattIng •••••••••••••••••••••••••••••••••••••••••••••••••• 1-5 1.6 Utll Itfes •••••••••••••••••••••••••••••••••••••••••••••••••••••••• -
The UCSD P-System STATUT ORIL Y EX E:M PT
DOCfi!D(ov~ by NSA on 12-01-2011, Transparency Case# 5335]UNCLASSIFIED The UCSD p-System STATUT ORIL Y EX E:M PT This paper discusses the UCSD p-System, an operating system for small computers developed at the University of California at San Diego. The discussion includes the overall system, file managing, editing, and programming in Pascal on the system. INTRODUCTION The UCSD p-System was developed at the University of California at San Diego to support Pascal programming on microcomputers. Similar to MS-DOS, the p-System is an operating system for small computers but is, in many ways, very different. The p-System is written in Pascal and now supports not only Pascal, but also FORTRAN, COBOL, BASIC, and Modula-2. The concept was to have an operating system that, once it was implemented on a machine, allowed any program written under that operating system to be truly transportable from computer to computer. That is to say, the p-System compiler would not actually translate the program into a language that was specific for, say, an 8088 chip on the IBM-PC, but rather would translate it into a "pseudo" language that, when used with an operating system designed for the PC, would run correctly. Similarly, if the operating system were implemented on a Digital Equipment Corporation (DEC) computer, this same pseudo code would still work properly with no modifications. The particular version of UCSD p-System tested was written for the IBM-PC and requires two single-sided double-density disk drives and at least 128K of memory. -
P-System Editors Pascal Assembler
COMPUTER TECHNOLOGY p-System Editors Pascal Assembler 35 NORTH EDISON WAY, SUITE 4· RENO, NEVADA 89502· (702) 322-6868 Contributors at SofTech Microsystems: Software Development: Mark Allen, Gail Anderson, David Berger, Barry Demchak, William Franks, Rich Gleaves, Dean Jacobs, Richard Kaufmann, Stephen Koehler, Mark Overgaard, Stan Stringfellow. Documentation: Randy Clark, Barry Demchak, Rich Gleaves, C.A. Irvine, Bruce Sherman, Stan Stringfellow. End-user Support: H. Blake Berry, Jr., David Barto, Carolyn Chase, Randy Clark, Karen Fraser, Nancy Lanning, Bruce Sherman, George Symons, John Tennant. And thanks too to all the people not named here, at SofTech Microsystems or elsewhere, including the people at Courseware who prepared the illustrations. · DISCLAIMER: These documents and the software they describe are subject to change without notice. No warranty express or implied covers their use. Neither the manufacturer nor the seller is responsible or liable for any consequences of their use. SofTech Microsystems provides telephone and mail support for those users who have purchased their system from either SofTech Microsystems or UCSD (version 1.5 or later). This includes users who purchased their system from retail outlets of SofTech Microsystems. All other users of UCSD Pascal or the UCSD p-System should <;ontact their supplier for support. SofTech Microsystems does not have the resources to support users who purchased their software from other vendors. ACKNOWLEDGEMENTS: The UCSD Pascal project was initiated and guided by the director of the Institute for Information Systems, Professor Kenneth L. Bowles. While at UCSD, the project was supported by a variety of generous contributions, both of money and personal time. -
& Electrical Engineering
COMPUTER ARCUTECTURFL Gordon Bell Vice President, Engineering Digital Equipment Corporation & Professor of Computer Science & Electrical Engineering Carnegie-Mellon University (on leave) Abstract Minimal cost computer designs ( i.e. minicomputers) are predicated on using technological cost-performance improvements which occur at an annual rate of 25-305. New applications are thereby feasible with the decreasing costs. A significant number of minicomputers are manufactured in which the cost is constant (or rising), thereby providing more performance (capabilities). The higher performance machines "taket1 their characteristics from the larger, general purpose camputers (e.g. floating point arith- metic, multiprocessors, cache memories and memory management) . The origin and evolution of the minicomputer will be discussed with regard to technology and applications. 7 17178 THR PDP-I? FAMILY AND VAX-Ill780 FOR A LARGE VIRTUAL ADDRESS Gordon Bell Vice President, Engineering Digital Equipment Corporation & Professor of Computer Science & Electrical Engineering Carnegie-Mellon University (on leave) Abstract In the eight years the PDP-11 has been on the market, more than 50,000 units in ten different models have been sold. Although one of the system design goals was a broad range of models, the actual range of 500 to 1 (in price and memory size) has exceeded the design goal. The PDP-11 was designed and first implemented to be a mall minicomputer. Its first extension was to a bigger physical address, memory segmentation for multiprogramming and for higher performance. This part of the talk will briefly reflect the experience in the design process, comment on its success from the point of view of the goals, and its use of technology. -
It Has to Be Good: a History of the Petroleum
It Has to be Good A History of the Petroleum Abstracts Service at The University of Tulsa John A. Bailey Any opinions or interpretation of facts contained in this document are solely those of the author and do not necessarily reflect policies of The University of Tulsa Copyright 2004 John A. Bailey All Rights Reserved Preface This is the story of an uncommon partnership between industry and an academic institution. An industry segment had a need and a prominent university had the vision, talent and determination to fulfill that need. It is also the story of a great deal of hard work, innovation, occasional crisis and cooperation. It is the story of how an organization reflects the characteristics, experience and mindset of the men (and, so far, they have all been men) that led it. This, then, is the story of the Petroleum Abstracts Service at The University of Tulsa that began over 40 years ago. We have attempted to make the story as interesting as possible, a challenge for someone trained as an engineer and computer professional. While some of the information presented here comes from surviving documents, particularly for the early years, much of it is based on memory and occasional hearsay. The reader will also encounter the occasional inside joke. For these offenses, and for any other deficiencies, the author accepts, however begrudgingly, full responsibility. A Need and an Opportunity The late 1950s was not a good time for the petroleum exploration and production industry. Following the resolution of the Suez crisis in 1956, a surplus of crude supply developed and the resulting decline in oil prices began to erode the economics of the industry. -
Coecim\F 11 -~ 12 655 33'4 31 331/.- 1/2
NOVEMBER 3, 1980 111\'2-1 6 18 323,i, 32'" 32118-:je an Gas 1.96 8 69 20 19~, 1934- 'I. l..opeIIICI .I" "U1 ''I FIlIPwI' :£.411 I 1/, JU'/2 '1'1\'2 XJU'II 5 88 15 14'A1 14'h ...... CinciMH .90 8 252 28 2634 27~-1:tt Ccpwld 1.28 I 2 18'12 18'12- '4 E FllP\..it 2.08 6 334 26~ 2614 26'12- =III 6 175 351f2 341J. 3511. ...... or Fill 2.40 7 129 29~ r29 29~- lie Corckwa .30 10 320 4 3la- ',II ESystm 1.20 22'frt- ~ F1aStei UO 6 11 15 243J& 25 - '4 .U 1434- =III ... 227 27=111 26~ 27 ...... Citicorp 1.16 72898 25'1. 23=111 p24la- ~ Corelnd EaglePc .76 AIor 1.20 8 267 35'" 34'4 3434- ~ CornG 1.688 ~-'I. .... 5 48¥e 48la 48?'e+!fa CitiesSy 3.20 7 318 54 53 531f.- J',~ 54'4+13Jo Easco 1.10 191f2- I~ FMC 1.20 6 269 24 221h p23¥a+ 'AI Corcrill 1.24 213J&-134 13 282 10'/. r8¥a 10 + 'I. CitytnYest 1 31056 I~ J21,'.1 gl~+ "It Eastern Air p91f2+ ~ FMCpf 2'4 .... 134 34 34 ...... 8 63 22lh r2J11. 21'4-1=111 City Illy wts .... 326 Pie 1 Pie ...... ~-'!iI EasApf 2.69 233Jo ..... FooteC UO 6 56 19=111 18'" 18'1.-1 10 392 13 12'4 12~- I/a City lily pf 2 .... 110 22lh r21 22lh- 34 ~C~~ 17!M1- 'I. EastGsF .80 13:tt ... -
General Disclaimer One Or More of the Following Statements May Affect
General Disclaimer One or more of the Following Statements may affect this Document This document has been reproduced from the best copy furnished by the organizational source. It is being released in the interest of making available as much information as possible. This document may contain data, which exceeds the sheet parameters. It was furnished in this condition by the organizational source and is the best copy available. This document may contain tone-on-tone or color graphs, charts and/or pictures, which have been reproduced in black and white. This document is paginated as submitted by the original source. Portions of this document are not fully legible due to the historical nature of some of the material. However, it is the best reproduction available from the original submission. Produced by the NASA Center for Aerospace Information (CASI) N APF16-M SFC'02121 N I j O L1 1. C/J :9E C; r`• ii. Technical Report 'M DA -TA BASE MANAGEMENT' S -T- L.JI D ' INTERIM REPORT (NASA-CR-1`-0167) DATA BASE MANAGEMENT STUDY N77-15671 Interim Report (Teledyne Brown Engineering) 62 p HC A04/MF A01 CSCL 09B Uaclas G3/60 12515 May 19/6 a FED 1' RWEIVEC' NASA M %CIU INPUT R*NGH TELEDYNE BROWN ENGINEERING C^umrnings Research Park- Huntsville, Alabama 35807 I TECHNICAL REPORT APF76-MSFC-02127 DATA BASE IMAGEMENT STUDY INTERIM REPORT May, 1976 Prepared for Data Systems Laboratory George C. Marshall Space Flight Center Huntsville, Alabama Contract No. NAS8-31488 Prepared by Advanced Projects Division . Teledyne Brown Engineering . Huntsville, Alabama ABSTRACT This interim report presents the results of work performed by Teledyne Brown Engineering (TBE) under NASA contract NAS8-31488. -
A Complete Bibliography of Publications in Science of Computer Programming
A Complete Bibliography of Publications in Science of Computer Programming Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 23 July 2021 Version 2.85 Title word cross-reference .NET [1085, 1074]. 0 [195, 291, 202, 572, 183, 515, 265, 155, 192, 231, 243, 514, 245, 1980, 295, 156, 151, 206, 1 + 118 [2359]. 10 [91]. $102.50 [267, 268]. 146, 203, 213, 289, 285, 286, 287, 219, 244, 11 [95]. 12 [101]. 13 [103]. 14 [107]. 15 [112]. 207, 246, 182, 229, 153, 321, 296, 217, 208, 16 [117]. 18 [125]. 19 [131]. 2 [43]. 20 [147]. 297, 193, 180, 298, 67, 204, 267, 268, 194, 21 [160]. 22 [178]. 23 [190]. 24 [242]. 3 [47]. 216, 320, 181, 317, 145, 214, 266, 269, 397, 3=2 [693]. $31.25 [320]. 4 [54]. 5 [61]. 6 [66]. 169, 574, 390, 215, 173, 1976, 227, 185, 575, + 2 7 [72]. $74.25 [318]. 8 [77]. [2065, 2428]. 226, 318, 270, 201, 288, 166, 205, 196, 284, 3 [466]. [1492]. 1 [944]. fun [1352]. SCR [1723]. 230, 247, 248, 249, 250, 524]. 0-06-042225-4 M jj [1894]. CSP B [1280]. ∆IC [879]. E3 [180]. 0-12-064460-6 [214]. 0-12-274060-2 [523]. j [1050, 1534]. k [1890, 2529]. λ [146]. -
ISO-7185 Standard Pascal
Pascal ISO 7185:1990 This online copy of the unextended Pascal standard is provided only as an aid to standardization. In the case of di erences between this online version and the printed version, the printed version takes precedence. Do not mo dify this do cument. Do not include this do cumentinanothersoftware pro duct. You may print this do cument for p ersonal use only. Do not sell this do cument. Use this information only for good; never for evil. Do not exp ose to re. Do not op erate heavy equipment after reading, may cause drowsiness. Do not read under the in uence of alcohol (although there havebeen several uncon rmed rep orts that alcohol actually improves the readability). The standard is written in English. If you have trouble understanding a particular section, read it again and again and again... Sit up straight. Eat your vegatables. Do not mumble. c ISO/IEC 1991 ISO/IEC 7185:1990(E) ii ISO/IEC 7185:1990(E) Acknowledgements The e orts are acknowledged of all those who contributed to the work of the BSI and ISO Pascal working groups, and in particular: Tony Addyman Harris Hall John Reagan Albrecht Biedl Carsten Hammer Mike Rees Bob Brewer Atholl Hay Arthur Sale Co en Bron Tony Hetherington Paula Schwartz David Burnett-Hall Steve Hobbs Barry Smith David Bustard Mel Jackson John Souter Barry Byrne Scott Jameson Manfred Stadel Klaus Daessler David Jones Bob Tennent Richard De Morgan David Joslin Tom Turba Norman Diamond KatsuhikoKakehi Eiiti Wada Bob Dietrich Olivier Lecarme Willem Wakker Ken Edwards Jim Miner David Watt Jacques Farre Wes Munsil Jim Welsh Bill Findlay Bill Price Brian Wichmann The e orts are acknowledged of all those who contributed to the work of JPC, and in particular: Michael Alexander Steven Hobbs David L.