Computer History Wiki - User contributions [en]

Amber Operating System

2025-12-01T19:55:40Z

Flx: wikify S-1 supercomputer

Amber was an [[operating system]] for the [[S-1 supercomputer]]. It drew a lot from [[Multics]].

== External Links ==

* [http://www.mit.edu/~cbf/thesis.htm The Amber Operating System], thesis by Charles Frankston.

[[Category: Operating Systems]]

Ken Thompson

2025-12-01T17:02:43Z

Flx: caption missing paren

[[Image:KenDMR.jpg|400px|thumb|right|Ken Thompson (sitting) and Dennis Ritchie (standing)]]

'''Ken Thompson''' (often referred to as '''ken''') was an influential American computer scientist, best known for his work on [[UNIX]] (produced in collaboration with [[Dennis Ritchie]]). He also initiated the [[C programming language]], although most of the work on that was done by Ritchie.

He attended the University of California, Berkeley, where he received an undergraduate degree in 1965, and a master's degree in 1966. He went to work at [[Bell Labs]] in 1966, joining the Computing Sciences Research Center. He spent the rest of his career at the Labs, and its descendants, retiring in 2000. He was part of the Bell team which joined the [[Multics]] project; after Bell pulled out of Multics, he and Ritchie eventually fell into UNIX and C.

{{semi-stub}}

==Further reading==

* Brian Kernighan, [https://www.amazon.com/UNIX-History-Memoir-Brian-Kernighan/dp/1695978552 UNIX: A History and a Memoir] - has a brief bio of Thompson at the end of Chapter 2

==External links==

* [http://cs.bell-labs.co/who/ken/ Ken Thompson's Home Page]
* [https://history.computer.org/pioneers/pdfs/T/Thompson.pdf Kenneth Thompson] - brief biography at the IEEE Computer Society
* D. M. Ritchie and K. Thompson, [https://www.nokia.com/bell-labs/about/dennis-m-ritchie/cacm.html ''The Unix Time-sharing System''] ([https://www.nokia.com/bell-labs/about/dennis-m-ritchie/cacm.pdf PDF]) - 1978 [[Bell System Technical Journal]] version
* [https://www.nokia.com/bell-labs/about/dennis-m-ritchie/picture.html An amusing photo] - "Ken and [DMR] in front of a PDP-11"
* [https://computerhistory.org/wp-content/uploads/2019/10/102685442.03.01.jpg Ken and DMR] - from another angle

{{DEFAULTSORT: Thompson, Ken}}
[[Category: People]]

IAS computer

2025-12-01T16:05:29Z

Flx: /* Copies */ missing whitespace

The '''IAS computer''' (sometimes called the '''IAS machine'''; it seems not to have had a formal name, although some later contemporary documents call it 'MANIAC', a name used by the Los Alamos copy) was a very early [[electronic]] [[program]]mable [[computer]]. The group that designed and built it began the task in June, 1946, initial operation began in the fall of 1950, and it was formally dedicated on 10 June, 1952. Its most significant contribution was the vast list of first-generation computers, both in the US, and around the world, which were copies of it (below).

The group, the '''Electronic Computer Project''' (ECP), was assembled by [[John von Neumann]] at the [[Institute for Advanced Study]] (IAS) at Princeton (von Neumann's base institution at the time). This machine became his focus after his involvement in the planning for, and design of, the [[EDVAC]] had enlightened him to the promise of the field. (He broke off his connection to [[John Mauchly]], and especially [[J. Presper Eckert]], because they were focused on starting a business, the eventual [[Eckert–Mauchly Computer Corporation]], and he wished to make all his work public - as the many copies of the IAS computer testified.)

The engineers on the ECP team initially included Julian Bigelow (Chief Engineer; replaced mid-way with initial team-member James Pomerene), John Davis, Robert Shaw, Ralph Slutz, and Willis Ware; Morris Rubinoff and Richard Snyder joined later. Other members of the team included Arthur Burks, Jule Charney, Hewitt Crane, N. Emslie, Gerald Estrin, E. Frei, Herman Goldstine, T. Hildebrandt, G. Kent, W. Melville, J. Rosenberg, Morris Rubinoff, Richard L. Snyder, and others. Their work was widely distributed via progress reports, which were circulated extensively. The IAS closed the ECP in 1957-58 (the exact date is uncertain); apparently because as an organization the IAS was uncomfortable with such an essentially practical effort. The personnel then scattered, taking their knowledge with them; many became leading lights on other early computers.

==Technical details==

Not one of the many, many later books which describe the IAS machine (below) give complete coverage of its [[architecture]]. This description is mostly gleaned from the ''Final Progress Report'' (below); the [[instruction set]] is enumerated at the end of that, and is given below.

It eventually used 40 [[Williams tube]]s for its [[main memory]] (after the [[Selectron]] project failed to produce usable memory, although a later copy used them). They contained 1K words in total, each tube using a 32x32 [[array]]. (Although this memory had to be [[memory refresh|refreshed]], refresh cycles could be combined with read/write operations when possible.) The [[logic]] was constructed using [[vacuum tube]]s (although only about 3,000; many fewer than the [[ENIAC]]).

It was an [[asynchronous]] [[parallel computer]] internally, using 40-[[bit]] [[word]]s. It used [[binary]], with the sign bit at the left (and [[two's complement]]), and the binary point between it and the next bit; i.e. words can represent values between 1 and -1.

The machine included 3 [[register]]s, each 40 bits long:

* RI (also given as R1 in documentation) - the Accumulator; one input to the [[adder]], receives the output from the adder
* RII (also R2) - the Arithmetic Register; used in multiplication and division
* RIII (also R3) - the Memory Register; the other input (possibly complemented, or zeroed) to the adder

Each register is composed internally of a pair of 'sub-registers' (termed "ranks"), denoted as Rn (the "permanent rank") and Rn (the "temporary rank") in contemporary documentation. RI and RII can perform single-bit left and right shifts when copying data from the Rn rank to Rn; an un-shifted copy can take place from Rn to Rn. RIII can also be copied to RII, and RII to RI.

[[Instruction]]s were 20 bits long, and contained a 10-bit [[operation code|opcode]] and a 10-bit [[address]].  There were about 30 in total; the number changed over time (e.g. when the [[input/output|I/O]] system was first redone, in 1952).

It had instructions to perform multiplication and division, but no special hardware; both were performed a bit at a time, with shifting (performed with the sub-registers described above) and addition/subtraction. (Throughout the contemporary documentation, a great amount of attention is paid to the details of the arithmetic - as one might expect of a design in which John von Neumann was involved!)

I/O was on [[paper tape]] initially, later (1952) switched to [[punched card]]s, and supplemented with a 7" [[CRT]] for [[graphics]] output. It was eventually (June, 1953) given an IAS-built [[drum]] of 2K words; a 12K one from [[Engineering Research Associates|ERA]] was later (1955) installed.

===Instruction set===

Two instructions were stored in each word, referred to as the 'first' (left) and 'second' (right) 'phases'; executed in that order. A few instructions could be executed in the left phase only, and one in the right only; such limitations are given in the table below (a blank entry means 'either').

The 'step digit', bit 11, may be 0 ([[halt]] after executing the instruction) or 1 in many instructions. If so, it is indicated by an 'S' in 'bits' column (and also in the numeric opcode). "S=1" means it ''must'' be set in that instruction. The 'clear digit', bit 18, is available in some instructions; if so, it is indicated by a 'C' in the 'bits' column (and will set the appropriate bit in the numeric opcode). It may be 0 (see 'Comment' for action) or 1 (clear R1 before commencing).

Potential [[operand]]s are generally R1, R2, and R3 (referred to as "R3" in the table); and the contents ('b') of the memory location (address 'x'). Most instruction (unless otherwise noted) leave b in R3. A detailed description of each instruction is provided on the given page of the ''Final Progress Report''.

{| class="wikitable"
! Group !! Opcode !! Name !! Page !! Bits !! Phase !! Brief description !! Comment
|-
| rowspan="8" | {{VerticalTextUp|Summation}} || S712 || Plus clear || 22 || S ||   || Load b into R1
|-
| S710 || Plus hold || 23 || S ||   || Add b to R1
|-
| S732 || Minus clear || 24 || S ||   || Load 2-b into R1
|-
| S730 || Minus hold || 24 || S ||   || Subtract b from R1
|-
| S752 || Plus absolute clear || 25 || S ||   || Load abs(b) into R1
|-
| S750 || Plus absolute hold || 25 || S ||   || Add abs(b) to R1
|-
| S772 || Minus absolute clear || 26 || S ||   || Load 2-abs(b) into R1
|-
| S770 || Minus absolute hold || 26 || S ||   || Subtract b from R1 || It is not clear if/how this differs from 'Minus hold'
|-
| rowspan="4" | {{VerticalTextUp|Other}} || S702/700 || Multiply no round off || 27 || SC ||   || Multiply R2 and b; high order result to R1, low order to R2 || If C=0, add the old contents of R1 to the product
|-
| S706/704 || Multiply round off || 28 || SC ||   || As previous || Ditto
|-
| S760 || Division || 28 || S ||   || Divide R1 by b; leaves result in R2, twice the remainder in R1
|-
| S714 || Load RII || 29 || SC ||   || Load R2
|-
| rowspan="4" | {{VerticalTextUp|Trivial}} || 1650 || Store || 30 || S=1 ||   || Store R1; clear R3
|-
| 1652 || Store clear || 30 || S=1 ||   || Clear R1, R3, and memory
|-
| S640 || Un-conditional transfer || 31 ||   ||   || Next instruction will be from 'b' (opposite phase from this one, if step bit is set); clear R3 || b is stored in R3
|-
| S660 || Conditional transfer || 32 ||   ||   || If R1 >= 0, then as above; if < 0, a [[no-op]]
|-
| rowspan="1" | {{VerticalTextUp|Special}} || 1711-1773 || Quick sum || 33 || S=1 || first || See entry in ''Final Progress Report''
|-
| rowspan="4" | {{VerticalTextUp|Non-memory}} || S500 || Right shift, no round off || 34 || SC ||   || Shift R1/R2 double-width register right N bits, ''always'' retaining sign bit in R1; copy old contents of R2 to R3 || N is given in bits 4-9, and must be > 0 and < 47; if C=0, no effect, if C=1 clear R1 before shift
|-
| S504 || Right shift, round off || 35 || SC ||   || Not implemented
|-
| S520 || Left shift || 35 || SC ||   || Shift R1 and R2 independently left N bits, with the sign bit of R1 copied into the low bit of both; copy old contents of R2 to R3 || As for 'right shift, no round off'; but if C=1, R1 is cleared after shift, and the sign bit of R1 is cleared before being copied to R2
|-
| S510-S572 || R2 to R1|| 36 || S ||   || Same as 'Summation' group, but the operand is in R2, not memory
|-
| rowspan="6" | {{VerticalTextUp|Input-output}} || 1200-1376 || IBM and drum priming || 37 || S || second || See entry in ''Final Progress Report'' || S is only recommended
|-
| 1010 || IBM input to memory || 39 || S=1 || first || Ditto; the second instruction in the word must be a [[jump]] to the next instruction
|-
| 1116 || IBM output to [sic] memory || 39 || S=1 || first || Ditto
|-
| 1210-1230 || Drum input to memory || 39 || S=1 || first || Ditto
|-
| 1316-1336 || Drum output from memory || 40 || S=1 || first || Ditto
|}

''NOTE: the document uses "digit" where we would now say 'bit'.''

The [[operation code]]s are given in a table in the ''Final Progress Report'', but not in numeric form; and the column for each bit in the opcode has an individual name, not a number. It is not known if the columns are in numeric order; if they are, the step bit is in the bit number indicated elsewhere in the document (11), but the clear digit bit is not (it is given elsewhere as bit 18, but is 19 in the table). The opcodes are given above in octal, as if the bit columns in the ''Final Progress Report'' are in numeric order. The bit columns (numbered by apparent value, based on position) are labelled:

{| class="wikitable"
! Bit !! '0' Value !! '1' Value
|-
| 11 || No step || Step
|-
| 12 || Ext. || Int.
|-
| 13 || Arith. || Wms.
|-
| 14 || AT || NAT
|-
| 15 || # || Abs.
|-
| 16 || +R || -L
|-
| 17 || x/÷ || ∑
|-
| 18 || No RO || RO
|-
| 19 || Hold || Clear
|-
| 20 || colspan="2" style="text-align:center;" | Spare
|}

==Copies==

As mentioned, many copies of it were built, early on (and a few later), some with the help of people who had worked on the IAS machine. The faithfulness of the copies varied from machine to machine (apparently including a last one, built with [[transistor]]s); the later ones used [[core memory]]. The list of the US ones, with their dates of completion, is:

* AVIDAC (Argonne) - January, 1953
* CYCLONE (Iowa State University) - July, 1959
* ILLIAC (Illinois) - September, 1952
* JOHNNIAC (Rand) - March, 1954
* MANIAC (Los Alamos) - March, 1952 (slightly before the original)
* MISTIC (Michigan State University) - November, 1957 (a copy of the ILLIAC)
* ORACLE (Oak Ridge) - September, 1953
* ORDVAC (Aberdeen) - November, 1951

(The MANIAC was said to have been so named in protest against the 'cute' names which had become the fashion.) Elsewhere, they included:

* BESK (Royal Institute of Technology, Sweden) - November, 1953 (included hardware [[floating point]])
* DASK (Academy of Technical Sciences, Denmark) - 1957 (a copy of BESK)
* EDB-1 (Facit, Sweden) - 1957 (another copy of BESK, without floating point)
* MUSASINO-1 (NTT, Japan) - March, 1957
* SARA (SAAB, Sweden) - 1957 (another tweaked copy of BESK)
* SILLIAC (University of Sydney, Australia) - June, 1956
* SMIL (Lund University, Sweden) - June, 1956
* TRASK (Datasystem AB, Sweden) - 1965 (another copy of BESK, using transistors and core)
* WEIZAC (Weizmann Institute, Israel) - October, 1955

The [[IBM 701]] was apparently a 'cleaned up' copy as well (a different word length, with half-word addresses), as were the [[EDB-2]] and [[EDB-3]] families built in Sweden from 1957 on, and the FACOM 201 (a copy of the MUSASINO-1) produced by Fujitsu from 1960.

Several other machines (such as the [[BESM 1]]) were built after close study of the IAS computer's documentation (and in the BESM 1's case, that of the BESK as well), but were not copies of it.

{{semi-stub}}

==Further reading==

===Books===

* Herman H. Goldstine, ''The Computer from Pascal to von Neumann'', Princeton University, Princeton, 1972 - contains details of the entire effort, in which Goldstine participated
* William Aspray, ''John von Neumann and the Origins of Modern Computing'', MIT Press, Cambridge, 1990 - not much technical detail, but a good overall history, and a lot about problem areas the machine was used for
* Julian Bigelow ''Computer Development at the Institute for Advanced Study''; pp. 291-310 in Nicholas Metropolis, Jack Howlett, Gian-Carlo Rota (editors), [https://www.sciencedirect.com/book/9780124916500/a-history-of-computing-in-the-twentieth-century ''A History of Computing in the Twentieth Century''], Academic Press, New York, 1980 - the IAS computer is covered in the first section of Part IV, but with a focus on the electrical engineering; many descendants are covered in detail in other sections
* George Dyson, ''Turing's Cathedral: The Origins of the Digital Universe'', Pantheon, New York, 2012 - focused on the creation of this machine at the Institute for Advanced Study
* Raul Rojas, Ulf Hashagen, [https://doc.lagout.org/science/0_Computer%20Science/0_Computer%20History/The%20First%20Computers%20-%20History%20and%20Architectures.pdf ''The First Computers: History and Architectures''], MIT Press, Cambridge, 2002 - the IAS machine is covered in chapter II/4; no detail of the machine, but interesting coverage of the background and influence


===Papers===

* Arthur W. Burks, Herman H. Goldstine, John von Neumann, [https://www.cs.unc.edu/~adyilie/comp265/vonNeumann.html ''Preliminary discussion of the logical design of an electronic computing instrument''], Institute for Advanced Study, Princeton, June, 1946 - thoughts about the design of a computer - before any had ever been built!

* W. H. Ware, [http://bitsavers.trailing-edge.com/pdf/rand/P-377_The_History_And_Development_Of_The_IAS_Computer_Mar53.pdf ''The History and Development of the Electronic Computer Project at the Institute for Avanced Study''] (Rand Report P-377, March, 1953) - includes interesting detail of the electrical engineering design philosophy; implementation details of many of the 'copy' machines; and personnel notes
* Gerald Estrin, [https://dl.acm.org/doi/pdf/10.1145/800259.809005 ''A description of the electronic computer at the Institute for Advanced Studies''], Proceedings of the 1952 ACM national meeting (Toronto), September 1952 - very complete, but low-level, description

* Nicholas Metropolis, J. Worlton, [https://www.osti.gov/servlets/purl/4628499 ''A Trilogy On Errors in the History of Computing''], Los Alamos National Laboratory, Los Alamos, 1972 - contains a section on the mis-identification of the IAS machine as the 'MANIAC'; also historical notes about both machines


==External links==

* [http://www.bitsavers.org/pdf/ias/ IAS] - documentation at [[Bitsavers]] (skimpy)
** [http://www.bitsavers.org/pdf/ias/IAS_Final_Report_Jan54.pdf ''Final Progress Report on the Physical Realization of an Electronic Computing Instrument''] - contains a lot of details on the mathematics, and a detailed list of instructions
* John Deane, [https://archive.computerhistory.org/resources/access/text/2017/11/102693640-05-01-acc.pdf ''The IAS Computer Family Scrapbook''] - lists further information sources for each machine
* [https://www.ias.edu/electronic-computer-project Electronic Computer Project]

[[Category: Early Computers]]

Compatible Time-Sharing System

2025-12-01T11:17:22Z

Flx: /* History */ missing whitespace

The '''Compatible Time-Sharing System''' (usually '''CTSS''', for short) was a ground-breaking [[operating system]], the first [[time-sharing]] OS to be used in service.

The 'compatible' refers to the fact that it could simulate the [[Fortran Monitor System]], the [[batch operating system]] previously run on the [[IBM 7090]] and [[IBM 7094]] [[mainframe]] computers on which CTSS ran.

CTSS provided access to users on terminals connected to [[asynchronous serial line]]s, both local, and remote (via [[modem]]s). It had a [[file system]] which gave each user a [[directory]] in which they could keep their files, but it also allowed sharing of files between users.

It was similar to later time-shared systems, in that typing a command name caused that program to be loaded in from [[disk]] and run, but the [[command interpreter]] was part of the OS, not a separate user program.

Among the many important applications which were created for CTSS, along with the usual [[compiler]]s, [[assembler]], etc, were:

* RUNCOM, which allowed sequences of commands kept in a file to be run; this was part of the inspiration for the separate command interpreters, and their command file capabilities, of [[Multics]] and [[UNIX]]
* [[TYPSET]] and [[RUNOFF]], a [[text editor]] and [[word processor|type-setting]] program, the latter an inspiration for the later [[roff]] family of Multics and UNIX
* MAIL, one of the first [[electronic mail]] systems

It was also used as the development platform for Multics; a number of tools used in bringing up Multics were written for CTSS, including a [[cross-compiler]], etc.

==History==

The concept of time-sharing, as a way to improve the productivity of writing programs, had been discussed at [[Massachusetts Institute of Technology|MIT]] for some time, with a 1959 memo from John McCarthy being influential. A 'proof-of-concept' prototype was demonstrated at MIT on a lightly-modified [[IBM 709]] computer in 1960.

Work on what became CTSS itself started at the MIT Computation Center in 1961, running at first on the 709; the result was first demoed in November, 1961, handling four [[user]]s, by [[swapping]] to [[magnetic tape]] (with one [[magnetic tape drive|tape drive]] per user). The 709 was upgraded to a 7090 beginning in the spring of 1962, with the changeover complete by the late summer.

During 1962 and 1963, the system was improved and extended, and finally entered full service in the summer of 1963. [[Project MAC]] acquired their own 7094, which was delivered in October 1963, and CTSS came up on it several weeks later. The Computation Center machine was upgraded to a 7094 in 1964.

In its final form, CTSS ran on two modified 7094s at MIT; the so-called 'red machine' at Project MAC, and the 'blue machine' at the MIT Computation Center. (The names referred to the color of the side-panels on the machine.) The modifications included:

* a interval timer (to allow compute-bound user [[process]]es to be [[interrupt]]ed to allow other users to run);
* memory boundary and relocation registers
* a second 32K [[word]] [[main memory]] bank; the CTSS supervisor was held in what was called 'bank A', and user programs were in 'bank B'
* a mode bit in the CPU, to prevent users from executing I/O instructions (which trapped to the CTSS supervisor, for users)

The 'blue' machine at the Computation Center was returned to IBM in late 1968, and was replaced by the other, which soldiered on until it became too expensive and difficult to maintain. It was finally shut down on July 20, 1973.

==Graphics==

[[Image:Pdp7-kludge.png|thumb|right|Kludge display with PDP-7]]
CTSS also pioneered hardware and software for computer graphics, created at the MIT Electronics Systems Laboratory. The first ESL display console, also called the '''Kludge display''' was directly controlled from the 7094 CPU. Later a PDP-7 was used as a buffer computer, considerably reducing the load on the 7094. A second display console was built, based on a PDP-9. The first console was moved along with the Project MAC CTSS computer to MIT building 39 when the Computation Center machine was retired. The second console stayed with Project MAC.

ESL also designed an inexpensive display terminal called ARDS, '''Advanced Remote Display Station'''. It was based on a Tektronix storage tube.

==Influence==

CTSS was a very influential system; almost every operating system running today is, to some degree, a descendant. This specifically includes UNIX, about which Dennis Ritchie said:

: ''In most ways UNIX is a very conservative system. Only a handful of its ideas are genuinely new. In fact, a good case can be made that it is in essence a modern implementation of MIT’s CTSS system. This claim is intended as a compliment to both UNIX and CTSS. Today, more than fifteen years after CTSS was born, few of the interactive systems we know of are superior to it in ease of use; many are inferior in basic design.''

==See also==

* [[Michigan Algorithm Decoder]] - used on CTSS

==Further reading==

* [http://larch-www.lcs.mit.edu:8001/~corbato/sjcc62/ An Experimental Time-Sharing System] - The first paper about CTSS, for the [[FJCC]], from May 3, 1962
* [http://www.bitsavers.org/pdf/mit/lcs/tr/MIT-LCS-TR-0012.pdf The MAC System: A Progress Report] - MAC-TR-12, Robert M. Fano, October, 1964 - A later version of CTSS
* [http://www.bitsavers.org/pdf/mit/lcs/tr/MIT-LCS-TR-0016.pdf CTSS Technical Notes] - MAC-TR-16, Jerry Saltzer, March 15, 1965

==External links==

* [http://www.bitsavers.org/pdf/mit/ctss/ CTSS] - material at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/mit/ctss/CTSS_ProgrammersGuide.pdf The Compatible Time-Sharing System: A Programmer's Guide]
** [http://www.bitsavers.org/pdf/mit/ctss/CTSS_ProgrammersGuide_Dec69.pdf The Compatible Time-Sharing System: A Programmer's Guide (Second Edition)]
* [http://www.piercefuller.com/library/ctss.html CTSS] - downloadable source code and listings
* [https://people.csail.mit.edu/saltzer/Multics/CTSS-Documents/CTSS-Documents.html CTSS Documents] - a good overview of the available documentation
* [http://multicians.org/thvv/7094.html The IBM 7094 and CTSS] - Contains many links to original documents
* [http://multicians.org/project-mac.html Project MAC] - Contains a lot of information about CTSS and its origins
* [https://history.computer.org/pubs/2011-06-ctss.pdf Compatible Time-Sharing System (1961-1973): Fiftieth Anniversary Commemorative Overview]
* [https://softpanorama.org/History/ctss.shtml CTSS: the seminal system that "taught the world how to do time-sharing."]

[[Category: Operating Systems]]
[[Category: Demo Software]]

Super Dimension Fortress

2025-12-01T06:54:41Z

Flx: fix dead link

'''Super Dimension Fortress''' (usually referred to as the acronym, ''SDF'') is an organization which provides public-access [[UNIX]] and other historical systems; it is a recognized non-profit. It is "a networked community of free software authors, teachers, librarians, students, researchers, hobbyists, computer enthusiasts, the aural and visually impaired", and was founded in 1987.

It has recently taken over much of the old [[Living Computer Museum]]; a new organization, the 'Interim Computer Museum', has been set up to do so.

==External links==

* [https://sdf.org/ SDF Public Access UNIX System]
** [https://wiki.sdf.org/doku.php?id=start SDF User Contributed Tutorials] - actually a [[wiki]], contains other material
** [https://sdf.org/?ssh Connecting to Vintage Systems at SDF]
** [https://mastodon.sdf.org/about SDF Mastodon] - a "decentralized social media powered by [[Mastodon]]"
* [https://icm.museum ICM - a computer museum for the interim]
** [https://icm.museum/news.html News from the Interim Computer Museum]

[[Category: History]]

DOS extender

2025-12-01T05:42:33Z

Flx: hyphenation and spelling

A '''DOS Extender''' allows a [[program]] that is written for a '[[protected mode]]' environment to run under [[MS-DOS]]. MS-DOS is a '[[real mode]]' [[operating system]], but with some 'tricks' it's possible to run programs meant for [[OS/2]] 1.x on MS-DOS.

Now you may be wondering, what is 'real mode', 'protected mode', and a 'DOS extender', not to mention how they all interact with each other. I'll try to explain this.

The old 8086/8088 [[CPU]]s could address 1MB of [[RAM]] on their 20-bit [[address bus]] (2^20 is 1,048,576) and this memory is chopped up into 64KB [[segment]]s. The [[IBM PC]] reserves the top 384KB for adapters, hardware shared memory, and the [[ROM BIOS]], leaving 640KB for MS-DOS and your [[user]] programs. This is where that misattributed quote "640KB ought to be enough for anyone" comes from. This 8086/8088 'mode' is called the 'real' mode.

Well remember leaving the old [[CP/M]] computers that typically had 48KB or 64KB of RAM, 640KB seemed plenty at the time. Naturally it was a matter of time until people were making programs where they ran out of memory.

The solution from Intel was the [[Intel 80286|80286]] processor which was fully backwards compatible with the [[Intel 8086|8088/8086]], however it included a new mode of operation, protected mode, which when activated would supply a virtual [[address space]] of 1GB (1,073,741,824), and a 24-bit memory bus (2^24 is 16,777,216), allowing users to access 16MB of RAM.

Another big feature of protected mode is that memory is then protected so if a program accesses memory that it shouldn't, it'll generate a protection [[trap|fault]]. The 80286 also introduced the [https://en.wikipedia.org/wiki/Task_state_segment Task State Segment] (TSS) to support [[multi-tasking]] in hardware. The idea being with these two features a rogue program wouldn't crash the entire OS.

Intel's thinking was that the 8088/8086 software was a fad, and that once people saw the power of protected mode, they'd never want to leave it, so there is *NO* method for switching the 80286 back from protected mode to real mode once it's been entered.

Naturally this would require a whole new operating system to function in protected mode, and it would be incompatible with old MS-DOS programs as they simply will not function in protected mode. IBM & Microsoft started to collaborate on this new OS, called OS/2. The biggest obstacle that faced the team was that a new operating system that didn't support the growing 'legacy' base of MS-DOS applications would be doomed to fail. The IBM AT had this 'cheat' that while doing its POST in BIOS, the CPU would be switched to protected mode, to check & detect the memory. Then the instruction pointer would be saved in the start of RAM, and the keyboard controller would be used to reset the CPU, allowing the BIOS to continue back in real mode. While this did work, it was far too slow for an operating system to use where you may need to switch several thousand times a second.

Gordon Letwin spent a lot of time on trying to find a way to switch the 80286 from protected mode to real mode, when he hit upon what is known as the [[triple fault]]. The idea is that you place your instruction pointer much like the keyboard controller reset method, but you then remove all 'safety nets' by clearing the [[interrupt]] table for the CPU, and cause it to crash by throwing an interrupt. The CPU can't process the interrupt because the table is invalid, so it will end up doing a quick reset as the [[microcode]] assumes the processor has encountered a critical software problem.

This was a big save for OS/2 as now it could boot up into protected mode, run protected mode programs, and would allow the user to select a special 'DOS box' that would switch the processor into real mode, and run MS-DOS programs while switching back & forth between real & protected mode to service interrupts, and allow OS/2 programs to continue to execute in the background.

However when the first version of OS/2 was released in 1988, it had a confusing topview-like interface, which was full screen text, and didn't appear to multi-task as you could only work on one thing at a time.

So with that the idea of a dos extender was born.

The people behind [[Tenberry]] worked with Microsoft, and decided that they could bring the number one benefit of protected mode, a larger address space, to MS-DOS by writing a special program, the DOS Extender. Since MS-DOS & the PC BIOS are real mode programs, and can't function in protected mode, what Tenberry did was write a special loader that could load OS/2 programs into protected mode, but every time the program would make a MS-DOS call the DOS Extender would intercept the call, switch the processor into real mode, make the call, then return to protected mode, and return the result to the program.

The result being that you didn't have to install a new operating system, just rebuild your applications, link with the DOS Extender and now you could have access to 16MB of RAM!

After seeing that the 8086 was not a passing fad, Intel then built the [[i386|80386]] CPU which not only included a software method of switching from protected mode to real mode, but also included the ability to run 8086 programs in a hardware [[virtual machine]]. And since the 80386 is upwards compatible with the 80286, these DOS Extenders could continue to function, even if they relied on the triple fault.

[[Category: DOS Enhancements]]

Installing Windows NT 3.51 on Qemu

2025-11-28T02:51:19Z

Flx: use code block

This is a small guide to installing Windows NT 3.51 on [[qemu]].

[[Image:Windows NT 3.51 on Qemu.jpg|300px|thumb|right|Windows NT 3.51 running on Qemu]]

The NT 3.51 install is somewhat straighforward in terms of hardware.

NT 3.51 is expecting an ISA computer, and this will limit your choice of network cards to the NE2000.

With Qemu 0.10.5 I was able to select the cpu level so I don't know if it's as troubled as NT 3.1.

The NT 3.51 CD-ROM is not bootable. You will either have to have the floppies, or do a 'network' install. I recommend using MS-DOS to mount the CD-ROM and start an install that way - see [[Installing MS-DOS on Qemu]].

== disk setup ==
I've also had issues with a 1GB disk to install into, however I've had a 500MB disk work fine. At times the installer will pause seeming to lock but it's working... There must be some IO timeout issues at hand..

== networking ==
The NE2000 is setup by default on the IO port of 0x300 and IRQ 9 (which is mapped to 2...)

== running the emulator ==
This is how I run my emulator...

<pre>
qemu -L . -m 32 -hda nt351.disk -cpu 486 -net nic,model=ne2k_isa -net user -M isapc
</pre>

== Going from here ==
With Windows NT 3.51 installed there are a few things you'll probably want...

=== Service pack 5 ===
I would recommend installing the last service pack for NT 3.51, sp5 which you can obtain [http://support.microsoft.com/kb/128465 here].

=== New Shell ===
This was an 'alpha' of the Windows 95 shell ported to Windows NT 3.51.. You can download it [http://toastytech.com/guis/newshell2.zip here]. This will make NT 3.51 'feel' like NT 4.0

=== Internet Explorer ===
You can install the internet explorer for Windows 3.1 .. The last version was 5.01. You can download it from [http://www.oldapps.com/download.php?oldappsid=ie501.exe here].

=== Automatic login ===
Also you may want to have windows automatically log you in, use regedt32 to setup the registery as mentioned [http://support.microsoft.com/kb/97597 here].

=== FireFox ===
Yes, you can run firefox 2.0 on NT 3.51!

<pre>
Firefox 2 running under NT 3.51 (I had to delete nsSearchService.js
and nsSafebrowsingApplication.js to make it run under NT 3.51 and 95)
Flash 7 also runs great, as long as it has the NT 3.51 version of WININET.DLL.
</pre>

This information comes from http://toastytech.com/guis/misc4.html

[[Category:QEMU Tutorials]] [[Category:Qemu]]

Qemu

2025-11-28T02:47:02Z

Flx: update QEMU recent release

'''Qemu''' is a machine emulator & system virtualizer.

[[Image:Windows nt 4 0 MIPS.png|300px|thumb|right|Windows NT 4.0 MIPS under Qemu]]

Qemu can emulate numerous CPUs and machine types. Most are geared towards running [[Linux]], the x86/x64 emulators are the most flexible, and most well used. The latest version, released in October 2025, is 10.1.2.

As of 0.15.0 the following machine emulators are available:

*[[i386-softmmu]] IBM PC emulator
*[[x86_64-softmmu]] x64 IBM PC emulator
*[[arm-softmmu]]
*[[cris-softmmu]]
*[[m68k-softmmu]]
*[[microblaze-softmmu]]
*[[mips-softmmu]]
*[[mips64-softmmu]]
*[[mipsel-softmmu]]
*[[mips64el-softmmu]]
*[[ppc-softmmu]]
*[[ppcemb-softmmu]]
*[[ppc64-softmmu]]
*[[sh4-softmmu]]
*[[sh4eb-softmmu]]
*[[sparc-softmmu]]
*[[sparc64-softmmu]]
*[[s390x-softmmu]]

While not active, there is also the following in the tree:
*[[DEC Alpha]] (really incomplete)

== Running Qemu ==

Qemu is driven by command line arguments... The first thing that you typically do is setup a virtual hard disk with qemu-img. Once your disk is ready then you can configure each system emulator with various flags.

=== qemu-img ===
<pre>
qemu-img version 0.14.92, Copyright (c) 2004-2008 Fabrice Bellard
usage: qemu-img command [command options]
QEMU disk image utility

Command syntax:
check [-f fmt] filename
create [-f fmt] [-o options] filename [size]
commit [-f fmt] [-t cache] filename
convert [-c] [-p] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-s snapshot_name] filename [filename2 [...]] output_filename
info [-f fmt] filename
snapshot [-l | -a snapshot | -c snapshot | -d snapshot] filename
rebase [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F backing_fmt] filename
resize filename [+ | -]size

Command parameters:
'filename' is a disk image filename
'fmt' is the disk image format. It is guessed automatically in most cases
'cache' is the cache mode used to write the output disk image, the valid
options are: 'none', 'writeback' (default), 'writethrough' and 'unsafe'
'size' is the disk image size in bytes. Optional suffixes
'k' or 'K' (kilobyte, 1024), 'M' (megabyte, 1024k), 'G' (gigabyte, 1024M)
and T (terabyte, 1024G) are supported. 'b' is ignored.
'output_filename' is the destination disk image filename
'output_fmt' is the destination format
'options' is a comma separated list of format specific options in a
name=value format. Use -o ? for an overview of the options supported by the
used format
'-c' indicates that target image must be compressed (qcow format only)
'-u' enables unsafe rebasing. It is assumed that old and new backing file
match exactly. The image doesn't need a working backing file before
rebasing in this case (useful for renaming the backing file)
'-h' with or without a command shows this help and lists the supported formats
'-p' show progress of command (only certain commands)

Parameters to snapshot subcommand:
'snapshot' is the name of the snapshot to create, apply or delete
'-a' applies a snapshot (revert disk to saved state)
'-c' creates a snapshot
'-d' deletes a snapshot
'-l' lists all snapshots in the given image

Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels nbd blkdebug sheepdog blkverify host_device file
</pre>
=== Qemu ===

Please note that some of these flags change between versions

Qemu 0.15.0 rc2
<pre>
QEMU emulator version 0.14.92, Copyright (c) 2003-2008 Fabrice Bellard
usage: qemu [options] [disk_image]

'disk_image' is a raw hard disk image for IDE hard disk 0

Standard options:
-h or -help display this help and exit
-version display version information and exit
-machine [type=]name[,prop[=value][,...]]
selects emulated machine (-machine ? for list)
property accel=accel1[:accel2[:...]] selects accelerator
supported accelerators are kvm, xen, tcg (default: tcg)
-cpu cpu select CPU (-cpu ? for list)
-smp n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]
set the number of CPUs to 'n' [default=1]
maxcpus= maximum number of total cpus, including
offline CPUs for hotplug, etc
cores= number of CPU cores on one socket
threads= number of threads on one CPU core
sockets= number of discrete sockets in the system
-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]
-fda/-fdb file use 'file' as floppy disk 0/1 image
-hda/-hdb file use 'file' as IDE hard disk 0/1 image
-hdc/-hdd file use 'file' as IDE hard disk 2/3 image
-cdrom file use 'file' as IDE cdrom image (cdrom is ide1 master)
-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]
[,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]
[,cache=writethrough|writeback|none|unsafe][,format=f]
[,serial=s][,addr=A][,id=name][,aio=threads|native]
[,readonly=on|off]
use 'file' as a drive image
-set group.id.arg=value
set <arg> parameter for item <id> of type <group>
i.e. -set drive.$id.file=/path/to/image
-global driver.property=value
set a global default for a driver property
-mtdblock file use 'file' as on-board Flash memory image
-sd file use 'file' as SecureDigital card image
-pflash file use 'file' as a parallel flash image
-boot [order=drives][,once=drives][,menu=on|off]
'drives': floppy (a), hard disk (c), CD-ROM (d), network (n)
-snapshot write to temporary files instead of disk image files
-m megs set virtual RAM size to megs MB [default=128]
-mem-path FILE provide backing storage for guest RAM
-k language use keyboard layout (for example 'fr' for French)
-audio-help print list of audio drivers and their options
-soundhw c1,... enable audio support
and only specified sound cards (comma separated list)
use -soundhw ? to get the list of supported cards
use -soundhw all to enable all of them
-usb enable the USB driver (will be the default soon)
-usbdevice name add the host or guest USB device 'name'
-device driver[,prop[=value][,...]]
add device (based on driver)
prop=value,... sets driver properties
use -device ? to print all possible drivers
use -device driver,? to print all possible properties
File system options:
-fsdev local,id=id,path=path,security_model=[mapped|passthrough|none]
Virtual File system pass-through options:
-virtfs local,path=path,mount_tag=tag,security_model=[mapped|passthrough|none]

-name string1[,process=string2]
set the name of the guest
string1 sets the window title and string2 the process name (on Linux)
-uuid %08x-%04x-%04x-%04x-%012x
specify machine UUID

Display options:
-display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]
[,window_close=on|off]|curses|none|
vnc=<display>[,<optargs>]
select display type
-nographic disable graphical output and redirect serial I/Os to console
-curses use a curses/ncurses interface instead of SDL
-no-frame open SDL window without a frame and window decorations
-alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)
-ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt)
-no-quit disable SDL window close capability
-sdl enable SDL
-spice <args> enable spice
-portrait rotate graphical output 90 deg left (only PXA LCD)
-rotate <deg> rotate graphical output some deg left (only PXA LCD)
-vga [std|cirrus|vmware|qxl|xenfb|none]
select video card type
-full-screen start in full screen
-g WxH[xDEPTH] Set the initial graphical resolution and depth
-vnc display start a VNC server on display

1 target only:
-win2k-hack use it when installing Windows 2000 to avoid a disk full bug
-no-fd-bootchk disable boot signature checking for floppy disks
-no-acpi disable ACPI
-no-hpet disable HPET
-balloon none disable balloon device
-balloon virtio[,addr=str]
enable virtio balloon device (default)
-acpitable [sig=str][,rev=n][,oem_id=str][,oem_table_id=str][,oem_rev=n][,asl_compiler_id=str][,asl_compiler_rev=n][,data=file1[:file2]...]
ACPI table description
-smbios file=binary
load SMBIOS entry from binary file
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
specify SMBIOS type 0 fields
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=uuid][,sku=str][,family=str]
specify SMBIOS type 1 fields

Network options:
-net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]
create a new Network Interface Card and connect it to VLAN 'n'
-net user[,vlan=n][,name=str][,net=addr[/mask]][,host=addr][,restrict=on|off]
[,hostname=host][,dhcpstart=addr][,dns=addr][,tftp=dir][,bootfile=f]
[,hostfwd=rule][,guestfwd=rule] connect the user mode network stack to VLAN 'n', configure its
DHCP server and enabled optional services
-net tap[,vlan=n][,name=str],ifname=name
connect the host TAP network interface to VLAN 'n'
-net socket[,vlan=n][,name=str][,fd=h][,listen=[host]:port][,connect=host:port]
connect the vlan 'n' to another VLAN using a socket connection
-net socket[,vlan=n][,name=str][,fd=h][,mcast=maddr:port[,localaddr=addr]]
connect the vlan 'n' to multicast maddr and port
use 'localaddr=addr' to specify the host address to send packets from
-net dump[,vlan=n][,file=f][,len=n]
dump traffic on vlan 'n' to file 'f' (max n bytes per packet)
-net none use it alone to have zero network devices. If no -net option
is provided, the default is '-net nic -net user'
-netdev [user|tap|socket],id=str[,option][,option][,...]

Character device options:
-chardev null,id=id[,mux=on|off]
-chardev socket,id=id[,host=host],port=host[,to=to][,ipv4][,ipv6][,nodelay]
[,server][,nowait][,telnet][,mux=on|off] (tcp)
-chardev socket,id=id,path=path[,server][,nowait][,telnet],[mux=on|off] (unix)
-chardev udp,id=id[,host=host],port=port[,localaddr=localaddr]
[,localport=localport][,ipv4][,ipv6][,mux=on|off]
-chardev msmouse,id=id[,mux=on|off]
-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]
[,mux=on|off]
-chardev file,id=id,path=path[,mux=on|off]
-chardev pipe,id=id,path=path[,mux=on|off]
-chardev console,id=id[,mux=on|off]
-chardev serial,id=id,path=path[,mux=on|off]

Bluetooth(R) options:
-bt hci,null dumb bluetooth HCI - doesn't respond to commands
-bt hci,host[:id]
use host's HCI with the given name
-bt hci[,vlan=n]
emulate a standard HCI in virtual scatternet 'n'
-bt vhci[,vlan=n]
add host computer to virtual scatternet 'n' using VHCI
-bt device:dev[,vlan=n]
emulate a bluetooth device 'dev' in scatternet 'n'

Linux/Multiboot boot specific:
-kernel bzImage use 'bzImage' as kernel image
-append cmdline use 'cmdline' as kernel command line
-initrd file use 'file' as initial ram disk

Debug/Expert options:
-serial dev redirect the serial port to char device 'dev'
-parallel dev redirect the parallel port to char device 'dev'
-monitor dev redirect the monitor to char device 'dev'
-qmp dev like -monitor but opens in 'control' mode
-mon chardev=[name][,mode=readline|control][,default]
-debugcon dev redirect the debug console to char device 'dev'
-pidfile file write PID to 'file'
-singlestep always run in singlestep mode
-S freeze CPU at startup (use 'c' to start execution)
-gdb dev wait for gdb connection on 'dev'
-s shorthand for -gdb tcp::1234
-d item1,... output log to /tmp/qemu.log (use -d ? for a list of log items)
-D logfile output log to logfile (instead of the default /tmp/qemu.log)
-hdachs c,h,s[,t]
force hard disk 0 physical geometry and the optional BIOS
translation (t=none or lba) (usually qemu can guess them)
-L path set the directory for the BIOS, VGA BIOS and keymaps
-bios file set the filename for the BIOS
-enable-kvm enable KVM full virtualization support
-xen-domid id specify xen guest domain id
-xen-create create domain using xen hypercalls, bypassing xend
warning: should not be used when xend is in use
-xen-attach attach to existing xen domain
xend will use this when starting qemu
-no-reboot exit instead of rebooting
-no-shutdown stop before shutdown
-loadvm [tag|id]
start right away with a saved state (loadvm in monitor)
-option-rom rom load a file, rom, into the option ROM space
-clock force the use of the given methods for timer alarm.
To see what timers are available use -clock ?
-rtc [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]
set the RTC base and clock, enable drift fix for clock ticks (x86 only)
-icount [N|auto]
enable virtual instruction counter with 2^N clock ticks per
instruction
-watchdog i6300esb|ib700
enable virtual hardware watchdog [default=none]
-watchdog-action reset|shutdown|poweroff|pause|debug|none
action when watchdog fires [default=reset]
-echr chr set terminal escape character instead of ctrl-a
-virtioconsole c
set virtio console
-show-cursor show cursor
-tb-size n set TB size
-incoming p prepare for incoming migration, listen on port p
-nodefaults don't create default devices
-prom-env variable=value
set OpenBIOS nvram variables
-semihosting semihosting mode
-old-param old param mode
-readconfig <file>
-writeconfig <file>
read/write config file
-nodefconfig
do not load default config files at startup

During emulation, the following keys are useful:
ctrl-alt-f toggle full screen
ctrl-alt-n switch to virtual console 'n'
ctrl-alt toggle mouse and keyboard grab

When using -nographic, press 'ctrl-a h' to get some help.
</pre>

== Qemu tutorials ==
So far we've setup the following tutorials suitable for Qemu:

*[[Installing MS-DOS on Qemu]]
*[[Installing Windows 95 on Qemu]]

*[[Installing Windows NT 3.1 on Qemu]]
*[[Installing Windows NT 3.5 on Qemu]]
*[[Installing Windows NT 3.51 on Qemu]]
*[[Installing Windows NT 4.0 on Qemu]]
*[[Installing Windows NT 4.0 on Qemu(MIPS)]]

*[[Installing Windows 2000 on Qemu]]
*[[Installing Windows XP on Qemu]]

*[[Installing Windows 2003 x86 on Qemu]]
*[[Installing Windows 2003 x64 on Qemu]]

*[[Installing Windows Vista x86 on Qemu]]

*[[Installing OpenBSD 4.5 i386 on Qemu]]
*[[Installing OpenBSD 4.5 x64 on Qemu]]

*[[Installing NeXTSTEP on Qemu]] This also gives a guide on compiling Qemu, prior to the 0.15 release.

*[[Installing Xenix 2.x on Qemu]]

*[[Installing NetBSD 6.1.5 Sparc on Qemu]]
*[[Installing NetBSD 6.1.5 Sparc64 on Qemu]]

{{semi-stub}}

== External links ==

* Qemu's main site - http://wiki.qemu.org/Index.html
* Win32 builds of Qemu including ready to run images http://www.h7.dion.ne.jp/~qemu-win/
* Automated builds of Qemu are available [http://qemu.weilnetz.de/w64/ here for Win64], and [http://qemu.weilnetz.de/w32/ here for Win32].

[[Category: Emulators]]

Digital Storage Systems Interconnect

2025-11-28T02:29:23Z

Flx: typo? DDSSI -> DSSI in 1 place

[[File:BC22Q-09 DSSI Cable.jpg|thumb|right|250px|DSSI cable]]

The '''Digital Storage Systems Interconnect''' (usually given as '''DSSI''') is a [[mass storage]] [[bus]] from [[Digital Equipment Corporation|DEC]]. The DSSI specification lists the main attributes of DSSI as: 8-bit wide [[parallel]]; multi-drop linear bus electrical topology; low-cost, [[single-ended signalling]] interface circuitry; [[direct current|DC]] coupling. The DSSI's [[analog]] characteristics mean that DSSI installations require [[terminator]]s.

The DSSI is an alternate physical layer in the [[Computer Interconnect]] system; the CI system had a 'native' physical layer before the creation of DSSI. (DSSI is also an alternative mass storage [[drive]] to [[device controller|controller]] interface bus, from the earlier [[Standard Disk Interconnect]].) The relationship between the DSSI and the CI's physical layer is shown in the following diagram:
<pre>
<-----+
+---------------------+ |
| Port Driver | |
| Layer | |
| ( SCA Specification)| |
+---------------------+ |
| |
| |
....................... |
. CI Port Adapter . |
. ( eg: VAX CI Port ) . |
....................... |
| | P
+------> | | P
| +---------------------+ | D
| | CI Port | |
C | | Layer | | L
I | | ( DEC Std 161 ) | | A
| +---------------------+ | Y
A | | | | E
R | +------+ +------+ | R
C | | | |
H | +----------------------+ +---------------------+ |
I | | DSSI Datalink | | CI Datalink | |
T | | Layer | .... | Layer | |
E | | ( DSSI Spec. ) | | ( Dec Std 161 ) | |
C | +----------------------+ +---------------------+ |
T | | | <-----+
U | | | <-----+ P L
R | +----------------------+ +---------------------+ | H A
E | | DSSI Physical | | CI Physical | | Y Y
| | Interconnect | | Interconnect | | S E
| | ( DSSI Spec. ) | | ( DEC Std 161 ) | | I R
| +----------------------+ +---------------------+ | C
+------> <-----+ A
L

Figure 1-2: CI PPD Architectural Layers
</pre>

DSSI thus made it possible to build [[VAXcluster]]s from [[MicroVAX]] and smaller [[VAX]] computers, by adding CI-bus functionality to smaller VAX systems. It can also be used to create loosely-coupled [[multi-processor]]s, by sharing a number of [[disk drive]]s between two systems. Such shared drives are termed 'Integrated Storage Elements' (ISEs).

A description of the DSSI from the 'Digital's Storage System Interconnect' protocol specification document:

"The DSSI, supporting the needs of low-end and mid-range systems, is one in a family of high-performance computer-to-computer interconnects .. that combine a common host interface and port layer with an implementation-specific datalink and physical interconnect.
CI-class interconnects provide the transmission services required by Digital's [[System Communication Architecture]] (SCA) - a four-tiered set of protocols and interfaces.."

== Advance in DSSI Interface Usage ==

In the beginning there were DSSI interfaces and DSSI Integrated Storage Elements connected to them. Each individual ISE was a kind of [[Hierarchical Storage Controller]], i.e. a [[VAXcluster|cluster-capable]] controller, managing just a single storage device. This was a smart but expensive design and limited storage capacity to a maximum of 8 DSSI nodes (i.e. one or two DSSI controllers and seven resp. six DSSI devices) per DSSI bus.

In 1994 a new concept was introduced for DSSI devices: The '''[[HSD05 Array Controller]]''' as a first of three models of DSSI-to-[[SCSI]] bus adapters (HSD05/[[HSD10 DSSI-to-SCSI Bus Adapter|HSD10]]/[[HSD30]]). From now on an HSD05 could connect up to seven SCSI devices (disk and tape drives) to a DSSI bus as a single DSSI node, thus multiplying the available storage capacity. As an additional effect, the costs were reduced because cheaper SCSI disks (without a complex DSSI interface) could be used.

== DSSI Cabling ==

The [http://bitsavers.org/pdf/dec/dsa/dssi/EK-RF72D-UG-008_RF_Series_Integrated_Storage_Element_Users_Guide_Apr93.pdf "RF Series Integrated Storage Element User Guide"] (EK-RF72D-UG-008) says "The DSSI bus is a 50-conductor cable. Inside an enclosure, the bus may be a flat ribbon cable or a round bundle of twisted pairs. Between enclosures, the bus is a shielded round cable approximately ½-inch in diameter."

The short cables run from the [[printed circuit board|PCBs]] that implement the interfaces to a standard [[connector]] on the back of the enclosure. (Different enclosures use different short cables with a given board; see the "KFQSA Module Installation and User Manual", Section 2.1 for a partial list.)

=== Connectors ===

[[Image:DSSI_Connectors.png|thumb|350px|left|DSSI MR & PS Connectors]]

The long inter-enclosure DSSI cables are found with two different types of connectors:

* '''MR''' (Micro Ribbon or midrange), with flat [[contact]]s = "50 Way High Density Micro Ribbon"
* '''PS''' (Pin Socket or pedestal style), with round [[pin]]s = "50 Way High Density Honda"

[[File:DSSI MR Connector female (Cable).jpg|thumb|right|80px|MR female connector]]

When found on cables, these exist in both 'straight' and 'right-angle' forms (to allow cables to be neatly dressed, in part so they are less likely to get damaged).

With these two different types of connectors, ''three'' different basic types of long DSSI cables are needed (cable names for types available from DEC included):

* MR-MR - BC21Q-xx (2x straight); BC29S-xx (right-angle to straight)
* PS-PS - BC21M-xx (2x right-angle)
* MR-PS - BC22Q-xx (right-angle PS to straight MR); BC29R-xx (right-angle PS to right-angle MR)

(As usual with DEC cables, the '-xx' gives the length, numerically.) The MR-PS cables can be reversed to provide PS-MR.

Two types of DSSI connectors are found on devices:

* Single DSSI '''Device Connector''' 50-pin ([[SCSI]]-like)
* Dual 3.5" / Single 5.25" DSSI '''Disk Interface Card Assembly''' e.g. for [[VAX 4000]], BA430/BA440

== DSSI Controllers/Interfaces ==

* [[KFQSA]] [[QBUS]] DSSI Adapter
* [[KFMSA]] [[Extended Memory Interconnect|XMI]] Dual DSSI Adapter
* [[KFMSB]] XMI DSSI adapter
* [[KFESA]] [[Extended Industry Standard Architecture|EISA]] DSSI Adapter
* [[KFESB]] EISA DSSI Adapter
* [[KFPSA]] [[Peripheral Component Interconnect|PCI]] DSSI Adapter
* [[KFE52]] [[VAXft]] Multi-Function Interface
* [[KDXDA]] [[VAXft 810]] DSSI Interface
* [[EDA640]] [[MicroVAX 3300/3400]] [[KA640]] embedded DSSI Adapter (EDA)
* [[KFA40]] [[DEC 4000]] I/O Module
* [[SHAC]] [[VAX 4000 series]] embedded DSSI Adapter
* [[SWIFT]] [[VAXft series]] embedded DSSI Adapter

== DSSI Hierarchical Storage Controllers (HSDs) ==

[[Hierarchical Storage Controller]]s:

* [[HSD05]]
* [[HSD10 DSSI-to-SCSI Bus Adapter|HSD10]]
* [[HSD30]]
* [[HSD50]]

== DSSI Storage Expanders ==

* [[B213F]]
* [[B400X]]
* [[BA42A]]
* [[R215F]]
* [[R23RF]]
* [[R400X]]
* [[SF12]]
* [[SW301]]

== DSSI Disk Drives ==

[[Disk]]s:

* [[RF30]]
* [[RF31]]
* [[RF31F]]
* [[RF31T]]
* [[RF32]]
* [[RF35]]
* [[RF36]]
* [[RF37]]
* [[RF70]]
* [[RF71]]
* [[RF72]]
* [[RF73]]
* [[RF74]]
* [[RF75]]

== DSSI Solid State Disk Drives ==

[[Solid state disk]] drives:

* [[EF51R Solid State Disk Drive|EF51R]]
* [[EF52R Solid State Disk Drive|EF52R]]
* [[EF53 Solid State Disk Drive|EF53]]

== DSSI Tape Drives ==

* [[TF30]]
* [[TF70]]
* [[TF85]]
* [[TF86]]
* [[TF87]]
* [[TF88]]
* [[TF89]]

== Images ==

[[File:DSSI_PS_Connector_female_(Cable).jpg|thumb|left|300px|PS female connector]]
[[File:DSSI PS Connector female (Cable)-2.jpg|thumb|left|80px|PS female connector]]
[[File:DSSI_PS_Connector_male_(CPU).jpg|thumb|left|300px|PS male connector (CPU)]]
[[File:DSSI_PS_Terminator_female.jpg|thumb|left|300px|PS female terminator]]
[[File:BC22Q-09 Label.jpg|thumb|left|300px|BC22Q-09 label]]
[[File:DSSI_Interface_Card_Assembly.png|thumb|left|350px|Interface Card Assembly (5.25" FH disk)]]
[[File:DSSI_Interface_Card_Assembly_Dual_RF35_Connector.jpg|thumb|left|300px|Interface Card Assembly Dual RF35]]
[[File:DSSI_Device_Connector_RF30.jpg|thumb|left|300px| Device Connector RF30]]

 

{{semi-stub}}

==External Links==

* [http://bitsavers.org/pdf/dec/dsa/dssi/ DSSI] - DSSI and related documents at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/dec/dsa/dssi/Digitals_Storage_System_Interconnect_Rev_1.0.0_199003.txt Digital's Storage System Interconnect] - protocol specification document
* [http://www.bitsavers.org/pdf/dec/vax/3800/EK-338AC-DH-003_MicroVAX_Dual-Host_Systems_Dec90.pdf MicroVAX Dual-Host Systems] (EK-338AC-DH-003) - contains a clear description of how a DSSI can be used to create a loosely-couple multi-processor
* [https://manx-docs.org/collections/mds-199909/cd1/cluster/410abmgd.pdf DSSI VMScluster Installation and Troubleshooting Guide] (EK-410AB-MG.D01)
* [https://decdoc.itsx.net/dec94mds/rf72dug8.pdf RF Series Integrated Storage Element User Guide] (EK-RF72D-UG-008)
* [https://manx-docs.org/collections/mds-199909/cd2/cabinets/348abmg2.pdf BA430 BA440 Enclosure Maintenance.pdf] (EK-348AB-MG-002)

[[Category: DEC Buses]]
[[Category: DEC Mass Storage]]
[[Category: DSSI]]
[[Category: DEC Interface Standards]]

Honeywell 6000 series

2025-11-28T02:08:43Z

Flx: fix wikilink

[[Image:CISLMultics.jpg|350px|thumb|right|An SCU (left) and an H6180 CPU (center) at CISL]]

The '''Honeywell 6000 series''' was a long-lived family of [[mainframe]]s, in production from 1970 to 1989. They are probably best-known now for being the machines that [[Multics]] ran on for most of its life, after the initial period on a [[General Electric]] [[GE-645]] machine.

They were descendants of the [[GE 600 series]] family; after GE's computer business was sold to [[Honeywell]] in 1970, the 6000 series were Honeywell's replacements. They used [[Transistor-transistor logic|TTL]] [[Integrated circuit|SSI integrated circuits]] and larger [[printed circuit board]]s, unlike the older (and obsolescent) discrete [[transistor]] GE machines.

The basic [[architecture]] of the GE and Honeywell series was the same: a [[tightly-coupled]] [[multi-processor]], with all the [[Central Processing Unit|CPUs]] sharing access to a collection of [[multi-port memory]] units. All used 36-bit [[word]]s, and almost identical [[instruction set]]s; Honeywell added an [[Commercial Instruction Set|Extended Instruction Set]] (EIS) which provided string-manipulation instructions, [[binary-coded decimal|packed decimal]] instructions, etc.

Most 6000 series machines ran [[GCOS]] (General Comprehensive Operating System), an evolution of the earlier GECOS (General Electric Comprehensive Operating Supervisor) - early Honeywell documentation continued to call it GECOS.

Some models in the line had the additional [[hardware]] - the 'Appending Unit' (APU) - needed to implement the [[segment]]ed [[single-level memory]] used by Multics, which ran only on those models of the GE 600 and Honeywell 6000 series lines.

==System organization==

Systems were constructed of 3 main kinds of units: CPUs, I/O controllers, and memories (technically, System Control Units, or SCUs, with the memories being an integral part of the SCU - although later documentation relegates the SCU to being a logically separate control unit, and refers to the combination of an SCU and memory as a Central Memory Unit, or CMU - although this term seems not to have caught on widely, probably because the term 'SCU' was too engrained by that point).

CPUs were connected to SCUs (with a separate cable from each CPU to each SCU); I/O controllers were also connected to SCUs (again, a separate cable for each pairing), and could send [[interrupt]]s to the CPUs via the SCUs.

The first generation of I/O controllers was the IOM (Input/Output Multiplexer); these were later replaced by the IMU (Information Multiplexer Unit), which was programmable. Again, the term 'IOM' seems have persisted as the name for I/O Controllers.

All [[disk]] drives, [[magnetic tape|tape]] drives, etc were connected to the IOMs, via mass storage and magnetic tape processors, respectively. Eventually a 'Microprogrammed Peripheral Controller' (MPC) was used to control disk and tape drives.

[[Asynchronous serial line|Serial lines]], etc, were connected to a [[Front end|Front End Processor]] ('FNP', in Multics jargon), which were connected to IOMs (although some documentation indicates they could be connected directly to SCUs - although perhaps only on GCOS machines). There were several generations of these.

'Unit record' devices such as card readers, etc, were attached to a 'unit record processor', likewise attached to an IOM.

===Maximum configurations===

The maximum numbers of CPUs, IOMs, etc which could be connected to one system varied from generation to generation, and also between models; the GCOS-only units generally had lower limits than the Multics-capable ones.

This was in part a cost measure; the point-point cabling system required a separate port on each unit for each connection, and providing more ports required more hardware, increasing the cost. Even so, on many units, extra ports were installable options (although obviously there had to be provision for such).

Most SCUs provided 8 ports, but many CPUs and IOMs had only 4 ports, and could thus only connect to up to 4 SCUs. There were other limits, too; a CPU had a 'CPU number', assigned via switches, and many GCOS-only CPUs had only 2 bits of CPU number, whereas Multics-capable CPUs had 3.

The practical limit to the size of systems was caused by most SCUs having a maximum of 8 ports; each CPU used one port, as did each IOM. Later on an attempt was made to 'break' this limit by developing 'port sharing' technology. 6-CPU Multics systems did exist, however.

==Generations==

There were several generations of 6000 series machines, although some of the different names were more marketing gloss than significant changes. Performance improvements between the various generations were minimal.

Performance differences between the models of a generation were often a result of the usual marketing-driven nonsense; i.e. there was really only one kind of machine, and the lower-performing models in the range had been 'crippled' somehow (e.g. slower [[clock]]s), to reduce their performance.

Describing the various models in each generation is further complicated by the fact that model numbers were allocated to configurations; i.e. a system with one CPU would be a model xxx, and one with two CPUs would be a model yyy.

'''Note:''' ''The data below is generally sourced from Honeywell documentation, including marketing material. It is occasionally inconsistent as to the maximum number of CPUs, etc supported on any model. It is possible that the specifications changed over time.''

===6000 Series===

The first incarnation, announced in February 1971; the CPU speed was about 1 MIPS. Model numbers of the form 60xx indicated a GCOS machine; 61xx numbers indicated Multics.

The GCOS machines were the models 6030, 6040, 6050, 6060, 6070 and 6080.  The lower-priced, odd-third-digit models did not include the EIS; the others did. A low-end model, the 6025, was introduced in 1973. Systems could have a maximum of 4 CPUs and 4 IOMs.

In 1973 the model 6180, which supported Multics, was added. It was significantly different, architecturally, from the predecessor GE 645: on the GE machine, the 'protection rings' used for security on Multics had been simulated in [[software]]; on the 6180, rings were implemented in hardware. This allowed all cross-ring memory references to be checked in hardware, instead of software (the source of many security holes when the checks were not performed properly).

The first-generation SCUs used with these models, with [[core memory]], had a maximum capacity of 256KW each (later ones, with [[DRAM]], could hold considerably more).

===Series 60, Level 66 and Level 68===

Announced in April 1974, introduced in 1975, these were re-badged versions of the 6000 series, in slightly lower cabinets; they did, however, offer larger memory units. The incandescent light bulbs in the [[front panel]]s (which changed from the white of the original 6000's, to black) were replaced by [[Light Emitting Diode|LEDs]].

The Level 66 machines were GCOS, and Level 68 were Multics.

GCOS models included the 66/05, /10, /20, /40, /60 and /80.

The Multics models were the 68/60 and 68/80, which were identical except that in the former, the [[cache]] was disabled. Systems could have a maximum of 7 CPUs and 4 IOMs, although the total of the two was restricted to 8.

===Level 66/DPS and Level 68/DPS===

A 1977 re-naming of the line (no hardware changes); the Level 66's were GCOS, and the Level 68's were Multics. The names DPS-68 (and presumably DPS-66, to match) were also used.

GCOS models seem to have included the 66/DPS05 and /DPS1 through /DPS5, with varying numbers of CPUs (2, 3 and 4 in the last three). The /DPS1-/DPS5 could all be configured with up to four SCUs and four IOMs.

===DPS-8===

A lightly re-engineered version (about 1/3 of the boards were identical; 1/3, or slightly more, were lightly modified; the rest were totally different) of the previous generation, announced in October 1979, and released that year.

The extensive 'lights and switches' maintenance panels of the earlier machines were replaced with a console terminal, driven by a [[microprocessor|microcomputer]], the 'diagnostic processor', which interfaced to the CPUs, SCUs and IOMs; the smaller configuration panels were retained.

DPS-8 systems supported a maximum of four SCU's, down from the eight of earlier models, although each DPS-8 SCU could provide up to 16 Mbytes of memory, for 64 Mbytes total. A maximum of four IOMs were normally supported. The SCUs and IOMs were not separate cabinets, as in early models, but shared a cabinet with the CPU.

The low-end GCOS models - the DPS-8/20 and DPS-8/44 - used [[microcode]], instead of being hard-wired (as all the other 6000 series processors were). Other GCOS models included the DPS-8/47, /49, /52, /62 and /70 (the first two being implemented in 74F TTL technology). The /47 was limited to a single CPU and IOM, and the /49 to four CPUs and two IOMs; the /70 could support up to four IOMs.

The Multics units were the DPS-8/M models - the DPS-8/52M, DPS-8/62M and DPS-8/70M; all likewise limited to 4 SCUs (although this was not a problematic limit, as SCUs now could handle much more memory). Apparently all three used the same hardware, but the two lower-performance one has delays inserted into their clocks. The /70M came with an 8KW [[cache]]; later, an optional 32KW cache was introduced. The performance with the 8KW cache was about 1.68 times that of the 6180; with the 32KW cache, about 1.85.

==NSA architectural extension==

[[Image:L66VUPanel.jpg|150px|thumb|left|Level 66 New System Architecture Virtual Unit [[front panel]]]]

In mid-1973, a team looked at the possibility of porting GCOS to the Multics hardware, to gain increased security, but this was decided to be un-economic.

The effort did result in a new architectural extension to the 6000 Series, the 'New Series 6000 Architecture' or 'New System Architecture' (NSA); also later known as the 'Advanced Development Program' (ADP), and 'Virtual Memory and Security' (VMS).

It added a set of registers used to produce a more secure system, using [[domain]] ideas and '[[working set]]s'; and also [[virtual memory]] (which the GCOS machines had not previously supported - they only had [[base and bounds]] [[memory management]] hardware).

Implementation was delayed until the late 1970s, as GCOS was not in a position to use it until then. The concept was that the Series 60 machines could have either a Multics-style AU ('Appending Unit'), or the NSA-style VU ('Virtual Unit') optionally added to the CPU; the VU was actually available as an add-on option for deployed Level 66 machines.

The later DPS/8 machines also implemented as standard the 'VU' hardware, which was used by the GCOS 8 version of GCOS, which came into use starting in 1980.
 

==External links==

* [http://www.bitsavers.org/pdf/honeywell/large_systems/multics/ Multics] - mostly software, but some hardware
** [http://www.bitsavers.org/pdf/honeywell/large_systems/multics/AL39-0_MULTICS_Processor_Manual_Draft_Oct75.pdf Multics Processor Manual] - October, 1975 version
** [http://www.bitsavers.org/pdf/honeywell/large_systems/multics/AL39-01B_MULTICS_Processor_Manual_Feb82.pdf Multics Processor Manual] - February, 1982 version
** [http://www.bitsavers.org/pdf/honeywell/large_systems/multics/AL39-01C_MULTICS_Processor_Manual_Nov85.pdf Multics Processor Manual] - November, 1985 version
** [http://www.bitsavers.org/pdf/honeywell/large_systems/multics/_58009997-040_MULTICS_Differences_Manual_DPS_8-70M_Aug83.pdf Multics Differences Manual DPS 8/70M] - differences between the Level 68 and 68/DPS-8 processors
* [http://www.bitsavers.org/pdf/honeywell/cp-6/CP6_Seminar1_Aug85.pdf CP-6 Internals Seminar] - Covers the NSA architecture at the start
* [http://www.feb-patrimoine.com/english/gecos_to_gcos8_part_2.htm From GECOS to GCOS8: Part II - The Honeywell years]
* [http://ana-3.lcs.mit.edu/~jnc/tech/multics/MulticsPanels.html Multics and Related 6000 Series Front Panels] - Images of most of the front panels

[[Category: Mainframes]]
[[Category: 36-bit Computers]]

Unix/32V

2025-11-28T02:01:12Z

Flx: formatting, wikilinks, and grammar improvement

{{Infobox OS
| image = 32v.png
| caption = Logging into a 32v system
| name = 32V
| creator = Bell Labs / AT&T / [[Western Electric]]
| current version = 1.0 (1979)
| year introduced = 1979
| type = Multitasking, multiuser
| architecture = [[VAX]], theoretically [[portable]]
}}

'''32V''' is the first 32-bit version of [[UNIX]] created by Bell Labs. 32V is basically a 32-bit version of [[Seventh Edition Unix]] [[portable|ported]] to the [[VAX]]. While not the first 32-bit version of Unix (the [[Interdata]] one was), it was the most influential. 32V could only run on the [[VAX-11/780]] as it was the only VAX in existence at that time.

It's also worth noting that the [[Computer Systems Research Group‎]] used 32V as the basis for their work on 32-bit [[BSD]] Unix, starting with [[3 BSD|BSD 3.0]] which was a 32V kernel with demand paged [[virtual memory]], and the BSD 2.x utilities, rolled into one. Neither 32V nor BSD 3.0 include [[TCP/IP]]. Additionally, AT&T used 32V as the basis for [[UNIX System III|SYSIII]] work on both the [[PDP-11]] & VAX. This makes 32V the 'common ancestor' of both SYSV & 4BSD. Also be sure to check out the installation instructions [[Setting Up Version 1.0 of UNIX/32V Operating System]].

== The AT&T vs BSDi/CSRG Lawsuit ==

Because 32V is the basis for BSD 3.0 it was also the source of contention of the lawsuit. The whole issue has been made moot since Caldera bought the rights to UNIX, and released 32V as free software.

(AT&T is American Telephone and Telegraph, a U.S. Corporation;
BSDi is Berkeley Software Design Inc;
CSRG is the University of California's Computer Systems Research Group.)

== Manual Pages ==
Right now I've just inputted section 1 and they all need formatting to make them more wiki friendly. Eventually I'll have a 32/v man page .. page with each section with the normal spelling of the commands.

For now you can see all the section 1 commands, as I've tried to reflect in their name the release, section & command name.

*[[:Category:32v man section 1|32v man section 1]]

For example ls would be found as [[32v_1m_ls]].

== How do I get this to run?! ==

Right now, you have a variety of options to run 32V on your computer:

First you can follow our guide aptly named [[Installing 32V on SIMH]].
This guide was derived from [http://zazie.tom-yam.or.jp/starunix/ http://zazie.tom-yam.or.jp/starunix/], And you could follow it as well. Be sure you have the VAX-11/780 emulator from [[SIMH]] 3.8-0 or higher, if you are going to follow either of the prior links. 
The last, and easier solution is available [https://sourceforge.net/project/downloading.php?group_id=204974&filename=unix32v-0.3.exe&a=43027585 here]. This is a pre-configured ready to run windows package with 32V.

== Pictures of the tapes! ==
[[Image:32v-tape1.jpg|150px|Close up of the label]][[Image:32v-tape2.jpg|150px|picture of the tape]]

== What Runs? ==

Not very much... 32V does not provide any modern networking, and the C compiler is far from ANSI. I've also had issues with the [[FORTRAN]] compiler as its hash table size is too small to compile [[Zork]], and it is different regarding CLOSE and some other nonsense...

== Games ==
Yes, it wouldn't be fun without games.

<pre>
arithmetic
backgammon
bcd
ching
fish
fortune
hangman
number
quiz
random
trek
wump
</pre>

==See also==

* [[32V man pages]]
* [[A UNIX™ Operating System for the DEC VAX-11/780 Computer]]

==External links==

* [https://minnie.tuhs.org/cgi-bin/utree.pl?file=32V 32V] - 32V tree at [[The Unix Heritage Society|TUHS]]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=32V/usr/doc/summary What's New: Highlights of the UNIX/32V System]
* [http://squoze.net/UNIX/32v/ UNIX/32v]

{{Nav Unix}}

[[Category: VAX Operating Systems]]
[[Category: Non-DEC Operating Systems]]
[[Category: Unix OS's]]

A/UX

2024-12-29T05:34:43Z

Flx: /* Physical Hardware */ nested list and AWG -> Apple Workgroup Server

{{Infobox OS
| image = softpc-on-aux.png
| caption = A/UX 3.0.0 desktop
| name = A/UX
| creator = Apple/UniSoft
| current version = 3.11
| year introduced = 1988
| type = Multitasking, multiuser
| architecture = [[Macintosh]]
}}

After [[Steve Jobs]] left [[Apple]], they scrambled to put together a system that could compete with [[NeXT]]. Hearing that NeXT was going to enter the [[UNIX|Unix]] [[workstation]] market, Apple commissioned [[UniSoft]] to help port [[SYSVr2]] to its [[Macintosh II]] lineup.

== Significant Versions ==
=== 0.7 ===
[[Image:AUX 0.7 desktop.png|thumb|right|150px|A/UX 0.7's UI]]
This version is more infamous because it included the source code to the kernel, which can be built with a little bit of work. There is no real Toolbox in this version, but rather a bare minimal SYSV port. This version uses a SYSV filesystem, while later versions of A/UX used 4.2BSD's [[BSD Fast File System|FFS]].
=== 1.1.1 ===
[[Image:AUX 1.1.1 desktop.png|thumb|right|150px|A/UX 1.1.1's GUI]]
This is a super barebones version, the toolbox is barely able to run the terminal application and some simple desktop widgets.
=== 2.0 ===
[[Image:AUX 2.0 desktop.png|thumb|right|150px|A/UX 2.0's GUI]]
Version 2.0 is more polished, and able to run a finder that is more parallel to [[System 6]].
=== 3.0 ===
[[Image:AUX 3.0 desktop.png|thumb|right|150px|A/UX 3.0's GUI]]
This is the best version to get ahold of. 3.0 emulates a [[System 7|System 7.0.1]] environment.
=== 3.1.1 ===
This version was the final released version, in 1995
=== 4.0 ===
This version was announced, and abandoned in 1996

== How do I get this to run?! ==

=== Physical Hardware ===
You will need an actual [[Macintosh]] that is supported. The best machines are the Quadra series. Note, not all Quadras will run A/UX.

The supported Macintosh Machines:
* for A/UX 1.0 ~ A/UX 2.0 (68020 w/PMMU, 68030)
** Macintosh II, Rev B, with a 68851 PMMU
** Macintosh SE/30
** Macintosh IIx, IIcx, IIsi, IIci, IIfx
* A/UX 3.0 ~ A/UX 3.1.1 (68040)
** Centris 610, Centris 650
** Quadra 605, 610, 650, 700, 800, 900, 950.
** Apple Workgroup Server 60, 80, 95

The Macintosh environment from 3.0.1 did not run on Shoebill at one point; now it does.

However the Unix side of 3.0.0 and 3.0.1 (below) does work. You can create a hybrid setup by replacing the /mac directory on 3.0.1 media with the /mac directory of 3.0.0 install media.

=== Emulation ===
There is now 2 emulators capable of running A/UX, [[Shoebill]] and [[Qemu]].

==== Shoebill ====
Shoebill emulator can run A/UX 1.1.1, 2.0 & 3.0.0 (*NOTE that version 3.0.0 seems to work the best). The latest version includes SDL support which can run on *NIX'es and Windows.

==== Qemu ====
The latest qemu-system-m68k includes a Quadra 800 machine profile which can run 3.0.1 and above.

You can build it from the current dev branch, full instructions are [https://www.emaculation.com/forum/viewtopic.php?f=37&p=71794#p71794 here].

<pre>
git clone -b q800.upstream https://www.gitlab.com/mcayland/qemu q800-upstream
cd q800-upstream
./configure --target-list=m68k-softmmu --enable-gtk --enable-sdl
make
</pre>

With Qemu in hand, you'll need to configure it for install with the [https://surfdrive.surf.nl/files/index.php/s/ZcJMgrSBqFAqfQA/download BootFloppy], [https://vpsland.superglobalmegacorp.com/install/MacOS/OS/Apple-AUX-3.0.1.7z ISO] and a pre-partitioned disk image.
General instructions are from [https://www.emaculation.com/doku.php/m68k-qemu-on-windows here].

(as of now the SCSI disk won't respond with Apple codes so the disk tool won't work).
<pre>
qemu-img.exe create -f raw AUX301.img 2G
qemu-img.exe create -f raw pram.img 256
</pre>

The command line to install is like this:
<pre>
qemu-system-m68k.exe ^
-L pc-bios ^
-m 32 ^
-M q800 ^
-display sdl ^
-serial stdio ^
-bios Quadra800.rom ^
-g 800x600x8 ^
-net nic,model=dp83932 -net user ^
-drive file=pram-i1.img,format=raw,if=mtd ^
-device scsi-hd,scsi-id=0,drive=fd0,vendor="SEAGATE",product="ST225N",ver="1.0" ^
-drive file=AUXBootfloppy.img,media=disk,format=raw,if=none,id=fd0 ^
-device scsi-hd,scsi-id=1,drive=hd0,vendor="SEAGATE",product="ST225N",ver="1.0" ^
-drive file=AUX301.img,media=disk,format=raw,if=none,id=hd0 ^
-device scsi-cd,scsi-id=3,drive=cd0,vendor="MATSHITA",product="CD-ROM CR-8005",ver="1.0k" ^
-drive file=AUX301.iso,format=raw,media=cdrom,if=none,id=cd0
</pre>

==What Runs?==

Some early GNU stuff will compile, however keep in mind that during the lifespan of A/UX GNU started up the Apple protest over the 'look and feel' lawsuit.

==External links==

* [http://www.aux-penelope.com/ A/UX Server Penelope] - General information
** [http://www.aux-penelope.com/hardware.htm Hardware Requirements]
* [https://www.macintoshrepository.org/1696-a-ux-apple-unix-for-68k-version-3-0-1-3-1-update A/UX (Apple UNIX for 68k) version 3.0.1 + 3.1 update] - More sources for the emulator and OS
* [https://virtuallyfun.com/wordpress/category/aux/ A/UX archives] - Posts on various topics

===Documentation===

* [http://christtrekker.users.sourceforge.net/doc/aux/faq.html Semi-official FAQ list for A/UX]
* [http://n-1.nl/apple_aux/aux-faq/part1/ Apple A/UX FAQ List (1/4)] - A/UX Faq: THE place to start
* [http://n-1.nl/apple_aux/aux-faq/part2/ Apple A/UX FAQ List (2/4)]
* [http://n-1.nl/apple_aux/aux-faq/part3/ Apple A/UX FAQ List (3/4)]
* [http://n-1.nl/apple_aux/aux-faq/part4/ Apple A/UX FAQ List (4/4)]


===UNIX Timeline===

* [http://www.unix.org/Posters/download/unix_posterA3.pdf The Single UNIX Specification History & Timeline]

{{Nav Unix}}

[[Category: Apple Operating Systems]]
[[Category: Unix-based OS's]]

PuTTY

2024-08-02T19:14:36Z

Flx: bump to latest putty 0.81

Putty is a [[telnet]]/[[SSH]] [[client]] for Win32 Operating systems (Windows 95+). The best part about putty is that it does not require any installation, nor any other system packages, you can just download and run the exe. Putty also can handle various terminal types built in, and can store connection profiles into the registry.

== Information from the homepage ==

<pre>
PuTTY is a free implementation of SSH and Telnet for Windows and Unix platforms, along with an xterm terminal emulator.
It is written and maintained primarily by Simon Tatham.

The latest version is 0.81.

LEGAL WARNING: Use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is outlawed.
I believe it is legal to use PuTTY, PSCP, PSFTP and Plink in England and Wales and in many other countries,
but I am not a lawyer and so if in doubt you should seek legal advice before downloading it. You may find useful information at cryptolaw.org, which collects information on cryptography laws in many countries, but we can't vouch for its correctness.

Use of the Telnet-only binary (PuTTYtel) is unrestricted by any cryptography laws.

Latest news:
2024-04-15 PuTTY 0.81 released
</pre>

== Downloading ==

You can download the win32 i386 version directly [http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe here]. 
All other downloads are from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html download page].

==External links==

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY: a free SSH and Telnet client] - Original home page
* [https://www.putty.org/ Download PuTTY] - New home page

{{semi-stub}}

[[Category: Terminal Emulators]]

Coherent

2024-04-07T06:01:59Z

Flx: spelling fix

[[Image:Coherent 4 print ad.jpg|200px|thumb|right|A print Coherent ad]]

'''Coherent''' was a 'clean room' clone of [[Seventh Edition Unix|Unix v7]], originally written for the [[PDP-11]] in 1980. It was [[software port|ported]] to run on the [[IBM-compatible PC|IBM PC]] in 1983 and to the [[Zilog Z8000]]-based [[Commodore 900]] in 1985.

Coherent was somewhat famous for being audited by [[Bell Labs]] and was vetted to be free of AT&T code. Despite its low price it failed to achieve any significant market share.

A review from 1991 can be found [http://aplawrence.com/Reviews/coherent_1991.html here]

Coherent has been recently [[open source]]d, under a 3-clause [[BSD]] license.

More information about the source code to Coherent can be found at [http://www.nesssoftware.com/home/mwc/source.php www.nesssoftware.com].

== Getting it to run ==
Right now the easiest way is to use [[Qemu]]. I've found that a memory size of 8MB is the best, as I had several issues with 12MB. The [[fsck]] of a large [[disk]] during [[bootstrap|boot]] does take a long time, so you need to be patient or use a small disk.

{{semi-stub}}

{{Nav Unix}}

[[Category: UNIX Clones]]

RD50

2024-02-07T07:50:06Z

Flx: fix broken wikilink

The '''RD50''' from [[DEC]] is a re-branded [[Seagate]] 5.25" full height ST-506 5MB [[ST506 disk interface|ST506]] disk.

It was used on the following DEC computers:

* [[Rainbow Series]]
* [[Professional 300 Series]]

[[Category: DEC ST506 Disk Drives]]

VIC-20

2024-02-07T07:41:04Z

Flx: CPU and RAM description

[[Image:vic20.jpg|thumb|150px|right|Vic 20]]

The VIC-20 was Commodore's attempt at an ultra cheap computer that would lay much of the physical design influence for the later [[Commodore 64]], [[Commodore 128]], and even the [[Amiga 500]], [[Amiga 600]] and [[Amiga 1200]].

The VIC-20 released in 1980, containing a ~1 MHz [[MOS Technology 6502|6502]] CPU and 5 KB of RAM. While the RAM could be expanded, the default RAM is significantly lower than the 64 KB included in the [[Commodore 64]], which was [[Commodore Business Machines|Commodore's]] next computer in 1982.

The manual for the VIC-20 is available [http://www.replacementdocs.com/download.php?view.2918 here].

{{stub}}

[[Category: Commodore 8-bit Computers]]

Windows NT 3.1 December 1991 beta

2024-02-07T07:33:51Z

Flx: wikify links - CPU arch

{{Infobox OS
| image = windowsntdec1991cd.jpg
| caption = The October 1991 CD
| name = Windows NT December 1991 beta
| creator = Microsoft
| year introduced = 1991
| architecture = [[Intel 80386|i386]] [[MIPS]]
}}

This release features both [[Intel 80386|i386]] & [[MIPS]] at parity.

Other beta information can be found back [[Windows NT 3.1 Betas|here]]

[[Category: Microsoft Operating Systems]]

Gzip

2024-02-07T07:28:02Z

Flx: bump to latest gzip 1.13 in 2023

gzip is a better compression program then the old "compress" found on Unix research systems version 6 and higher. The latest version is 1.13 and for the most part the source should work on just about any 32- or 64-bit C compiler.

The homepage for gzip is: http://www.gnu.org/software/gzip/

{{stub}}
[[Category:GNU_Software]]
[[Category:Compression Software]]

Qemu

2024-02-07T04:19:57Z

Flx: bump QEMU latest version to 8.2.1 - homepage already linked in external links

Qemu is a machine emulator & system virtualizer.

[[Image:Windows nt 4 0 MIPS.png|300px|thumb|right|Windows NT 4.0 MIPS under Qemu]]

Qemu can emulate numerious CPUs and machine types. Most are geared towards running Linux, the x86/x64 emulators are the most flexible, and most well used. The latest version, released in January 2024, is 8.2.1.

As of 0.15.0 the following machine emulators are available:

*[[i386-softmmu]] IBM PC emulator
*[[x86_64-softmmu]] x64 IBM PC emulator
*[[arm-softmmu]]
*[[cris-softmmu]]
*[[m68k-softmmu]]
*[[microblaze-softmmu]]
*[[mips-softmmu]]
*[[mips64-softmmu]]
*[[mipsel-softmmu]]
*[[mips64el-softmmu]]
*[[ppc-softmmu]]
*[[ppcemb-softmmu]]
*[[ppc64-softmmu]]
*[[sh4-softmmu]]
*[[sh4eb-softmmu]]
*[[sparc-softmmu]]
*[[sparc64-softmmu]]
*[[s390x-softmmu]]

While not active, there is also the following in the tree:
*Dec Alpha (really incomplete)

== Running Qemu ==

Qemu is driven by command line arguments... The first thing that you typically do is setup a virtual hard disk with qemu-img. Once your disk is ready then you can configure each system emulator with various flags.

=== qemu-img ===
<pre>
qemu-img version 0.14.92, Copyright (c) 2004-2008 Fabrice Bellard
usage: qemu-img command [command options]
QEMU disk image utility

Command syntax:
check [-f fmt] filename
create [-f fmt] [-o options] filename [size]
commit [-f fmt] [-t cache] filename
convert [-c] [-p] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-s snapshot_name] filename [filename2 [...]] output_filename
info [-f fmt] filename
snapshot [-l | -a snapshot | -c snapshot | -d snapshot] filename
rebase [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F backing_fmt] filename
resize filename [+ | -]size

Command parameters:
'filename' is a disk image filename
'fmt' is the disk image format. It is guessed automatically in most cases
'cache' is the cache mode used to write the output disk image, the valid
options are: 'none', 'writeback' (default), 'writethrough' and 'unsafe'
'size' is the disk image size in bytes. Optional suffixes
'k' or 'K' (kilobyte, 1024), 'M' (megabyte, 1024k), 'G' (gigabyte, 1024M)
and T (terabyte, 1024G) are supported. 'b' is ignored.
'output_filename' is the destination disk image filename
'output_fmt' is the destination format
'options' is a comma separated list of format specific options in a
name=value format. Use -o ? for an overview of the options supported by the
used format
'-c' indicates that target image must be compressed (qcow format only)
'-u' enables unsafe rebasing. It is assumed that old and new backing file
match exactly. The image doesn't need a working backing file before
rebasing in this case (useful for renaming the backing file)
'-h' with or without a command shows this help and lists the supported formats
'-p' show progress of command (only certain commands)

Parameters to snapshot subcommand:
'snapshot' is the name of the snapshot to create, apply or delete
'-a' applies a snapshot (revert disk to saved state)
'-c' creates a snapshot
'-d' deletes a snapshot
'-l' lists all snapshots in the given image

Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels nbd blkdebug sheepdog blkverify host_device file
</pre>
=== Qemu ===

Please note that some of these flags change between versions

Qemu 0.15.0 rc2
<pre>
QEMU emulator version 0.14.92, Copyright (c) 2003-2008 Fabrice Bellard
usage: qemu [options] [disk_image]

'disk_image' is a raw hard disk image for IDE hard disk 0

Standard options:
-h or -help display this help and exit
-version display version information and exit
-machine [type=]name[,prop[=value][,...]]
selects emulated machine (-machine ? for list)
property accel=accel1[:accel2[:...]] selects accelerator
supported accelerators are kvm, xen, tcg (default: tcg)
-cpu cpu select CPU (-cpu ? for list)
-smp n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]
set the number of CPUs to 'n' [default=1]
maxcpus= maximum number of total cpus, including
offline CPUs for hotplug, etc
cores= number of CPU cores on one socket
threads= number of threads on one CPU core
sockets= number of discrete sockets in the system
-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]
-fda/-fdb file use 'file' as floppy disk 0/1 image
-hda/-hdb file use 'file' as IDE hard disk 0/1 image
-hdc/-hdd file use 'file' as IDE hard disk 2/3 image
-cdrom file use 'file' as IDE cdrom image (cdrom is ide1 master)
-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]
[,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]
[,cache=writethrough|writeback|none|unsafe][,format=f]
[,serial=s][,addr=A][,id=name][,aio=threads|native]
[,readonly=on|off]
use 'file' as a drive image
-set group.id.arg=value
set <arg> parameter for item <id> of type <group>
i.e. -set drive.$id.file=/path/to/image
-global driver.property=value
set a global default for a driver property
-mtdblock file use 'file' as on-board Flash memory image
-sd file use 'file' as SecureDigital card image
-pflash file use 'file' as a parallel flash image
-boot [order=drives][,once=drives][,menu=on|off]
'drives': floppy (a), hard disk (c), CD-ROM (d), network (n)
-snapshot write to temporary files instead of disk image files
-m megs set virtual RAM size to megs MB [default=128]
-mem-path FILE provide backing storage for guest RAM
-k language use keyboard layout (for example 'fr' for French)
-audio-help print list of audio drivers and their options
-soundhw c1,... enable audio support
and only specified sound cards (comma separated list)
use -soundhw ? to get the list of supported cards
use -soundhw all to enable all of them
-usb enable the USB driver (will be the default soon)
-usbdevice name add the host or guest USB device 'name'
-device driver[,prop[=value][,...]]
add device (based on driver)
prop=value,... sets driver properties
use -device ? to print all possible drivers
use -device driver,? to print all possible properties
File system options:
-fsdev local,id=id,path=path,security_model=[mapped|passthrough|none]
Virtual File system pass-through options:
-virtfs local,path=path,mount_tag=tag,security_model=[mapped|passthrough|none]

-name string1[,process=string2]
set the name of the guest
string1 sets the window title and string2 the process name (on Linux)
-uuid %08x-%04x-%04x-%04x-%012x
specify machine UUID

Display options:
-display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]
[,window_close=on|off]|curses|none|
vnc=<display>[,<optargs>]
select display type
-nographic disable graphical output and redirect serial I/Os to console
-curses use a curses/ncurses interface instead of SDL
-no-frame open SDL window without a frame and window decorations
-alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)
-ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt)
-no-quit disable SDL window close capability
-sdl enable SDL
-spice <args> enable spice
-portrait rotate graphical output 90 deg left (only PXA LCD)
-rotate <deg> rotate graphical output some deg left (only PXA LCD)
-vga [std|cirrus|vmware|qxl|xenfb|none]
select video card type
-full-screen start in full screen
-g WxH[xDEPTH] Set the initial graphical resolution and depth
-vnc display start a VNC server on display

1 target only:
-win2k-hack use it when installing Windows 2000 to avoid a disk full bug
-no-fd-bootchk disable boot signature checking for floppy disks
-no-acpi disable ACPI
-no-hpet disable HPET
-balloon none disable balloon device
-balloon virtio[,addr=str]
enable virtio balloon device (default)
-acpitable [sig=str][,rev=n][,oem_id=str][,oem_table_id=str][,oem_rev=n][,asl_compiler_id=str][,asl_compiler_rev=n][,data=file1[:file2]...]
ACPI table description
-smbios file=binary
load SMBIOS entry from binary file
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
specify SMBIOS type 0 fields
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=uuid][,sku=str][,family=str]
specify SMBIOS type 1 fields

Network options:
-net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]
create a new Network Interface Card and connect it to VLAN 'n'
-net user[,vlan=n][,name=str][,net=addr[/mask]][,host=addr][,restrict=on|off]
[,hostname=host][,dhcpstart=addr][,dns=addr][,tftp=dir][,bootfile=f]
[,hostfwd=rule][,guestfwd=rule] connect the user mode network stack to VLAN 'n', configure its
DHCP server and enabled optional services
-net tap[,vlan=n][,name=str],ifname=name
connect the host TAP network interface to VLAN 'n'
-net socket[,vlan=n][,name=str][,fd=h][,listen=[host]:port][,connect=host:port]
connect the vlan 'n' to another VLAN using a socket connection
-net socket[,vlan=n][,name=str][,fd=h][,mcast=maddr:port[,localaddr=addr]]
connect the vlan 'n' to multicast maddr and port
use 'localaddr=addr' to specify the host address to send packets from
-net dump[,vlan=n][,file=f][,len=n]
dump traffic on vlan 'n' to file 'f' (max n bytes per packet)
-net none use it alone to have zero network devices. If no -net option
is provided, the default is '-net nic -net user'
-netdev [user|tap|socket],id=str[,option][,option][,...]

Character device options:
-chardev null,id=id[,mux=on|off]
-chardev socket,id=id[,host=host],port=host[,to=to][,ipv4][,ipv6][,nodelay]
[,server][,nowait][,telnet][,mux=on|off] (tcp)
-chardev socket,id=id,path=path[,server][,nowait][,telnet],[mux=on|off] (unix)
-chardev udp,id=id[,host=host],port=port[,localaddr=localaddr]
[,localport=localport][,ipv4][,ipv6][,mux=on|off]
-chardev msmouse,id=id[,mux=on|off]
-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]
[,mux=on|off]
-chardev file,id=id,path=path[,mux=on|off]
-chardev pipe,id=id,path=path[,mux=on|off]
-chardev console,id=id[,mux=on|off]
-chardev serial,id=id,path=path[,mux=on|off]

Bluetooth(R) options:
-bt hci,null dumb bluetooth HCI - doesn't respond to commands
-bt hci,host[:id]
use host's HCI with the given name
-bt hci[,vlan=n]
emulate a standard HCI in virtual scatternet 'n'
-bt vhci[,vlan=n]
add host computer to virtual scatternet 'n' using VHCI
-bt device:dev[,vlan=n]
emulate a bluetooth device 'dev' in scatternet 'n'

Linux/Multiboot boot specific:
-kernel bzImage use 'bzImage' as kernel image
-append cmdline use 'cmdline' as kernel command line
-initrd file use 'file' as initial ram disk

Debug/Expert options:
-serial dev redirect the serial port to char device 'dev'
-parallel dev redirect the parallel port to char device 'dev'
-monitor dev redirect the monitor to char device 'dev'
-qmp dev like -monitor but opens in 'control' mode
-mon chardev=[name][,mode=readline|control][,default]
-debugcon dev redirect the debug console to char device 'dev'
-pidfile file write PID to 'file'
-singlestep always run in singlestep mode
-S freeze CPU at startup (use 'c' to start execution)
-gdb dev wait for gdb connection on 'dev'
-s shorthand for -gdb tcp::1234
-d item1,... output log to /tmp/qemu.log (use -d ? for a list of log items)
-D logfile output log to logfile (instead of the default /tmp/qemu.log)
-hdachs c,h,s[,t]
force hard disk 0 physical geometry and the optional BIOS
translation (t=none or lba) (usually qemu can guess them)
-L path set the directory for the BIOS, VGA BIOS and keymaps
-bios file set the filename for the BIOS
-enable-kvm enable KVM full virtualization support
-xen-domid id specify xen guest domain id
-xen-create create domain using xen hypercalls, bypassing xend
warning: should not be used when xend is in use
-xen-attach attach to existing xen domain
xend will use this when starting qemu
-no-reboot exit instead of rebooting
-no-shutdown stop before shutdown
-loadvm [tag|id]
start right away with a saved state (loadvm in monitor)
-option-rom rom load a file, rom, into the option ROM space
-clock force the use of the given methods for timer alarm.
To see what timers are available use -clock ?
-rtc [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]
set the RTC base and clock, enable drift fix for clock ticks (x86 only)
-icount [N|auto]
enable virtual instruction counter with 2^N clock ticks per
instruction
-watchdog i6300esb|ib700
enable virtual hardware watchdog [default=none]
-watchdog-action reset|shutdown|poweroff|pause|debug|none
action when watchdog fires [default=reset]
-echr chr set terminal escape character instead of ctrl-a
-virtioconsole c
set virtio console
-show-cursor show cursor
-tb-size n set TB size
-incoming p prepare for incoming migration, listen on port p
-nodefaults don't create default devices
-prom-env variable=value
set OpenBIOS nvram variables
-semihosting semihosting mode
-old-param old param mode
-readconfig <file>
-writeconfig <file>
read/write config file
-nodefconfig
do not load default config files at startup

During emulation, the following keys are useful:
ctrl-alt-f toggle full screen
ctrl-alt-n switch to virtual console 'n'
ctrl-alt toggle mouse and keyboard grab

When using -nographic, press 'ctrl-a h' to get some help.
</pre>

== Qemu tutorials ==
So far we've setup the following tutorials suitable for Qemu:

*[[Installing MS-DOS on Qemu]]
*[[Installing Windows 95 on Qemu]]

*[[Installing Windows NT 3.1 on Qemu]]
*[[Installing Windows NT 3.5 on Qemu]]
*[[Installing Windows NT 3.51 on Qemu]]
*[[Installing Windows NT 4.0 on Qemu]]
*[[Installing Windows NT 4.0 on Qemu(MIPS)]]

*[[Installing Windows 2000 on Qemu]]
*[[Installing Windows XP on Qemu]]

*[[Installing Windows 2003 x86 on Qemu]]
*[[Installing Windows 2003 x64 on Qemu]]

*[[Installing Windows Vista x86 on Qemu]]

*[[Installing OpenBSD 4.5 i386 on Qemu]]
*[[Installing OpenBSD 4.5 x64 on Qemu]]

*[[Installing NeXTSTEP on Qemu]] This also gives a guide on compiling Qemu, prior to the 0.15 release.

*[[Installing Xenix 2.x on Qemu]]

*[[Installing NetBSD 6.1.5 Sparc on Qemu]]
*[[Installing NetBSD 6.1.5 Sparc64 on Qemu]]

== See Also ==

* Qemu's main site - http://wiki.qemu.org/Index.html
* Win32 builds of Qemu including ready to run images http://www.h7.dion.ne.jp/~qemu-win/
* Automated builds of Qemu are available [http://qemu.weilnetz.de/w64/ here for Win64], and [http://qemu.weilnetz.de/w32/ here for Win32].

{{semi-stub}}

[[Category: Emulators]]

Vice

2024-02-07T04:16:52Z

Flx: bump VICE version to current v3.8

Vice is the popular, and portable emulator for various [[Commodore]] 8bit microcomputers. The latest version is Version 3.8, released in Dec 2023.

The homepage for VICE is [https://vice-emu.sourceforge.io/ here].

== Platforms ==

Vice runs on the following platforms:
*MS-DOS
*Microsoft Windows
*Acorn RISC OS systems
*BeOS systems
*QNX systems
*OS/2 systems
*Solaris systems
*SCO based systems
*Amiga based or derived systems
*Mac OS X systems
*GP2X systems
*SkyOS systems
*Minix 3.x systems
*Atari Mint systems

== Emulated Systems ==

Vice can emulate the following machines:

*[[Commodore 64]]
*[[Commodore 64DTV]]
*[[Commodore 128]]
*[[Vic 20]]
*[[PET]]
*[[Plus4]]
*[[CBM-II]]

[[Category:Emulators]]

2024-02-07T04:11:26Z

Flx: add project homepage link

'''Previous''' is an [[emulator]] for the old [[NeXT Computer, Inc]] machines namely the:

*NeXT Computer
*NeXTcube
*NeXTstation Turbo
*NeXTstation Color

From the website:

Previous is a Next computer hardware emulator. It aims to emulate a Next Cube or a Next Station with all its peripheral.

The emulator is not complete yet.

Current status
*Processor 68030 and 68040 CPUs work, including MMU for both, FPU is platform sensitive and has minor incompleteness
*Memory All memory + Mono video memory is handled + experimental color display
*User input Keyboard works, but partially bad key assignment Mouse works, but problems with losing focus
*DMA works for SCSI, MO, Memory to Memory and partially for Ethernet, with dummy for Sound and SCC
*SCSI Works
*SCSI peripherals CDROM and Hdd emulated
*Cube MO drive works, including real Reed Solomon ECC
*Timers Real time clock + 2 internal timers handled (known issues for event counter)

Currently Previous can boot up all available versions of NeXTSTEP and OPENSTEP that run on the 68000 platform.

== External Links ==
[https://previous.unixdude.net/ Previous - A NeXT Computer Emulator]

{{semi-stub}}

[[Category: Emulators]]

Windows 1.0 Premiere Edition

2024-02-06T17:29:14Z

Flx: move to External Links section

{{Infobox OS
| image = Windows_1.0_Premiere_Edition_floppy_disks.jpg
| caption = Microsoft Windows 1.0 Premiere Edition
| name = Microsoft Windows 1.0 Premiere Edition
| creator = Microsoft
| year introduced = 1985
| architecture = [[i8086]]
}}

Microsoft Windows Premiere Edition is a preliminary release of the Microsoft Windows 1.0 operating environment, which shipped to testers in July 1985 to provide an early look at the Windows product, before the final product was finished and ready to be shipped. The final release was Windows 1.01.

Quoting Tandy Trower (Microsoft Windows 1.0 product manager): "But by the early summer of 1985, we were still not close to being done, so Steve declared we should release a preliminary release that I dubbed the "Premiere Edition", which we provided to key application vendors, analysts, and members of the press for feedback and in partial fulfillment of Ballmer’s promise to ship the product that summer."

According to Trower, the memory management code of the operating system needed to be rewritten at a later point in development:

"Then just at the point I was starting to feel more optimistic about wrapping things up the architect of the memory management code told me he found a critical defect in its design and would need to re-write it, basically rendering all testing to date useless. I pleaded with him to find an easier way, but after a thorough discussion there was no option other than to let him proceed and restart the testing process."

NOTE to users: A properly preserved and fully original copy of this release is available as a "BetaArchive exclusive".

==trueyanksfan's copy==
A user named trueyanksfan owns a copy of the original floppy disk set of this release and also provided pictures (shown here on the right) on the forum. Only the fourth disk was usable though, since the remaining three disks were since overwritten.

Shown below is a copy of the fourth disk, with updated files from between October 23rd and October 28th, 1985, which were likely provided to testers for further evaluation prior to the product's release.

==Alias' copy==
A picture of the floppy disk set of this and a screenshot of the Windows logo screen were provided by a user named Alias, who eventually provided the site with a well preserved and fully original copy, currently provided to visitors as a BetaArchive exclusive..

==Picture==

[[Image:Windows 1.0 Premiere Edition .png|200px]]

==External links==
* [http://www.betaarchive.com/forum/viewtopic.php?f=1&t=33172 A BetaArchive Exclusive: Windows 1.0 Premiere Edition!]
* [http://www.betaarchive.com/forum/viewtopic.php?t=33024 Windows 1.0 Premier Edition picture]
* [http://technologizer.com/2010/03/08/the-secret-origin-of-windows/2/ Tandy Trower - The Secret Origin of Windows]

[[Category: Microsoft Operating Systems]]

User talk:Flx

2024-02-06T17:28:03Z

Flx: using External Links

==External links==

Wikipedia style, which we generally follow, is to corral external links to an 'External links' section at the bottom, instead of including them in the body of the text. I don't know why they did it that way; it was started ''very'' early, before I joined, and I joined in August, 2003.

It was more habit than anything else to do this here (I happen to like it), but it does have its advantages: they often decay over time, so having them all in one place makes it easy to check them, and replace them with Internet Archive links when needed. (I wonder if we should change style to link directly to IA copies, in general? I'll have to ask, see what people think. Although having the original URL generally makes it easy to find the IA copy when the original goes away.) [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 17:42, 6 February 2024 (CET)
: I am willing to do that & keep external links in the dedicated External Links section. The [[Windows 1.0 Premiere Edition]] page is an interesting case because it is a mirror of this page https://www.betaarchive.com/wiki/index.php/Windows_1.0/Premiere_Edition which also has the links inline. One thing I'm not sure on this site is if we use the inline ref citations, ex: https://en.wikipedia.org/wiki/Wikipedia:Inline_citation#Ref_tags [[User:Flx|Flx]] ([[User talk:Flx|talk]]) 18:27, 6 February 2024 (CET)

Windows 1.0 Premiere Edition

2024-02-06T15:53:24Z

Flx: add missing external links

{{Infobox OS
| image = Windows_1.0_Premiere_Edition_floppy_disks.jpg
| caption = Microsoft Windows 1.0 Premiere Edition
| name = Microsoft Windows 1.0 Premiere Edition
| creator = Microsoft
| year introduced = 1985
| architecture = [[i8086]]
}}

Microsoft Windows Premiere Edition is a preliminary release of the Microsoft Windows 1.0 operating environment, which shipped to testers in July 1985 to provide an early look at the Windows product, before the final product was finished and ready to be shipped. The final release was Windows 1.01.

Quoting Tandy Trower (Microsoft Windows 1.0 product manager): "But by the early summer of 1985, we were still not close to being done, so Steve declared we should release a preliminary release that I dubbed the "Premiere Edition", which we provided to key application vendors, analysts, and members of the press for feedback and in partial fulfillment of Ballmer’s promise to ship the product that summer." Source: [http://technologizer.com/2010/03/08/the-secret-origin-of-windows/2/ [1]]

According to Trower, the memory management code of the operating system needed to be rewritten at a later point in development:

"Then just at the point I was starting to feel more optimistic about wrapping things up the architect of the memory management code told me he found a critical defect in its design and would need to re-write it, basically rendering all testing to date useless. I pleaded with him to find an easier way, but after a thorough discussion there was no option other than to let him proceed and restart the testing process."

NOTE to users: A properly preserved and fully original copy of this release is available on this site as a "BetaArchive exclusive". [http://www.betaarchive.com/forum/viewtopic.php?f=1&t=33172 See here for details].

==trueyanksfan's copy==
A user named trueyanksfan owns a copy of the original floppy disk set of this release and also provided pictures (shown here on the right) on the forum. Only the fourth disk was usable though, since the remaining three disks were since overwritten.

Shown below is a copy of the fourth disk, with updated files from between October 23rd and October 28th, 1985, which were likely provided to testers for further evaluation prior to the product's release.

==Alias' copy==
A [http://www.betaarchive.com/forum/viewtopic.php?t=33024 picture] of the floppy disk set of this and a screenshot of the Windows logo screen were provided by a user named Alias, who eventually provided the site with a well preserved and fully original copy, currently provided to visitors as a BetaArchive exclusive..

==Picture==

[[Image:Windows 1.0 Premiere Edition .png|200px]]

[[Category: Microsoft Operating Systems]]

QuickC for Windows

2024-02-06T15:34:51Z

Flx: capitalize DOS & whitespace

{{Infobox Software
| image = QuickC front.jpg|150px
| caption = A retail copy of QuickC for Windows
| name = QuickC for Windows
| creator = Microsoft
| year introduced = 1990
| architecture = [[i8086]], [[i286]]
| type = Compiler
| language = C
}}

QuickC for Windows was a [[C (language)|C]] [[compiler]] hosted in [[Microsoft Windows 3.0]]. This was the cheapest way of writing [[protected mode]] [[program]]s, as this retailed for $149, along with the $150 cost of Windows 3.0. DOS Extenders of the time with compilers cost several thousand dollars. Not only was this a super cheap solution, but the superior winhelp help engine made programming easier.

The [[interface]] from QuickC for windows eventually found its way into the Visual C++, as both share many common elements. What had started as an entry level compiler, was to give rise to the next generation tools.

You could target both MS-DOS & Windows 3.0 with this compiler, although the MS-DOS programs were restricted to real mode only. There was no DOS extender support. However with the [[QuickWin]] [[library]], it was desirable to port simple command line/text programs to Windows in order to use the additional memory.

The few restrictions is that you cannot create static libraries. There is support for creating Windows DLL's however you cannot call the QuickWin functions from those DLL's. The compiler is a DLL called from the interface, so you cannot invoke any of it from the command line.

A good review is available in the [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false InfoWorld Nov 18, 1991].

{{semi-stub}}

[[Category: C Compilers]]

VAX 8600

2024-02-05T07:30:07Z

Flx: grammar & style

{{InfoboxVAX-Data
| name = VAX 8600
| Announcement = 31 October 1984
| FRS-date = March 1985
| Codename = Venus
| OS-support-VMS = V4.0
| CPU-module = KA86
| Num-proc = 1
| VMS-CPU = 4
| VMS-XCPU = 0
| SID = 0408F3FE
| XSID = 00000000
| CPU-technology = ECL Gate Array
| CPU-cycle = 80ns
| CPU-clock = 12.5MHz
| Instruction-buffer = 8 bytes [[#ref_1|[1]]]
| Translation-buffer = 512 entries [[#ref_1|[1]]]
| Gate-delay = 1ns
| WCS = 8K 86-bit words [[#ref_1|[1]]]
| Cache = 16KB [[#ref_1|[1]]]
| Compatibility-mode = Yes
| Console-processor = T-11 [[#ref_1|[1]]]
| Console-device = RL02 [[#ref_1|[1]]]
| Minimum-memory = 4MB
| Maximum-memory = 368MB
| Memory-checking = 7-bit ECC/longword [[#ref_1|[1]]]
| Max-I/O-throughput = 20MB/s
| BUS-MASSBUS = 4 @ 2.0MB/s
| BUS-UNIBUS = 7 @ 1.5MB/s
| LAN-support = optional
| VUPs = 4.2
}}

The '''VAX 8600''' was [[Digital Equipment Corporation|DEC]]'s second-generation [[VAX]], intended as the replacement for the [[VAX-11/780]]. It was intended to offer several times the performance of the 11/780, at roughly the same price. It could be field-upgraded to a [[VAX 8650]].

{{stub}}

==References==

* <div id="ref_1">[1] VAX Hardware Handbook Volume 1 - 1986. </div>

==External links==

* [http://www.bitsavers.org/pdf/dec/vax/8600/ 8600] - documentation at [[Bitsavers]]
* [http://www.bitsavers.org/pdf/dec/vax/handbook/VAX_Hardware_Handbook_Volume_1_1986.pdf VAX Hardware Handbook Volume 1] - the VAX 8600 is described on pages 1-23–1-28 (pp. 38-43 of the PDF) and covered in detail in Chapter 7 (pp. 210-228)
* [https://manx-docs.org/collections/antonio/dec/db86xtd2.pdf VAX 8600/8650 SBIA Technical Description] (EK-DB86X-TD-002)

{{Nav VAX}}

[[Category: DEC VAX systems]]

Altair 8800

2024-02-05T03:27:07Z

Flx: mention Altair bus -> S-100 bus development

The '''Altair 8800''' from MITS (Micro Instrumentation and Telemetry Systems) was the first mass-produced [[personal computer]] to be openly available. It was introduced in January, 1975, as a kit; later, pre-assembled units were made available.

It was a [[microcomputer]], built around an [[Intel 8080]] [[microprocessor]]. The early 8800's were unreliable, and had a weak [[power supply]]; the later 8800a was better, but it was only with the 8800b that it became really reliable. It originally came with no [[peripheral]]s, just a [[front panel]]; later, a variety of optional add-on units, including a [[floppy disk]] drive, were made available.

It is famous for being the machine that got [[Bill Gates]] and [[Paul Allen]] started; MITS did a deal with them to write a [[BASIC]] [[interpreter]] for it (Allen was actually hired as a MITS employee).

The Altair 8800 was implemented as a set of cards (ex: a CPU card, a memory card, optional serial or disk controller cards, etc) connected by a 100-pin backplane. Both MITS and third-party companies produced cards using this bus. This 100-pin Altair bus led to the standardization of the [[S-100]] bus, which is very similar, but not 100% compatible.

{{semi-stub}}

==External links==

* [http://www.bitsavers.org/pdf/mits/8800/ 8800] - documentation at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/mits/8800/Altair_Age_Of_Altair_Catalog-1975.pdf The Age of Altair] - catalog
** [http://www.bitsavers.org/pdf/mits/8800/Altair_Computer_Report_1975.pdf MITS Altair Computer Report]
** [http://www.bitsavers.org/pdf/mits/8800/Altair_PriceList_19750401.pdf MITS Altair Price List]

[[Category: 8-bit Personal Computers]]

MediaWiki talk:Sidebar

2024-02-05T02:57:14Z

Flx: closed: fixed

== link to Random page removed ==

Is there a reason the link to Special:Random was removed from the nav sidebar? (recently replaced with Special:PrefixIndex). I found that link very convenient when browsing casually, or for finding pages that might need some cleanup.

Of course the actual https://gunkies.org/wiki/Special:Random still exists, but less convenient. [[User:Flx|Flx]] ([[User talk:Flx|talk]]) 21:49, 3 February 2024 (CET)

: No particularly good reason; I wanted to add the 'prefix' entry, and didn't want to expand the box, so I figured that 'random page' was something that nobody ever used, and so could be safely removed. But if you actually used it, I'm more than happy to put it back. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 07:26, 4 February 2024 (CET)
:: Thank you! [[User:Flx|Flx]] ([[User talk:Flx|talk]]) 03:57, 5 February 2024 (CET)

DEMOS

2024-02-03T20:52:09Z

Flx: standardize name to avoid redirect

{{Infobox OS
| image = Demos on Windows 95.jpg
| caption = Logging into a DEMOS 3.0 unix system
| name = DEMOS / Демос
| creator = Kurchatov Institute of Atomic Energy parts from AT&T/Western Electric & CSRG
| current version = 3.0
| year introduced = 1983?
| type = Multitasking, multiuser
| architecture = [[PDP-11]], [[CM 1700]], 68020, XT Clones.
}}

DEMOS / Демос was a Soviet version of [[Unix]] that included portions of AT&T Unix, portions from [[BSD]], and some parts translated into Russian, and other utilities written in Russian. I think the PDP-11 version 2 of DEMOS was based on [[2.9BSD|2.9 BSD]].

There was also a 32bit version to the [[VAX]] clone, the [[CM 1700]] although I can't find any solid information other than it was based on [[4.2 BSD]].

In the book [[4.2_BSD#The_Cuckoo.27s_Egg|The Cuckoo's Egg]], it's mentioned that the Russians already had the source to 4.2 BSD. On some mechanical translations it does appear that the KGB had nothing to do with providing the BSD to the DEMOS team.

== Getting it to run ==
Right now the easiest way is to simply download the archive from [http://code.google.com/p/vak-opensource/downloads/detail?name=dvk-demos.zip&can=2&q= Serge Vakulenko]'s site. Just unzip & run. Binaries are included for Linux / Windows. You'll want some kind of terminal capable of ASCII / Cyrillic / KOI8-R.

{{stub}}

{{Nav Unix}}

[[Category: Unix-based OS's‎]]
[[Category: PDP-11 Operating Systems]]

MediaWiki talk:Sidebar

2024-02-03T20:49:47Z

Flx: sidebar link to Special:Random

PC/370

2023-12-23T14:30:00Z

Flx: typo

PC/370 is a simple [[System/370]] emulator that simulates a few mainframe environments, and provides the means to build assembly programs on the PC, and run them.

*[http://don-higgins.net/pc370.htm http://don-higgins.net/pc370.htm]

PC/370 is generally considered obsolete, and it no longer needs to be paid for.

== Links of interest ==
*[http://www.billqualls.com/assembler/ http://www.billqualls.com/assembler/] A PDF copy of the book "Mainframe Assembler Programming" released by it's author.

{{stub}}
[[Category:Emulators]]

QNX

2023-12-20T11:02:10Z

Flx: cleanup extra char

[[Image:Qnx4n000.png|thumb|right|200px|QNX 4.0 boot]]

QNX was noted for being used as the [[Operating system|OS]] for the Unisys ICON computer systems in Ontario High schools. It's a [[POSIX]] influenced [[Real-time system|RTOS]].

== History ==

* 1982: Quantum Software - QUNIX for Intel 8088
* 1984: QUNIX was renamed to QNX
* 2004: QNX is acquired by Harman International Industries
* 2010: QNX is acquired by BlackBerry

== QNX 4 ==

Versions of QNX 4 were released between 1990 and 1997. QNX 4.24 was used as the origin of QNX/Neutrino. Future versions (except for 4.25) are based on the QNX/Neutrino fork.

Latest Version: 4.25

== QNX 6 ==

Versions of QNX 6 were released between 2001 and 2014, based on the QNX/Neutrino fork. Neutrino added support for [[MIPS]], PowerPC, SH-4, and [[ARM]] CPU architectures.

This should be what RIM has purchased for use in the Playbook tablet.

Latest Version: 6.6

== QNX 7 ==

QNX 7 is the current version, initially released in 2017. Supported CPU architectures include 32-bit and 64-bit ARM, and 64-bit x86.

Latest Version: 7.1 (2020)

== References ==
* [http://www.qnx.com/developers/docs/qnxcar2/index.jsp?topic=%2Fcom.qnx.doc.neutrino.getting_started%2Ftopic%2Fpreface_History.html Preface to the QNX Neutrino Programmer's Guide]
* [https://www.qnx.com/developers/docs/7.1/#com.qnx.doc.neutrino.prog/topic/64bits.html Programmer's Guide: 32- and 64-Bit Architectures]
* [https://webcache.googleusercontent.com/search?q=cache:EnqHVmO55MEJ:www.qnx.com/developers/docs/qnxcar2/topic/com.qnx.doc.neutrino.getting_started/topic/s3_qnx2nto_Platforms.html&hl=en&gl=us| QNX Neutrino - MIPS, PPC, SH4, and ARM Support]
* [https://www.qnx.com/developers/articles/rel_6423_0.html QNX Software Development Platform 7.0: Release Notes]
* [https://www.forbes.com/sites/greatspeculations/2014/06/06/a-look-at-blackberrys-qnx-business/?sh=1282d1eb1123 Forbes: A Look at BlackBerry's QNX Business]

{{stub}}
[[Category:Operating Systems]]

QNX

2023-12-20T11:01:47Z

Flx: acquisition & version history

[[Image:Qnx4n000.png|thumb|right|200px|QNX 4.0 boot]]

QNX was noted for being used as the [[Operating system|OS]] for the i Unisys ICON computer systems in Ontario High schools. It's a [[POSIX]] influenced [[Real-time system|RTOS]].

== History ==

* 1982: Quantum Software - QUNIX for Intel 8088
* 1984: QUNIX was renamed to QNX
* 2004: QNX is acquired by Harman International Industries
* 2010: QNX is acquired by BlackBerry

== QNX 4 ==

Versions of QNX 4 were released between 1990 and 1997. QNX 4.24 was used as the origin of QNX/Neutrino. Future versions (except for 4.25) are based on the QNX/Neutrino fork.

Latest Version: 4.25

== QNX 6 ==

Versions of QNX 6 were released between 2001 and 2014, based on the QNX/Neutrino fork. Neutrino added support for [[MIPS]], PowerPC, SH-4, and [[ARM]] CPU architectures.

This should be what RIM has purchased for use in the Playbook tablet.

Latest Version: 6.6

== QNX 7 ==

QNX 7 is the current version, initially released in 2017. Supported CPU architectures include 32-bit and 64-bit ARM, and 64-bit x86.

Latest Version: 7.1 (2020)

== References ==
* [http://www.qnx.com/developers/docs/qnxcar2/index.jsp?topic=%2Fcom.qnx.doc.neutrino.getting_started%2Ftopic%2Fpreface_History.html Preface to the QNX Neutrino Programmer's Guide]
* [https://www.qnx.com/developers/docs/7.1/#com.qnx.doc.neutrino.prog/topic/64bits.html Programmer's Guide: 32- and 64-Bit Architectures]
* [https://webcache.googleusercontent.com/search?q=cache:EnqHVmO55MEJ:www.qnx.com/developers/docs/qnxcar2/topic/com.qnx.doc.neutrino.getting_started/topic/s3_qnx2nto_Platforms.html&hl=en&gl=us| QNX Neutrino - MIPS, PPC, SH4, and ARM Support]
* [https://www.qnx.com/developers/articles/rel_6423_0.html QNX Software Development Platform 7.0: Release Notes]
* [https://www.forbes.com/sites/greatspeculations/2014/06/06/a-look-at-blackberrys-qnx-business/?sh=1282d1eb1123 Forbes: A Look at BlackBerry's QNX Business]

{{stub}}
[[Category:Operating Systems]]

QNX

2023-12-20T10:27:13Z

Flx: wikify RTOS

[[Image:Qnx4n000.png|thumb|right|200px|QNX 4.0 boot]]

QNX was noted for being used as the os for the iCON computer systems in Ontario High schools. It's a [[POSIX]] influenced [[Real-time system|RTOS]].

== History ==

* 1982: Quantum Software - QUNIX for Intel 8088

== QNX 4 ==

Latest Version:

== QNX 6 ==

Latest Version: 6.5.0
This should be what RIM has purchased for use in the Playbook tablet.

{{stub}}
[[Category:Operating Systems]]

PuTTY

2023-12-19T21:22:28Z

Flx: update PuTTY site readme and release

Putty is a [[telnet]]/[[SSH]] [[client]] for Win32 Operating systems (Windows 95+). The best part about putty is that it does not require any installation, nor any other system packages, you can just download and run the exe. Putty also can handle various terminal types built in, and can store connection profiles into the registry.

== Information from the homepage ==

<pre>
PuTTY is a free implementation of SSH and Telnet for Windows and Unix platforms, along with an xterm terminal emulator.
It is written and maintained primarily by Simon Tatham.

The latest version is 0.80.

LEGAL WARNING: Use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is outlawed.
I believe it is legal to use PuTTY, PSCP, PSFTP and Plink in England and Wales and in many other countries,
but I am not a lawyer and so if in doubt you should seek legal advice before downloading it. You may find useful information at cryptolaw.org, which collects information on cryptography laws in many countries, but we can't vouch for its correctness.

Use of the Telnet-only binary (PuTTYtel) is unrestricted by any cryptography laws.

Latest news:
2023-12-18 PuTTY 0.80 is released
</pre>

== Downloading ==

You can download the win32 i386 version directly [http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe here]. 
All other downloads are from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html download page].

==External links==

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY: a free SSH and Telnet client] - Original home page
* [https://www.putty.org/ Download PuTTY] - New home page

{{semi-stub}}

[[Category: Terminal Emulators]]

Port

2023-12-19T11:11:27Z

Flx: typo "c"ommunication

'''Port''', in computers, can refer to several different things:

* [[hardware port]] - a means of gaining access to a computer or a sub-system
* [[networking port]] - a communication point
* [[software port]] - moving code from one environment to another

{{disambiguation}}

Hypervisor

2023-12-18T11:22:23Z

Flx: re-order section

A '''hypervisor''' is a [[software]] package which provides [[virtual machine]]s.

There are two main types of hypervisors, classified by their level of abstraction from the physical hardware:
* Type 1 - 'native' hypervisors, which are [[operating system]]s which run directly on the bare machine
* Type 2 - 'hosted' hypervisors, which are [[application]]s which run under a general-purpose OS.

The Type 2 hypervisors, for example VMware Workstation or Oracle VirtualBox, run as an application within the host operating system, ex: as a Linux or Windows program. To minimize overhead, Type 1 hypervisors avoid the need for the host to run another operating system, and they instead run directly on the bare-metal hardware. Examples of Type 1 hypervisors include VMware ESXi, Microsoft Hyper-V, and KVM.

[[File:Hypervisor-type1vs2.png]]

Early hypervisors were created by IBM, including [[CP_operating_system|CP/CPS]] and [[VM/370]], which allowed for creating VMs of different operating systems on the mainframe.

{{semi-stub}}

[[Category: OS Concepts]]

Hypervisor

2023-12-18T11:21:37Z

Flx: early IBM implementations

A '''hypervisor''' is a [[software]] package which provides [[virtual machine]]s.

There are two main types of hypervisors, classified by their level of abstraction from the physical hardware:
* Type 1 - 'native' hypervisors, which are [[operating system]]s which run directly on the bare machine
* Type 2 - 'hosted' hypervisors, which are [[application]]s which run under a general-purpose OS.

The Type 2 hypervisors, for example VMware Workstation or Oracle VirtualBox, run as an application within the host operating system, ex: as a Linux or Windows program. To minimize overhead, Type 1 hypervisors avoid the need for the host to run another operating system, and they instead run directly on the bare-metal hardware. Examples of Type 1 hypervisors include VMware ESXi, Microsoft Hyper-V, and KVM.

Early hypervisors were created by IBM, including [[CP_operating_system|CP/CPS]] and [[VM/370]], which allowed for creating VMs of different operating systems on the mainframe.

[[File:Hypervisor-type1vs2.png]]

{{semi-stub}}

[[Category: OS Concepts]]

Hypervisor

2023-12-18T11:16:21Z

Flx: examples of Type 1 vs Type 2 hypervisors + diagram

File:Hypervisor-type1vs2.png

2023-12-18T11:15:32Z

Flx: Comparison of Type 1 vs Type 2 hypervisor architecture. Own work, created 2023-12-18 using draw.io

Comparison of Type 1 vs Type 2 hypervisor architecture.
Own work, created 2023-12-18 using draw.io

Bash

2023-11-21T06:46:28Z

Flx: +link

[[GNU]] Bourne-Again SHell

Perhaps one of the most famous programs from the [[GNU]] project.

== Version 1 ==

In the early days...

The [https://groups.google.com/g/gnu.announce/c/hvhlR1Vn1P0/m/NYwp-4_0CaUJ?hl=en beta announcement for bash 0.99] came in June 1989. The intention was to keep compatibility with the Bourne shell, and the source code for this GPL implementation, as well as binaries for several architectures such as [[Sun-3]]/[[Sun-4]]/[[VAX]], were published with the announcement.

Without the earliest versions in the [https://ftp.gnu.org/gnu/bash/ release archive], bash reached version 1.14 by mid 1994. The latest available patch is bash 1.14.7 from August 1996.

== Version 2 ==

More mainstream, and starting to get [[Linux]] central.

bash 2.0 was released in December 1996, with the most recent 2.05b in August 2004.

== Version 3 ==

bash 3.0 was released in August 2004, with the most recent 3.2 coming in October 2006. This version had a long lifespan, with minor patches like 3.2.48 in 2009 and 3.2.57 in 2014.

Notably, bash 3.x was the last version released under the GPLv2. This means that some products that have an incompatible license with GPLv3 have stayed on bash 3.x; for example Apple kept bash 3.2 as the default shell of Mac OS X / macOS until 2019

== Version 4 ==

bash 4.0 was released in February 2009, with the most recent 4.4 patch in January 2018. As suggested above, this version adopted the GPLv3 license.

== Version 5 ==

bash 5.0 was released in January 2019, with the most recent 5.2 patch in November 2023. This is the version under active development as of 2023.

== References ==
* [https://ftp.gnu.org/gnu/bash/ GNU bash release archive]
* [https://thenextweb.com/news/why-does-macos-catalina-use-zsh-instead-of-bash-licensing Why does macOS Catalina use ZSH instead of Bash]
* [https://git.savannah.gnu.org/cgit/bash.git/tree/COPYING?h=bash-3.2-beta GPLv2 in bash 3.2] & [https://git.savannah.gnu.org/cgit/bash.git/tree/COPYING?h=bash-4.0 GPL v3 in bash 4.0]

[[Category:GNU_Software]]
{{stub}}

Bash

2023-11-21T06:45:48Z

Flx: update history through bash 5.x

GNU Bourne-Again SHell

Perhaps one of the most famous programs from the [[GNU]] project.

== Version 1 ==

In the early days...

The [https://groups.google.com/g/gnu.announce/c/hvhlR1Vn1P0/m/NYwp-4_0CaUJ?hl=en beta announcement for bash 0.99] came in June 1989. The intention was to keep compatibility with the Bourne shell, and the source code for this GPL implementation, as well as binaries for several architectures such as [[Sun-3]]/[[Sun-4]]/[[VAX]], were published with the announcement.

Without the earliest versions in the [https://ftp.gnu.org/gnu/bash/ release archive], bash reached version 1.14 by mid 1994. The latest available patch is bash 1.14.7 from August 1996.

== Version 2 ==

More mainstream, and starting to get [[Linux]] central.

bash 2.0 was released in December 1996, with the most recent 2.05b in August 2004.

== Version 3 ==

bash 3.0 was released in August 2004, with the most recent 3.2 coming in October 2006. This version had a long lifespan, with minor patches like 3.2.48 in 2009 and 3.2.57 in 2014.

Notably, bash 3.x was the last version released under the GPLv2. This means that some products that have an incompatible license with GPLv3 have stayed on bash 3.x; for example Apple kept bash 3.2 as the default shell of Mac OS X / macOS until 2019

== Version 4 ==

bash 4.0 was released in February 2009, with the most recent 4.4 patch in January 2018. As suggested above, this version adopted the GPLv3 license.

== Version 5 ==

bash 5.0 was released in January 2019, with the most recent 5.2 patch in November 2023. This is the version under active development as of 2023.

== References ==
* [https://ftp.gnu.org/gnu/bash/ GNU bash release archive]
* [https://thenextweb.com/news/why-does-macos-catalina-use-zsh-instead-of-bash-licensing Why does macOS Catalina use ZSH instead of Bash]
* [https://git.savannah.gnu.org/cgit/bash.git/tree/COPYING?h=bash-3.2-beta GPLv2 in bash 3.2] & [https://git.savannah.gnu.org/cgit/bash.git/tree/COPYING?h=bash-4.0 GPL v3 in bash 4.0]

[[Category:GNU_Software]]
{{stub}}

Compaq

2023-11-21T05:58:51Z

Flx: Compaq, not Canon, buys DEC

'''Compaq''' was a producer of [[personal computer]]s, founded in 1982. Most notably, they were the first to successfully produce an [[IBM-compatible PC]], making PC compatibility (and the resultant ability to run [[software]] produced for the [[IBM PC]] - unusual in an era when most software had to be customized to each vendor's machines) a major theme of their marketing. The resultant widespread adoption heralded the development of the computerized society.

Compaq's machines led [[International Business Machines|IBM]]'s for quite a while; they were, for instance, the first to produce a machine built around the [[Intel 80386]].

Compaq bought [[Digital Equipment Corporation|DEC]] in 1998, but its attempt to become a full-service computer company by doing so failed; it, in turn, was merged with [[Hewlett-Packard]] in 2002.

{{semi-stub}}

==Further reading==

* Rod Canion, ''Open: How Compaq Ended IBM's PC Domination and Helped Invent Modern Computing'', Benbella Books, Dallas

[[Category: Computer Manufacturers]]

Compiling Dungeon on RT-11

2023-11-20T19:04:47Z

Flx: clean HTML markup

Thanks to the countless comments on the SIMH list, and the final missing step from Peter Schorn, one of the source copies of Dungeon now builds.

Naturally you'll need [[SIMH]]'s pdp11 emulator.

If you want to follow along, you’ll need the pdp11 emulator from SIMH, and the following disk images:
*[http://simh.trailing-edge.com/kits/rt11swre.tar.Z rt11swre.tar.Z]
*[http://www.headcrashers.org/comp/rx01/fortran-iv/fortran-iv-v021-compiler-files.img fortran-iv-v021-compiler-files.img]
*[http://www.headcrashers.org/comp/rx01/fortran-iv/fortran-iv-v021-objecttime-system.img fortran-iv-v021-objecttime-system.img]
*[http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rt/dsk/misc/dunsrc.dsk dunsrc.dsk]

Then create an ini file like this:

<pre>
set cpu 256k
set rq0 rx50
set rq1 rx50
set rq2 rx50
set rq3 rx50

att rk0 rtv4_rk.dsk
att rk1 dunsrc.dsk

boot rk0
</pre>

Then go ahead and run it:
<pre>
PDP-11 simulator V3.8-1
Disabling CR

RT-11SJ V04.00C

.D 56=5015

.TYPE V4USER.TXT
Welcome to RT-11 Version 4. RT-11 V04 provides new hardware support
and some major enhancements over Version 3B.

Please use the HELP command; it describes the new options in many
of the utilities.

If you are using a terminal that requires fill characters,
modify location 56 with a Deposit command before proceeding with
system installation. LA36 DECwriter II and VT52 DECscope terminals
do NOT require such modification.

.D 56=0

.
</pre>
Hit Control+E and “insert” the first Fortran disk

<pre>
Simulation stopped, PC: 156070 (MOV (SP)+,R2)
sim> att rx0 fortran-iv-v021-compiler-files.img
RX: buffering file in memory
sim> c
</pre>
Then we are going to do the following:

<pre>
.ASSIGN RK0: OUP

.ASSIGN DX0 INP

.R PIP
*SY:*.*=INP:FORTRA.HLP,DEMO.FOR
*^C

.RUN INP:FORGEN
Answer questions with:
"?" or carriage return (<CR>) for information,
YES(Y) for affirmation, anything else for NO.

A maximum of 56 lines are allowed per listing page.
Is this acceptable? Y
A maximum of 136 characters are allowed in a formatted
(ASCII) record. Is this acceptable? Y
A maximum of 6 channels may be open at a given time.
Is this acceptable? Y
The FORTRAN compiler can compile system-specific OPEN and CLOSE
statement keywords for RT-11, RSX-11, and RSTS/E systems. These
statements are currently compiled for the following system: RT-11
Is this acceptable? Y
FORTRAN can produce inline code for EAE, EIS or FIS hardware,
or it can produce threaded (THR) code which is hardware independent.
Should the compiler produce EAE code? N
Should the compiler produce EIS code? N
Should the compiler produce FIS code? N
Should the compiler produce THR code? Y
The inline compiler can optimize for SPEED or for SIZE. These
optimizations are mutually exclusive. Do you want
the optimization to be for SPEED? N
Do you wish a threaded only compiler? Y
Compiler options selection complete.

.@INP:F4LTHR

.R LINK
*OUP:FORTRA=INP:FROOT///S
*INP:F0,INLINE,OUP:DEFLTS/O:1
*INP:F1/O:1
*INP:F2/O:1
*INP:F3/O:1
*INP:F4/O:1
*INP:F5/O:1
*INP:F6/O:1
*INP:F7/O:1
*INP:F8/O:1
*INP:F9/O:1
*INP:F10/O:1
*INP:LOOP/O:1
*INP:F11/O:1
*INP:F12/O:1
*INP:F13/O:1
*INP:F14/O:1
*INP:F15/O:1
*INP:F16/O:1
*INP:F17/O:1
*INP:CDUMP/O:1//
*^C

.
</pre>
Ok, now the compiler should be created. We next need to interrupt the emulator again (control+e) and insert the objecttime diskette. We will now build our Fortran library.

<pre>
Simulation stopped, PC: 151412 (ASL R3)
sim> att rx0 fortran-iv-v021-objecttime-system.img
RX: writing buffer to file
RX: buffering file in memory
sim> c

.R LIBR
*OUP:FORLIB=INP:NHD,OTSCOM,NOVIR,V2NS/G
Global? $ERRS
Global? $ERRTB
Global? $VRINT
Global?
*^C
</pre>
Now with that out of the way, we build a test program to make sure our compiler & library are working.
<pre>
.COMPILE DEMO.FOR
.MAIN.

.LINK DEMO,FORLIB

.RUN DEMO
***** RT11 FORTRAN IV V2 DEMONSTRATION TEST *****

INSTALLATION SUCCESSFUL IF NO ERROR MESSAGES
WERE PRINTED ABOVE.

**** FORTRAN DEMONSTRATION TEST COMPLETE *****
</pre>
Ok everything looks fine! Now onward to Dungeon! First we copy everything to the RK0 disk…
<pre>
.COPY RK1:*.* *.*
Files copied:
RK1:ACTORS.FTN to DK:ACTORS.FTN
RK1:CLOCKR.FTN to DK:CLOCKR.FTN
RK1:DEMONS.FTN to DK:DEMONS.FTN
RK1:DGAME.FTN to DK:DGAME.FTN
RK1:DINIT.FTN to DK:DINIT.FTN
RK1:DMAIN.FTN to DK:DMAIN.FTN
RK1:DSUB.FTN to DK:DSUB.FTN
RK1:DUNGEO.DOC to DK:DUNGEO.DOC
RK1:DVERB1.FTN to DK:DVERB1.FTN
RK1:DVERB2.FTN to DK:DVERB2.FTN
RK1:GDT.FTN to DK:GDT.FTN
RK1:OBJCTS.FTN to DK:OBJCTS.FTN
RK1:RRND.MAC to DK:RRND.MAC
RK1:RSXTIM.MAC to DK:RSXTIM.MAC
RK1:SVERBS.FTN to DK:SVERBS.FTN
RK1:VERBS.FTN to DK:VERBS.FTN
RK1:VMSRND.MAC to DK:VMSRND.MAC
RK1:BALLOP.FOR to DK:BALLOP.FOR
RK1:DINDX.DAT to DK:DINDX.DAT
RK1:DSO1.FOR to DK:DSO1.FOR
RK1:DSO2.FOR to DK:DSO2.FOR
RK1:DSO3.FOR to DK:DSO3.FOR
RK1:DSO4.FOR to DK:DSO4.FOR
RK1:DSO5.FOR to DK:DSO5.FOR
RK1:DSO6.FOR to DK:DSO6.FOR
RK1:DSO7.FOR to DK:DSO7.FOR
RK1:LIGHTP.FOR to DK:LIGHTP.FOR
RK1:NOBJS.FOR to DK:NOBJS.FOR
RK1:NP.FOR to DK:NP.FOR
RK1:NP1.FOR to DK:NP1.FOR
RK1:NP2.FOR to DK:NP2.FOR
RK1:NP3.FOR to DK:NP3.FOR
RK1:NROOMS.FOR to DK:NROOMS.FOR
RK1:ROOMS.FOR to DK:ROOMS.FOR
RK1:RTTIM.FOR to DK:RTTIM.FOR
RK1:SOBJS.FOR to DK:SOBJS.FOR
RK1:VILLNS.FOR to DK:VILLNS.FOR
RK1:VMSTIM.FOR to DK:VMSTIM.FOR
RK1:D.ODL to DK:D.ODL
RK1:DTEXT.DAT to DK:DTEXT.DAT
RK1:RSTSCB.CTL to DK:RSTSCB.CTL
RK1:RSXBLD.CMD to DK:RSXBLD.CMD
RK1:RSXCMP.CMD to DK:RSXCMP.CMD
RK1:RTBLD.COM to DK:RTBLD.COM
RK1:RTCMP.COM to DK:RTCMP.COM
RK1:VMSBLD.COM to DK:VMSBLD.COM
RK1:VMSCMP.COM to DK:VMSCMP.COM
</pre>
Then we need to make some space…
<pre>
.DELETE *.DAT
Files deleted:
DK:DINDX.DAT ? Y
DK:DTEXT.DAT ? Y
</pre>
Now we can compile the fortran
<pre>
.@RTCMP

.COM/NOLINE DMAIN.FTN,DGAME.FTN,DSUB.FTN
DUNGEO
GAME
XENDMV
XVEHIC
RSPEAK
RSPSUB
RSPSB2
OBJACT
BUG
NEWSTA
QHERE
QEMPTY
JIGSUP
?FORTRAN-I-[JIGSUP] Errors: 0, Warnings: 4
OACTOR
PROB
RMDESC
RAPPLI

.COM/NOLINE DINIT.FTN
INIT
PROTCT

.COM/NOLINE NP,NP1,NP2,NP3
RDLINE
PARSE
ORPHAN
LEX
SPARSE
?FORTRAN-I-[SPARSE] Errors: 0, Warnings: 1
GETOBJ
?FORTRAN-I-[GETOBJ] Errors: 0, Warnings: 1
SCHLST
?FORTRAN-I-[SCHLST] Errors: 0, Warnings: 2
THISIT
SYNMCH
UNPACK
SYNEQL
TAKEIT
GWIM

.COM/NOLINE/NOVEC GDT.FTN
GDT

.COM/NOLINE VERBS.FTN,OBJCTS.FTN
VAPPLI
?FORTRAN-I-[VAPPLI] Errors: 0, Warnings: 1
CLOCKD
OAPPLI

.COM/NOLINE SVERBS.FTN,DVERB1.FTN,DVERB2.FTN,ACTORS.FTN,DEMONS.FTN,CLOCKR.FTN
SVERBS
TAKE
DROP
PUT
VALUAC
SAVEGM
RSTRGM
WALK
CXAPPL
AAPPLI
THIEFD
?FORTRAN-I-[THIEFD] Errors: 0, Warnings: 3
FIGHTD
BLOW
SWORDD
?FORTRAN-I-[SWORDD] Errors: 0, Warnings: 1
INFEST
CEVAPP
?FORTRAN-I-[CEVAPP] Errors: 0, Warnings: 4
LITINT

.COM/NOLINE ROOMS.FOR,NROOMS.FOR
RAPPL1
?FORTRAN-I-[RAPPL1] Errors: 0, Warnings: 2
RAPPL2
?FORTRAN-I-[RAPPL2] Errors: 0, Warnings: 1
LOOKTO
EWTELL

.COM/NOLINE SOBJS.FOR,NOBJS.FOR,BALLOP.FOR,LIGHTP.FOR,VILLNS.FOR
SOBJS
?FORTRAN-I-[SOBJS ] Errors: 0, Warnings: 1
NOBJS
?FORTRAN-I-[NOBJS ] Errors: 0, Warnings: 2
MIRPAN
BALLOP
LIGHTP
TROLLP
CYCLOP
THIEFP
?FORTRAN-I-[THIEFP] Errors: 0, Warnings: 2

.COM/NOLINE DSO1.FOR,DSO2.FOR,DSO3.FOR,DSO4.FOR,DSO5.FOR,DSO6.FOR,DSO7.FOR
PRINCR
?FORTRAN-I-[PRINCR] Errors: 0, Warnings: 2
INVENT
?FORTRAN-I-[INVENT] Errors: 0, Warnings: 1
PRINCO
MOVETO
SCORE
SCRUPD
FINDXT
FWIM
YESNO
ROBADV
?FORTRAN-I-[ROBADV] Errors: 0, Warnings: 1
ROBRM
?FORTRAN-I-[ROBRM ] Errors: 0, Warnings: 1
WINNIN
FIGHTS
VILSTR
GTTIME
OPNCLS
LIT
?FORTRAN-I-[LIT ] Errors: 0, Warnings: 1
WEIGHT
?FORTRAN-I-[WEIGHT] Errors: 0, Warnings: 1
GHERE
MRHERE
ENCRYP
CPGOTO
?FORTRAN-I-[CPGOTO] Errors: 0, Warnings: 1
CPINFO

.COM/NOLINE RTTIM.FOR
ITIME

.COM RRND.MAC
ERRORS DETECTED: 0
</pre>
So far so good. Now we can delete the source from our primary disk, take note that we don’t delete the demo program:
<pre>
.DELETE *.FOR
Files deleted:
DK:DEMO.FOR ? N
DK:BALLOP.FOR ? Y
DK:RTTIM.FOR ? Y
DK:VMSTIM.FOR ? Y
DK:DEMOF1.FOR ? Y
DK:DSO3.FOR ? Y
DK:TEST55.FOR ? Y
DK:GETSTR.FOR ? Y
DK:PUTSTR.FOR ? Y
DK:DSO1.FOR ? Y
DK:DSO2.FOR ? Y
DK:DSO4.FOR ? Y
DK:DSO5.FOR ? Y
DK:DSO6.FOR ? Y
DK:DSO7.FOR ? Y
DK:LIGHTP.FOR ? Y
DK:NOBJS.FOR ? Y
DK:NP.FOR ? Y
DK:NP1.FOR ? Y
DK:NP2.FOR ? Y
DK:NP3.FOR ? Y
DK:NROOMS.FOR ? Y
DK:ROOMS.FOR ? Y
DK:SOBJS.FOR ? Y
DK:VILLNS.FOR ? Y
</pre>
Next we need to remove the ftn files:
<pre>
.DEL *.FTN
Files deleted:
DK:ACTORS.FTN ? Y
DK:CLOCKR.FTN ? Y
DK:DEMONS.FTN ? Y
DK:DGAME.FTN ? Y
DK:DINIT.FTN ? Y
DK:DMAIN.FTN ? Y
DK:DSUB.FTN ? Y
DK:DVERB1.FTN ? Y
DK:DVERB2.FTN ? Y
DK:GDT.FTN ? Y
DK:OBJCTS.FTN ? Y
DK:SVERBS.FTN ? Y
DK:VERBS.FTN ? Y
</pre>
Now we are going to link our executable dungeo.sav . However the default link procedures will not work for us, it’s just easier to paste this entire thing into the console.
<pre>
.LINK/INCLU/PRO/MAP:NL:/BOT:1200/EXE:DUNGEO DMAIN,DGAME,DSUB,RRND,RTTIM
*DINIT,GDT/O:1
*NP,NP1,NP2,NP3/O:1
*VERBS,OBJCTS/O:1
*SVERBS/O:2
*DVERB1/O:2
*DVERB2/O:2
*ACTORS/O:2
*DEMONS/O:2
*CLOCKR/O:2
*ROOMS/O:3
*NROOMS/O:3
*SOBJS/O:3
*NOBJS/O:3
*BALLOP,LIGHTP,VILLNS/O:3
*DSO1/O:4
*DSO2/O:4
*DSO3/O:4
*DSO4/O:4
*DSO5/O:4
*DSO6/O:4
*DSO7/O:4
*SY:FORLIB//
Library search? $SHORT
Library search?
</pre>
Now we don’t need the object files anymore they can be deleted. However we are NOT going to delete the system objects so this isn’t a wholesale deletion.
<pre>
.DEL *.OBJ
Files deleted:
DK:SYSLIB.OBJ ? N
DK:ODT.OBJ ? N
DK:VDT.OBJ ? N
DK:VTHDLR.OBJ ? N
DK:PLOT55.OBJ ? N
DK:DEFLTS.OBJ ? N
DK:FORLIB.OBJ ? N
DK:DEMO.OBJ ? Y
DK:DMAIN.OBJ ? Y
DK:DGAME.OBJ ? Y
DK:DSUB.OBJ ? Y
DK:DINIT.OBJ ? Y
DK:NP.OBJ ? Y
DK:NP1.OBJ ? Y
DK:NP2.OBJ ? Y
DK:NP3.OBJ ? Y
DK:GDT.OBJ ? Y
DK:VERBS.OBJ ? Y
DK:OBJCTS.OBJ ? Y
DK:SVERBS.OBJ ? Y
DK:DVERB1.OBJ ? Y
DK:DVERB2.OBJ ? Y
DK:ACTORS.OBJ ? Y
DK:DEMONS.OBJ ? Y
DK:CLOCKR.OBJ ? Y
DK:ROOMS.OBJ ? Y
DK:NROOMS.OBJ ? Y
DK:SOBJS.OBJ ? Y
DK:NOBJS.OBJ ? Y
DK:BALLOP.OBJ ? Y
DK:LIGHTP.OBJ ? Y
DK:VILLNS.OBJ ? Y
DK:DSO1.OBJ ? Y
DK:DSO2.OBJ ? Y
DK:DSO3.OBJ ? Y
DK:DSO4.OBJ ? Y
DK:DSO5.OBJ ? Y
DK:DSO6.OBJ ? Y
DK:DSO7.OBJ ? Y
DK:RTTIM.OBJ ? Y
DK:RRND.OBJ ? Y
</pre>
Now with enough disk space free’d we can copy back the database files needed
<pre>
.COPY RK1:*.DAT *.*
Files copied:
RK1:DINDX.DAT to DK:DINDX.DAT
RK1:DTEXT.DAT to DK:DTEXT.DAT
</pre>
And now we can run dungeon!
<pre>
.R DUNGEO
Welcome to Dungeon. This version created 18-JUL-80.
You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
>HISTORY
Revision history:

18-JUL-80 Transportable data base file (V2.5A).
28-FEB-80 Compressed text file (V2.4A).
15-NOV-79 Bug fixes (V2.3A).
18-JAN-79 Revised DECUS version (V2.2A).
10-OCT-78 Puzzle Room (V2.1A).
10-SEP-78 Endgame (V2.0A).
10-AUG-78 DECUS version (V1.1B).
14-JUN-78 Public version with parser (V1.1A).
4-MAR-78 Debugging version (V1.0A).
>QUIT
Your score would be 0 [total of 585 points], in 2 moves.
This gives you the rank of Beginner.
Do you wish to leave the game?
Y

.
</pre>
You can always hit control+e to exit SIMH.

Well there you have it, the Fortran installation, compilation, linking & execution of the oldest source version I can find at the moment of Dungeon/Zork. Who knows, maybe someday this may help someone revive other old programs.

[[Category:Tutorials]]

RC25 disk drive

2023-11-20T08:41:39Z

Flx: typo - 52MB = 26MB per platter x2

{{Infobox Disk drive
| name = RC25
| manufacturer = [[Digital Equipment Corporation|DEC]]

| controller = [[KLESI Low-End Storage Interconnect‎]]
| capacity = 26 Mbytes (fixed) 26 Mbytes (removeable)
| transfer rate = 1.25 Mbytes/sec

| average access time = 30.5-45.5 msec

| rpm = 2850
| revolution time = 10.5 msec

| average seek = 20-35 msec
| maximum seek = 55 msec
| media = 1 fixed 1 removeable
| surfaces = 4 (2 fixed, 2 removeable)
| number of heads = 4
| tracks = 821
| sectors = 31
| bytes per sector = 512
| tracks per inch = 1,000
| density = 12,350 bits/inch

| start time = 60 secs (max)
| stop time = 30 secs (max)
| physical size = 10.4" x 19.9" x 22.1"
| weight = 65 lbs (single drive)
| power consumption = 300 watts (idle)
}}

The '''RC25 disk drive''' was a combination [[non-removable-media disk]] and [[removable-pack disk]] (using a sealed [[pack]]) on a singled [[spindle]], from [[Digital Equipment Corporation|DEC]]. Each 8" [[platter]] had a capacity of 26 MB, for a total of 52 MB. It connected to the [[device controller]] via the DEC standard [[Low End System Interconnect]] [[bus]]; a second 'slave' drive can be connected to the first 'master' drive. It uses the [[Mass Storage Control Protocol]], and is member of the [[Digital Storage Architecture]].

{{semi-stub}}

==External links==

* [http://bitsavers.org/pdf/dec/disc/rc25/ rc25] - documentation at [[Bitsavers]]
* [http://bitsavers.org/pdf/dec/brochures/DEC-RS25-DiskSubsystem.pdf RC25 Disk Subsystem]
* [https://manx-docs.org/collections/antonio/dec/ek-0rc25-ps-002.pdf RC25 Disk Subsystem Pocket Service Guide] (EK-0RC25-PS-002)

[[Category: DEC Non-removable-media Disks]]
[[Category: DEC Removable-pack Disks]]
[[Category: LESI Disk Drives]]

Random Access Memory

2023-11-20T08:38:25Z

Flx: reference SRAM when comparing DRAM

'''Random Access Memory''' (often given as '''RAM''') is slang term for a computer's [[main memory]]. RAM is almost always implemented with [[Dynamic RAM]] now, instead of [[Static RAM]], for cost-savings; it can be written and read at will.

Many people confuse this with [[disk]] [[secondary memory]] (although technically disks are also [[random access]] - unlike, say, tape [[secondary storage]]).

{{semi-stub}}

[[Category: Computer Basics]]

Gcc

2023-11-20T06:54:32Z

Flx: spelling & punctuation

'''GCC''' is the [[GNU]] compiler collection. It includes the following languages:

*C
*C++
*Objective C
*Java
*Fortran 77

Depending on the release version, it will include more languages....

GCC can target to [[binutils]] [[assembler]]/[[linker]], along with other vendor provided assember linkers.

GCC has gone thru several notable versions:

== 1.x ==

The 1.x versions of GCC don't have full ./configure scripts, but instead require you to move files around and build. It's not an ANSI C compiler, but it's moving towards ANSI C, and away from K&R type conventions, however it can compile K&R code. I've had a few 'issues' where some things crash when built with gcc 1.x on the VAX while the default compiler (PCC) will build them. Unless you are using [[4.2 BSD]], I'd avoid the the 1.x GCC chain.

I think the primary platforms were 68000 SUN workstations (SunOS 2-4) and the VAX running BSD.

An interesting gcc 1.x distribution was [[Xmgcc]].

The first Linux versions (from 0.01) used GCC 1.40, ported by Linus to Minix (as a cross-compiler). Then shortly later he ported it to run natively on Linux itself, where it was of course used to build the kernel and all the tools. GCC 1.42, in particular, followed Linux for quite a while before finally moving to GCC 2.x

== 2.x ==

While 2.x versions of GCC were very stable (2.5.8 and beyond) the project started to stagnate, and it lead to the EGCS project just after the 2.7 releases of GCC. The EGCS work was rolled back in for a 2.95 release of GCC, then going forward for 3.0 once it had stabilized. 2.x also added C++ & Objective C support.

== 3.x ==

== 4.x ==

GCC 4.0 is retargeting to support the [[llvm]] project to allow for better optimizations.

{{semi-stub}}

[[Category: GNU Software]]
[[Category: C Compilers]]

SunOS

2023-11-20T06:09:10Z

Flx: sync infobox with Solaris wikilinks

{{wp-orig}}

{{Infobox OS
| name = SunOS
| creator = [[Sun Microsystems]]
| current version = SunOS 4.1.4 (1994)
| year introduced = 1982/1983
| type = [[Multi-tasking]], [[multi-user]] [[UNIX]]
| architecture = [[Sun-1]], [[Sun-2]], [[Sun-3]], [[Sun-4]] ([[SPARC]])
}}

== Introduction ==

SunOS is, in a sense, the predecessor to [[Solaris]], Sun's current operating system, and was the first Unix system used by many. Unlike Solaris, which is based primarily upon [[System V]], SunOS is based extensively on [[BSD]], and by the 4.x releases, being based heavily on 4.3 BSD. For this reason, SunOS 4.x maintained some extremely loyal users into the 21st century, long after Sun had moved their entire base to Solaris. Sun finally discontinued support for SunOS in 2003.

==History==
{| class="wikitable"
! '''SunOS version'''
! '''Release date'''
! '''[[Code base]]'''
! Description
|-
|'''Sun UNIX 0.7'''
|1982
|UniSoft [[Version 7 Unix|UNIX v7]]
|Bundled with [[Motorola 68000|68000]]-based Sun-1 system
|-
|'''SunOS 1.0'''
|1983
| rowspan = "5" |4.1BSD
|Support for [[Motorola 68010|68010]]-based Sun-1 and [[Sun-2]] systems
|-
|'''SunOS 1.1'''
|Apr 1984
|
|-
|'''SunOS 1.2'''
|Jan 1985
|Support for Sun 2/50
|-
|'''SunOS 1.3'''
|
|Support for Sun 2/160
|-
|'''SunOS 1.4'''
|Mar 1985
|
|-
|'''SunOS 2.0'''
|May 1985
|4.2BSD
|Introduced VFS layer and the NFS protocol
|-
|'''SunOS 3.0'''
|Feb 1986
|4.2BSD + [[System V]] IPC
| coincided with release of [[Motorola 68020|68020]]-based [[Sun-3]] series. Optional System V tape offered utilities and development libraries.
|-
|'''SunOS 3.2'''
|Sep 1986
| rowspan = "3" | Same as 3.0, plus some 4.3BSD
|First support for [[Sun-4]] series
|-
|'''SunOS 3.4'''
|May 1987
|Support for Sun 3/60
|-
|'''SunOS 3.5'''
|Jan 1988
|
|-
|'''SunOS 4.0'''
|Dec 1988
| rowspan = "17" | 4.3BSD with System V IPC
| New virtual memory system, dynamic linking, automounter, System V STREAMS I/O. Sun386i support.
|-
|'''SunOS 4.0.1'''
|1988
|
|-
|'''SunOS 4.0.2'''
|Sep 1989
|Sun386i only
|-
|'''SunOS 4.0.3'''
|May 1989
|Support for Sun 3/80, 3/470, 3/480 (sun3x)
|-
|'''SunOS 4.0.3c'''
|Jun 1989
|[[SPARCstation 1]] (Sun-4c) only
|-
|'''SunOS 4.1'''
|Mar 1990
|Support for [[Sun-2]] systems dropped
|-
|'''SunOS 4.1e'''
|Apr 1991
|Sun-4e only
|-
|'''SunOS 4.1.1'''
|Mar 1990
|Bundled with [[OpenWindows]] 2.0
|-
|'''SunOS 4.1.1B'''
|Feb 1991
|
|-
|'''SunOS 4.1.1.1'''
|Jul 1991
|
|-
|'''SunOS 4.1.1_U1'''
|Nov 1991
|Sun-3/3x only
|-
|'''SunOS 4.1.2'''
|Dec 1991
|Support for multiprocessor (SPARCserver 600MP) systems; first CD-ROM-only release
|-
|'''SunOS 4.1.3'''
|Aug 1992
|
|-
|'''SunOS 4.1.3C'''
|Nov 1993
|SPARCclassic/SPARCstation LX only
|-
|'''SunOS 4.1.3_U1'''
|Dec 1993
|
|-
|'''SunOS 4.1.3_U1B'''
|Feb 1994
|Earliest release for which [[Y2K]] compliance patches were available
|-
|'''SunOS 4.1.4'''
|Nov 1994
|Last release of SunOS 4
|}

== Availability ==

SunOS was apparently redistributable by users when it was released, as Sun was more interested in selling their hardware, with their software as a tack-on service. As Solaris is still freely available, it is presumable SunOS tape images are acceptable for redistribution. They can be run on [[The Machine Emulator]], apparently.

* SunOS 2.x to 4.x for [[Sun-2]] - https://web.archive.org/web/20060709183240/http://www.soupwizard.com:80/sun2/sunos/
* SunOS 4.x for [[Sun-3]] - http://www.sun3arc.org/

{{Nav Unix}}

[[Category: Unix-based OS's]]

RF35

2023-11-20T06:05:59Z

Flx: expand page based on DEC docs EK-RF72D-UG-007

{{Infobox Disk drive
| name = RF35
| manufacturer = [[Digital Equipment Corporation]]
| controller = all [[Digital Storage Systems Interconnect#Family of DSSI Products|DSSI Controllers]]
| capacity = 852 Mbytes (formatted)
| transfer rate = 4.0 Mbytes/sec
| average access time = 15.1 msec
| average seek = 9.5 msec
| start time = < 30 sec
| stop time = < 15 sec
| physical size = 3.5" half height
}}

The RF35 is a [[Digital Storage Systems Interconnect|DSSI]] hard drive produced by Digital Equipment Corporation from about 1991. This is called an Integrated Storage Element (ISE), which combines the Head-disk assemblies (HDA) and a controller with [[Mass Storage Control Protocol|MSCP]] server. The MSCP server allows the disk to queue I/O requests from multiple hosts at a time. One of the use cases for this feature is to provide storage to a [[VAXcluster]] made of small systems like the MicroVAX.

The drive uses a 50-pin DSSI interface and a 5-pin Molex power connector, providing access to 852 MB of storage. There are 7 platters, each with 2 heads, for a total of 14 data surfaces and ~60MB per surface. The disk geometry is 14 tracks, 2,086 cylinders, 58 sectors per track (including 1 replacement sector).

The disk controller contains a [[Motorola M68000 Family|MC680x0]] microprocessor, RAM, and NVRAM. A number of diagnostic and utility programs are available to the controller. At startup, there is a POST test and diagnostics continue executing periodically while the disk runs. In addition to error codes visible via the diagnostic programs, the disk has an amber-colored Fault LED.

The [[RF31T]] is a lower-capacity version of the RF35, but with an improved seek rate.

{{stub}}

==External Links==
* [https://manx-docs.org/collections/antonio/dec/rf72dug7.pdf RF Series Integrated Storage Element User Guide] (EK-RF72D-UG-007)
* [https://decdoc.itsx.net/dec94mds/rf72dug8.pdf RF Series Integrated Storage Element User Guide] (EK-RF72D-UG-008)
* [https://www.computerhistory.org/collections/catalog/102768242 RF35 in the collection of the Computer History Museum]

[[Category: DSSI Disk Drives]]
[[Category: DEC Non-removable-media Disks]]

User:Flx

2023-11-20T00:39:48Z

Flx: create user info page

== About ==

I am a Linux user since ~2003, and SPARC user since I bought my first Sun server (for no reason in particular). There is something interesting about "odd" architectures and front panel switches, before everything came to x86.

Experience:
* (work) IT automation: Terraform, Ansible, Jenkins/GitHub, BladeLogic, AWS
* (work) Containerization: Kubernetes, OpenShift, Podman/Buildah, Docker
* (work) Compute, Storage, and Network: Proxmox, ESXi, TrueNAS, ZFS, Cisco, Mikrotik
* (work) Database: Oracle DB, Wallets, and some PL/SQL
* (home) Hosting: k3s, Postgres, MySQL, apache, nginx, bind9
* (volunteer) repair & troubleshoot museum exhibits, ex: Altair 8800, IMSAI 8080, Toshiba T1100+, PDP-9

== Collection ==

* Sun Netra T1 AC200
* Sun Fire 280R (gone)
* Sun Netra X1 (gone?)
* Sun Fire v100
* Sun Fire X4100 M2
* Sun Ray 2
* Intersil 6100
* PiDP-8 (replica)
* PiDP-11 (replica)
* KENBAK-1 (replica)
* several ThinkPads & ThinkCentre USFF PCs
* several Ryzen workstations
* more Raspberry Pi than I can count