ISIS (operating system)
Operating system
ISIS, short for Intel System Implementation Supervisor, was an operating system for early Intel microprocessors like the 8080. It was originally developed by Ken Burgett and Jim Stein under the management of Steve Hanna and Terry Opdendyk for the Intel Microprocessor Development System with two 8" floppy drives, starting in 1975, and later adopted as ISIS-II as the operating system for the PL/M compiler, assembler, link editor, and In-Circuit Emulator (developed by Steve Morse). The ISIS operating system was developed on an early prototype of the MDS 800 computer, the same type of hardware that Gary Kildall used to develop CP/M.
Overview
Communication with the user is terminal-like. Its user interface is somewhat CP/M-like, even from the program interface point of view. For file opening, the program sends the name of file and gets back a handle. Each device has a name, which is entered between a pair of colons (:F0: and :F1: are floppies, :LP: is printer, etc.). Each diskette has one directory and no subdirectories. ISIS-II has been distributed as part of the Intel Microprocessor Development System and includes standard operating system commands (COPY, DELETE, DIR, RENAME, FORMAT) and debugging software (assembler, linker and debugger for external debugging in the developed device). There are two editors, one of which, AEDIT, contains editing macros support. File editing is provided directly on diskette (a .BAK file is always created).
This brief starts where responsible research should: with the source description of “ISIS (operating system)” as operating system. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as operating system. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jul 17, 2026. The linked authority identifier is Q5973993. 1 of 1 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1975.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “ISIS (operating system)”, its source revision and the description used here.
- Expand the search: follow ISIS (operating system) primary sources, ISIS (operating system) archive and ISIS research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “ISIS (operating system)”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “ISIS (operating system)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.