{"title":"Implementing SNOBOL 4 for the 8086 micro-computer family","authors":"M. Emmer","doi":"10.1145/1164662.1164663","DOIUrl":"https://doi.org/10.1145/1164662.1164663","url":null,"abstract":"A commercial product called SNOBOL4+ for the 8086/8088 computer family is described. It implements the entire SNOBOL4 language, and shows reasonable execution speed. Sample programs in the standard SNOBOL4 language reference text which were run on an IBM 360 model 65 execute approximately 10 times slower on an 8088 equipped IBM PC (3.5 times slower on a PC AT).The internal construction of the SNOBOL4 interpreter has been well described elsewhere (Griswold, Ralph E., The Macro Implementation of SNOBOL4. San Francisco: W. H. Freeman and Co., 1972, 310 pages). This note explains some of the design decisions made for this specific implementation. It is hoped that lessons learned the proverbial \"hard way\" may benefit others when implementing large systems for the 8086/8088. The \"lessons\" reflect the author's personal bias and experience. Some are conjectural, others resulted from doing things over the \"right\" way.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"29 12","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1984-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"113980469","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The TurboDOStm operating system","authors":"K. Bierman","doi":"10.1145/1164658.1164660","DOIUrl":"https://doi.org/10.1145/1164658.1164660","url":null,"abstract":"A commercially available multi-microcomputer system is described. Facilities and features are described from a user's standpoint. Several research problems are proposed.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1984-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125195382","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"VT: a virtual terminal window package for UNIX","authors":"R. Gammill, P. Ram","doi":"10.1145/1164654.1164656","DOIUrl":"https://doi.org/10.1145/1164654.1164656","url":null,"abstract":"A window package called VT has been developed for UNIX version 6 and the Heath H19 terminal. The package is written in C and is implemented entirely at the user level. Only a nonstandard system call named port is required. VT enables the user to act as if he is commanding several terminals while using a single CRT terminal. The user can make rectangular windows, each with a shell (UNIX command interpreter), and concurrently run commands in each window. All input and output for each shell is confined to its own window, so each window serves as a virtual terminal. Implementation under Version 7 and later releases of UNIX is planned.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"80 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1984-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126324572","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Public domain software: part I","authors":"E. S. Wheeler","doi":"10.1145/1164654.1164655","DOIUrl":"https://doi.org/10.1145/1164654.1164655","url":null,"abstract":"A selection of some of the microcomputer public domain software: Part 1. Languages and Language Development.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1984-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128454496","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The Xcode machine","authors":"F. Tisato, R. Zicari","doi":"10.1145/1113563.1113565","DOIUrl":"https://doi.org/10.1145/1113563.1113565","url":null,"abstract":"This paper defines the abstract machine architecture of a node of a distributed system. The abstract machine is close to the physical architecture of existing real systems, so that the set of abstract primitives can be easily mapped onto the instruction set of any physical machine.The abstract machine is defined via its \" machine language\" X-code. The X-code primitives have been designed to support the typical problems which arise in distributed systems and embedded applications.The work described in this paper is part of a larger project (C-net) sponsored by CNR - the Italian Research Council - with the goal of providing tools and methodologies for designing distributed systems composed of heterogeneous physical nodes.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1984-02-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125680498","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Some basic concepts in micro computer security","authors":"Ray Todd Stevens","doi":"10.1145/1113563.1113564","DOIUrl":"https://doi.org/10.1145/1113563.1113564","url":null,"abstract":"The simple fact is that while most of us who work in micro computer security are off working and dreaming about the latest and best ideas for \"truely\" securing the computers under our care our employees, employers, and/or clients are not properly using even the very simplest security routines and therefore the system already in place. We should, therefore, take our heads out of the clouds and educate our fellow voyagers through the world of micro computers in some of the rudimentaries of computer security. This papers is, therefore, designed to point out some of the facts we should be sharing with them.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1984-02-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125429749","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"How do you spell relief?","authors":"H. Hodge","doi":"10.1145/1164715.1164716","DOIUrl":"https://doi.org/10.1145/1164715.1164716","url":null,"abstract":"A while ago in the mail I received a packet of book order postcards from a publisher. Sorting through them, I noticed something called CDP ExamGuide, by the Washington chapter of the DPMA. Well, I thought to myself, since I have never had any formal DP training, I wonder how I would do on that. Besides, it is job-related, so I can deduct it from my income tax. I figured that I would do all right on the software section, and possibly pass the analysis. The other three sections (hardware , management, and quantitative methods) I wrote off in advance. Which goes to show the trouble into which one can get on under-specified problems. The first section in the book was hardware, so I went ahead and did it, and actually passed by a few percentage points. My nodding acquaintance with unit-record equipment in Vietnam served me in good stead, although I have had absolutely no use for it since. And so on to software, the area in which I make my living. Oh, the shame of it! I scored barely over fifty percent. All these years I have been taking money under false pretenses. The major general who wrote me a letter thanking me for the good job I did will have to be court-martialed. Those issues of the Sigsmall Newsletter containing my articles will have to be recalled and revised (good job for you, George). Actually, the result could have been foreseen. I worked just enough with COBOL to decide that I never wanted to do so again. At least one of the answers was flat wrong, from my experience-apparently DPMA is used to working on bigger systems than I am. After that, I put the book away permanently. I can salvage only one consolation from the entire crushing experience-I will never be qualified to be a DP manager.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"48 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1983-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127875674","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"An evaluation of RQL: a relational data base system for a low end microcomputer configuration","authors":"Susan Masters, James R. Driscoll","doi":"10.1145/1164712.1164713","DOIUrl":"https://doi.org/10.1145/1164712.1164713","url":null,"abstract":"Microcomputers for data-base applications are available in a wide range of prices. At the low-end, the minimum configuration for any serious Data Base work would be a processor and memory unit, two floppy diskette drives, a keyboard, a video display unit, and a printer [2]. This configuration would be adequate for small applications. As an example, an Apple II computer with two floppy disk drives, video display, and printer retails for approximately $3000.00.The availability of Data Base Management Systems for low-end microcomputers is very limited [1,2]. There appear to be only two relational systems commercially available for low-end configurations - RQL (Relational Query Language) and RMS (Relational Menu System). Both of these systems are available from Hello Software, 8380 Roanne Drive, Orlando, Florida 32817, U.S.A. The RQL system runs on the Apple II microcomputer. Although it was designed for use in a classroom environment, RQL may also be suitable in a small business environment.RQL is a relationally complete system [3,4]. Through a combination of automatic navigation and a relational processing query language, the RQL system allows the unsophisticated user direct interaction with data bases. Furthermore, RQL can manage multiple data bases with each data base extending across a maximum of eight volumes (floppy diskettes) [4]. However, since low-end configurations are inherently slow, the RQL system is unavoidably sluggish at times.The purpose of this paper is to demonstrate features of the RQL system and discuss its recent use in a learning environment and its potential use in a small business environment. For demonstration purposes a real-world situation typical of a small business organization will be used and a data base will be established for it using the RQL system (Release 3).","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1983-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132048585","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Computer security for minis and micros","authors":"Anne-Marie Claybrook","doi":"10.1145/1164706.1164707","DOIUrl":"https://doi.org/10.1145/1164706.1164707","url":null,"abstract":"Mini and micro computers were originally designed mainly for low cost, real time computer applications. Security in these dedicated systems was not a concern. Now that minis and micros are being used in multi-user environments, security is much more a concern. In the commercial arena, security for word processing applications urgently needs to be addressed. Security and integrity are concerns in the communications area where minis and micros are used for both front-ends and network switches. Finally, with the widespread use of small computers in defense applications, data security in terms of the Department of Defense (DoD) national security policy also needs to be addressed.This paper provides some background on computer security to those new to the area and gives a general context for the two architecture papers following this overview.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1983-02-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134382149","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Security in the Nebula computer architecture","authors":"Will Dietz, L. Szewerenko","doi":"10.1145/1164706.1164708","DOIUrl":"https://doi.org/10.1145/1164706.1164708","url":null,"abstract":"The problem of security in multi-function computer systems arises because the software in such systems is too complex to be proven to be correct. Multilevel secure operating systems attempt to deal with this problem by dividing the applications software into separate \"tasks\" and controlling the ways in which these tasks interact. While the internal behavior of each task still cannot be guaranteed, the security of the system as a whole can be demonstrated, provided the restrictions on task interaction can be enforced.To control the interaction of tasks, it must be possible to isolate each task from undesired examination or interference by other tasks. This isolation is usually accomplished by providing each untrusted task with its own \"virtual\" environment. The trusted system software and the hardware are responsible for making sure that an untrusted program cannot operate outside its own environment and that the physical resources allocated to establish the virtual environment do not violate the isolation requirements. Communication between these virtual environments is then controlled by the trusted system software.Ultimately, the realization of such an operating system structure produces a quantity of \"trusted system software\" that still must be verified to insure the security of the system. To practically realize such a system, careful design of the software and hardware is required to minimize the amount of verified code and isolate it from corruption by the unverified system software.The Nebula computer architecture includes a set of mechanisms that are designed to provide the isolation necessary to establish a secure system. Of more practical importance is the fact that these mechanisms will allow valid operations to be identified with minimal overhead and to proceed with minimal interference. These mechanisms are described below under the general headings of virtual addressing, protection states, secure user I/0 and task execution control.","PeriodicalId":232893,"journal":{"name":"ACM Sigsmall Newsletter","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1983-02-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128212664","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
