This paper describes a real-time interactive multiprocess operating system (RIMOS) which extends the INTEL MDS system. Only the kernel has been implemented and tested so far, but this includes a powerful message system which should give the final system a wide range of capabilities. The only supporting software needed for RIMOS is INTEL's ISIS. (The INTEL monitor is used only at the start to load ISIS.)
{"title":"An operating system for the INTEL MDS system: the kernel","authors":"M. K. Agoston","doi":"10.1145/1041244.1041247","DOIUrl":"https://doi.org/10.1145/1041244.1041247","url":null,"abstract":"This paper describes a real-time interactive multiprocess operating system (RIMOS) which extends the INTEL MDS system. Only the kernel has been implemented and tested so far, but this includes a powerful message system which should give the final system a wide range of capabilities. The only supporting software needed for RIMOS is INTEL's ISIS. (The INTEL monitor is used only at the start to load ISIS.)","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1977-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125652495","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}
In 1946, when the first electronic digital computer was unveiled, predictions were made that two such computers, one located on the East Coast and one located on the West Coast, would provide all of the computing power the U.S. would ever need. This prediction has proved particularly embarrassing in view of the proliferation of minicomputers over the last ten years. Heedless of the failure of this earlier prognosticator, this paper is an attempt to predict minicomputer trends over the next five years. Luckily, we have substantially more history on which to base our projections.
{"title":"The minicomputer phenomenon-projections for the next five years","authors":"W. Churchman","doi":"10.1145/1041231.1041235","DOIUrl":"https://doi.org/10.1145/1041231.1041235","url":null,"abstract":"In 1946, when the first electronic digital computer was unveiled, predictions were made that two such computers, one located on the East Coast and one located on the West Coast, would provide all of the computing power the U.S. would ever need. This prediction has proved particularly embarrassing in view of the proliferation of minicomputers over the last ten years. Heedless of the failure of this earlier prognosticator, this paper is an attempt to predict minicomputer trends over the next five years. Luckily, we have substantially more history on which to base our projections.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116754596","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}
Where is the small computer field headed? In order to talk about the future of small computers and their applications, I have to take on the role of a prognosticator, a predictor of future trends and events. Prognostication is an art to which mystical or magical qualities are often attributed, but which in reality is nothing more than a combination of reasoning and imagination based upon observation. The injection of imagination about possible trends and developments makes prognostication a bit different from a narrow linear extrapolation of identified trends. The imagination component is heavily influenced by personal values and philosophies, and represents a feedback of oughts and shoulds into the course of events as they develop. Prognostication is thus a method of extrapolating observed current trends into the future coupled with the prognosticator's opinions of what should be happening. In the terms of the scientist or engineer, prognostication is like an operational amplifier system in which the input signal is the observed set of trends and the feedback network is the prognosticator's personal philosophy and imagination. For example, in predicting the fate of civilization, if one is a congenital pessimist like the members of the Club of Rome, then the predictions will come out claiming disaster and ruin. If one is an optimist about the expanding possibilities created by advancing technology, then a totally different character of prediction will result. When you listen to what I have to say, be warned that I have a definite personal point of view regarding computer technology and its proper uses, and that this shapes the nature of the imagination content and the trends I select to emphasize.
{"title":"Trends in applications","authors":"C. Helmers","doi":"10.1145/1041231.1041236","DOIUrl":"https://doi.org/10.1145/1041231.1041236","url":null,"abstract":"Where is the small computer field headed? In order to talk about the future of small computers and their applications, I have to take on the role of a prognosticator, a predictor of future trends and events. Prognostication is an art to which mystical or magical qualities are often attributed, but which in reality is nothing more than a combination of reasoning and imagination based upon observation. The injection of imagination about possible trends and developments makes prognostication a bit different from a narrow linear extrapolation of identified trends. The imagination component is heavily influenced by personal values and philosophies, and represents a feedback of oughts and shoulds into the course of events as they develop. Prognostication is thus a method of extrapolating observed current trends into the future coupled with the prognosticator's opinions of what should be happening. In the terms of the scientist or engineer, prognostication is like an operational amplifier system in which the input signal is the observed set of trends and the feedback network is the prognosticator's personal philosophy and imagination. For example, in predicting the fate of civilization, if one is a congenital pessimist like the members of the Club of Rome, then the predictions will come out claiming disaster and ruin. If one is an optimist about the expanding possibilities created by advancing technology, then a totally different character of prediction will result. When you listen to what I have to say, be warned that I have a definite personal point of view regarding computer technology and its proper uses, and that this shapes the nature of the imagination content and the trends I select to emphasize.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"98 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133584903","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}
Every computer and data-processing system implemented today will eventually be replaced. There are many possible futures. It is necessary to examine these possibilities and to identify those actions which can be taken today in order to be prepared to move readily into the future. Such actions involve questions of standards of programming languages, of modularity and of documentation. Events of the past point up the types of decisions which must be made.
{"title":"Possible futures and present actions","authors":"G. Hopper","doi":"10.1145/1041231.1041233","DOIUrl":"https://doi.org/10.1145/1041231.1041233","url":null,"abstract":"Every computer and data-processing system implemented today will eventually be replaced. There are many possible futures. It is necessary to examine these possibilities and to identify those actions which can be taken today in order to be prepared to move readily into the future. Such actions involve questions of standards of programming languages, of modularity and of documentation. Events of the past point up the types of decisions which must be made.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"10 4","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114130142","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}
This paper presents a method to increase the efficiency of general purpose minicomputer usage in a laboratory environment through subroutines to a higher level language. As an example, the implementation of a general purpose routine for the complete support of an Analog-to-Digital Subsystem is given; both from the viewpoint of the implementation in an assembly language and the usage of the corresponding FORTRAN subroutine. To extend the capability of such a system, certain non-FORTRAN attributes were included in the implementation. These extensions include the ability to use FORTRAN completion subroutines. That is, after an event or series of events has occurred, it is possible for the assembly language event processor to interrupt the execution of the main FORTRAN program and start up correctly a FORTRAN completion routine to manipulate the data as required by that application. When that task is finished, the main program will be continued from where it was suspended with no apparent side effects. This feature allows a fairly complex (but nevertheless straight-forward) FORTRAN program to control several experiments or portions of the same experiment in a completely asynchronous way.
{"title":"Interrupt driven fortran for laboratory support","authors":"S. Alpert","doi":"10.1145/1041231.1041237","DOIUrl":"https://doi.org/10.1145/1041231.1041237","url":null,"abstract":"This paper presents a method to increase the efficiency of general purpose minicomputer usage in a laboratory environment through subroutines to a higher level language. As an example, the implementation of a general purpose routine for the complete support of an Analog-to-Digital Subsystem is given; both from the viewpoint of the implementation in an assembly language and the usage of the corresponding FORTRAN subroutine. To extend the capability of such a system, certain non-FORTRAN attributes were included in the implementation. These extensions include the ability to use FORTRAN completion subroutines. That is, after an event or series of events has occurred, it is possible for the assembly language event processor to interrupt the execution of the main FORTRAN program and start up correctly a FORTRAN completion routine to manipulate the data as required by that application. When that task is finished, the main program will be continued from where it was suspended with no apparent side effects. This feature allows a fairly complex (but nevertheless straight-forward) FORTRAN program to control several experiments or portions of the same experiment in a completely asynchronous way.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"58 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125122279","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}
The 2nd of July was an anniversary for me, because I reported to the Mark I computer on the 2nd of July, 1944: 30 years in the computer industry. I can now spread out those 30 years in front of me and I can see that the changes are coming closer and faster. The time between major changes is getting shorter and shorter. It is more important than ever that today's decisions be made in the light of what is coming in the future. Because the changes are not going to be ten years from now, they may not even be five years from now, they may appear two years from now, we have less time to make valid decisions today for what we will be doing in the future.
{"title":"Technology: future directions","authors":"G. Hopper","doi":"10.1145/1041231.1041234","DOIUrl":"https://doi.org/10.1145/1041231.1041234","url":null,"abstract":"The 2nd of July was an anniversary for me, because I reported to the Mark I computer on the 2nd of July, 1944: 30 years in the computer industry. I can now spread out those 30 years in front of me and I can see that the changes are coming closer and faster. The time between major changes is getting shorter and shorter. It is more important than ever that today's decisions be made in the light of what is coming in the future. Because the changes are not going to be ten years from now, they may not even be five years from now, they may appear two years from now, we have less time to make valid decisions today for what we will be doing in the future.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115900899","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}
Minis and micros have been praised for their low cost, flexibility, and general upheavel of traditional Renaissance Computers (general purpose computers). Indeed, minicomputers have revolutionized computing because of their special-purpose, dispersed, Common Computer image.
{"title":"Minicomputer systems in business: what are the limiting factors?","authors":"T. Lewis","doi":"10.1145/1164909.1164915","DOIUrl":"https://doi.org/10.1145/1164909.1164915","url":null,"abstract":"Minis and micros have been praised for their low cost, flexibility, and general upheavel of traditional Renaissance Computers (general purpose computers). Indeed, minicomputers have revolutionized computing because of their special-purpose, dispersed, Common Computer image.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"41 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125571166","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}
We have recently received a Varian 520/i minicomputer to be used mainly for teaching purposes. Since our only I/O device is a standard teletype (equipped with a paper tape read/punch), we immediately faced the problem of software development. The existing system programs for that purpose, namely the assemblers, loaders and editor are very impractical to use with a teletype. A typical step in the debugging process involves: (1) loading the assembler, (2) assembling the program, (3) loading the program (normally overlaying the assembler or part of it), (4) executing the program and deciding on necessary changes, (5) loading the editor, and (6) editing the changes into the source paper tape.
{"title":"On the efficient use of a minicomputer with limited I/O","authors":"D. Salomon","doi":"10.1145/1164909.1164914","DOIUrl":"https://doi.org/10.1145/1164909.1164914","url":null,"abstract":"We have recently received a Varian 520/i minicomputer to be used mainly for teaching purposes. Since our only I/O device is a standard teletype (equipped with a paper tape read/punch), we immediately faced the problem of software development. The existing system programs for that purpose, namely the assemblers, loaders and editor are very impractical to use with a teletype. A typical step in the debugging process involves: (1) loading the assembler, (2) assembling the program, (3) loading the program (normally overlaying the assembler or part of it), (4) executing the program and deciding on necessary changes, (5) loading the editor, and (6) editing the changes into the source paper tape.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"69 4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1976-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123247426","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}
Datapro reports that compact, low-cost business data processing systems will soon be as commonplace in most offices as typewriters and copy machines. They report over 130 current minicomputer systems from 46 vendors in use. These systems are characterized by a price tag of $5,000 to $100,000, main memory from 8K to 64K, 16-bit words, data entry peripherals, and low-cost auxiliary storage.
{"title":"Minicomputer systems in business","authors":"T. Lewis","doi":"10.1145/1164870.1164873","DOIUrl":"https://doi.org/10.1145/1164870.1164873","url":null,"abstract":"<u>Datapro</u> reports that compact, low-cost business data processing systems will soon be as commonplace in most offices as typewriters and copy machines. They report over 130 current minicomputer systems from 46 vendors in use. These systems are characterized by a price tag of $5,000 to $100,000, main memory from 8K to 64K, 16-bit words, data entry peripherals, and low-cost auxiliary storage.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1975-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123981276","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}
There have been many taxonomies of computer usage presented. Some are based upon the hardware and software involved. Others are based upon application characteristics. And on and on. The taxonomy (actually a dichotomy) which I wish to consider is based upon the support characteristics of a system. The split is a clean one. It is based on whether or not a system is directly supported by a staff with computer system expertise. By direct support, I mean that there are one or more people who are under control of the organization, i.e. people who reside in-house and whose allegiance is to that organization. Presumably then, we are considering people who are on the premises and being paid by the organization. A second ingredient of direct support is the ability of such people to react in a real-time sense to emergencies which arise in the use of a system. The dichotomy, then, is based on the existence of a controlled, real-time support staff. The real-time aspect of this dichotomy is exactly what the term implies. Some organizations would suffer with down-times measured in minutes. Others could go 24--48 hours with little, if any, inconvenience.
{"title":"A dichotomy of computer usage","authors":"Ted Cary","doi":"10.1145/1164864.1164868","DOIUrl":"https://doi.org/10.1145/1164864.1164868","url":null,"abstract":"There have been many taxonomies of computer usage presented. Some are based upon the hardware and software involved. Others are based upon application characteristics. And on and on. The taxonomy (actually a dichotomy) which I wish to consider is based upon the support characteristics of a system. The split is a clean one. It is based on whether or not a system is directly supported by a staff with computer system expertise. By direct support, I mean that there are one or more people who are under control of the organization, i.e. people who reside in-house and whose allegiance is to that organization. Presumably then, we are considering people who are on the premises and being paid by the organization. A second ingredient of direct support is the ability of such people to react in a real-time sense to emergencies which arise in the use of a system. The dichotomy, then, is based on the existence of a controlled, real-time support staff. The real-time aspect of this dichotomy is exactly what the term implies. Some organizations would suffer with down-times measured in minutes. Others could go 24--48 hours with little, if any, inconvenience.","PeriodicalId":377377,"journal":{"name":"ACM Sigmini Newsletter","volume":"58 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1975-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123034194","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}