Computer History Wiki - User contributions [en]

UNIX Fourth Edition

2025-11-11T06:25:47Z

ForOldHack: /* External links */ Added news, since this is *news*. Its OMG news! OMG! Sorry, but I am excited. UNIX > XENIX.

{{Infobox OS
| name = Unix V4
| creator = AT&T/[[Western Electric]]
| year introduced = November, 1973
| previous version = [[UNIX Third Edition|V3]]
| current version = V4
| next version = [[UNIX Fifth Edition|V5]]
| type = [[Multi-tasking]], [[multi-user]]
| architecture = [[PDP-11 architecture|PDP-11]]
}}

'''UNIX Fourth Edition''' (often referred to as '''UNIX V4''' or '''V4 UNIX''' - 'Unix' was still normally given in all capital letters at this point in time) was an important early version of [[UNIX]]. It was the first version in which the [[kernel]] was written in [[C programming language|C]]. It also had minor changes to the [[UNIX file system‎]] (such as the ability of any [[inode]] to hold a [[peripheral|device]] 'special file'), which left it in the form it retained until the [[BSD Fast File System]].

Apparently, the only model of PDP-11 supported was the [[PDP-11/45]].

A complete copy of Fourth Edition does not seem to be extant. [[The Unix Heritage Society|TUHS]] has a copy of the 'UNIX Programmer's Manual' and the [[source]] for what would become the V4 kernel. The main differences in this 'nsys' kernel compared to the later V4 kernel are the earlier V3 way of registering signal handlers, and a few not yet implemented system calls. Most importantly [[pipe]]s had not yet been implemented, making this kernel not fully functional even on a V3 system.

==Possible Source(s)==

"A tape-based piece of unique Unix history may have been lying quietly in storage at the University of Utah for 50+ years. The question is whether researchers will be able to take this piece of middle-aged media and rewind it back to the 1970s to get the data off."

* [https://www.theregister.com/2025/11/07/unix_fourth_edition_tape_rediscovered/ UNIX fourth edition tape rediscovered]

"– The 4th Edition (November 1973 — Research-V4) contains only source markup
for the manual pages: 18975 lines of troff code."

Research UNIX v4, dated to 1973:
https://www.spinellis.gr/pubs/jrnl/2016-EMPSE-unix-history/html/unix-history.pdf

==External links==

* [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4 V4]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys nsys] - complete kernel source
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/11-45 11-45] - possibly physical layout of the UNIX group's PDP-11/45
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/low.s low.s] - possibly configuration of the UNIX group's PDP-11/45
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man0/intro UNIX Programmer's Manual Fourth Edition - Introduction]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man5/fs.5 File system]
* [http://squoze.net/UNIX/v4man/ UNIX Programmer's Manual: Fourth Edition]

====News====

* [https://news.ycombinator.com/item?id=45840321 Ycombinator]
* [https://discuss.systems/@ricci/115504720054699983 Discuss.systems]
** "We have arranged to deliver it to the Computer History Museum."
<blockquote>I have the equipment. It is a 3M tape so it will probably be fine.
It will be digitized on my analog recovery set up and I'll use Len Shustek's readtape program to recover the data.
The only issue right now is my workflow isn't a "while you wait" thing, so I need to pull all the pieces into one physical location and test everything before I tell Penny it's OK to come out.

The whole process is test the condition on a tape retensioner. I'm hoping I don't have to bake it, since that takes a day, then digitize it, shuttle the 10s of gigabytes of samples to another machine to decode it. I want to skip the shuttle step and get the analyzer running on the digitizer. -bitsavers.org</blockquote>

{{Nav Unix}}

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

KDJ11-B CPU

2025-11-11T00:05:46Z

ForOldHack: /* Cache Problems */ disable cache

[[Image:m8190.jpg|200px|thumb|right|M8190]]

The '''KDJ11-B''' CPU board (M8190) is the second-generation [[QBUS]] [[Central Processing Unit|CPU]] card using the [[J-11 chip set]] of the [[PDP-11]] (the first being the the [[KDJ11-A CPU]]). It is a [[DEC card form factor|quad-height]] board, and is used in the [[PDP-11/83]] and [[PDP-11/84]] systems.

Its principal improvement over the KDJ11-A is its support of the [[Private Memory Interconnect]] [[bus]], a high-performance variant of the QBUS; it also supports the [[KTJ11-B UNIBUS adapter]], a QBUS->[[UNIBUS]] adapter used in the PDP-11/84.

It also provides a built-in [[asynchronous serial line|serial]] console, [[Read-only memory|ROM]]s to contain diagnostic and [[bootstrap]] programs, and an [[EEPROM]] to contain configuration information.

Like the KDJ11-A, the -B also contains an 8K-byte write-through [[cache]] (set size 1, block size 1 16-bit [[word]]), protected by [[parity]]. The KDJ11-B additionally provides two sets of tag fields for each cache entry, so that the CPU and [[Direct Memory Access|DMA]] from the QBUS can interact with the cache simultaneously. Cache control logic inspects DMA transfers and invalidates cache entries for memory words which are written to by a device.

Also like the KDJ11-A, it can also use the [[FPJ11 floating point accelerator]] [[integrated circuit|chip]] to speed up the [[FP11 floating point|FP11]] implementation in the J-11.

As far as is known, the various models of the KDJ11-B differ only in their speed (CPU and [[clock]] [[crystal]]) and whether or not they come with the FPJ11. [[Digital Equipment Corporation|DEC]] documentation refers to certain models being used in certain machines, but as far as is known, in fact any model will work in any machine.

==Cache Problems==

The KDJ11-B cache implementation makes hard-to-diagnose stability problems a possibility. Below are some problems observed in a [https://forum.vcfed.org/index.php?threads/july-2024-ebay-qbus-lot-repair-thread.1249049/ VCFed Forums repair thread from July 2024]:

===Intermittent CPU Stoppage===

During testing of [[Clearpoint QED1]] and [[MSV11-J]] [[PMI]] memories, the system would randomly stop while running '''VMJAB0''', the [[MSV11-J]] exerciser from [[XXDP]]. There was no error printout, no trap messages, no HALT to [[ODT]], and the '''RUN''' lamp was out. The system came up from a restart and reported no errors in its self-tests. '''OKDAG0''', the KDJ11-B cluster diagnostics, reported no errors, even with the switches set to 000300Q for extended cache tag and data RAM tests. After entering field service mode in '''VMJAB0''' and disabling the J-11 cache, '''VMJAB0''' would run without error or stoppage. After an extended run of '''VMJAB0''', the system power-on diagnostics stopped with an error #162, which did not state that it was cache related, but should be -- #62 is a cache error, and for errors greater than 100, one subtracts 100 and uses the resulting number.

This problem was found to be a failing cache SRAM at position E10. The faulty chip was located through process of elimination, and was the fourth chip replaced. All other cache RAMs were OK.

===Consistent Error 62 with Printout===

During burn-in testing of a repaired KDJ11-B from a large lot of scrap [[QBus]] boards, the KDJ11-B began stopping on every reset with a #62 cache error. The error could be bypassed with a '''CTRL+O 4''' bypass. Once bypassed, the system could boot into [[XXDP]], but '''OKDAG0''' KDJ11-B cluster diagnostics reported no problems, even when run with the switches set to 000300Q for extended cache tag and data RAM tests.

This problem was found to be a failing cache SRAM at position E104, which is in the DMA tag RAM array. The faulty chip was located through process of elimination, and was the eleventh chip replaced. All other cache RAMs were OK.

===Consistent Error 62 with Lockup===

During burn-in testing of a repaired KDJ11-B from a large lot of scrap [[QBus]] boards, the KDJ11-B began locking up on every reset with test #62 displayed on the lights. The system locked up hard and could not be HALTed to [[ODT]] without a reboot. No error was printed to the console. The [[EEPROM]] was moved to another KDJ11-B and configured to enter [[ODT]] on power-on, and skip all testing. This allowed booting into [[XXDP]] and running '''OKDAG0''', KDJ11-B cluster diagnostics. With switches set to 000300Q for extended cache tag and data RAM tests, '''OKDAG0''' would stop with the message:

'''ERROR IN RECORDING HITS THROUGH HITS/MISS REGISTER'''

Error printout indicated that the hit/miss shift register was not recording any hits, and remaining 000000Q regardless of the hit pattern attempting to be written to it.

The hit/miss register is implemented in the J-11 processor itself, but is fed signals from the DC350 gate array, which contains the cache control registers. These signals are combined through a 74S260 dual 5-input NOR gate at E22. The 74S260 had failed, and resolved the error upon replacement.

===Bus Errors===

There is a jumper that will disable the cache, for testing. its labeled W20.

==DC350 Gate Array Incompatibilities==

During the diagnosis of a cache problem in this [https://forum.vcfed.org/index.php?threads/july-2024-ebay-qbus-lot-repair-thread.1249049/ VCFed Forums repair thread from July 2024], it was discovered that DC350 gate arrays may not be interchangeable between board revisions. A LSI gold lid gate array from an early KDJ11-B with green top-side ECO was replaced with a silver lid gate array made in Japan from a later revision KDJ11-B. This resulted in a "mostly working" KDJ11-B, but '''OKDAG0''' cluster diagnostics would randomly stop to [[ODT]] or loop endlessly without printout of pass completion or errors, and never prompted for user input for the KDJ11-B lamp register test. It is assumed that the DC350 revision was incompatible with the board revision.

==See also==

* [[KDJ11 PMI/UNIBUS backplane]]
* [[KDJ11-D CPU]]

==External links==

* [http://www.bitsavers.org/pdf/dec/pdp11/1173/EK-KDJ1B-UG_KDJ11-B_Nov86.pdf KDJ11-B CPU Module User's Guide] (EK-KDJ1B-UG-001)
* [http://www.bitsavers.org/pdf/dec/pdp11/1173/EK-247AA-MG-001_KDJ11-B_CPU_System_Maintenance_Nov88.pdf KDJ11-B CPU System Maintenance] (EK-247AA-MG-001)
* [http://www.bitsavers.org/pdf/dec/pdp11/1173/KDJ11-B_Processor_Spec_Jun1984.pdf KDJ11-B Processor Specification]
* [http://www.bitsavers.org/pdf/dec/pdp11/1184/MP-02015-01_11-84_Maintenance_Print_Set_198412.pdf 11/84 Field Maintenance Print Set (MP-02015-001)] - Contains KDJ11-B Field Maintenance Print Set (MP-01969-01) on pp. 94-126

[[Category: PDP-11 QBUS Processors]]
[[Category: Private Memory Interconnect]]

UNIX Fourth Edition

2025-11-08T02:49:49Z

ForOldHack: /* Reverted mistake */

{{Infobox OS
| name = Unix V4
| creator = AT&T/[[Western Electric]]
| year introduced = November, 1973
| previous version = [[UNIX Third Edition|V3]]
| current version = V4
| next version = [[UNIX Fifth Edition|V5]]
| type = [[Multi-tasking]], [[multi-user]]
| architecture = [[PDP-11 architecture|PDP-11]]
}}

'''UNIX Fourth Edition''' (often referred to as '''UNIX V4''' or '''V4 UNIX''' - 'Unix' was still normally given in all capital letters at this point in time) was an important early version of [[UNIX]]. It was the first version in which the [[kernel]] was written in [[C programming language|C]]. It also had minor changes to the [[UNIX file system‎]] (such as the ability of any [[inode]] to hold a [[peripheral|device]] 'special file'), which left it in the form it retained until the [[BSD Fast File System]].

Apparently, the only model of PDP-11 supported was the [[PDP-11/45]].

A complete copy of Fourth Edition does not seem to be extant. [[The Unix Heritage Society|TUHS]] has a copy of the 'UNIX Programmer's Manual' and the [[source]] for what would become the V4 kernel. The main differences in this 'nsys' kernel compared to the later V4 kernel are the earlier V3 way of registering signal handlers, and a few not yet implemented system calls. Most importantly [[pipe]]s had not yet been implemented, making this kernel not fully functional even on a V3 system.

==Possible Source(s)==

"A tape-based piece of unique Unix history may have been lying quietly in storage at the University of Utah for 50+ years. The question is whether researchers will be able to take this piece of middle-aged media and rewind it back to the 1970s to get the data off."

* [https://www.theregister.com/2025/11/07/unix_fourth_edition_tape_rediscovered/ UNIX fourth edition tape rediscovered]

"– The 4th Edition (November 1973 — Research-V4) contains only source markup
for the manual pages: 18975 lines of troff code."

Research UNIX v4, dated to 1973:
https://www.spinellis.gr/pubs/jrnl/2016-EMPSE-unix-history/html/unix-history.pdf

==External links==

* [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4 V4]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys nsys] - complete kernel source
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/11-45 11-45] - possibly physical layout of the UNIX group's PDP-11/45
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/low.s low.s] - possibly configuration of the UNIX group's PDP-11/45
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man0/intro UNIX Programmer's Manual Fourth Edition - Introduction]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man5/fs.5 File system]
* [http://squoze.net/UNIX/v4man/ UNIX Programmer's Manual: Fourth Edition]

{{Nav Unix}}

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

UNIX Fourth Edition

2025-11-08T02:47:17Z

ForOldHack: /* Possible alternative hardware for UNIX v4 from

{{Infobox OS
| name = Unix V4
| creator = AT&T/[[Western Electric]]
| year introduced = November, 1973
| previous version = [[UNIX Third Edition|V3]]
| current version = V4
| next version = [[UNIX Fifth Edition|V5]]
| type = [[Multi-tasking]], [[multi-user]]
| architecture = [[PDP-11 architecture|PDP-11]]
}}

'''UNIX Fourth Edition''' (often referred to as '''UNIX V4''' or '''V4 UNIX''' - 'Unix' was still normally given in all capital letters at this point in time) was an important early version of [[UNIX]]. It was the first version in which the [[kernel]] was written in [[C programming language|C]]. It also had minor changes to the [[UNIX file system‎]] (such as the ability of any [[inode]] to hold a [[peripheral|device]] 'special file'), which left it in the form it retained until the [[BSD Fast File System]].

Apparently, the only model of PDP-11 supported was the [[PDP-11/45]].

"Amoug the new *goodies* are:
1) Separate I and D space for the resident monitor on 11/45s and 11/70s/"

https://www.spinellis.gr/pubs/jrnl/2016-EMPSE-unix-history/html/unix-history.pdf

A complete copy of Fourth Edition does not seem to be extant. [[The Unix Heritage Society|TUHS]] has a copy of the 'UNIX Programmer's Manual' and the [[source]] for what would become the V4 kernel. The main differences in this 'nsys' kernel compared to the later V4 kernel are the earlier V3 way of registering signal handlers, and a few not yet implemented system calls. Most importantly [[pipe]]s had not yet been implemented, making this kernel not fully functional even on a V3 system.

==Possible Source(s)==

"A tape-based piece of unique Unix history may have been lying quietly in storage at the University of Utah for 50+ years. The question is whether researchers will be able to take this piece of middle-aged media and rewind it back to the 1970s to get the data off."

* [https://www.theregister.com/2025/11/07/unix_fourth_edition_tape_rediscovered/ UNIX fourth edition tape rediscovered]

"– The 4th Edition (November 1973 — Research-V4) contains only source markup
for the manual pages: 18975 lines of troff code."

Research UNIX v4, dated to 1973:
https://www.spinellis.gr/pubs/jrnl/2016-EMPSE-unix-history/html/unix-history.pdf

==External links==

* [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4 V4]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys nsys] - complete kernel source
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/11-45 11-45] - possibly physical layout of the UNIX group's PDP-11/45
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/low.s low.s] - possibly configuration of the UNIX group's PDP-11/45
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man0/intro UNIX Programmer's Manual Fourth Edition - Introduction]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man5/fs.5 File system]
* [http://squoze.net/UNIX/v4man/ UNIX Programmer's Manual: Fourth Edition]

{{Nav Unix}}

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

UNIX Fourth Edition

2025-11-08T02:39:41Z

ForOldHack: /* Possible source tape discovered */

{{Infobox OS
| name = Unix V4
| creator = AT&T/[[Western Electric]]
| year introduced = November, 1973
| previous version = [[UNIX Third Edition|V3]]
| current version = V4
| next version = [[UNIX Fifth Edition|V5]]
| type = [[Multi-tasking]], [[multi-user]]
| architecture = [[PDP-11 architecture|PDP-11]]
}}

'''UNIX Fourth Edition''' (often referred to as '''UNIX V4''' or '''V4 UNIX''' - 'Unix' was still normally given in all capital letters at this point in time) was an important early version of [[UNIX]]. It was the first version in which the [[kernel]] was written in [[C programming language|C]]. It also had minor changes to the [[UNIX file system‎]] (such as the ability of any [[inode]] to hold a [[peripheral|device]] 'special file'), which left it in the form it retained until the [[BSD Fast File System]].

Apparently, the only model of PDP-11 supported was the [[PDP-11/45]].

A complete copy of Fourth Edition does not seem to be extant. [[The Unix Heritage Society|TUHS]] has a copy of the 'UNIX Programmer's Manual' and the [[source]] for what would become the V4 kernel. The main differences in this 'nsys' kernel compared to the later V4 kernel are the earlier V3 way of registering signal handlers, and a few not yet implemented system calls. Most importantly [[pipe]]s had not yet been implemented, making this kernel not fully functional even on a V3 system.

==Possible Source(s)==

"A tape-based piece of unique Unix history may have been lying quietly in storage at the University of Utah for 50+ years. The question is whether researchers will be able to take this piece of middle-aged media and rewind it back to the 1970s to get the data off."

* [https://www.theregister.com/2025/11/07/unix_fourth_edition_tape_rediscovered/ UNIX fourth edition tape rediscovered]

"– The 4th Edition (November 1973 — Research-V4) contains only source markup
for the manual pages: 18975 lines of troff code."

Research UNIX v4, dated to 1973:
https://www.spinellis.gr/pubs/jrnl/2016-EMPSE-unix-history/html/unix-history.pdf

==External links==

* [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4 V4]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys nsys] - complete kernel source
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/11-45 11-45] - possibly physical layout of the UNIX group's PDP-11/45
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/low.s low.s] - possibly configuration of the UNIX group's PDP-11/45
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man0/intro UNIX Programmer's Manual Fourth Edition - Introduction]
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man5/fs.5 File system]
* [http://squoze.net/UNIX/v4man/ UNIX Programmer's Manual: Fourth Edition]

{{Nav Unix}}

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

Professional 300 Series

2025-04-21T02:48:07Z

ForOldHack: /* External links */ added some pictures, looking for the graphics card....

The '''Professional 300 Series''' is a family of [[PDP-11]]-based [[personal computer]]s from [[Digital Equipment Corporation|DEC]].

The major difference to the 'real' PDP-11s is that a [[motherboard]] is used, instead of a [[backplane]]. The second difference is that a [[bit-mapped display]] is provided, instead of an [[ASCII]] [[video terminal]]. The third difference is the use of the [[CTI BUS]] (Computing Terminal Interconnect) bus, which is used solely on the PRO series.

The Professional came in three versions:

* Professional 325
* Professional 350
* Professional 380

The common system components are:

* [[VR201]] Video Monitor (standard)
* [[LK201]] Keyboard
* [[P/OS]] Professional 300 Operating System Software
* [[P/OS Software]]

== ZIF Connectors ==

The Professional 300 Series computer uses Zero insertion force (ZIF) connectors for its CTI modules.

Insertion:

* Hold the module by the zero insertion force (ZIF) connector and pull the handle out turning it 90° clockwise.
* Slide the module into the slot in the card cage. Turn the handle straight up and push it in toward the module.

Removal:

* Turn the handle 90° clockwise and pull it out.
* Carefully pull the module out of the card cage.

== Professional 325 / Professional 350 ==

The Professional 325 and the Professional 350 personal computers came out in 1982.

Both use the [[RX50]] dual floppy drive and the [[PDP-11/23]] chip set ([[F-11]]).
They are equipped with 512 KB memory and a bit-mapped video controller (960 x 240 pixels)

=== Professional 325 ===

The Professional 325 is the base model with only little expansion capabilities:

* You can only upgrade to a fixed disk by upgrading to a Professional 350, i.e. by installing a Professional 350 system board
* There is only one free slot for an CTI expansion module.

[[Image:Professional_325_System_Module_Layout.png|thumb|upright|center|600px|Professional 325 System Module Layout]] 

=== Professional 350 ===

The Professional 350 comes with either an [[RD50]] 5 MB or an [[RD51]] 10 MB fixed disk.

There are four free CTI option slots for expansions.

With the Professional 350, up to one MB of memory can be added in increments of 256 KB. Each 256 KB memory option occupies one option slot.

It can be upgraded with the VC241-A Extended Bit-map Option (EBO), which adds two bit-map planes to the standard video generator for a total of three planes. Each plane supports a display of 960 x 240 pixels. In addition, the extended bit-map option adds a color output map that can simultaneously display on a color monitor eight colors from a palette of 256 colors. It displays eight of a possible 16 shades of gray on the monochrome monitor.

Note: The extended bit map module supports the 13-inch color monitor ([[VR241]]).

[[Image:Professional_350_System_Module_Layout.png|thumb|upright|center|600px|Professional 350 System Module Layout]] 

== Professional 380 ==

[[Image:Professional_380_System_Module_Layout.png|thumb|upright|center|600px|Professional 380 System Module Layout]] 

The model 380 was introduced in 1985, the main change was the [[PDP-11/73]] chip set ([[J11]]) and a completely new mainboard.

=== Overview OF PRO 380 Differences from PRO 325/350 ===

The Professional 380 is the newest member of the PRO 300 series.
It differs from the Professional 350 in several ways.
One of the most important of these is that it uses the more powerful J-11 processor chipset instead of the F-11 processor chipset.
It also has increased graphics functionality in that it supports a new high resolution mode, and it offers a palette of 4,096 colors to choose from instead of the 256 available in the 350.
The hardware layout is somewhat different: the first 512KB of memory resides on the system module, the base video subsystem is also on the system module, and the Extended Bitmap Option is a daughtercard on the system module. This means that there are additional slots available in the cardcage for options. P/OS V2.0A or higher is required for PRO 380 support.

== PRO Operating Systems ==

* [[P/OS]]
* [[CP/M]]
* [[PRO/VENIX]]
* [[RT-11]]
* [[UCSD p-System]]
* [[CTS-300]]
* [[Xenix]]
* [[Idris]]
* [[2.9BSD]]
* [[MUMPS]]

==External links==

* [https://bitsavers.org/pdf/dec/pdp11/pro3xx/ PRO3xx] - documentation at [[Bitsavers]]
** [https://bitsavers.org/pdf/dec/pdp11/pro3xx/Professional_Series_Handbook_1985.pdf Professional Series Handbook]
** [https://bitsavers.org/pdf/dec/pdp11/pro3xx/EK-PC300-V1-001_pro300tecV1.pdf Professional 300 Series - Technical Manual: Volume 1]

* [https://oldvcr.blogspot.com/2025/04/lets-give-provenix-barely-adequate-pre.html Getting a TCP stack (slurp-CK) working on a real Dec Peo 380. ] [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:21, 21 April 2025 (CEST)
* [https://oldvcr.blogspot.com/2025/03/more-pro-for-dec-professional-380.html Pictures of inside a DEC Pro 380] [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:47, 21 April 2025 (CEST)

{{PDP-11}}

[[Category: DEC Personal Computers]]
[[Category: PDP-11 Systems]]

Professional 300 Series

2025-04-21T02:22:48Z

ForOldHack: /* External links */ added link to getting slurp-CK working on a real Dec Peo 380.

The '''Professional 300 Series''' is a family of [[PDP-11]]-based [[personal computer]]s from [[Digital Equipment Corporation|DEC]].

The major difference to the 'real' PDP-11s is that a [[motherboard]] is used, instead of a [[backplane]]. The second difference is that a [[bit-mapped display]] is provided, instead of an [[ASCII]] [[video terminal]]. The third difference is the use of the [[CTI BUS]] (Computing Terminal Interconnect) bus, which is used solely on the PRO series.

The Professional came in three versions:

* Professional 325
* Professional 350
* Professional 380

The common system components are:

* [[VR201]] Video Monitor (standard)
* [[LK201]] Keyboard
* [[P/OS]] Professional 300 Operating System Software
* [[P/OS Software]]

== ZIF Connectors ==

The Professional 300 Series computer uses Zero insertion force (ZIF) connectors for its CTI modules.

Insertion:

* Hold the module by the zero insertion force (ZIF) connector and pull the handle out turning it 90° clockwise.
* Slide the module into the slot in the card cage. Turn the handle straight up and push it in toward the module.

Removal:

* Turn the handle 90° clockwise and pull it out.
* Carefully pull the module out of the card cage.

== Professional 325 / Professional 350 ==

The Professional 325 and the Professional 350 personal computers came out in 1982.

Both use the [[RX50]] dual floppy drive and the [[PDP-11/23]] chip set ([[F-11]]).
They are equipped with 512 KB memory and a bit-mapped video controller (960 x 240 pixels)

=== Professional 325 ===

The Professional 325 is the base model with only little expansion capabilities:

* You can only upgrade to a fixed disk by upgrading to a Professional 350, i.e. by installing a Professional 350 system board
* There is only one free slot for an CTI expansion module.

[[Image:Professional_325_System_Module_Layout.png|thumb|upright|center|600px|Professional 325 System Module Layout]] 

=== Professional 350 ===

The Professional 350 comes with either an [[RD50]] 5 MB or an [[RD51]] 10 MB fixed disk.

There are four free CTI option slots for expansions.

With the Professional 350, up to one MB of memory can be added in increments of 256 KB. Each 256 KB memory option occupies one option slot.

It can be upgraded with the VC241-A Extended Bit-map Option (EBO), which adds two bit-map planes to the standard video generator for a total of three planes. Each plane supports a display of 960 x 240 pixels. In addition, the extended bit-map option adds a color output map that can simultaneously display on a color monitor eight colors from a palette of 256 colors. It displays eight of a possible 16 shades of gray on the monochrome monitor.

Note: The extended bit map module supports the 13-inch color monitor ([[VR241]]).

[[Image:Professional_350_System_Module_Layout.png|thumb|upright|center|600px|Professional 350 System Module Layout]] 

== Professional 380 ==

[[Image:Professional_380_System_Module_Layout.png|thumb|upright|center|600px|Professional 380 System Module Layout]] 

The model 380 was introduced in 1985, the main change was the [[PDP-11/73]] chip set ([[J11]]) and a completely new mainboard.

=== Overview OF PRO 380 Differences from PRO 325/350 ===

The Professional 380 is the newest member of the PRO 300 series.
It differs from the Professional 350 in several ways.
One of the most important of these is that it uses the more powerful J-11 processor chipset instead of the F-11 processor chipset.
It also has increased graphics functionality in that it supports a new high resolution mode, and it offers a palette of 4,096 colors to choose from instead of the 256 available in the 350.
The hardware layout is somewhat different: the first 512KB of memory resides on the system module, the base video subsystem is also on the system module, and the Extended Bitmap Option is a daughtercard on the system module. This means that there are additional slots available in the cardcage for options. P/OS V2.0A or higher is required for PRO 380 support.

== PRO Operating Systems ==

* [[P/OS]]
* [[CP/M]]
* [[PRO/VENIX]]
* [[RT-11]]
* [[UCSD p-System]]
* [[CTS-300]]
* [[Xenix]]
* [[Idris]]
* [[2.9BSD]]
* [[MUMPS]]

==External links==

* [https://bitsavers.org/pdf/dec/pdp11/pro3xx/ PRO3xx] - documentation at [[Bitsavers]]
** [https://bitsavers.org/pdf/dec/pdp11/pro3xx/Professional_Series_Handbook_1985.pdf Professional Series Handbook]
** [https://bitsavers.org/pdf/dec/pdp11/pro3xx/EK-PC300-V1-001_pro300tecV1.pdf Professional 300 Series - Technical Manual: Volume 1]

* [https://oldvcr.blogspot.com/2025/04/lets-give-provenix-barely-adequate-pre.html Getting a TCP stack (slurp-CK) working on a real Dec Peo 380. ] [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:21, 21 April 2025 (CEST)

{{PDP-11}}

[[Category: DEC Personal Computers]]
[[Category: PDP-11 Systems]]

User talk:ForOldHack

2025-03-08T00:03:51Z

ForOldHack: /* Note removal */

==Sigs on Talk: pages==

We generally try and follow the Wikipedia style of signing posts on Talk: pages (so that people reading them will know straight off, without having to look in the history, who made comments, and when). There's even special Wiki syntax to do this easily; just add <nowiki>~~~~</nowiki> to the end of your post, and it will be automagically transformed in this sig, with the user and time. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 13:21, 11 March 2019 (CET)

: Hmm, something else is going on. '[[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:41, 12 March 2019 (CET)' gives me date and time, and <nowiki>~~~~</nowiki> gives me 4 tildies.

: Oh, now I understand to escape the wiki process and get tildies, use <nowiki>~~~~</nowiki>, but to get the sig use [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:42, 12 March 2019 (CET)

:: I have not seen such a funny time stamp in 34 years, when we were using uwasa.fi as a mail relay. ( Time is Wasausa, Finland ) [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:45, 12 March 2019 (CET)

: Please don't forget; I can add the sig manually, but it's easier for you. Thanks! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:52, 22 March 2019 (CET)

: A reminder... [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 19:19, 11 January 2024 (CET)

::Thank you, I appreciate it. I thought it was a Bot, but after I saw the change, I started again with the [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 00:09, 12 January 2024 (CET) habit. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 00:09, 12 January 2024 (CET)

== Infobox line captions ==

The captions in info boxes are specified in the template, as are the argument names; trying to change either in the invocation has no effect.

If you want to change the 'Year introduced' caption, I'd be OK with that, but just to 'Introduced' I think might be potentially confusing without something to indicate that it's a temporal meaning - e.g. 'Date introduced', or something. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 12:04, 7 April 2019 (CEST)

:Introduced sounds like marketing speak, I would prefer Release dates, since that would cover both people receiving mag tapes, and downloading comparable source. I got Redhat 5.0 on the day of release, and was able to torrent it, and was able to install it quickly. I went to a user group meeting, and for the cost of $5, got 1) a backup CD, 2) a great Tshirt, 3) a great how-to manual, and 4) some nifty stickers. Needless to say, from that day forward, I saw the lack of value in Microsoft Products. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 11:52, 12 April 2019 (CEST)

:: OK, 'Date released' would work in [[Template:Infobox Software]], [[Template:Infobox OS]], and [[Template:Infobox App]]. I'll go ahead and make that change (although it will only be in the caption, not in the argument name - if I change that, I'd have to change every article that calls those templates).
:: Not sure that to do about [[Template:Infobox Machine]], etc - would 'Date introduced' work there? [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 16:20, 16 April 2019 (CEST)

: Back to the Temporal part, We want a label to indicate its first start of general use, so that a corresponding date tag, could map to what hardware it would run on, i.e. XENIX would have a 1985 release date, and the current hardware was XTs, Turbo XTs, ATs and a few clones,
:Verses ATT SYS V, I guess I see through the eyes of my first C teacher, Barry Kercheval, who liked Sun workstations, because of their OS, and their compiler. The MS-DOS C compilers at the time were hacks, Microsoft C was bad, Aztek C was a bit better, Manx C would make code easy to port from Amiga to PC, and we would get constant diffrences between those and XENIX, and the other boxes we would remote into to look at their compilers. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 11:52, 12 April 2019 (CEST)

:: The way I'd handle OS's where they were released on different dates on different hardware would be to put multiple entries in the 'Date released' box (sort of like the mutiple entries under 'Capacity' [[RL01/02 disk drive|here]]); one line for each type of hardware. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 16:20, 16 April 2019 (CEST)

:For RT-11, A list of boxes that it could run on, and the corresponding CPUs and memory cards that would support it, would be useful. i.e. It would not run on this hardware, but certainly would run on the current hardware of the day. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 11:52, 12 April 2019 (CEST)

== External link syntax ==

We generally like to give the title of our external links, using the syntax <nowiki>'[URL title]'</nowiki>, so instead of:

[http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html]

one sees this:

[http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html Digital Equipment Corporation Indicator Panels]

Much nicer for our readers! The title is formally given inside <title> tags in the HTML of the page, and displayed by the browser (often in the window title bar, but exactly how will depend on the browser and OS).

PS: You shouldn't stick a sig in additions to ''content'' pages (where it intrudes), you only need to do it on Talk: pages. The reasoning (it dates to a very early stage on Wikipedia, before even I started there) seems to be that if one wants to know where something in a content page comes from, one looks at the History of that page; on Talk: pages (especially if one is reading one later - see for example the discussion at [[Help talk:Introduction to Categories]]), one can easily see who posted a given item directly, without needing to grub around in the history. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:25, 7 April 2019 (CEST)

:Very sorry, I had forgot, and even forgot to look it up. I am so amazed by the tiny bits I have found, I only used some of those machines a few times, they were apprently very popular because they were so fantastic.
:Ill follow this convention on. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:57, 8 April 2019 (CET)

Sure. BTW, [https://en.wikipedia.org/wiki/Wikipedia:SIG here] is the Wikipedia sig policy, which we follow (although we don't follow Wikipedia in most things, in this one we do). [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:12, 9 April 2019 (CEST)

:When a user sees this: [[http://mercury.lcs.mit.edu/~jnc/humour/sys286.notes System 286 release notes]] it had me choking with laughter. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 10:59, 12 April 2019 (CET)

:: Actually, I didn't write that - someone else at MIT did (don't recall who). The only humour thing I did was the first "Alice's" hack - Alice's PDP-10, maybe? [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:36, 13 April 2019 (CEST)

Practice makes perfect [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Linking Wikipedia manual of style: Links]

== new user ==

I don't see a new user. You are the newest user since 8 March 2019.
[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 11:25, 11 April 2019 (CEST)

Right, you created a new page, [[User talk:ForOldHack/My sandbox‎‎]], in the 'User talk' namespace. On this wiki, only [https://en.wikipedia.org/wiki/Wikipedia:Administrators admins] can create new user accounts. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:12, 11 April 2019 (CEST)

Yes, I understand. Page deleted. It does help a lot that you have more Wikipedia experience then I. Thanks. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 10:35, 12 April 2019 (CEST)

: Technically, you 'blanked' the page; it (and its history) are still there. It is actually possible to remove a page totally, but only admins have that ability. Please let me know if you ever want a page (e.g. that one) nuked. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:43, 13 April 2019 (CEST)

:Yes, I have grabbed the information off that page, it can go into the great bit bucket (trash/recycler/ /dev/null)

:How many euphemisms can we come up with for deleting a file/page? [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 19:43, 17 April 2019 (CEST)

:: OK, I have deleted that page. If I misunderstood you, or you change your mind, please let me know and I can restore it. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 16:45, 24 April 2019 (CEST)

No, I copied the information here. It was an experiment and it did not come out as planned. ( silent back pages ).
Good to know we can bring back pages if we make mistakes.

But the more I read here about DEC/PDP/VAX, The more I agree with your respect for its elegance. I wish I had had more time with the hardware, and could have worked with it the way I have worked with PCs.

Got a Mac Performa 630CD running today, just by cleaning it thoroughly, and giving it time to ... coalesce.

It seems as though this Wiki is coming along with the company of a few devoted fans. Great work.

== Visualization ==

This is an exercise to create a text based
visualization tool to categorize memory boards and their resultant available operating systems:

Chips: Motherboard OS
1x16 DRAM IBM PC V1 DOS 1.0 ( August 1981 )
DOS 1.1 ( August 1981 )
CPM-86
UCSD-p

Hm... Chart:

[https://d1k5w7mbrh6vq5.cloudfront.net/images/cache/01/fd/0f/01fd0fcde84b7edd8bcbb946c2729d01.png?c8c3be714 Dos chart, and early windows, no server.]

[[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 10:35, 12 April 2019 (CEST)

== Kirk CD set! ==

You can find them on his site [https://www.mckusick.com/csrg/index.html here for sale]. Its a KLUNKY ordering thing, straight out of 1993, but I got my CD/DVD set in Hong Kong no worries!
Totally worth it!

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 14:03, 25 September 2019 (CEST)

:Thanks, All I needed was the correct search terms. Found them.
:The two talks I went to were the fixing the C port, and getting VM running on the VAX, both were fantastic lectures
:on UNIX history. It was nice that Kirk was so accessible, vs meeting Bill Joy at USENIX, and him walking off because he was busy.

Links: ( not on the article, so best of luck finding them.. :)

:https://archive.org/details/The_CSRG_Archives_CD-ROM_1_August_1998_Marshall_Kirk_McKusick
:https://archive.org/details/The_CSRG_Archives_CD-ROM_2_August_1998_Marshall_Kirk_McKusick
:https://archive.org/details/The_CSRG_Archives_CD-ROM_3_August_1998_Marshall_Kirk_McKusick
:https://archive.org/details/The_CSRG_Archives_CD-ROM_4_August_1998_Marshall_Kirk_McKusick

== Tapes ==

"So I had a source tape of GNU 0.1." Do you still have that tape? Or any other old tapes? [[User:Larsbrinkhoff|Larsbrinkhoff]] ([[User talk:Larsbrinkhoff|talk]]) 14:10, 29 May 2020 (CEST)

No, I do not have that tape, or any tapes. Lost 10+ years ago. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 09:23, 14 June 2020‎

== RS-232 ==

We actually already have an [[EIA RS-232 serial line interface]] article, linked to at the top of the article, which defines 'DCE', 'DTE' etc. Also, higher speeds were more common later, but early interfaces only supported lower speeds - e.g. the [[KL11]] only went up to 2400 baud, but even lower speeds were common; e.g. early [[KD11-B CPU]]s only supported 110 baud. What character coding was used with 5-bit characters? With only 32 available values, there aren't enough for letters and numbers. Etc, etc, etc. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 00:06, 23 June 2020 (CEST)

:Ah-HA, baud is short for Baudot code, which was a 5 bit character encoding, which was 26 letters, a space and a peroid, and STOP which was carried over to Telegrams, NULL, delete, and one more... FS?!?!?! It was known as Baudot-Murry, and is still used as ITA2 "ITA2 is still used in telecommunications devices for the deaf (TDD), telex, and some amateur radio applications, such as radioteletype ("RTTY"). ITA2 is also used in Enhanced Broadcast Solution (an early 21st century financial protocol specified by Deutsche Börse) to reduce the character encoding footprint"

:Why would the KD-11-B CPU support a serial link? For a debugging terminal or a logging printer?
:The TTYs that were at Lawrence Hall Of Science, and Willard Jr High school,

::VT-52s supported 75,110,150, 300,600, 1200,2400,4800, 9600 bps.
:ASR-33s supported 110, 10 cps, but the modems, The LDS I remember had a 75/110 switch.

== PDP-11/03 ==
Whist grabbing all the DEC documentation off Archive.org, I came across a MiniMINC manual, apparently a dual 8" Floppy PDP-11/03 variant. [https://archive.org/details/TNM_MiniMINC_desktop_computer_-_Digital_Equipment_20180102_0716/page/n5/mode/2up PDP-11/03 variant. Do we have room at the VERY low end of the PDP line for this?

== Real mode ==

I've never heard the term 'real mode' applied generally to machines, only to x86 machines. A quick Web search seems to confirm this; see e.g. [https://en.wikipedia.org/wiki/Real_mode Wikipedia]. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:47, 2 July 2020 (CEST)
:I would be in favor of renaming the page to something else than "Real mode" - it *is* x86 specific and it should therefore be named accordingly - not sure what's the best title, but e.g. "x86 Real Mode Memory Model" maybe? Or something better. Or a general "x86 Memory Models" with a section "Real Mode"? [[User:Tor|Tor]] ([[User talk:Tor|talk]]) 16:17, 13 August 2020 (CEST)

:: Real Mode Memory x86(only)

:::https://devblogs.microsoft.com/oldnewthing/20200728-00/?p=104012

:::https://devblogs.microsoft.com/oldnewthing/20171113-00/?p=97386

:::"This makes for a bit of trouble if you’re writing a program that needs to run in both real mode and protected mode. When you reach the end of the first 64KB block, how much do you increment the segment/selector by to reach the next 64KB block?

Enter the __AHINCR variable.

The __AHINCR variable is a variable exported from KERNEL. In real mode Windows, the value is 0x1000. In protected mode Windows, the value is 0x0008. When your program reaches the end of a 64KB block, it uses the __AHINCR value to decide how much to increment the segment/selector by in order to reach the next 64KB block.

Most programmers never saw this variable. It was hidden inside the code generated by the compiler.

With the introduction of enhanced mode Windows, the memory manager did a little more. Enhanced mode Windows used the 80386, “Now with 32-bit registers!✨” This means that the offset portion of a selector:offset address can be a 32-bit value."

"Real mode, also called real address mode, is an operating mode of all x86-compatible CPUs. The mode gets its name from the fact that addresses in real mode always correspond to real locations in memory. Real mode is characterized by a 20-bit segmented memory address space (giving exactly 1 MiB of addressable memory) and unlimited direct software access to all addressable memory, I/O addresses and peripheral hardware. Real mode provides no support for memory protection, multitasking, or code privilege levels. "

:The word memory, occurs 5 times, and address occurs twice. I/O Does not have addresses, it has numbered ports.
Real mode does not apply to x64 CPUs.
Something else applies: and DEC was one of the first, and all others followed:
Memory partitioning: VMS Partitions the 4GB address space into 4 parts, P0 ~ P4:

"VAX has a byte-addressable 32-bit virtual address space divided in 512
byte pages. The page is basic unit of mapping and protection. The
address space of a process is divided into P0, P1, P2 regions each 1GB.
P2 is the system address space that is shared between all processes. "

"The address space is split so that 2 GB of address space is directly accessible to user-mode processes (applications, for example your Opera Browser and the other 2 GB is only accessible to kernel-mode processes (Windows operating system, drivers, etc.)."

From Raymond Chen: [https://devblogs.microsoft.com/oldnewthing/20200728-00/?p=104012 A look back at memory models in 16-bit MS-DOS]

<blockquote>Yep. All of these memory models are still possible in protected mode (and still useful on the 286). But when the first OSes written for the 386 showed up, they basically all decided to make all the segments† 4GB large covering the entire (virtual) address space, which is technically the same as the Tiny model. Then when AMD designed x86-64 long mode, they pretty much deleted support for the other models. It doesn’t matter nowadays, because the segments point into the same virtual address space, so the other models really don’t have much benefit except for a very small number of edge cases.

† In protected mode, segments are regions of memory described by descriptors in the GDT or LDT and identified by selectors loaded into the *S registers; that’s my position on the terminology as backed up by the Intel IA-32 Architecture Software Developer’s Manual, Raymond.</blockquote>

VAX for the Win. Much more flexible and much more responsive, it can cache VM for both Applications and DATA, as well as for system processes. Which leaves it up to the OS to manage the caching for databases. I wonder what the benchmarks say...

:That is what I had thought. Keep in mind, I have over 50 edits on the Wikipedia IBM PC page, mostly to reflect IBMs documentation, after all, they made the machine. The same is true of Intel, I quote the manual, because they made the processor.

[https://courses.cs.washington.edu/courses/csep551/04wi/Messages/paper20/0020.html Review for VAX/VMS Virtual Memory Management paper]

There are a number of other errors (e.g. it's not ''just'' about addressing, as the intro currently implies), and the new revision is poorly organized. I was going to fix it, but as I started to do that, I realized it would take a lot of time, and I have other things I have to get to this morning, I can't just disrupt my entire day to jump on this. So I' going to have to leave it in its current state for the moment. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:16, 2 July 2020 (CEST)

:If "it's not ''just'' about addressing." and your citation says "also called real address mode" I fail to see why you cited an article that compelling supports the case.
:If you would prefer only finished articles, I can edit offline, and make my own scratch pad, and citations.
:I am mostly interested in the GDT of the 286 used by XENIX right now. ( The port of GNU C to 286 Xenix is still in limbo, while the Port of GNU C, was done a long time ago, and is kept current. Microsoft crippled 286 Xenix just to sell more software at $500.00 a pop. ( The College paid for 1 copy, and installed it 6 times. Since the computers were not networked, they had no way to complain.

::No its just just about addressing, and included both register file, and virtual IO, which are now features of the Intel Processor line.
::Some guidance would be good. No need to disrupt your day. Thanks [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 02:30, 3 July 2020 (CEST)

:A place for references, but fraught with errors: https://wiki.osdev.org/Virtual_8086_Mode

:Less errors https://www.singlix.com/trdos/archive/OSDev_Wiki/Protected%20Mode%20Software%20Architecture.pdf
"

== AIX for PS2 ==
http://ohlandl.ipv7.net/AIX_1-3/AIX_Index.html ; Many broken links but there are mirrors.

::AIX 1.3 ( there were 1.1, 1.2, and 1.3 versions for ) PS/2 Model 80, and later It was installed on a Model 70, - 386 only.

::Disk source [ https://winworldpc.com/product/aix/aix-ps2 AIX for the PS/2 Model 80 ]

::Running under emulation [ https://www.youtube.com/watch?v=27AnJ8MWBGc&ab_channel=DigitalArchaeologist AIX 1.3 on VirtualBox ] [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 00:16, 12 January 2024 (CET)

= AIX for PS/2 RS6000 S/370 =
Documentation
http://ps-2.kev009.com/aixps2/boo2pdf/

RT for MCA
http://ohlandl.ipv7.net/CPU/RT_Accelerator.html

Where all the books are:
http://ps-2.kev009.com/tavi/ps2pages/aix.html

Timeline for OSs
https://en.wikipedia.org/wiki/Timeline_of_operating_systems

== Scratch space for VMS E ==
ftp://nic.funet.fi/pub/msdos/games/strategy/

https://volafile.org/r/1en13tpxw

http://www.loper-os.org/

http://piotrkosoft.net/pub/windows/addons/gta3/mods/?C=S;O=D

http://www.kevra.org/TheBestOfNext/NeXTProducts/NeXTSoftware/NeXTSoftware.html

https://ia600306.us.archive.org/30/items/TheOriginalShareware1992V1/file_listing-ls.txt

https://unicom.crosenthal.com/pw/faq/sco-xenix.faq

http://www.nj7p.org/Manuals/PDFs/Intel/461830-001.pdf

= Real Mode test ASM =

There are several errors in this, its from PC TECH Magazine, TECH notes, but I do not know the issue number,
and I am trying to find it. verified errors will have a E in front of them.
What is seriously missing is a hex dump of this program, so I can fix the x86 assembly.
Found a hex dump, and am disassembling it now.

The actual archive is located here: http://www.ittnnet.com/downloads/PCMAG/VOL11N20.ZIP
Volume 11 of PC TECH Journal. ( 1988 )
File is VIRT8086.EXE, Assembly file is VIRT8086.ASM ( that you use an assembler on ), and VIRT8086.SCR, which is a debug script that contains the errors, shown here.

NVIRT8086.BIN ;This (N)ames the file VIRT8086.BIN so you can rename it later.
E100 'MZ' ;The "E" and "F" lines below create the EXE header.
E102 B1 00 02 00 01 00 20 00 11 00
E10C FF FF 0C 00 00 01 00 00 00 00
E116 00 00 3E 00 00 00 00 01 FB 30
E120 6A 72 ; Binary shows '6A' not 'CA'
E F122 13D 00 ; This should continue the entering of data into hex location E122, but it does not, and 13D is not a valid hex byte.
E13E 01 ; Consistent with binary.
E F13F 2FF 00 ; This should enter the data into E13F but it does not.
A300
MOV AX,0003
MOV DS,AX ;next line is MOVE EAX, CR0
DB 0F 20 C0
DB 66
TEST AX,0001 ;with line above & below, TEST EAX, 00000001H
DB 99 99
JZ 325 ;jump to GotReal if protection disabled
NOP
NOP
MOVE DX,0000 ;offset of 'protect w/ no paging' message
DB 66
TEST AX,0000 ;with line above & below, TEST EAX, 00000000H
DB 00 80
JZ 328 ;jump to WriteIt if no paging
NOP
NOP
MOV DX,033 ;offset of 'protect w/ paging' message
JMP 0328 ;jump to WriteIt
NOP
;next line is label GotReal
MOVE DX, 0065 ;offset of 'real mode' message
;next line is label WriteIt
E MOV AH,09
INT 21
E MOV AH,4C
INT 21 ;return to DOS, after printing message.
; Message area;
E 330 'CPU IS RUNNING IN PROTECTED MODE...PAGING DISABLED$'
E 363 'CPU IS RUNNING IN PROTECTED MODE...PAGING ENABLED$'
E 395 'CPU IS RUNNING IN REAL MODE$'
RCX ;This is supposed to put 2B1 bytes into the CX register.
2B1
W ;This writes the file to disk
Q ;This quits the debugger.

You must rename VIRT8086.BIN to VIRT8086.EXE and execute from the command line.

( note: Running in V86 or Protected mode, slows Video, by 50 to 70% ).

Xenix Benchmarks:
From: https://web.archive.org/web/20141202093953/http://wiretap.area.com/Gopher/Library/Techdoc/Bench/dhryst.txt

MANUF MODEL PROC CLOCK NOREG REG OS,COMPILER,NOTES
----- ----- ---- ----- ----- --- -----------------
IBM PC/AT 80286 9.05 696 692 XENIX SCO SVR2.1,cc large,
IBM PC/AT 80286 9.05 1464 1484 XENIX SCO SVR2.1,cc small,
Intel Inboard 38 80386 16.00 4603 4922 SCO XENIX 386 Beta 6/16/87,cc Beta ,cache on, 32 bit memory
NCR PC-8 80286 8.00 653 649 XENIX SCO SVR2.0.4,cc large,
NCR PC-8 80286 8.00 981 983 XENIX SCO SVR2.0.4,cc middle
NCR PC-8 80286 8.00 1283 1299 XENIX SCO SVR2.0.4,cc small,
Spectrix M Series 10 68000 10.00 571 592 Xenix ,Greenhills 1.7.14 -O,
TANDY 3000HD 80286 10.00 1318 1346 XENIX System V/286,cc large,
TANDY 3000HD 80286 10.00 2071 2164 XENIX System V/286 Xenix,cc small,
Tandy 6000 68000 8.00 1286 1362 XENIX 3.1,cc 1.0 ,
Tandy 6000 68000 8.00 1288 1366 XENIX 3.0.0,cc 3.0.0 NONE,Tandy Ver. 3.1.2
Tandy 3000 80286 8.00 1455 1543 Xenix 2.00,cc ,

PDP-11/73

2025-01-10T18:42:16Z

ForOldHack: /* From Digital */ Added the Micro version of RSX-11M

[[Image:mpdp73.jpg|right|thumb|200px|PDP-11/73]]
The '''PDP-11/73''' is a high-end [[QBUS]] [[PDP-11]] system. Confusingly, the [[Central Processing Unit|CPU]] board is the [[KDJ11-B]] (M8190), the same as the [[PDP-11/83]] - no [[Digital Equipment Corporation|DEC]] '-11/xx' system seems to use the earlier [[KDJ11-A]] (M8192). (The ''Microcomputer Products Handbook'' does refer to the KDJ11-A as the "LSI-11/73 microcomputer", however.)

The difference between the /73 and /83 is that the latter uses [[Private Memory Interconnect|PMI]] [[main memory]], instead as the QBUS memory of the -11/73.

== OS ==
The PDP-11/73 and PDP-11/83 Micro PDPs ran RXS-11 M, RXS-11 M Plus, and BSD

== hampage.hu ==
Quoting:

Introduced in 1984. Successor of the [[PDP-11/23]]. At that time the components were VLSI, and these PDP-11's were marketed as MicroPDP's (this has in fact begun with the PDP-11/23). The PDP-11/73 had a 15MHz [[J-11 chip set]]-based CPU with 22-bit memory management for the 4MB RAM max. Just to make life more complicated, 18 MHz PDP-11/83 CPU boards can also be found in PDP-11/73 systems, as a PDP-11/83 CPU (M8190-A[DE]) with QBUS memory (instead of the PMI memory used in those systems) is called a PDP-/73...

There was no UNIBUS equivalent.(Incorrect. The [[PDP-11/84]] shared the same CPU, and had a [[UNIBUS]].)

The J-11 was manufactured by Harris Semiconductors, and it hasn't been fully completed, it lacked the WCS and CIS options.

A very popular enclosure is displayed to the right: this was the [[BA23 Enclosure|BA23]] standing tower configuration, that had place for a 8x4 backplane, an [[RX50]] floppy or [[TK50]] streaming tape drive and an RDxx hard disk. The BA23 could also be rack-mounted.

[[Image:pdp11-73.jpg|150px|thumb|left|PDP-11/73 in a different style of box]]

 
{{semi-stub}}

==Further reading==

* ''MicroPDP-11 Systems Owner's Manual'' (EK-MIC11-OM) - This, and the three related MicroPDP-11 manuals below, are not specific to the PDP-11/73, but contain a great deal of material which applies to the MicroPDP-11/73

==External links==

* [http://bitsavers.org/pdf/dec/pdp11/microPDP11/AZ-FI13A-MC_MicroPDP11_Systems_Owners_Manual_Jun86.pdf MicroPDP-11 Systems Owner's Manual] (AZ-FI13A-MC)
* [http://bitsavers.org/pdf/dec/pdp11/microPDP11/EK-MIC11-TM-002_MicroPDP11_Systems_Technical_Manual_Sep85.pdf MicroPDP-11 Systems Technical Manual] (EK-MIC11-TM-002)
* [https://vt100.net/mirror/antonio/ek-mic11-sg-001.pdf MicroPDP-11 Systems Maintenance Guide] (EK-MIC11-SG-001)
* [http://bitsavers.org/pdf/dec/pdp11/handbooks/PDP-11_Systems_Handbook_1987.pdf PDP-11 Systems Handbook]
* [http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/pdp11/handbooks/EB-24944-18_Micro_PDP-11_Handbook_1983-84.pdf PDP-11 Micro/PDP-11 Handbook 1983-84] (EB-24944-18)

{{PDP-11}}

[[Category: QBUS PDP-11s]]

PDP-11/73

2025-01-10T17:59:53Z

ForOldHack: /* External links */ added earler handbook, 1983 vs 1987

[[Image:mpdp73.jpg|right|thumb|200px|PDP-11/73]]
The '''PDP-11/73''' is a high-end [[QBUS]] [[PDP-11]] system. Confusingly, the [[Central Processing Unit|CPU]] board is the [[KDJ11-B]] (M8190), the same as the [[PDP-11/83]] - no [[Digital Equipment Corporation|DEC]] '-11/xx' system seems to use the earlier [[KDJ11-A]] (M8192). (The ''Microcomputer Products Handbook'' does refer to the KDJ11-A as the "LSI-11/73 microcomputer", however.)

The difference between the /73 and /83 is that the latter uses [[Private Memory Interconnect|PMI]] [[main memory]], instead as the QBUS memory of the -11/73.

== hampage.hu ==
Quoting:

Introduced in 1984. Successor of the [[PDP-11/23]]. At that time the components were VLSI, and these PDP-11's were marketed as MicroPDP's (this has in fact begun with the PDP-11/23). The PDP-11/73 had a 15MHz [[J-11 chip set]]-based CPU with 22-bit memory management for the 4MB RAM max. Just to make life more complicated, 18 MHz PDP-11/83 CPU boards can also be found in PDP-11/73 systems, as a PDP-11/83 CPU (M8190-A[DE]) with QBUS memory (instead of the PMI memory used in those systems) is called a PDP-/73...

There was no UNIBUS equivalent.(Incorrect. The [[PDP-11/84]] shared the same CPU, and had a [[UNIBUS]].)

The J-11 was manufactured by Harris Semiconductors, and it hasn't been fully completed, it lacked the WCS and CIS options.

A very popular enclosure is displayed to the right: this was the [[BA23 Enclosure|BA23]] standing tower configuration, that had place for a 8x4 backplane, an [[RX50]] floppy or [[TK50]] streaming tape drive and an RDxx hard disk. The BA23 could also be rack-mounted.

[[Image:pdp11-73.jpg|150px|thumb|left|PDP-11/73 in a different style of box]]

 
{{semi-stub}}

==Further reading==

* ''MicroPDP-11 Systems Owner's Manual'' (EK-MIC11-OM) - This, and the three related MicroPDP-11 manuals below, are not specific to the PDP-11/73, but contain a great deal of material which applies to the MicroPDP-11/73

==External links==

* [http://bitsavers.org/pdf/dec/pdp11/microPDP11/AZ-FI13A-MC_MicroPDP11_Systems_Owners_Manual_Jun86.pdf MicroPDP-11 Systems Owner's Manual] (AZ-FI13A-MC)
* [http://bitsavers.org/pdf/dec/pdp11/microPDP11/EK-MIC11-TM-002_MicroPDP11_Systems_Technical_Manual_Sep85.pdf MicroPDP-11 Systems Technical Manual] (EK-MIC11-TM-002)
* [https://vt100.net/mirror/antonio/ek-mic11-sg-001.pdf MicroPDP-11 Systems Maintenance Guide] (EK-MIC11-SG-001)
* [http://bitsavers.org/pdf/dec/pdp11/handbooks/PDP-11_Systems_Handbook_1987.pdf PDP-11 Systems Handbook]
* [http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/pdp11/handbooks/EB-24944-18_Micro_PDP-11_Handbook_1983-84.pdf PDP-11 Micro/PDP-11 Handbook 1983-84] (EB-24944-18)

{{PDP-11}}

[[Category: QBUS PDP-11s]]

KD11-E/EA microcode

2024-10-03T22:47:38Z

ForOldHack: /* Added Enginering drawings for The KD-11-EA */

The engineering drawings for the [[KD11-E CPU]] and [[KD11-EA CPU]] provide nice [[flow chart]]s for the [[microcode]] in these [[Central Processing Unit|CPUs]]; with one tiny exception, the microcode in the two is identical. (The KD11-EA contains additional microcode associated with the [[FP11-A Floating-Point Processor]], which is not covered here.)

The difference is that the [[microinstruction]] 17-JJ is stored in location 002 in the KD11-E, and location 0744 in the KD11-EA. The reason for the change is unknown. Also, a dump of the KD11-EA microcode gives a different 'next microinstuction', from that given in the prints, for microinstruction 26-L (location 646); the prints show 9-F (location 320) as the next, but the dump gives 745. Again, the reason is unknown.

[https://bitsavers.org/pdf/dec/pdp11/1134/MP00190_1134A_KD11-EA.pdf Engineering drawings for the KD11-EA CPU]

==Flow chart index==

The [[instruction]]s/functionality covered on each page are as follows:

{| class="wikitable"
! Page !! Contents
|-
| 2 || Instruction fetch and dispatch
|-
| 3 || Double op, source fetch
|-
| 4 || MOV
|-
| 5 || Double op, byte or SUB
|-
| 6 || Double op, destination fetch
|-
| 7 || Single op, modified dest
|-
| 8 || Single op, non-modified dest
|-
| 9 || JMP
|-
| 10 || JSR
|-
| 11 || SWAB
|-
| 12 || Shift, rotate
|-
| 13 || MFPI
|-
| 14 || MTPI
|-
| 15 || MTPS
|-
| 16 || MFPS
|-
| 17 || MARK, BR, RTS, CLx, SEx, SOB, RTI, RTT, NEG, WAIT, RESET
|-
| 18 || MUL/DIV
|-
| 19 || MUL
|-
| 20 || MUL
|-
| 21 || DIV
|-
| 22 || DIV
|-
| 23 || ASH/ASHC
|-
| 24 || Shift right
|-
| 25 || Shift left
|-
| 26 || Power on, trap
|}

==Microcode==

The following table, indexed by microinstruction number (in octal), gives the location of each microinstruction in the flow diagrams, the next microinstruction(s), and the operation performed by that microinstruction.

The microengine of the KD11-E/EA uses a technique called a 'branch microtest' (abbreviated to 'BUT' in the drawings), where the 'next microinstruction' field (in each microinstruction - there is no 'micro-PC') can be OR'd with various bits provided by the [[logic]] in the KD11-E/EA, to provide [[conditional branch]]ing. More than one bit at a time can be OR'd, thereby providing multi-way branching.

In the table below, for every microinstruction which can have variation as to the next microinstruction, all possible 'next microinstruction' destinations are listed. Note that depending on the bit(s) being tested, various bits of the 'next microinstruction' [[address]] may be set.

This can result in rather odd code layout, since a multi-way branch may require microinstructions to be scattered throughout the [[address space]], with a fixed numerical relationship among their addresses - the exact relationship depending on which bit is being tested.

One microinstruction (015), the main dispatch in instruction decoding, greatly extends the technique, with the aid of an instruction decode [[read-only memory|ROM]], so the next microinstruction in its case may be one of dozens. They are mostly arranged in groups of eight, with one of each group for each [[PDP-11 architecture#Addressing modes|addressing mode]] in the [[operand]]s. (In the table below, such a destination is notated as 'YYx'.)

During the transcription of this information, a number of errors in the drawings were found - places were two different microinstructions were assigned to the same location. These have been corrected (and checked against a dump of the microcode).

{| class="wikitable"
! μinstruction !! μcode flow diagram location !! next μinst !! Operation
|-
| 000 || 2-A || 016,017 || Service intr/trap, store vector
|-
| 001 || 26-M || 432 || Move PC to B
|-
| 002
|-
| 003 || 17-LL || 000 || Initialize system for 150msec
|-
| 004 || 17-L || 525 || Destination register to PC
|-
| 005 || 13-E || 371 || Fetch destination address, enable previous mode
|-
| 006 || 17-R || 541 || PSW to R12
|-
| 007 || 17-X || 542 || PSW to R12
|-
| colspan = "4" |  
|-
| 010 || 14-D || 644 || Fetch word from top of stack
|-
| 011 || 17-EE || 645 || Fetch top of stack
|-
| 012 || 17-NN || 014 || No operation
|-
| 013 || 17-OO || 460 || Vector to R15
|-
| 014 || 17-MM || 012,013 || Service interrupt/trab, fetch vector
|-
| 015 || 2-C || + || Increment PC, ubranch on instruction
|-
| 016 || 2-B || 015 || Fetch next instruction, load into IR
|-
| 017 || 26-A || 460 || Move vector to R15
|-
| colspan = "4" |  
|-
| 020 || 17-A || 553 || Sign extend BREG
|-
| 021 || 9-A || 000 || Jump address to PC
|-
| 022 || 9-C || 317 || Jump address to BREG
|-
| 023 || 9-D || 317 || Fetch jump address
|-
| 024 || 9-B || 021 || Decrement RDST, enable stack overflow
|-
| 025 || 9-G || 321 || Decrement RDST, enable stack overflow
|-
| 026 || 9-I || 322 || Fetch index data
|-
| 027 || 9-L || 324 || Fetch index data
|-
| colspan = "4" |  
|-
| 030 || 11-A || 343 || Swap destination operand to R12
|-
| 031 || 11-C || 355 || Fetch swapped destination operand
|-
| 032 || 11-E || 344 || Fetch swapped destination operand
|-
| 033 || 11-G || 345 || Fetch destination address
|-
| 034 || 11-D || 031 || Decrement RDST, enable stack overflow
|-
| 035 || 11-I || 346 || Decrement RDST, enable stack overflow
|-
| 036 || 11-K || 347 || Fetch index data
|-
| 037 || 11-N || 351 || Fetch index data
|-
| colspan = "4" |  
|-
| 040 || 7-A || 000 || Operate and load condition codes
|-
| 041 || 7-B || 217 || Fetch destination operand
|-
| 042 || 7-D || 275 || Fetch destination operand
|-
| 043 || 7-F || 276 || Fetch destination address
|-
| 044 || 7-C || 041 || Decrement RDST, enable stack overflow
|-
| 045 || 7-H || 277 || Decrement RDST, enable stack overflow
|-
| 046 || 7-K || 301 || Fetch index data
|-
| 047 || 7-M || 303 || Fetch index data
|-
| colspan = "4" |  
|-
| 050 || 4-A || 000 || Operate and load condition codes
|-
| 051 || 4-B || 217 || Set up destination address
|-
| 052 || 4-P || 217 || Set up destination address, increment RDST
|-
| 053 || 4-F || 141 || Fetch destination address
|-
| 054 || 4-C || 051 || Decrement RDST, enable stack overflow
|-
| 055 || 4-H || 142 || Decrement RDST, enable stack overflow
|-
| 056 || 4-J || 144 || Fetch index data
|-
| 057 || 4-M || 146 || Fetch index data
|-
| colspan = "4" |  
|-
| 060 || 6-A || 265 || Destination operand to BREG
|-
| 061 || 6-B || 265 || Fetch destination operand
|-
| 062 || 6-D || 263 || Fetch destination operand
|-
| 063 || 6-F || 264 || Fetch destination address
|-
| 064 || 6-C || 061 || Decrement RDST, enable stack overflow
|-
| 065 || 6-I || 266 || Decrement RDST, enable stack overflow
|-
| 066 || 6-L || 662 || Fetch index data
|-
| 067 || 6-O || 272 || Fetch index data
|-
| colspan = "4" |  
|-
| 070 || 5-A || 050 || Destination operand to BREG
|-
| 071 || 5-B || 217 || Fetch destination operand
|-
| 072 || 5-D || 242 || Fetch destination operand
|-
| 073 || 5-F || 243 || Fetch destination address
|-
| 074 || 5-C || 071 || Decrement RDST, enable stack overflow
|-
| 075 || 5-H || 244 || Decrement RDST, enable stack overflow
|-
| 076 || 5-K || 246 || Fetch index data
|-
| 077 || 5-N || 661 || Fetch index data
|-
| colspan="4" |   
|-
| 100 || 13-A || 463 || Destination data to R12, enable previous mode
|-
| 101 || 13-B || 455 || Move destination address to R12
|-
| 102 || 13-D || 005 || Move destination address to R12
|-
| 103 || 13-G || 372 || Fetch destination address
|-
| 104 || 13-C || 101 || Decrement RDST, enable stack overflow
|-
| 105 || 13-I || 373 || Decrement RDST, enable stack overflow
|-
| 106 || 13-K || 374 || Fetch index data
|-
| 107 || 13-N || 376 || Fetch index data
|-
| colspan = "4" |  
|-
| 110 || 3-A || 05x, 06x. 07x || Source operand to R12 and BREG
|-
| 111 || 3-B || 05x, 06x. 07x || Fetch source operand
|-
| 112 || 3-D || 205 || Fetch source operand
|-
| 113 || 3-F || 206 || Fetch source address
|-
| 114 || 3-C || 111 || Decrement RSRC, enable stack overflow
|-
| 115 || 3-H || 207 || Decrement RSRC, enable stack overflow
|-
| 116 || 3-K || 212 || Fetch index data
|-
| 117 || 3-N || 214 || Fetch index data
|-
| colspan = "4" |  
|-
| 120 || 15-A || 675 || Destination operand to R12 and BREG
|-
| 121 || 15-F || 675 || Fetch destination operand
|-
| 122 || 15-H || 663 || Fetch destination operand
|-
| 123 || 15-J || 664 || Fetch destination address
|-
| 124 || 15-G || 121 || Decrement RDST, enable stack overflow
|-
| 125 || 15-M || 665 || Decrement RDST, enable stack overflow
|-
| 126 || 15-O || 667 || Fetch index data
|-
| 127 || 15-R || 672 || Fetch index data
|-
| colspan = "4" |  
|-
| 130 || 16-A || 705 || PSW data to R12
|-
| 131 || 16-C || 706 || Place destination address on bus address lines
|-
| 132 || 16-F || 706 || Destination address to bus, increment RDST
|-
| 133 || 16-G || 710 || Fetch destination address
|-
| 134 || 16-E || 131 || Decrement RDST, enable stack overflow
|-
| 135 || 16-J || 711 || Decrement RDST, enable stack overflow
|-
| 136 || 16-L || 712 || Fetch index data
|-
| 137 || 16-O || 714 || Fetch index data
|-
| colspan = "4" |  
|-
| 140 || 17-U || 210 || RDST to BREG
|-
| 141 || 4-G || 143 || Increment RDST
|-
| 142 || 4-I || 143 || Fetch destination address
|-
| 143 || 4-Q || 217 || Setup destination address, enable KT maintenance
|-
| 144 || 4-K || 145 || Increment PC
|-
| 145 || 4-L || 143 || Determine destination address
|-
| 146 || 4-N || 147 || Increment PC
|-
| 147 || 4-O || 241 || Determine address of destination address
|-
| colspan = "4" |  
|-
| 150 || 17-KK || 07x || Zero R12
|-
| 151 || 10-A || 336 || Jump address to BREG
|-
| 152 || 10-C || 327 || Jump address to BREG
|-
| 153 || 10-D || 327 || Fetch jump address
|-
| 154 || 10-B || 336 || Decrement RDST, jump address to BREG
|-
| 155 || 10-F || 330 || Decrement RDST, enable stack overflow
|-
| 156 || 10-H || 331 || Fetch index data
|-
| 157 || 10-K || 333 || Fetch index data
|-
| colspan = "4" |  
|-
| 160 || 8-A || 000 || Operate on operand, load condition codes
|-
| 161 || 8-B || 265 || Fetch destination operand
|-
| 162 || 8-D || 306 || Fetch destination operand
|-
| 163 || 8-F || 307 || Fetch destination address
|-
| 164 || 8-C || 161 || Decrement RDST, enable stack overflow
|-
| 165 || 8-H || 310 || Decrement RDST, enable stack overflow
|-
| 166 || 8-K || 312 || Fetch index data
|-
| 167 || 8-N || 314 || Fetch index data
|-
| colspan = "4" |  
|-
| 170 || 12-A || 356 || Destination operand to BREG
|-
| 171 || 12-C || 370 || Fetch destination operand
|-
| 172 || 12-E || 357 || Fetch destination operand
|-
| 173 || 12-G || 360 || Fetch destination addressa
|-
| 174 || 12-D || 171 || Decrement RDST, enable stack overflow
|-
| 175 || 12-I || 361 || Decrement RDST, enable stack overflow
|-
| 176 || 12-L || 363 || Fetch index data
|-
| 177 || 12-O || 365 || Fetch index data
|-
| colspan = "4" |   
|-
| 200 || 17-I || 522 || Sign extend BREG
|-
| 201 || 26-FF || 202 || Set R15 to 26
|-
| 202 || 26-GG || 577 || Fetch new PSW
|-
| 203 || 17-Q || 000 || Operate, set condition codes
|-
| 204 || 17-W || 000 || Operate, set condition codes
|-
| 205 || 3-E || 05x,06x,07x || Increment RSRC
|-
| 206 || 3-G || 211 || Increment RSRC
|-
| 207 || 3-I || 211 || Fetch source address
|-
| colspan = "4" |  
|-
| 210 || 17-T || 000 || Operate, send condition codes
|-
| 211 || 3-J || 05x,06x,07x || Fetch source operand
|-
| 212 || 3-L || 213 || Increment PC
|-
| 213 || 3-M || 211 || Determine source address
|-
| 214 || 3-O || 215 || Increment PC
|-
| 215 || 3-P || 216 || Determine address of source address
|-
| 216 || 3-Q || 211 || Fetch source address
|-
| 217 || 4-E || 000 || Get destination data and store, enable KT maintenance
|-
| colspan = "4" |  
|-
| 220 || 18-A || 602 || Fetch multiplicand/divisor
|-
| 221 || 18-B || 602 || Fetch multiplicand/divisor
|-
| 222 || 18-D || 563 || Fetch multiplicand/divisor
|-
| 223 || 18-F || 565 || Fetch destination address
|-
| 224 || 18-C || 221 || Decrement RDST, enable stack overflow
|-
| 225 || 18-H || 567 || Decrement RDST, enable stack overflow
|-
| 226 || 18-J || 571 || Fetch index data
|-
| 227 || 18-M || 575 || Fetch index data
|-
| colspan = "4" |  
|-
| 230 || 23-A || 633 || Fetch shift count
|-
| 231 || 23-B || 633 || Fetch shift count
|-
| 232 || 23-D || 621 || Fetch shift count
|-
| 233 || 23-F || 622 || Fetch destination address
|-
| 234 || 23-C || 231 || Decrement RDST, enable stack overflow
|-
| 235 || 23-H || 624 || Decrement RDST, enable stack overflow
|-
| 236 || 23-J || 625 || Fetch index data
|-
| 237 || 23-M || 627 || Fetch index data
|-
| colspan = "4" |  
|-
| 240 || 17-V || 204 || RSRC to BREG
|-
| 241 || 4-P || 143 || Fetch destination address
|-
| 242 || 5-E || 217 || Increment RDST
|-
| 243 || 5-G || 245 || Increment RDST
|-
| 244 || 5-I || 245 || Fetch destination address
|-
| 245 || 5-J || 217 || Fetch destination operand
|-
| 246 || 5-L || 247 || Increment PC
|-
| 247 || 5-M || 245 || Determine destination address
|-
| colspan = "4" |  
|-
| 250 || 14-A || 000 || Move data to desination register
|-
| 251 || 14-B || 513 || Move destination address to R13
|-
| 252 || 14-F || 474 || Move destination address to R13
|-
| 253 || 14-H || 474 || Fetch destination address
|-
| 254 || 14-C || 251 || Decrement RDST, enable stack overflow
|-
| 255 || 14-I || 475 || Decrement RDST, enable stack overflow
|-
| 256 || 14-K || 476 || Fetch index data
|-
| 257 || 14-N || 506 || Fetch index data
|-
| colspan = "4" |  
|-
| 260 || 17-Z || 700,702 || Decrement RSRC, branch on 0
|-
| 261 || 5-P || 262 || Determine address of destination address
|-
| 262 || 5-Q || 245 || Fetch destination address
|-
| 263 || 6-E || 265 || Increment RDST
|-
| 264 || 6-G || 267 || Increment RDST
|-
| 265 || 6-H || 000 || Operate and load condition codes
|-
| 266 || 6-J || 267 || Fetch destination address
|-
| 267 || 6-K || 265 || Fetch destination operand
|-
| colspan = "4" |  
|-
| 270 || 17-P || 203 || RDEST to BREG
|-
| 271 || 6-N || 267 || Determine destination address
|-
| 272 || 6-P || 273 || Increment PC
|-
| 273 || 6-Q || 274 || Determine address of destination address
|-
| 274 || 6-R || 267 || Fetch destination address
|-
| 275 || 7-E || 217 || Increment RDST
|-
| 276 || 7-G || 300 || Increment RDST
|-
| 277 || 7-I || 300 || Fetch destination address
|-
| colspan = "4" |   
|-
| 300 || 7-J || 217 || Fetch destination operand
|-
| 301 || 7-L || 302 || Increment PC
|-
| 302 || 7-M || 300 || Determine destination address
|-
| 303 || 7-O || 304 || Increment PC
|-
| 304 || 7-P || 305 || Determine address of destination address
|-
| 305 || 7-Q || 300 || Fetch destination address
|-
| 306 || 8-E || 265 || Increment RDST
|-
| 307 || 8-G || 311 || Increment RDST
|-
| colspan = "4" |  
|-
| 310 || 8-I || 311 || Fetch destination address
|-
| 311 || 8-J || 265 || Fetch destination operand
|-
| 312 || 8-L || 313 || Increment PC
|-
| 313 || 8-M || 311 || Determine desination address
|-
| 314 || 8-O || 315 || Increment PC
|-
| 315 || 8-P || 316 || Determine address of desination address
|-
| 316 || 8-Q || 311 || Fetch destination address
|-
| 317 || 9-E || 320 || Increment RDST
|-
| colspan = "4" |  
|-
| 320 || 9-F || 000 || Jump address to PC
|-
| 321 || 9-H || 320 || Fetch jump address
|-
| 322 || 9-J || 323 || Increment PC
|-
| 323 || 9-K || 000 || Determine jump address
|-
| 324 || 9-M || 325 || Increment PC
|-
| 325 || 9-N || 326 || Determine address of jump address
|-
| 326 || 9-O || 320 || Fetch jump address
|-
| 327 || 10-E || 336 || Increment RDST
|-
| colspan = "4" |  
|-
| 330 || 10-G || 336 || Fetch jump address
|-
| 331 || 10-I || 332 || Increment PC
|-
| 332 || 10-J || 336 || Determine jump address
|-
| 333 || 10-L || 334 || Increment PC
|-
| 334 || 10-M || 335 || Determine address of jump address
|-
| 335 || 10-N || 336 || Fetch jump address
|-
| 336 || 10-O || 337 || Decrement SP
|-
| 337 || 10-P || 340 || Set up bus address
|-
| colspan = "4" |  
|-
| 3401 || 10-Q || 341 || Output RSRC to stack
|-
| 341 || 10-R || 342 || Move PC to RSRC
|-
| 342 || 10-S || 000 || BREG to PC
|-
| 343 || 11-B || 000 || Load condition codes
|-
| 344 || 11-F || 355 || Increment RDST
|-
| 345 || 11-H || 354 || Increment RDST
|-
| 346 || 11-J || 354 || Fetch destination address
|-
| 347 || 11-L || 350 || Increment PC
|-
| colspan = "4" |  
|-
| 350 || 11-M || 354 || Determine destination address
|-
| 351 || 11-O || 352 || Increment PC
|-
| 352 || 11-P || 353 || Determine address of destination address
|-
| 353 || 11-Q || 354 || Fetch destination address
|-
| 354 || 11-R || 355 || Fetch swapped destination operand
|-
| 355 || 11-S || 000 || Store data, load condition codes
|-
| 356 || 12-B || 050 || Shift operand
|-
| 3572 || 12-F || 370 || Increment RDST
|-
| colspan = "4" |  
|-
| 360 || 12-H || 362 || Increment RDST
|-
| 361 || 12-J || 362 || Fetch destination address
|-
| 362 || 12-K || 370 || Fetch destination operand
|-
| 363 || 12-M || 364 || Increment PC
|-
| 364 || 12-N || 362 || Determine destination address
|-
| 365 || 12-P || 366 || Increment PC
|-
| 366 || 12-Q || 367 || Determine address of destination address
|-
| 367 || 12-R || 362 || Fetch destination address
|-
| colspan = "4" |  
|-
| 370 || 12-S || 217 || Shift operand
|-
| 371 || 13-F || 463 || Increment RDST
|-
| 372 || 13-H || 455 || Increment RDST
|-
| 373 || 13-J || 455 || Fetch destination address
|-
| 374 || 13-L || 375 || Increment PC
|-
| 375 || 13-M || 455 || Determine destination address
|-
| 376 || 13-O || 377 || Increment PC
|-
| 377 || 13-P || 643 || Determine address of destination address
|-
| colspan = "4" |   
|-
| 400 || 18-S || 402,502 || Complement & test sign of multiplicand
|-
| 401 || 18-T || 404,406 || Test divisor for zero
|-
| 402 || 19-A || 403,503 || Zero R17 and B, test multiplicand
|-
| 403 || 19-J || 606 || Put multiplier in BX
|-
| 404 || 21-A || 612 || Put one's complement of divisor in R13
|-
| 405 || 19-D || 407 || Put one's complement of multiplier in R13
|-
| 406 || 22-W || 620 || Set V bit
|-
| 407 || 19-U || 413,417,433,437, 453,457,473,477 || Shift right (partial product, multiplier), decrement counter
|-
| colspan = "4" |  
|-
| 410 || 20-C || 420,422 || Test upper product for all 1's
|-
| 411 || 20-L || 611 || Clear C bit
|-
| 412 || 20-H || 414,416|| Test lower product for zero
|-
| 413 || 19-M || 413,417,433,437, 453,457,473,477 || Shift right (partial product, multiplier), decrement counter
|-
| 414 || 20-J || 411,511 || Test MSB of lower product
|-
| 415 || 20-G || 611 || Set C bit
|-
| 416 || 20-I || 414 || Set Z bit
|-
| 417 || 19-P || 607 || Store upper product
|-
| colspan = "4" |  
|-
| 420 || 20-E || 415 || Set V bit
|-
| 421 || 21-L || 424 || Fetch lower dividend
|-
| 422 || 20-D || 415,515 || Test MSB of lower product
|-
| 423 || 21-F || 424 || Take one's complement of upper dividend
|-
| 424 || 21-M || 425,435 || Shift upper dividend left, test sign of divisor
|-
| 425 || 21-O || 440,442 || Subtract divisor from dividend, test remainder
|-
| 426 || 22-S || 616 || Set V bit
|-
| 427 || 19-L || 407 || Subtract multiplicand from partial product
|-
| colspan = "4" |  
|-
| 430 || 25-A || 452,456 || Test counter for 0, fetch upper part of operand
|-
| 431 || 22-J || 616 || Clear V bit
|-
| 432 || 26-N || 731 || Move PC to R5
|-
| 433 || 19-T || 473 || Add multiplicand to partial product
|-
| 434 || 24-A || 516,517 || Test IR9 to determine ASH/ASHC
|-
| 435 || 21-N || 440,442 || Subtract divisor from dividend, test remainder
|-
| 436 || 17-D || 556 || BREG to SP
|-
| 437 || 19-Q || 607 || Store upper product
|-
| colspan = "4" |  
|-
| 440 || 21-P || 442,462 || Test first quotient bit
|-
| 441 || 22-B || 461 || Add divisor to remainder
|-
| 442 || 21-G || 640,650,660,670 || Shift remainder left, test sign of divisor, test LSB of quotient
|-
| 443 || 22-N || 615 || Srore remainder
|-
| 444 || 22-D || 614 || Srore remainder
|-
| 445 || 24-E || 635 || Save BX in B, clear N bit
|-
| 446 || 22-A || 441,451,461,471 || Test quotient LSB and sign of divisor
|-
| 447 || 24-D || 634 || Save BX in B, clear N bit
|-
| colspan = "4" |  
|-
| 4503 || 17-II || 744 || Step SP
|-
| 451 || 22-K || 471 || Add divisor to remainder
|-
| 452 || 25-D || 652,653 || Test IR9 to determine ASH/ASHC, fetch lower part of operand
|-
| 453 || 19-O || 413 || Subtract multiplicand from partial product
|-
| 454 || 24-K || 641 || Clear C bit
|-
| 455 || 13-R || 463 || Fetch destination data, enable previous mode
|-
| 456 || 25-B || 500,501 || Test IR9 to determine ASH/ASHC
|-
| 457 || 19-R || 607 || Store upper product
|-
| colspan = "4" |  
|-
| 460 || 26-B || 470 || Move PSW to B
|-
| 461 || 22-C || 444,544 || Test sign of dividend
|-
| 462 || 22-Y || 000 || Set V bit
|-
| 463 || 13-S || 472 || Decrement SP
|-
| 464 || 24-U || 465 || Store lower result, clear N bit
|-
| 465 || 24-X || 637 || Clear Z bit
|-
| 466 || 24-T || 465,467 || Store lower result, clear N bit, test for 0
|-
| 467 || 24-W || 637 || Clear Z bit
|-
| colspan = "4" |  
|-
| 470 || 26-C || 504 || Increment vector address
|-
| 471 || 22-L || 443,543 || Test sign of dividend
|-
| 472 || 13-P || 217 || Set up bus address
|-
| 473 || 19-N || 413,417,433,437, 453,457,473,477 || Shift right (partial product, multiplier), decrement counter
|-
| 474 || 14-G || 513 || Increment RDST
|-
| 475 || 14-J || 513 || Fetch destination address
|-
| 476 || 14-L || 552 || Increment PC
|-
| 477 || 19-S || 607 || Store upper product
|-
| colspan = "4" |   
|-
| 500 || 25-C || 512 || Clear BX to indicate C bit = 0
|-
| 501 || 25-M || 651 || No operation
|-
| 502 || 19-I || 403 || Zero R17 and B
|-
| 503 || 19-B || 405,505 || Put multiplier in R12 and test sign
|-
| 504 || 26-D || 560 || Fetch new PSW
|-
| 505 || 19-C || 603 || Put one's complement of multiplier in R13
|-
| 506 || 14-D || 510 || Increment PC
|-
| 507 || 19-F || 604 || Shift right (100000, 100000)
|-
| colspan = "4" |  
|-
| 510 || 14-P || 514 || Determine address of destination address
|-
| 511 || 20-K || 611 || Set C bit
|-
| 512 || 24-C || 445,447,545 || Store upper result, test sign of Z bit
|-
| 513 || 14-R || 520 || Setup bus address, enable previous mode
|-
| 514 || 14-Q || 513 || Fetch destination address
|-
| 515 || 20-F || 611 || Clear C bit
|-
| 516 || 24-B || 512,516 || Shift upper part of operand
|-
| 517 || 24-O || 707 || Fetch lower part of operand
|-
| colspan = "4" |  
|-
| 520 || 14-S || 000 || Output data to destination address
|-
| 521 || 21-C || 613 || Fetch lower dividend
|-
| 522 || 17-J || 523 || Shift BREG left one bit
|-
| 523 || 17-K || 000 || Add offset to PC
|-
| 524 || 22-V || 000 || Set V bit
|-
| 525 || 17-M || 527 || Fetch top of stack
|-
| 526 || 22-R || 616 || Clear V bit
|-
| 527 || 17-N || 533 || Step stack to pointer
|-
| colspan = "4" |  
|-
| 530 || 22-G || 431,531 || Clear U bit
|-
| 531 || 22-I || 616 || Set V bit
|-
| 532 || 22-H || 431 || Clear N bit, set Z bit
|-
| 533 || 17-O || 000 || Load stack data into destination register
|-
| 534 || 22-Q || 426,526 || Clear V bit
|-
| 535 || 17-GG || 537 || Step SP
|-
| 536 || 22-P || 526 || Clear N bit, set Z bit
|-
| 537 || 17-HH || 450 || Fetch top of stack
|-
| colspan = "4" |  
|-
| 540 || 26-KK || 741 || Clear IR to halt processor
|-
| 541 || 17-S || 000 || Mask and set condition codes
|-
| 542 || 17-Y || 000 || Mask and set condition codes
|-
| 543 || 22-M || 614 || Srore remainder
|-
| 544 || 22-E || 615 || Srore remainder
|-
| 545 || 24-F || 635 || Save BX in B, set N bit
|-
| 546 || 17-CC || 547 || Calculate offset
|-
| 547 || 17-DD || 000 || Subtract offset from PC
|-
| colspan = "4" |  
|-
| 550 || 24-M || 641 || Clear C bit
|-
| 551 || 17-G || 561 || Data to R5
|-
| 552 || 14-M || 513 || Determine destination address
|-
| 553 || 17-B || 555 || Shift BREG left, R5 to BXREG
|-
| 554 || 24-L || 641 || Set C bit
|-
| 555 || 17-C || 436 || Add PC to BREG
|-
| 556 || 17-E || 557 || BXREG to PC
|-
| 557 || 17-F || 551 || Fetch top of stack
|-
| colspan = "4" |  
|-
| 560 || 26-E || 562 || R6 <- R6-2, enable stack overflow
|-
| 561 || 17-H || 000 || Step SP
|-
| 562 || 26-F || 566 || Place SP address on bus lines
|-
| 563 || 18-E || 602 || Increment RDST
|-
| 564 || 24-V || 465 || Store lower result, set N bit
|-
| 565 || 18-G || 601 || Increment RDST
|-
| 566 || 26-G || 570 || Output old PSW, enable double bus errors
|-
| 567 || 18-I || 601 || Fetch destination address
|-
| colspan = "4" |  
|-
| 570 || 26-H || 572 || Decrement SP, enable stack overflow
|-
| 571 || 18-K || 574 || Increment PC
|-
| 572 || 26-I || 573 || Place SP address on bus lines
|-
| 573 || 26-J || 577 || Push old PC on stack
|-
| 574 || 18-L || 601 || Determine destination address
|-
| 575 || 18-N || 576 || Increment PC
|-
| 576 || 18-O || 600 || Determine address of destination address
|-
| 577 || 26-K || 646 || Decrement vector address
|-
| colspan = "4" |   
|-
| 600 || 18-P || 601 || Fetch destination address
|-
| 601 || 18-Q || 602 || Fetch multiplicand/divisor
|-
| 602 || 18-R || 400,401 || Load step counter, test IR9 for multiply/divide
|-
| 603 || 19-E || 407,507 || Test two's complement of multiplier
|-
| 604 || 19-G || 605 || Load B and R5 with 040000
|-
| 605 || 19-H || 610 || Zero lower product
|-
| 606 || 19-K || 407,427 || Test LSB of BX for first multiply step
|-
| 607 || 20-A || 610 || Store lower product
|-
| colspan = "4" |  
|-
| 610 || 20-B || 701 || C out is the sign of the product
|-
| 611 || 20-M || 000 || Transfer condition codes to PSW
|-
| 612 || 21-B || 421,521 || Fetch upper dividend and test sign
|-
| 613 || 21-D || 423,623 || Take two's complement of lower dividend
|-
| 614 || 22-F || 530,532 || Store quotient, clear N bit
|-
| 615 || 22-O || 534,536 || Store quotient, set N bit
|-
| 616 || 22-T || 617 || Clear C bit
|-
| 617 || 22-U || 000 || Transfer condition codes to PSW
|-
| colspan = "4" |  
|-
| 620 || 22-X || 000 || Set C bit
|-
| 621 || 23-E || 633 || Increment RDST
|-
| 622 || 23-G || 632 || Increment RDST
|-
| 623 || 21-E || 424,524 || Take two's complement of upper dividend
|-
| 624 || 23-I || 632 || Fetch destination address
|-
| 625 || 23-K || 626 || Increment PC
|-
| 626 || 23-L || 632 || Determine destination address
|-
| 627 || 23-N || 630 || Increment PC
|-
| colspan = "4" |  
|-
| 630 || 23-O || 631 || Determine address of destination address
|-
| 631 || 23-P || 632 || Fetch destination address
|-
| 632 || 23-Q || 633 || Fetch shift count
|-
| 633 || 23-R || 430,434 || Test sign of counter
|-
| 634 || 24-G || 636 || Set Z bit
|-
| 635 || 24-H || 636 || Clear Z bit
|-
| 636 || 24-I || 454,554 || V bit <- OVX
|-
| 637 || 24-J || 550,554 || V bit <- OVX
|-
| colspan = "4" |  
|-
| 640 || 21-J || 442,446 || Add divisor to remainder, test counter sign
|-
| 641 || 24-N || 000 || Transfer condition codes to PSW
|-
| 642 || 14-E || 25x || Increment SP
|-
| 643 || 13-Q || 455 || Fetch destination address
|-
| 644 || 14-T || 642 || Move stack data to R12
|-
| 645 || 17-FF || 535 || Data to PC
|-
| 6464 || 26-L || 320 || Fetch new PC
|-
| 647 || 26-CC || 654 || Add 2 to R15
|-
| colspan = "4" |  
|-
| 650 || 21-K || 442,446 || Add divisor to remainder, test counter sign
|-
| 651 || 25-N || 464,466,564 || Store upper result, test sign of Z bit
|-
| 652 || 25-H || 753 || Clear BX so that 0's shift into B
|-
| 653 || 25-E || 653,657 || Shift double operand left, decrement counter
|-
| 654 || 26-DD || 656 || Set R15 to 5
|-
| 655 || 25-K || 512 || Clear BX to indicate C bit is 0
|-
| 656 || 26-EE || 201 || Set R15 to 013
|-
| 657 || 25-F || 651,751 || Test R17 to determine C bit
|-
| colspan = "4" |  
|-
| 660 || 21-H || 442,446 || Subtract divisor from remainder, test counter sign
|-
| 661 || 5-O || 261 || Increment PC
|-
| 662 || 6-M || 271 || Increment PC
|-
| 663 || 15-I || 675 || Increment RDST
|-
| 664 || 15-K || 666 || Increment RDST
|-
| 665 || 15-N || 666 || Fetch destination address
|-
| 666 || 15-L || 675 || Fetch destination operand
|-
| 667 || 15-P || 671 || Increment PC
|-
| colspan = "4" |  
|-
| 670 || 21-I || 442,446 || Subtract divisor from remainder, test counter sign
|-
| 671 || 15-Q || 666 || Determine destination address
|-
| 672 || 15-S || 673 || Increment PC
|-
| 673 || 15-T || 674 || Determine address of destination address
|-
| 674 || 15-U || 666 || Fetch destination address
|-
| 675 || 15-B || 676 || Set R17 to all 1's
|-
| 676 || 15-C || 677 || Set R17 equal to PSW address
|-
| 677 || 15-D || 704 || Place PSW address on bus address lines
|-
| colspan = "4" |   
|-
| 700 || 17-BB || 546 || Swap bytes, shift BREG left
|-
| 701 || 20-N || 410,412 || Test upper product for zero
|-
| 702 || 17-AA || 000 || No operation
|-
| 703 || 24-R || 723 || Clear counter to indicate C bit is 0
|-
| 704 || 15-E || 000 || Output destination operand to PSW
|-
| 705 || 16-B || 000 || Move R12 to RDST
|-
| 706 || 16-D || 217 || Move PSW data to R12
|-
| 707 || 24-Q || 703,707,723,727 || Shift double operand right, increment counter
|-
| colspan = "4" |  
|-
| 710 || 16-H || 717 || Increment RDST
|-
| 711 || 16-K || 717 || Fetch destination address
|-
| 712 || 16-M || 713 || Increment PC
|-
| 713 || 16-N || 717 || Determine destination address
|-
| 714 || 16-P || 715 || Increment PC
|-
| 715 || 16-Q || 716 || Determine address of destination address
|-
| 716 || 16-R || 717 || Fetch destination address
|-
| 717 || 16-I || 706 || Place destination address on bus address lines
|-
| colspan = "4" |  
|-
| 720 || 26-HH || 741 || Clear IR to halt processor
|-
| 721 || 26-Z || 737 || Shift B left, zero B LSB
|-
| 722 || 26-Q || 734 || Put all 1's in the PC
|-
| 723 || 24-S || 464,466,564 || Store upper result, test sign of Z bit
|-
| 724 || 26-S || 735 || Move all 1's to B
|-
| 725 || 26-AA || 540,740 || Increment PC, branch on COUT
|-
| 726 || 26-II || 741 || Clear IR to halt processor
|-
| 727 || 24-P || 703,707,723,727 || Shift double operand right, increment counter
|-
| colspan = "4" |  
|-
| 730 || 26-JJ || 741 || Clear IR to halt processor
|-
| 731 || 26-O || 733 || Clear PC
|-
| 732 || 26-U || 736 || Move 016 to counter
|-
| 733 || 26-P || 720,722 || Test for 0 PC
|-
| 734 || 26-R || 724,726 || Test for 0 PC
|-
| 735 || 26-T || 730,732 || XOR PC and B
|-
| 736 || 26-V || 743 || Clear B
|-
| 737 || 26-X || 742 || Move B to BX
|-
| colspan = "4" |  
|-
| 740 || 26-BB || 647 || Clear R15
|-
| 741 || 26-LL || 000 || No operation
|-
| 742 || 26-Y || 721,725 || Add PC and BX, decrement count
|-
| 743 || 26-W || 737 || Put 1 in B
|-
| 744 || 17-JJ || 000 || Data to PSW
|-
| 745
|-
| 746
|-
| 747
|-
| colspan = "4" |  
|-
| 750
|-
| 751 || 25-G || 651 || Set counter to indicate C bit is 1
|-
| 752
|-
| 753 || 25-I || 753,757 || Shift single operand left, decrement counter
|-
| 754
|-
| 755 || 25-L || 512 || Set BX to indicate C bit is 1
|-
| 756
|-
| 757 || 25-J || 655,755 || Test R17 to determine C bit

|}

Notes:

1 - prints say 346; '6' written for '0'
 
2 - prints say 375; digit swap
 
3 - prints say 540; digit swap
 
4 - prints give a different 'next' from a microcode dump

+ - This is the main instruction decode multi-way branch. Possible next microinstructions include:

* 11x (indirect to 05x, 07x, 06x)
* 04x, 16x, 02x, 15x, 03x, 17x, 10x, 25x, 12x, 13x, 22x, 23x (instructions)
* 003, 004, 006, 007, 011, 014, 020, 150, 200, 260 (individual instructions)
* 270, 210, 240, 140 (simple instructions)

==External links==

* [http://www.bitsavers.org/pdf/dec/pdp11/1134/m8266_ucode.out.txt Dump of KD11-EA microcode on BitSavers] (in symbolic form)

[[Category: PDP-11 UNIBUS Processors]]

Talk:XENIX

2024-10-03T22:05:32Z

ForOldHack: /* PDP-11 versions */ There is NO DEC LSI-11 System, only CPU card.

==Recent updates==

Notes:
I listed the languages in alphabetical order,
except for 'C' as this is always a given for UNIX/xenix/linux/GNU systems.

I will research and add the release dates for as much as I can find.

I added links for references,
I added architectures,
and I will add a list of both
distribution repositories,
and running emulators and VMs.
( one click runs. )

How would Microsoft have gotten the first version of XENIX to run on a PDP-11,
i.e. what was their development machine/OS? PDP-11/RSTS-e?
I am wildly guessing, as besides the Zilog 8k, this architecture PDP-11,
which seems to be a specialty around here, I have never used. [[User:ForOldHack‎|ForOldHack‎]] ([[User talk:ForOldHack‎|talk]]) 22:02, 9 March 2019 (CET)

: There's a lot of PDP-11 ''hardware'' stuff documented, because I have a particular interest in them - I used them extensively at the start of my career. DEC ''software'' is not covered much, as we didn't use it - just Unix, which I have been covering.
: I have no idea what uSloth would have used for a PDP-11 port - did they really do one? They'd have needed a C compiler, and that would have been a lot of work (unless they used an existing one - maybe they brought up V7 on a PDP-11)? [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:25, 10 March 2019 (CET)

::They used a PDP-11 for a vast amount of their development, because the POS known as DOS could not do it, and they had a cross compiler on the PDP-11 for x68.
:::"1981: MS's Bob Greenberg ports PDP-11 v7 (from HCR or AT&T?) to Codata Z8000" http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml
::The history was unconceiling itself rather slowly, in leaps and bounds
::Apprently they used a PDP-11 to develop Xenix, and then soon switched to it, and used it for everything until they kluged together NT server, and even then ... I bet they still have a few things running in emulation... [[User:ForOldHack‎|ForOldHack‎]] ([[User talk:ForOldHack‎|talk]]) 07:45, 11 March 2019‎

== Humor ==

"where it still languishes today." This will remain as homage to the spirit of this wiki. [[User:ForOldHack‎|ForOldHack‎]] ([[User talk:ForOldHack‎|talk]])
07:40, 11 March 2019‎

== Version info project ==

Here is a bunch of version information:
"Having previously appointed myself SCO Director of Acronyms

http://www.cruzio.com/sco/
and keeper of the mysterious
OSR5 BTLD naming conventions,
I'll now declare myself MOSCOVA (Minister Of SCO Version Archaeology) and prepare a list of the last known versions of various dead SCO products, and the secret incantations necessary to determine if one really has that version. Please consider this a chain letter and forward it to any likely conspirators with useful information. The last person in the chain gets stuck with turning this into a TA. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|ForOldHack]]) 05:20, 6 December 2020

=== Version info: ===
SCO has many ways of identifying products and displaying version information.
Some of them actually agree.
1. Read the disk, tape or cd label.
2. tar tvf /dev/install | grep "#rel"
3. swconfig
4. grep "^#rel=" /etc/perms/*
5. uname -a (old Xenix 286 only)
6. uname -X | grep -y "rel" (OS only)

I suggest:
cd /etc/perms
grep "^#rel=" * | tr ":" "\011"
and:
swconfig
to get a shopping list.

If you have floppy images that are not easily identified, try:

strings image_file | grep "rel="
to extract the "custom" info line.
If the image is compressed,
run:
zcat imagefile.Z | strings | grep "rel="

There are also various names for the same products.
For example:

xnx296a, UFN and prd=xos are all the same.
Obtaining serial number information, and identifying cd roms
without proper labels, will be covered separately.

( If you enjoy headaches, read xnx296a https://www.scosales.com/ta/kb/103396.html

== XENIX 286 ONLY ==
Name Last Version Incantation

SCO Xenix 286 2.3.2 uname -a
DevSys 286 2.2.1 grep "^#rel=" /etc/perms/devsys
CGI 286 grep "^#rel=" /etc/perms/cgi
Text Processing System grep "^#rel=" /etc/perms/text
Eroff 2.0
VP/IX 286
MultiView 286
Man Pages
Games 2.2.2 grep "^#rel=" /etc/perms/games
Fox (dbase 2 clone)
MSBASIC 5.41 Appears on startup screen.
MultiPlan 3.00N
MS Word 3.0

== XENIX 386 ONLY ==

SCO Xenix 386 2.3.4 uname -X | grep -y "rel"
Tandy Xenix 386
Unisys Xenix 386
DevSys 386 2.3.0 grep "^#rel=" /etc/perms/devsys
Text Processing Sys
Man Pages 2.2.0 ???? grep "^#rel=" /etc/perms/man
Games
TCP/IP 1.2.0 grep "^#rel=" /etc/perms/tcprt
Streams runtime 1.0.0c grep "^#rel=" /etc/perms/streamsrt
Xenix-Net
UniPATH SNA-3270
Xsight for Xenix 2.0.0
Xsight for DOS 2.0.0
Xsight 386 complete 5.0.0
SCO Office Portfolio 2.0.1
SCO Manager 2.1
Multiview Runtime 1.6 ????
SCO Professional 2.1 grep "^#rel=" /etc/perms/pro
SCO Lyrix 6.1
Integra 1.1.1
Foxbase+ 2.1.2 Appears on startup screen.
HCR/SCO C++ 3.0.0
SCO C++ 3.1.0
SCO Accell
VP/IX 1.2.0 grep "^#rel=" /etc/perms/vpix
MS Word 3.0
ImageBuilder
MasterPlan
Statistician
Eroff 3.0
MS C 3.0
MS Basic Interpreter 5.41 Appears on startup.
MS Basic Compiler
MS Pascal Compiler
MS Fortran Compiler 3.0
LPI-Fortran 3.20.00
LPI-Basic
LPI-Cobol
LPI-Pascal
LPI-PL/I
LPI-RPG II
LPI-Debug
SCO PHIGS 1.0.0

== UNIX (ODT) ONLY SCO Open Desktop ==

SCO Unix 3.2v4.2 uname -X | grep -y "rel"
TCP/IP 1.2.1
LLI 3.4.0
DevSys 3.2.4.2
TCP/IP Dev Sys 1.2.1
Games 3.2.2
NFS Sys 1.1.1d
NFS Dev Sys 1.1.1c
Xsight 386 4.0.0
Xsight 386 Dev 4.0.0

=== Third Party ===

JTAPE for Xenix 386 2.55 grep "^#rel=" /etc/perms/jt
JTAPE for Unix 3.2 2.6 grep "^#rel=" /etc/perms/jt
(No JTAPE available for 286 or OSR5)."

[[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|ForOldHack]]) 05:20, 6 December 2020

== Capitalization ==

All the contemporary uSloth material pictured in various sources always spells it with caps - "XENIX". Which is a problem, because various practitioners using it back then spelled it 'Xenix', and that form is common/usual now. I'm not going to fix anything, but places that use "XENIX" are correct, so it's probably best not to 'fix' them. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:42, 24 November 2022 (CET)

: I have decided to fix it. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 19:21, 21 October 2023 (CEST)

== History Errors ==

I have found a lot of history, most of which the definitive sources are just plain wrong:

"V7 (7/79) also gave rise to several Unix ports: the 32-bit implementations as well as XENIX2, a Microsoft-Santa Cruz Operation collaboration, which was the first Unix implementation for the Intel 8086 chip (XENIX1 was based on V6). V7 also gave rise to Unix for the Z8000 and 68000 chips." -P Salus. pg 168. "A Quarter Century of UNIX."

https://wiki.tuhs.org/lib/exe/fetch.php?media=publications:qcu.pdf

Unix version 7, was the first 32bit implementation on a VAX, and Bill Joy added virtual memory over the Christmas break.
It is unknown whether that HCR or Microsoft ever got a hold of the Tape-2 from Ken Thompson.

XENIX2? Xenix-11 was the HCR port that Microsoft paid for them to do, to get both UNIX running on their PDP-11, and to add as much pollute and dilute ( their first attempt ), of BSD, and not much more than that and a name change. The Santa Cruz connection came later, first as consultants, then a whipping boys for all the poor work by MS.

The first implementation on the Intel 8086 chip, ( not the 8088 ), was by Intel.
Xenix-1(286)(1984) was after Xenix-11 (PDP-11), the 68000 ports were to RS TRS-80 Model 16, Sirtek M68000 card, The IBM 9000, and Sun-2s, ( Microsoft Internal use ), The Apple Lisa 2 and Fortune 32:16. ( the manuals were little more than V7 line printer pages, with little to reflect the actual underlying changes. ). The Z8000 port was so rare, that no archive exists, although there were announcements, there was no documented shipping/running/manual. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|ForOldHack]]) 07:37, 20 April 2023‎ (CET)

== The documented history of Xenix-11, Xenix-1, Xenix-3, and SCO System V, Xenix 386, 286 and 8086. ==

in Brief:
Platform Release
PDP-11 Xenix-11. This is what the Living Computer Museum supposedly has a tape of, and that someone got from HCR a few days earlier.
286* Intel Xenix-1.0 This is what Microsoft shipped in Oct 1984, (c) 1984, only to have an IBM Deal announced two months later.
M68000 Xenix-3 This was the most popular Xenix version with Radio Shacks TRS 80IIb.
286, 86 SCO System V
286, 386, Microchannel SCO System V.2

** This is the skeleton of the article re-write **
If this seems confusing? Hold on to your seats, it gets hugely confusing.

The list of Xenix ports:

Unix System 7 -> Microsoft paid HCR, Montreal, CA to port Unix System 7 to their PDP-11 machine.
1978~1981 Vaporware - used internally on PDP-11s for email, and to try and get the portable C compiler to output Intel Binaries.

It exists as a brochure, and maybe a mag tape at LCNM+L? but until its read, its unknown. I would bet its only the HCR port with the name change.

1981 Xenix-11 (for DEC PDP and VAX ) was announced, but since the VAX already had UNIX, no one was interested,
except for one tiny vendor who, instead of getting Xenix-11 from Microsoft, got it from HCR.

1982-02-02 Intel i80286 Introduced. ( This CPU and architecture was the great hope for multi-user systems, but it turned out to be "brain-dead" -Bill G. )

Everything Happened at once, in 1984. Intel shipped ( Xenix for 330 [Intel i80286], Radio Shack shipped[M68000], IBM Announced: IBM Xenix 1.0 [ IBM AT ]
( even though the IBM S9000 had both SO:OS and Xenix-3, Based on System-III)

Next up was Unix System III,
which was for Xenix-1, and Xenix-3, 3.2, 3.5 ( This was for the 68000 chips, and the Intel-SBC-286)

For the Fortune 31:16: "Fortune Operating System (FOR: PRO) is based on UNIX version 7, with
additional utilities from the University of California at Berkeley 4.1 UNIX, and the
Bell Laboratories UNIX System 3[ III ]. " http://bitsavers.org/pdf/fortuneSystems/service/1001240-05_Fortune_32-16_Field_Service_Manual_Apr1987.pdf

Which the description sounds exactly line Xenix-1 [ System

then Unix System V, which was the 286, and 8088 port for the IBM AT and the IBM PC,
with SCO's name on it, which was the basis for IBM Xenix 1.0, [Unix System V + BSD Utilities ]

and then followed by Unix System V.2
Which was the basis for IBM Xenix 2.0, and SCO System V Xenix 3.2.3.

"Is Unix big-endian or little endian?
In the SAS System, the following platforms are considered big endian: IBM mainframe, HP-UX, AIX, Solaris, and Macintosh. The following platforms are considered little endian: VAX/VMS, AXP/VMS, Digital UNIX, Intel ABI, OS/2, and Windows."
However... Intel spilled the beans about Intel's compiler:

"Xenix 286 Installation and Configuration - Release notes: Nov-84
"The original C compiler supported by XENIX 86 and XENIX 286 was developed by Dennis Ritchie at Bell Laboratories.
It was originally designed in 1973 around the PDP 11/44 architecture. In the late 1970's and early 1980's, the compiler was modified to support Intel's iAPX 8086 microprocessor. With the first release of this compiler, Microsoft Corporation chose to support the same 32-bit ordering supported under the Ritchie compiler. Meanwhile, with the design of the 8087 Fast Floating Point microprocessor, Intel also standardized a 32-bit ordering for the iAPX 8086 architecture. Intel, however, chose the same byte ordering that Digital Equipment Corporation selected for its VAX family of computers. Consequently, Microsoft 32-bit ordering is incompatible with the Intel 8087, 287, and 386 processors' 32-bit ordering."

"For the iAPX 8087 and 287 components to correctly interpret long values, the C compiler must perform a sequence of manipulations. For example, in order to provide support for the 8087 math component, the compiler generates instructions to swap the low word (bytes 0 and 1) with the high word (bytes 2 and 3). The 8087 then is able to operate on the representation it expects. Once the 8087 has completed an operation on a 32-bit value, the two words are swapped back.
In 1983, Microsoft and Intel were involved in the design of two strategically important projects. Microsoft was developing a new state-of-the-art compiler construction tool and a new C compiler for XENIX 286. At the same time, Intel began a project to support the Universal Development Interface (UDI) and translators .., for XENIX 286. During the development period, the two companies discovered the incompatibility. After careful analysis, they decided that Microsoft would make the data representation of 32-bit values compatible with the Intel architecture."

Microsoft-C was little-endian and Intel was big-endian or really,
The DEC VAX was Byte order 3412 ( i.e. Word 2, followed by word 1), and intel was 1234 ( word 1 followed by word 2) , but Microsoft's C compiler for Xenix was 3412, until at least June of 1986, when the 386 came out, which most unfortunately, hampers the performance of Xenix on the i80286 and the i8086, and the i8088. On the Motorola when upgraded to a 68020, there is a barrel shifter which can change the byte ordering in 1 cycle, so Motorola, never cared about the byte ordering.
"The data section performs all data operations, such as immediate data value moves . It also contains the barrel shifter, which performs one-cycle shifts of any amount on data." [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|ForOldHack]]) 07:37, 22 April 2023‎ (CET)

: The barrel shifter is irrelevant, the issue is the order of short-words in a long-word; switching them around involves plain moves.
: In general, ordering of bytes within words is a function of the [[instruction set architecture]]; i.e. it is built into the ''hardware'' on machines that implement that ISA. Compilers generally have ''no choice'' but to use the byte ordering that is native to the ISA.
: The original C compiler for the 8086 was a bit of an exception to that; the 8086 ISA didn't support long-words ''at all'' - so in that case, the compiler writers ''did'' get to make a choice. Unfortunately, they made the wrong one - they went with the screwy PDP-11 one (which is half big-endian - for the short-words within long-words, and half little-endian - for the bytes within short-words.) [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 00:55, 23 October 2023 (CEST)

== PDP-11 versions ==

The list entry "ran on a LSI-11/34" is confused; there is no such thing as an "LSI-11/34". This might refer to a [[PDP-11/34]] (which IIRC was used at one point for XENIX work at uSloth) or a [[PDP-11/23]], which is ''almost'' identical, programming-wise, to a PDP-11/34. (To the point that it was pretty trivial to move [[V6 UNIX]] from the [[PDP-11/40]] on which it ran natively, which is also very similar to these two, to the 11-23: see [[Running UNIX V6 on an -11/23]]) [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 23:15, 18 July 2024 (CEST)

: The PDP-11/34 was distinct from the LSI-11/34 being of a different type of silicon.
:*[[LSI-11]]

: The CPU Cards are different. The PDP-11 uses discreet logic.
: The LSI-11 used the [[LSI-11 chip set]].

: The history was that H** ported UNIX to the PDP-11/34, and then
: gave it to Microsoft to run on a LSI-11/34: Which is in pictures of Bill Gates computer collection,
: and then... Microsoft ran it on VAX-11/780. All of this is internal use only so its all based on historical posts,
: and not the analysis of data graveyards. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|ForOldHack]]) 22:56, 19 July 2024

:: I know all about the various PDP-11's; I worked very extensively with all of them.
:: The point is that there is ''no such thing'' as a "LSI-11/34". {fact checked as weird - due to MS Marketing}
:: Almost everything with 'LSI-11' CPU's is QBUS (with the exception of the [[PDP-11/24]] - {fact checked as true}
::: and it uses the [[F-11 chip set]], so it's technically not an LSI-11 anyway);
::: the -11/34 is a UNIBUS machine (and it uses a bespoke CPU, the [[KD11-E CPU]], which is not shared with any other machine). {fact checked as true}
:: Try finding "LSI-11/34" in ''any'' DEC document - one can't. ''It does not exist''. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 18:49, 20 July 2024 (CEST)

::Yes, I quite agree, and disagree.
::DEC Never sold a LSI-11 computer. They sold a PDP-11/03 with a Western Digital LSI-11 processor in it,
:: the LSI-11/34 is NOT a DEC product, its a Microsoft labeled machine.
:: "This PDP-11/23 was originally a PDP-11/03, but it was upgraded with the 11/23 CPU module."
:: It is unknown at this time, whether they upgraded the LSI-11 with a 11/23 or what happened,
:: BUT you can pretty much guarantee that it had little to do with DEC, and all to do with Microsoft's random directions.
:: The source of this information is the picture, and the head of MS Marketing for Xenix, which it means lies like a ambulance chasing lawyer.
:: But there is the name, Western Digital Sold PDP-11/03s as their machine the LSI-11/03, but the real problem,
:: In the photo of Bill Gates, I cannot make out the name on the Machine if its a DEC PDP-11/03 or the Western Digital Branded 11/03-LSI-11. ( The name plate was removed )
:: I was not there, but I have a picture, and videos.
:: And of the PDP-11/34, there is a video. Its a Microsoft guy, and I am going to tell you what I think of Microsoft guys: Untrustworthy.
:: https://www.youtube.com/watch?v=XT6t2L3SVM8&t=2s

== Some errors but we have a lot more actual dates ==

[https://www.abortretry.fail/p/the-history-of-xenix The History of XENIX]

Unix was originally created to run on mainframes, but eventually moved on to other systems. One of the first companies outside of AT&T to sell Unix was named Interactive Systems Corporation. Interactive Systems Corporation was founded by Peter G. Weiner in 1977. (Weiner was Brian Kernighan’s Ph.D. advisor. Kernighan was one of the creators of Unix.)

ISC produced a number of Unix based products, including a port of Unix to the IBM PC named PC/IX. PC/IX was followed in 1985 by 386/ix. While PC/IX was based on UNIX System III, 386/ix was based on UNIX System V, Release 3. Later, the operating system was renamed INTERACTIVE UNIX System V/386 and rebased on UNIX System V, Release 3.2. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|ForOldHack]]) 22:56, 19 July 2024

Repairing un-documented MOS memory boards

2024-08-26T02:16:41Z

ForOldHack: /* minor edit sp */ analyZer.

It is usually possible, even without schematics, to repair [[Metal Oxide Semiconductor|MOS]] [[main memory|memory]] [[printed circuit board|boards]] where the board is basically working, but just has some failing [[bit]]s.

The first step is to see if the failures are usually static (i.e. always at the same [[address]]). If not, the issue may be the [[power supply]], or [[circuit]]ry on the board which creates needed [[voltage]]s; this page does not cover those cases. However, static errors probably indicate a failing/failed [[integrated circuit|chip]], a common failure mode of old MOS memory chips.

The first step in working with one of them, without a circuit diagram, is to create a table which translates memory chip to bits.

First, one has to understand the high-level layout of the memory: examine the memory chips to see if they are YYKx1 - i.e. one bit wide. (The techniques below will work on multi-bit chips, using obvious changes, but since single-bit chips are the most common on older memory cards, the writeup here focuses on them.) Knowing the width of the [[bus]], and the number of chips, will give the number of banks of memory (needed for the table). For example, on a [[UNIBUS]] or [[QBUS]] memory card, the bus is 16 bits wide, so if there are 32 chips in the array, there will probably be 2 banks, each 16 bits wide.

From there, there are two basic techniques to populate the table:

* physically pulling chips
* use of a [[program]] and [[logic analyzer]] or [[oscilloscope]]

The choice of which one to use will depend on personal preferences, along with factors such as if the chips are [[chip socket|socketed]] (common on MOS memory boards, to simplify repairs).

==Pulling chips==

The general approach is to pull a chip, and then store data in memory, and read it back, to try and work out which bit that chip is. Having done that, then repeat with other chips to try and work out which bits are stored in which chips. (Unless the designers were doing something very strange, each chip will hold the same bit in all the [[word]]s in that bank.)

Usually a missing chip results in bits stored in that chip reading as '0', but it's possible they will read back as '1'. (The [[MSV11-J QBUS memory]] operates in the latter way, for instance.) To test for the first possibility, start by finding a location in each bank that can be written to all 0's and all 1's (read back after writing, to verify).

Then pull a chip, and then write all 1's to that word in each bank, and read it back. If one now has a 0 bit, congratulations: i) that verified that missing chips read as '0', ii) indicates which bank that chip is part of, and iii) the 0 bit indicates which bit that chip is - fill in that entry in the chip<->bit chart.

If not, try writing 0's to the words in each bank, and check for a '1' bit: if so, i) missing chips read as 1, etc. If neither this or the above is true, there's an issue.

Otherwise, try pulling another chip, and work out which bit that one is, and add it to the chart. Repeat for all the memory chips - although if you're lucky, after a couple you might find a pattern, and be able to predict which chips hold which bits. (But not always; many are random; see e.g. [[Q-RAM 11]] and [[NS23M]] for boards in which the bit assignment to chips is fairly random.) If there does seems to be a pattern, do a few spot tests of the predictions to make sure the hypothesized pattern is correct.

==Using a program==

The previous technique is viable if the memory chips are in sockets, which makes the chip removal needed, less painful. If the chips are soldered in, that technique is not really feasible.

For such boards, storing a word with a single '1' bit, can be used to the same effect. To start, the data sheet for the memory chips used will indicate which pin is the 'data in' pin. Connect the test device (either a logic analyzer, or oscilloscope, can be used) to that pin.

Write a very short program which [[loop]]s, storing a word in memory. Start with a word containing only a single '1' bit, and try using a destination location in each bank, looking for a '1' being written to that chip (you can trigger off the 'write' input to the chip; although some boards, e.g. the [[MSV11-Q QBUS memory|MSV11-Q]], send a 'write' to all the chips, and select the one to actually use by use of the RAS or CAS signal) to see if i) your probe is on the chip which corresponds to that bit, and ii) the chip is in the bank currently under test.

If not, use a word with a different bit set, and repeat. (Changing the word contents, while remaining on the same chip, will almost certainly be easier than keeping the data constant, and trying different chips.) By 'floating' the 1 bit along the word, it ''should'' be possible to work out which bit is stored in that chip.

Once that chip has been identified, move onto the next chip. Again, after a few chips have been done, it may be possible to see a pattern. (This technique was used to produce the bit charts for the [[MSV11-J memory module|MSV11-J]] and [[MSV11-Q QBUS memory|MSV11-Q]].)

==Repair==

With the completed chart in hand, given a failing word (address and bad data), it is possible to work out which chip is at fault, and it can be replaced.

[[Category: Memory Basics]]

Repairing un-documented MOS memory boards

2024-08-26T02:14:27Z

ForOldHack: /* Using a program */ added a comma.

It is usually possible, even without schematics, to repair [[Metal Oxide Semiconductor|MOS]] [[main memory|memory]] [[printed circuit board|boards]] where the board is basically working, but just has some failing [[bit]]s.

The first step is to see if the failures are usually static (i.e. always at the same [[address]]). If not, the issue may be the [[power supply]], or [[circuit]]ry on the board which creates needed [[voltage]]s; this page does not cover those cases. However, static errors probably indicate a failing/failed [[integrated circuit|chip]], a common failure mode of old MOS memory chips.

The first step in working with one of them, without a circuit diagram, is to create a table which translates memory chip to bits.

First, one has to understand the high-level layout of the memory: examine the memory chips to see if they are YYKx1 - i.e. one bit wide. (The techniques below will work on multi-bit chips, using obvious changes, but since single-bit chips are the most common on older memory cards, the writeup here focuses on them.) Knowing the width of the [[bus]], and the number of chips, will give the number of banks of memory (needed for the table). For example, on a [[UNIBUS]] or [[QBUS]] memory card, the bus is 16 bits wide, so if there are 32 chips in the array, there will probably be 2 banks, each 16 bits wide.

From there, there are two basic techniques to populate the table:

* physically pulling chips
* use of a [[program]] and [[logic analyser]] or [[oscilloscope]]

The choice of which one to use will depend on personal preferences, along with factors such as if the chips are [[chip socket|socketed]] (common on MOS memory boards, to simplify repairs).

==Pulling chips==

The general approach is to pull a chip, and then store data in memory, and read it back, to try and work out which bit that chip is. Having done that, then repeat with other chips to try and work out which bits are stored in which chips. (Unless the designers were doing something very strange, each chip will hold the same bit in all the [[word]]s in that bank.)

Usually a missing chip results in bits stored in that chip reading as '0', but it's possible they will read back as '1'. (The [[MSV11-J QBUS memory]] operates in the latter way, for instance.) To test for the first possibility, start by finding a location in each bank that can be written to all 0's and all 1's (read back after writing, to verify).

Then pull a chip, and then write all 1's to that word in each bank, and read it back. If one now has a 0 bit, congratulations: i) that verified that missing chips read as '0', ii) indicates which bank that chip is part of, and iii) the 0 bit indicates which bit that chip is - fill in that entry in the chip<->bit chart.

If not, try writing 0's to the words in each bank, and check for a '1' bit: if so, i) missing chips read as 1, etc. If neither this or the above is true, there's an issue.

Otherwise, try pulling another chip, and work out which bit that one is, and add it to the chart. Repeat for all the memory chips - although if you're lucky, after a couple you might find a pattern, and be able to predict which chips hold which bits. (But not always; many are random; see e.g. [[Q-RAM 11]] and [[NS23M]] for boards in which the bit assignment to chips is fairly random.) If there does seems to be a pattern, do a few spot tests of the predictions to make sure the hypothesized pattern is correct.

==Using a program==

The previous technique is viable if the memory chips are in sockets, which makes the chip removal needed, less painful. If the chips are soldered in, that technique is not really feasible.

For such boards, storing a word with a single '1' bit, can be used to the same effect. To start, the data sheet for the memory chips used will indicate which pin is the 'data in' pin. Connect the test device (either a logic analyser, or oscilloscope, can be used) to that pin.

Write a very short program which [[loop]]s, storing a word in memory. Start with a word containing only a single '1' bit, and try using a destination location in each bank, looking for a '1' being written to that chip (you can trigger off the 'write' input to the chip; although some boards, e.g. the [[MSV11-Q QBUS memory|MSV11-Q]], send a 'write' to all the chips, and select the one to actually use by use of the RAS or CAS signal) to see if i) your probe is on the chip which corresponds to that bit, and ii) the chip is in the bank currently under test.

If not, use a word with a different bit set, and repeat. (Changing the word contents, while remaining on the same chip, will almost certainly be easier than keeping the data constant, and trying different chips.) By 'floating' the 1 bit along the word, it ''should'' be possible to work out which bit is stored in that chip.

Once that chip has been identified, move onto the next chip. Again, after a few chips have been done, it may be possible to see a pattern. (This technique was used to produce the bit charts for the [[MSV11-J memory module|MSV11-J]] and [[MSV11-Q QBUS memory|MSV11-Q]].)

==Repair==

With the completed chart in hand, given a failing word (address and bad data), it is possible to work out which chip is at fault, and it can be replaced.

[[Category: Memory Basics]]

VMS

2024-08-26T02:09:45Z

ForOldHack: /* See also */ added the darker side of VMS upgrades

{{Infobox OS
| image = vms47.png
| caption = Logging into a 4.7 VMS system
| name = VMS
| creator = [[Digital Equipment Corporation]]
| current version = 7.3 (for VAX) 8.4 (for Alpha and Itanium) 9.2 (for x86)
}}

'''VMS ''' is a high-end, secure, [[multi-tasking]] [[operating system]] written by [[Digital Equipment Corporation]] and currently actively maintained by [[VMS Software, Inc.]] (VSI).

It runs on the [[VAX]], [[Alpha]], [[Itanium]], and [[Intel x86|x86]] platforms. Beginning with '''VMS''' V5.5, the OS was renamed to '''OpenVMS'''.

'''VMS ''' has been ported to x86 by VMS Software, Inc..

==Supported machines (by example)==

{| class="wikitable
| Version
| Machines
|-
| VAX/VMS V1.0
| [[VAX-11/780]]
|-
| VAX/VMS V2.0
| [[VAX-11/750]]
|-
| VAX/VMS V3.0
| [[VAX-11/730]]
|-
| VAX/VMS V4.0
| [[VAX 8600]]
|-
| [[MicroVMS]] V4.0
| [[MicroVAX I]] / [[MicroVAX II]]
|-
| VAX/VMS V5.0-2A
| [[VAX 6000 series|VAX 6000]]
|-
| OpenVMS AXP V1.0
| [[Alpha]]
|-
| OpenVMS V8.0
| [[Itanium]]
|-
| OpenVMS V9.0
| [[x86]]
|}

==Emulation==

VMS and OpenVMS can be run on [[SIMH]]'s VAX simulators. OpenVMS can also run on [[ES 40 Emulator]] which will run the Alpha version. Although VMS is still a commercial operating system, just like many varieties of commercial [[UNIX]] and [[Windows]], VMS Software, Inc. (which is the current owner of most of DEC's assets) has a hobbyist program which allows licenses to be obtained for non-commercial uses for the Alpha, Itanium, and x86 platforms.

There are currently no known hobbyist licenses for OpenVMS/VAX versions V5.x and higher.

See the following:

* http://www.wherry.com/gadgets/retrocomputing/vax-simh.html

==See also==

* [[Installing VMS V1.0 on SIMH]]
* [[Customizing VMS V1.0‎‎]]
* [[:Category:VMS Practical Guides|VMS Practical Guides]]
* [[VAXcluster]]
* [[ODS2]]
* [https://gunkies.org/wiki/THE_VAXORCIST Upgrade horror story: Literally. ]

==External links==

* [https://wiki.vmssoftware.com/Main_Page VSI OpenVMS Wiki]
* [https://web.archive.org/web/20170825003059/http://h41379.www4.hpe.com/openvms/os/openvms-release-history.txt OpenVMS release history] (via Wayback machine).
* [https://vmssoftware.com/about/roadmap/#vms-software-support-roadmap VSI OpenVMS Support Roadmap]
* [http://www.vaxarchive.org/hardware/vms-hw.html VAX/VMS Versions] - "which VMS versions are supported on which CPUs"

{{semi-stub}}

{{Nav VAX}}

[[Category: DEC Operating Systems]]
[[Category: VAX Operating Systems]]
[[Category: VMS]]

Talk:John Vincent Atanasoff

2024-08-19T02:08:44Z

ForOldHack: /* Problems */ Printer not found?

=== Problems ===

"the purely electronic portion of it eventually worked fine; its main remaining problem was elsewhere."

I am wondering if this is was also the first historic occurrence of "Printer not found..." [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:08, 19 August 2024 (CEST)

2024-01-11T18:23:57Z

ForOldHack: /* Preservation */

Talk:BASIC

2024-01-11T17:59:42Z

ForOldHack: /* Added link for Dartmouth BASIC GE-235 */

Talk:XENIX

2023-04-22T02:01:59Z

ForOldHack: /* The documented history of Xenix-11, Xenix-1, Xenix-3, and SCO System V, Xenix 386, 286 and 8086. */

==Recent updates==

Notes:
I listed the languages in alphabetical order,
except for 'C' as this is always a given for UNIX/xenix/linux/GNU systems.

I will research and add the release dates for as much as I can find.

I added links for references,
I added architectures,
and I will add a list of both
distribution repositories,
and running emulators and VMs.
( one click runs. )

How would Microsoft have gotten the first version of XENIX to run on a PDP-11,
i.e. what was their development machine/OS? PDP-11/RSTS-e?
I am wildly guessing, as besides the Zilog 8k, this architecture PDP-11,
which seems to be a specialty around here, I have never used. [[User:ForOldHack‎|ForOldHack‎]] ([[User talk:ForOldHack‎|talk]]) 22:02, 9 March 2019 (CET)

: There's a lot of PDP-11 ''hardware'' stuff documented, because I have a particular interest in them - I used them extensively at the start of my career. DEC ''software'' is not covered much, as we didn't use it - just Unix, which I have been covering.
: I have no idea what uSloth would have used for a PDP-11 port - did they really do one? They'd have needed a C compiler, and that would have been a lot of work (unless they used an existing one - maybe they brought up V7 on a PDP-11)? [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:25, 10 March 2019 (CET)

::They used a PDP-11 for a vast amount of their development, because the POS known as DOS could not do it, and they had a cross compiler on the PDP-11 for x68.
:::"1981: MS's Bob Greenberg ports PDP-11 v7 (from HCR or AT&T?) to Codata Z8000" http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml
::The history was unconceiling itself rather slowly, in leaps and bounds
::Apprently they used a PDP-11 to develop Xenix, and then soon switched to it, and used it for everything until they kluged together NT server, and even then ... I bet they still have a few things running in emulation... [[User:ForOldHack‎|ForOldHack‎]] ([[User talk:ForOldHack‎|talk]]) 07:45, 11 March 2019‎

Here is a bunch of version information:
"Having previously appointed myself SCO Director of Acronyms

http://www.cruzio.com/sco/
and keeper of the mysterious
OSR5 BTLD naming conventions,
I'll now declare myself MOSCOVA (Minister Of SCO Version Archaeology) and prepare a list of the last known versions of various dead SCO products, and the secret incantations necessary to determine if one really has that version. Please consider this a chain letter and forward it to any likely conspirators with useful information. The last person in the chain gets stuck with turning this into a TA.

=== Version info: ===
SCO has many ways of identifying products and displaying version information.
Some of them actually agree.
1. Read the disk, tape or cd label.
2. tar tvf /dev/install | grep "#rel"
3. swconfig
4. grep "^#rel=" /etc/perms/*
5. uname -a (old Xenix 286 only)
6. uname -X | grep -y "rel" (OS only)

I suggest:
cd /etc/perms
grep "^#rel=" * | tr ":" "\011"
and:
swconfig
to get a shopping list.

If you have floppy images that are not easily identified, try:

strings image_file | grep "rel="
to extract the "custom" info line.
If the image is compressed,
run:
zcat imagefile.Z | strings | grep "rel="

There are also various names for the same products.
For example:

xnx296a, UFN and prd=xos are all the same.
Obtaining serial number information, and identifying cd roms
without proper labels, will be covered separately.

( If you enjoy headaches, read xnx296a https://www.scosales.com/ta/kb/103396.html

== XENIX 286 ONLY ==
Name Last Version Incantation

SCO Xenix 286 2.3.2 uname -a
DevSys 286 2.2.1 grep "^#rel=" /etc/perms/devsys
CGI 286 grep "^#rel=" /etc/perms/cgi
Text Processing System grep "^#rel=" /etc/perms/text
Eroff 2.0
VP/IX 286
MultiView 286
Man Pages
Games 2.2.2 grep "^#rel=" /etc/perms/games
Fox (dbase 2 clone)

MSBASIC 5.41 Appears on startup screen.
MultiPlan 3.00N
MS Word 3.0

== XENIX 386 ONLY ==
SCO Xenix 386 2.3.4 uname -X | grep -y "rel"
Tandy Xenix 386
Unisys Xenix 386
DevSys 386 2.3.0 grep "^#rel=" /etc/perms/devsys
Text Processing Sys
Man Pages 2.2.0 ???? grep "^#rel=" /etc/perms/man
Games
TCP/IP 1.2.0 grep "^#rel=" /etc/perms/tcprt
Streams runtime 1.0.0c grep "^#rel=" /etc/perms/streamsrt
Xenix-Net
UniPATH SNA-3270
Xsight for Xenix 2.0.0
Xsight for DOS 2.0.0
Xsight 386 complete 5.0.0
SCO Office Portfolio 2.0.1
SCO Manager 2.1
Multiview Runtime 1.6 ????
SCO Professional 2.1 grep "^#rel=" /etc/perms/pro
SCO Lyrix 6.1
Integra 1.1.1
Foxbase+ 2.1.2 Appears on startup screen.
HCR/SCO C++ 3.0.0
SCO C++ 3.1.0
SCO Accell
VP/IX 1.2.0 grep "^#rel=" /etc/perms/vpix
MS Word 3.0
ImageBuilder
MasterPlan
Statistician
Eroff 3.0
MS C 3.0
MS Basic Interpreter 5.41 Appears on startup.
MS Basic Compiler
MS Pascal Compiler
MS Fortran Compiler 3.0
LPI-Fortran 3.20.00
LPI-Basic
LPI-Cobol
LPI-Pascal
LPI-PL/I
LPI-RPG II
LPI-Debug
SCO PHIGS 1.0.0

== UNIX (ODT) ONLY SCO Open Desktop
SCO Unix 3.2v4.2 uname -X | grep -y "rel"
TCP/IP 1.2.1
LLI 3.4.0
DevSys 3.2.4.2
TCP/IP Dev Sys 1.2.1
Games 3.2.2
NFS Sys 1.1.1d
NFS Dev Sys 1.1.1c
Xsight 386 4.0.0
Xsight 386 Dev 4.0.0

=== Third Party ===
JTAPE for Xenix 386 2.55 grep "^#rel=" /etc/perms/jt
JTAPE for Unix 3.2 2.6 grep "^#rel=" /etc/perms/jt
(No JTAPE available for 286 or OSR5)."

== Humor ==

"where it still languishes today." This will remain as homage to the spirit of this wiki. [[User:ForOldHack‎|ForOldHack‎]] ([[User talk:ForOldHack‎|talk]])
07:40, 11 March 2019‎

== Capitalization ==

All the contemporary uSloth material pictured in various sources always spells it with caps - "XENIX". Which is a problem, because various practitioners using it back then spelled it 'Xenix', and that form is common/usual now. I'm not going to fix anything, but places that use "XENIX" are correct, so it's probably best not to 'fix' them. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:42, 24 November 2022 (CET)

== History Errors ==
I have found a lot of history, most of which the definitive sources are just plain wrong:

"V7 (7/79) also gave rise to several Unix ports: the 32-bit implementations as well as XENIX2, a Microsoft-Santa Cruz Operation collaboration, which was the first Unix implementation for the Intel 8086 chip (XENIX1 was based on V6). V7 also gave rise to Unix for the Z8000 and 68000 chips." -P Salus. pg 168. "A Quarter Century of UNIX."

https://wiki.tuhs.org/lib/exe/fetch.php?media=publications:qcu.pdf

Unix version 7, was the first 32bit implementation on a VAX, and Bill Joy added virtual memory over the Christmas break.
It is unknown whether that HCR or Microsoft ever got a hold of the Tape-2 from Ken Thompson.

XENIX2? Xenix-11 was the HCR port that Microsoft paid for them to do, to get both UNIX running on their PDP-11, and to add as much pollute and dilute ( their first attempt ), of BSD, and not much more than that and a name change. The Santa Cruz connection came later, first as consultants, then a whipping boys for all the poor work by MS.

The first implementation on the Intel 8086 chip, ( not the 8088 ), was by Intel.
Xenix-1(286)(1984) was after Xenix-11 (PDP-11), the 68000 ports were to RS TRS-80 Model 16, Sirtek M68000 card, The IBM 9000, and Sun-2s, ( Microsoft Internal use ), The Apple Lisa 2 and Fortune 32:16. ( the manuals were little more than V7 line printer pages, with little to reflect the actual underlying changes. ). The Z8000 port was so rare, that no archive exists, although there were announcements, there was no documented shipping/running/manual.

== The documented history of Xenix-11, Xenix-1, Xenix-3, and SCO System V, Xenix 386, 286 and 8086. ==

in Brief:
Platform Release
PDP-11 Xenix-11. This is what the Living Computer Museum supposedly has a tape of, and that someone got from HCR a few days earlier.
286* Intel Xenix-1.0 This is what Microsoft shipped in Oct 1984, (c) 1984, only to have an IBM Deal announced two months later.
M68000 Xenix-3 This was the most popular Xenix version with Radio Shacks TRS 80IIb.
286, 86 SCO System V
286, 386,
Microchannel SCO System V.2

** This is the skeleton of the article re-write **
If this seems confusing? Hold on to your seats, it gets hugely confusing.

The list of Xenix ports:
Unix System 7 -> Microsoft paid HCR, Montreal, CA to port Unix System 7 to their PDP-11 machine.
1978~1981 Vaporware - used internally on PDP-11s for email, and to try and get the portable C compiler to output Intel Binaries.
It exists as a brochure, and maybe a mag tape at LCNM+L? but until its read, its unknown. I would bet its only the HCR port with the name change.

1981 Xenix-11 (for DEC PDP and VAX ) was announced, but since the VAX already had UNIX, no one was interested,
except for one tiny vendor who, instead of getting Xenix-11 from Microsoft, got it from HCR.

1982-02-02 Intel i80286 Introduced. ( This CPU and architecture was the great hope for multi-user systems, but it turned out to be "brain-dead" -Bill G. )

Everything Happened at once, in 1984. Intel shipped ( Xenix for 330 [Intel i80286], Radio Shack shipped[M68000], IBM Announced: IBM Xenix 1.0 [ IBM AT ]
( even though the IBM S9000 had both SO:OS and Xenix-3, Based on System-III)

Next up was Unix System III,
which was for Xenix-1, and Xenix-3, 3.2, 3.5 ( This was for the 68000 chips, and the Intel-SBC-286)

For the Fortune 31:16: "Fortune Operating System (FOR: PRO) is based on UNIX version 7, with
additional utilities from the University of California at Berkeley 4.1 UNIX, and the
Bell Laboratories UNIX System 3[ III ]. " http://bitsavers.org/pdf/fortuneSystems/service/1001240-05_Fortune_32-16_Field_Service_Manual_Apr1987.pdf

Which the description sounds exactly line Xenix-1 [ System

then Unix System V, which was the 286, and 8088 port for the IBM AT and the IBM PC,
with SCO's name on it, which was the basis for IBM Xenix 1.0, [Unix System V + BSD Utilities ]

and then followed by Unix System V.2
Which was the basis for IBM Xenix 2.0, and SCO System V Xenix 3.2.3.

"Is Unix big-endian or little endian?
In the SAS System, the following platforms are considered big endian: IBM mainframe, HP-UX, AIX, Solaris, and Macintosh. The following platforms are considered little endian: VAX/VMS, AXP/VMS, Digital UNIX, Intel ABI, OS/2, and Windows."
However... Intel spilled the beans about Intel's compiler:

"Xenix 286 Installation and Configuration - Release notes: Nov-84
"The original C compiler supported by XENIX 86 and XENIX 286 was developed by Dennis Ritchie at Bell Laboratories.
It was originally designed in 1973 around the PDP 11/44 architecture. In the late 1970's and early 1980's, the compiler was modified to support Intel's iAPX 8086 microprocessor. With the first release of this compiler, Microsoft Corporation chose to support the same 32-bit ordering supported under the Ritchie compiler. Meanwhile, with the design of the 8087 Fast Floating Point microprocessor, Intel also standardized a 32-bit ordering for the iAPX 8086 architecture. Intel, however, chose the same byte ordering that Digital Equipment Corporation selected for its VAX family of computers. Consequently, Microsoft 32-bit ordering is incompatible with the Intel 8087, 287, and 386 processors' 32-bit ordering."

"For the iAPX 8087 and 287 components to correctly interpret long values, the C compiler must perform a sequence of manipulations. For example, in order to provide support for the 8087 math component, the compiler generates instructions to swap the low word (bytes 0 and 1) with the high word (bytes 2 and 3). The 8087 then is able to operate on the representation it expects. Once the 8087 has completed an operation on a 32-bit value, the two words are swapped back.
In 1983, Microsoft and Intel were involved in the design of two strategically important projects. Microsoft was developing a new state-of-the-art compiler construction tool and a new C compiler for XENIX 286. At the same time, Intel began a project to support the Universal Development Interface (UDI) and translators ..,for XENIX 286. During the development period, the two companies discovered the incompatibility. After careful analysis, they decided that Microsoft would make the data representation of 32-bit values compatible with the Intel architecture."

Microsoft-C was little-endian and Intel was big-endian or really,
The DEC VAX was Byte order 3412 ( i.e. Word 2, followed by word 1), and intel was 1234 ( word 1 followed by word 2) , but Microsoft's C compiler for Xenix was 3412, until at least June of 1986, when the 386 came out, which most unfortunately, hampers the performance of Xenix on the i80286 and the i8086, and the i8088. On the Motorola when upgraded to a 68020, there is a barrel shifter which can change the byte ordering in 1 cycle, so Motorola, never cared about the byte ordering.
"The data section performs all data operations, such as immediate data value moves . It also contains the barrel shifter, which performs one-cycle shifts of any amount on data."

Talk:XENIX

2023-04-22T01:30:29Z

ForOldHack: /* Version info: */ added a minor link

Talk:XENIX

2023-04-20T07:43:44Z

ForOldHack: /* History Errors */ If this seems confusing? Hold on to your seats, it gets hugely confusing.

Talk:XENIX

2023-04-20T07:37:12Z

ForOldHack: /* History Errors */ and Intel spills the beans, i.e. Microsofts C compiler made 32-bit intigers incompatible with the 80287, until the 80387 was available.

Talk:Dennis Ritchie

2023-04-19T22:02:11Z

ForOldHack: /* should we list awards? */

A few more things:

This is the guy I met at Usenix...

He won a few awards:

IEEE Emanuel R. Piore Award, Ken Thompson and Dennis Ritchie
National Medal of Technology of 1998, Thompson and Ritchie jointly received the from President Bill Clinton for co-inventing the UNIX operating system and the C programming language, April 21, 1999.
Japan Prize for Information and Communications, Ritchie, along with Thompson, was awarded the Japan Prize for Information and Communications for his work in the development of the Unix operating system. 2011

"The PDP-7 Unix system was interesting enough that people were starting
to use it, even though it ran on a tiny computer and didn’t have a lot of software.
Still, it was clearly useful and had become the preferred computing
environment for a small group who found it more fun and productive than the
big central computer. Thus Ken Thompson, Dennis Ritchie and others began
to lobby for a larger computer that would support more users and enable
more interesting research." -Brian Kernighan, pg 41, "Unix: A History and a Memoir"

Dennis Ritchie

2023-04-19T21:47:30Z

ForOldHack: /* External links */ added link to Kernighan's memoir. A *must* read.

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

'''Dennis Ritchie''' (often referred to as '''dmr''') was an influential American computer scientist, best known for his work on [[UNIX]] and the [[C programming language]] - both produced in collaboration with [[Ken Thompson]].

He attended Harvard, where he received an undergraduate degree in 1963, and a doctoral degree in 1968. He went to work at [[Bell Labs]] in 1967, joining the Computing Sciences Research Center; he spent the rest of his career at the Labs, and its descendants. In 1968, he was part of the Bell team which joined the [[Multics]] project; after Bell pulled out of Multics, he and Thompson eventually fell into UNIX and C.

==External links==

* [https://www.bell-labs.com/usr/dmr/www/ Dennis Ritchie's Home Page]
** [https://www.bell-labs.com/usr/dmr/www/cacm.html The Unix Time-sharing System] ([https://www.bell-labs.com/usr/dmr/www/cacm.pdf PDF]) - 1978 [[BSTJ]] verson
** [https://www.bell-labs.com/usr/dmr/www/hist.html The Evolution of the Unix Time-sharing System] ([https://www.bell-labs.com/usr/dmr/www/hist.pdf PDF])
** [https://www.bell-labs.com/usr/dmr/www/retro.html The UNIX Time-sharing System - A Retrospective] ([https://www.bell-labs.com/usr/dmr/www/retro.pdf PDF])
** [https://www.bell-labs.com/usr/dmr/www/chist.html The Development of the C Language] ([https://www.bell-labs.com/usr/dmr/www/chist.pdf PDF])
** [https://www.bell-labs.com/usr/dmr/www/odd.html Odd Comments and Strange Doings in Unix]
** [https://www.bell-labs.com/usr/dmr/www/portpapers.html Papers about Unix Portability]
* [https://computerhistory.org/blog/discovering-dennis-ritchies-lost-dissertation/ Discovering Dennis Ritchie's Lost Dissertation]

** [https://www.amazon.com/UNIX-History-Memoir-Brian-Kernighan/dp/1695978552 Brian Kernighan's memoir of UNIX, Bell Labs and Dennis Ritchie.]

[[Category: People]]

XENIX

2023-04-03T22:25:27Z

ForOldHack: /* Getting this to run */ fix typo

[[Image:Xenix 386.jpg|thumb|right|200px|Xenix on a 386]]

'''Xenix''' (formally '''XENIX''', e.g. in contemporary [[Microsoft]] material) was Microsoft's [[software port|port]] of AT&T [[UNIX]]; it was a [[portable]] [[operating system]] with ports to various platforms. It was based on [[UNIX Sixth Edition|v6]], [[Unix Seventh Edition|v7]], [[UNIX System III|SYSIII]], and later [[UNIX System V|SYSV]].

: ''XENIX was originally developed on a DEC Virtual Address Extension (VAX) running the Virtual Memory System (VMS) and a PDP-11 running UNIX V7, albeit now using Microsoft's own in-house minicomputers, and then converted into assembly language specific to the new 16-bit Motorola 68000 and Intel 8086 microprocessors. This put XENIX at the high end of the microcomputer market, which was still dominated by 8-bit machines, but well below the lowest end of the minicomputer market'' - "XENIX -- Microsoft Short-lived Love Affair with Unix "

Unfortunately, "Xenix even incorporated the elements of BSD and became the most widely installed base of any Unix variant. Talking about the different modifications of Xenix, it was ported to Zilog Z8001, Intel 8086, Tandy Corporation’s 68000 based computers, and even a variant for Apple Lisa."

<blockquote>Modifications to Western Electric v7 included those necessary to transport the UNIX system from the larger PDP-11 mini computer to the 16-bit microprocessors. Currently scheduled machines included the DEC LSI-11/23, Zilogs Z8001 and Z8002, Intel's 8086 and 286, and Motorola's MC68000. - Robert Greenburg, uSloth. </blockquote>

Because of the price of the OS, about $500USD for the OS, and $500USD for the developer tools, combined with cheap [[IBM PC|PC]] and [[IBM-compatible PC|compatibles]], Xenix was the most widespread UNIX until the rise of [[Linux]]. Xenix due to its inherent [[multi-user]] capabilities became widespread in sales environments with POS (Point of Sales) terminals, and for scheduling systems commonly found in hotels and restaurants. Occasionally you can still find this setup still running on aging [[hardware]].

With the rise of the [[IBM PC]], it primarily became an [[Intel x86|x86]] based OS. Xenix eventually became [[SCO Unix]], then later SCO [[OpenServer]], where it still languishes today.

== Platforms ==

=== Intel ===

Xenix supported the following platforms:

*[[IBM 386]] [386 GT] The 32bit ones will run on Qemu/Virtual PC ( Sometimes called 386AT )
*IBM [[PS/2]] [386 MC] This version was specifically for [[MCA]] computers with a 386 or higher CPU. ( Sometimes called 386PS )
*SCO Announced Xenix for the Model 50(286), 60(286) and 80[Ran 386 MC], but its unknown if there are archives of it.
*[[IBM AT|IBM 286]] [286] - This version is now easy to find, but hard to run... It does not work on a 386.
*IBM PC [8088 or x86] - This is 'easy' to find.

This is a list of version numbers for the various Architectures:

*SysV 386 – 3.2, 4.2
*386 – 2.2.3b, 2.3.1, 2.3.2f, 2.3.4a, 2.3.4h ( SCO v2.2.3b, v2.3.2f, v2.3.4h)
<nowiki>*</nowiki>(You Plan to Install TCP/IP (XENIX.386 v2.3.4 only)
*286 – 2.1.3*, 2.2.1e, 2.2.3b, 2.3.2b, 2.3.2d ( SC0 v2.1.3, v2.2.1e, v2.2.3b, v2.3.2d)
<nowiki>*</nowiki>(Honey DanBer UUCP package v2.3.2 onward)
*8086 – 2.1.3* (SCO v2.1.3)

*These are currently the only two that boot on pcjs's website.

=== Motorola ===

*IBM System 9000 [[M68000]] [c 1984]
*[[Apple Lisa]] [[M68000]] [c 1984] The emulator [[idle]] can run this.

=== Others ===

*[[PDP-11]] - No versions of this exists online. There is a note that Xenix with Programmers console ran on a PDP-11/34. [https://comp.os.vms.narkive.com/Qoy6kBJU/xenix-vax-pdp# Xenix on PDP]
*[[Tandy TRS-80 Model II]] [[Z80A]] - There are disk images floating around.
*[[Zilog Z8001]] [c 1979] - I have only found sales literature that mentions this.*

<nowiki>*</nowiki> Note: This sounds like vaporware since neither the Onyx 1 nor the Commodore 900 ran Xenix

== Software ==

A quick list of a few software programs that were available on Xenix. I know the [[x86]] platform was the most supported, I now know that some of these made it to the less popular [[68000]] platform.

=== Microsoft ===

Microsoft made several of their programs in the 1980's available on the Xenix platform.
Microsoft Multiplan, and the BASIC Compiler.

=== Languages ===

*[[C programming language|C]]
*[[Basic]] - Basic [[Compiler]], Basic [[Interpreter]]
*[[Cobol]]
*[[FORTRAN|Fortran]]
*[[Pascal]]
*[[Assembler]]

"the base operating system does not include development tools such as a C compiler, but it does include the linker and, importantly, an assembler (which is needed to rebuild the configuration files). The assembler is, however, disguised to make it less obvious what it is by giving it a different name and that is what I have been trying to remember ever since I saw this post. Finally, this morning, it came to me. You ''should'' find that you have something called 'storel' (read it as 's-to-rel' as in 'something that transforms .s files into relocatable (ie .o) files' and the name becomes a little less obscure) on the system - I ''think'' that it lives in /bin. but it ''might'' be somewhere else such as /etc." (Source: [http://www.vcfed.org/forum/archive/index.php/t-49002.html here])

=== Applications ===

*Autodesk AutoCAD 10i
*Microsoft Multiplan (available on the Apple Lisa)
*Microsoft Word v5.0
*vi (Not really an application, but more of a torture device. May not be present on the x86 version, so ed will have to be used.)

=== Databases ===

*Foxpro

=== Games ===

* [[Rogue]]

=== SCO* ===

*SCO Professional
*SCO Lyrix (available on the Apple Lisa)
*SCO Integra
*SCO Manager
*SCO Multiview

<nowiki>*</nowiki> - ''SCO in this case refers to the original Santa Cruz Operation, and not the later SCO Group who bought the name and started the SCO/Linux lawsuits.''

== Getting this to run ==

The 8086 version of XENIX runs fine in an emulator.

Note: The 286 version of XENIX will only run on a 286 processor or a 286 processor emulator that handles the upper byte of the Global Descriptor byte 7, documented as reserved for use on a iAPX 386, by essentially ignoring it, and letting XENIX use it. A poor programming choice at best. (Now, that we know the publication dates of Intel's documentation (1982), we know they ignored the Intel documentation about the use of the upper byte of the descriptor words.. Details [http://www.os2museum.com/wp/ibm-xenix-two-steps-forward/comment-page-1/#comment-363304 here])

[[User:Neozeed]] wrote about [[Installing Xenix 2.x on Qemu|how to get it to run under QEMU 0.14]].

A repository has a file, that when run, unpacks Qemu 0.14, and has a disk, that boots straight into Xenix 2.3.4/386; the uname -a does confirm both the platform and the version.

Also, there is: [ftp://major.butt.care/mirrors/Unix/Xenix/Xenix-2.3.4.exe Xenix 2.3.4/386][https://archive.org/details/xenix-234-installer Backup]

Another directory has the same file from a SCO Mega pack called:
SCO Xenix 2.3.4 - preinstalled, run in Windows.

==External links==

===Announcements===

* [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=897/ENUS284-159&infotype=AN&subtype=CA&appname=skmwww XENIX Operating System for the IBM System 9000]
* [https://www.cbronline.com/news/santa_cruz_ships_xenix_v_for_ps2_developed_in_london/ Santa Cruz ships XENIX V for PS2 - Developed in London]

===History===

* [http://seefigure1.com/images/xenix/xenix-timeline.jpg The XENIX timeline] - The most comprehensive time vs port list
* [http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml Microsoft Short-lived Love Affair with Unix] - A detailed history
* [https://fossbytes.com/xenix-history-microsoft-unix-operating-system/ History Of Xenix - Microsoft's Forgotten Unix-based Operating System]
* [http://seefigure1.com/2014/04/15/xenixtime.html A bit of XENIX history] - XENIX history
* [http://www.edm2.com/index.php/XENIX XENIX] - Brief wiki page on XENIX; includes a bibliography

* [https://archive.org/details/byte-magazine-1981-06/page/n249 The UNIX Operating System and the XENIX Standard Operating Environment] - Byte Magazine Article on Xenix, BYTE June 1980, pg 249


===Emulators===

* [http://www.hampa.ch/pce/download.html PCE - PC Emulator] - [x86] Architecture
* [https://download.qemu.org/qemu-0.14.0.tar.gz QEMU v0.14runs SCO Xenix for i386 and i286]
* [https://www.pcjs.org/software/pcx86/sys/unix/sco/xenix/386/2.3.4h/ SCO Xenix 386 v2.3.4h] - 80386 version of Xenix

* [https://www.pcjs.org/disks/pcx86/unix/sco/xenix/286/2.1.3/ SCO Xenix 286 v2.1.3] - Runs Xenix 286 2.1.3 in a browser window.
* [https://www.pcjs.org/disks/pcx86/unix/sco/xenix/086/2.1.3/ SCO Xenix System V Release 2.1.3 for i8086] - Runs Xenix 8086 2.1.3 in a browser window.

* [https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand Tenon Xenix 286 2.3.2d on Linux w/ Qemu. ]

===Repositories===

* [ftp://major.butt.care/mirrors/Unix/Xenix/ 386, 286, x86, 386MC, Tandy, Lisa, Text, and Docs] Comprehensive Mirror
* [https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand Xenix286 on demand]

* [https://winworldpc.com/product/xenix/286 Xenix 286]
* [http://www.vcfed.org/forum/showthread.php?30490-Xenix-Development-Systems Xenix Development Systems]

* [https://macintoshgarden.org/apps/xenix-30-apple-lisa Xenix 3.0 for Apple Lisa]
* [http://tenox.pdp-11.ru/xenix/ Tenox Operating Systems Archive] - Includes Xenix documentation in PDF format]
* [https://archive.org/details/Xenix386Ports SCO Xenix and a set of ported software]

====Support Level Supplements for Xenix====

* [http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/vendor/sco/SLS/ SCO Xenix Update PTF/ltr/SLS files.]
* [http://ps-2.kev009.com/ohland/XENIX/XENIX_for_MCA.html SCO Xenix for MCA]
* [https://wdb1.sco.com/kb/showta?taid=102045&qid=1163837384&sid=1299958135&pgnum=1 Actual SCO/Xinous Updates]

===Archaeology===

* [https://museo.freaknet.org/gallery/software/xenix/versions.txt A list of version numbers pulled from disks]
* [http://seefigure1.com/2014/04/15/xenixtime.html A bit of XENIX History] (from a MS Developer '86 ~ '89)
* [http://www.os2museum.com/wp/category/xenix/ Category Archives: Xenix] - precursor to the next group
** [https://www.os2museum.com/wp/the-xenix-386-2-2-3-mystery/ The XENIX 386 2.2.3 Mystery]
** [http://www.os2museum.com/wp/the-xenix-2-2-3-mystery-continued/ The XENIX 2.2.3 Mystery, Continued]
** [http://www.os2museum.com/wp/oldest-surviving-386-pc-os/ Oldest Surviving 386 PC OS?]
* [https://soylentnews.org/search.pl?query=Xenix Searching For: Xenix] - Xenix at SoylentNews
** [https://soylentnews.org/article.pl?sid=17/03/03/1620222 Restoring Xenix 386 2.2.3c, Part 1]
** [https://soylentnews.org/article.pl?sid=17/03/07/1632251 Xenix 2.2.3c Restoration: No Tools, No Problem (Part 2)]
** [https://soylentnews.org/article.pl?sid=17/03/11/2014253 Xenix 2.2.3c Restoration: Damage Mapping (Part 3)]
** [https://soylentnews.org/article.pl?sid=17/03/13/086250 Xenix 2.2.3c Restoration: Xrossing The X (Part 4)] - Includes some extraordinary efforts to get some utilities to run
* [https://www.bell-labs.com/usr/dmr/www/xenix.gif XENIX ad from Dennis Ritchie's home page at Bell Labs]
* [https://www.linux-magazine.com/index.php/Online/Features/Remembering-XENIX Remembering XENIX]
* [https://www.snellman.net/blog/archive/2015-09-01-the-most-obsolete-infrastructure-money-could-buy/ The most obsolete infrastructure money could buy - my worst job ever] - XENIX 286 problem from hell

{{semi-stub}}

{{Nav Unix}}

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

XENIX

2023-04-03T22:24:17Z

ForOldHack: /* Repositories */ added collections of SLS.

[[Image:Xenix 386.jpg|thumb|right|200px|Xenix on a 386]]

'''Xenix''' (formally '''XENIX''', e.g. in contemporary [[Microsoft]] material) was Microsoft's [[software port|port]] of AT&T [[UNIX]]; it was a [[portable]] [[operating system]] with ports to various platforms. It was based on [[UNIX Sixth Edition|v6]], [[Unix Seventh Edition|v7]], [[UNIX System III|SYSIII]], and later [[UNIX System V|SYSV]].

: ''XENIX was originally developed on a DEC Virtual Address Extension (VAX) running the Virtual Memory System (VMS) and a PDP-11 running UNIX V7, albeit now using Microsoft's own in-house minicomputers, and then converted into assembly language specific to the new 16-bit Motorola 68000 and Intel 8086 microprocessors. This put XENIX at the high end of the microcomputer market, which was still dominated by 8-bit machines, but well below the lowest end of the minicomputer market'' - "XENIX -- Microsoft Short-lived Love Affair with Unix "

Unfortunately, "Xenix even incorporated the elements of BSD and became the most widely installed base of any Unix variant. Talking about the different modifications of Xenix, it was ported to Zilog Z8001, Intel 8086, Tandy Corporation’s 68000 based computers, and even a variant for Apple Lisa."

<blockquote>Modifications to Western Electric v7 included those necessary to transport the UNIX system from the larger PDP-11 mini computer to the 16-bit microprocessors. Currently scheduled machines included the DEC LSI-11/23, Zilogs Z8001 and Z8002, Intel's 8086 and 286, and Motorola's MC68000. - Robert Greenburg, uSloth. </blockquote>

Because of the price of the OS, about $500USD for the OS, and $500USD for the developer tools, combined with cheap [[IBM PC|PC]] and [[IBM-compatible PC|compatibles]], Xenix was the most widespread UNIX until the rise of [[Linux]]. Xenix due to its inherent [[multi-user]] capabilities became widespread in sales environments with POS (Point of Sales) terminals, and for scheduling systems commonly found in hotels and restaurants. Occasionally you can still find this setup still running on aging [[hardware]].

With the rise of the [[IBM PC]], it primarily became an [[Intel x86|x86]] based OS. Xenix eventually became [[SCO Unix]], then later SCO [[OpenServer]], where it still languishes today.

== Platforms ==

=== Intel ===

Xenix supported the following platforms:

*[[IBM 386]] [386 GT] The 32bit ones will run on Qemu/Virtual PC ( Sometimes called 386AT )
*IBM [[PS/2]] [386 MC] This version was specifically for [[MCA]] computers with a 386 or higher CPU. ( Sometimes called 386PS )
*SCO Announced Xenix for the Model 50(286), 60(286) and 80[Ran 386 MC], but its unknown if there are archives of it.
*[[IBM AT|IBM 286]] [286] - This version is now easy to find, but hard to run... It does not work on a 386.
*IBM PC [8088 or x86] - This is 'easy' to find.

This is a list of version numbers for the various Architectures:

*SysV 386 – 3.2, 4.2
*386 – 2.2.3b, 2.3.1, 2.3.2f, 2.3.4a, 2.3.4h ( SCO v2.2.3b, v2.3.2f, v2.3.4h)
<nowiki>*</nowiki>(You Plan to Install TCP/IP (XENIX.386 v2.3.4 only)
*286 – 2.1.3*, 2.2.1e, 2.2.3b, 2.3.2b, 2.3.2d ( SC0 v2.1.3, v2.2.1e, v2.2.3b, v2.3.2d)
<nowiki>*</nowiki>(Honey DanBer UUCP package v2.3.2 onward)
*8086 – 2.1.3* (SCO v2.1.3)

*These are currently the only two that boot on pcjs's website.

=== Motorola ===

*IBM System 9000 [[M68000]] [c 1984]
*[[Apple Lisa]] [[M68000]] [c 1984] The emulator [[idle]] can run this.

=== Others ===

*[[PDP-11]] - No versions of this exists online. There is a note that Xenix with Programmers console ran on a PDP-11/34. [https://comp.os.vms.narkive.com/Qoy6kBJU/xenix-vax-pdp# Xenix on PDP]
*[[Tandy TRS-80 Model II]] [[Z80A]] - There are disk images floating around.
*[[Zilog Z8001]] [c 1979] - I have only found sales literature that mentions this.*

<nowiki>*</nowiki> Note: This sounds like vaporware since neither the Onyx 1 nor the Commodore 900 ran Xenix

== Software ==

A quick list of a few software programs that were available on Xenix. I know the [[x86]] platform was the most supported, I now know that some of these made it to the less popular [[68000]] platform.

=== Microsoft ===

Microsoft made several of their programs in the 1980's available on the Xenix platform.
Microsoft Multiplan, and the BASIC Compiler.

=== Languages ===

*[[C programming language|C]]
*[[Basic]] - Basic [[Compiler]], Basic [[Interpreter]]
*[[Cobol]]
*[[FORTRAN|Fortran]]
*[[Pascal]]
*[[Assembler]]

"the base operating system does not include development tools such as a C compiler, but it does include the linker and, importantly, an assembler (which is needed to rebuild the configuration files). The assembler is, however, disguised to make it less obvious what it is by giving it a different name and that is what I have been trying to remember ever since I saw this post. Finally, this morning, it came to me. You ''should'' find that you have something called 'storel' (read it as 's-to-rel' as in 'something that transforms .s files into relocatable (ie .o) files' and the name becomes a little less obscure) on the system - I ''think'' that it lives in /bin. but it ''might'' be somewhere else such as /etc." (Source: [http://www.vcfed.org/forum/archive/index.php/t-49002.html here])

=== Applications ===

*Autodesk AutoCAD 10i
*Microsoft Multiplan (available on the Apple Lisa)
*Microsoft Word v5.0
*vi (Not really an application, but more of a torture device. May not be present on the x86 version, so ed will have to be used.)

=== Databases ===

*Foxpro

=== Games ===

* [[Rogue]]

=== SCO* ===

*SCO Professional
*SCO Lyrix (available on the Apple Lisa)
*SCO Integra
*SCO Manager
*SCO Multiview

<nowiki>*</nowiki> - ''SCO in this case refers to the original Santa Cruz Operation, and not the later SCO Group who bought the name and started the SCO/Linux lawsuits.''

== Getting this to run ==

The 8086 version of XENIX runs fine in an emulator.

Note: The 286 version of XENIX will only run on a 286 processor or a 286 processor emulator that handles the upper byte of the Global Descriptor byte 7, documented as reserved for use on a iAPX 386, by essentially ignoring it, and letting XENIX use it. A poor programming choice as best. (Now, that we know the publication dates of Intel's documentation (1982), we know they ignored the Intel documentation about the use of the upper byte of the descriptor words.. Details [http://www.os2museum.com/wp/ibm-xenix-two-steps-forward/comment-page-1/#comment-363304 here])

[[User:Neozeed]] wrote about [[Installing Xenix 2.x on Qemu|how to get it to run under QEMU 0.14]].

A repository has a file, that when run, unpacks Qemu 0.14, and has a disk, that boots straight into Xenix 2.3.4/386; the uname -a does confirm both the platform and the version.

Also, there is: [ftp://major.butt.care/mirrors/Unix/Xenix/Xenix-2.3.4.exe Xenix 2.3.4/386][https://archive.org/details/xenix-234-installer Backup]

Another directory has the same file from a SCO Mega pack called:
SCO Xenix 2.3.4 - preinstalled, run in Windows.

==External links==

===Announcements===

* [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=897/ENUS284-159&infotype=AN&subtype=CA&appname=skmwww XENIX Operating System for the IBM System 9000]
* [https://www.cbronline.com/news/santa_cruz_ships_xenix_v_for_ps2_developed_in_london/ Santa Cruz ships XENIX V for PS2 - Developed in London]

===History===

* [http://seefigure1.com/images/xenix/xenix-timeline.jpg The XENIX timeline] - The most comprehensive time vs port list
* [http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml Microsoft Short-lived Love Affair with Unix] - A detailed history
* [https://fossbytes.com/xenix-history-microsoft-unix-operating-system/ History Of Xenix - Microsoft's Forgotten Unix-based Operating System]
* [http://seefigure1.com/2014/04/15/xenixtime.html A bit of XENIX history] - XENIX history
* [http://www.edm2.com/index.php/XENIX XENIX] - Brief wiki page on XENIX; includes a bibliography

* [https://archive.org/details/byte-magazine-1981-06/page/n249 The UNIX Operating System and the XENIX Standard Operating Environment] - Byte Magazine Article on Xenix, BYTE June 1980, pg 249


===Emulators===

* [http://www.hampa.ch/pce/download.html PCE - PC Emulator] - [x86] Architecture
* [https://download.qemu.org/qemu-0.14.0.tar.gz QEMU v0.14runs SCO Xenix for i386 and i286]
* [https://www.pcjs.org/software/pcx86/sys/unix/sco/xenix/386/2.3.4h/ SCO Xenix 386 v2.3.4h] - 80386 version of Xenix

* [https://www.pcjs.org/disks/pcx86/unix/sco/xenix/286/2.1.3/ SCO Xenix 286 v2.1.3] - Runs Xenix 286 2.1.3 in a browser window.
* [https://www.pcjs.org/disks/pcx86/unix/sco/xenix/086/2.1.3/ SCO Xenix System V Release 2.1.3 for i8086] - Runs Xenix 8086 2.1.3 in a browser window.

* [https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand Tenon Xenix 286 2.3.2d on Linux w/ Qemu. ]

===Repositories===

* [ftp://major.butt.care/mirrors/Unix/Xenix/ 386, 286, x86, 386MC, Tandy, Lisa, Text, and Docs] Comprehensive Mirror
* [https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand Xenix286 on demand]

* [https://winworldpc.com/product/xenix/286 Xenix 286]
* [http://www.vcfed.org/forum/showthread.php?30490-Xenix-Development-Systems Xenix Development Systems]

* [https://macintoshgarden.org/apps/xenix-30-apple-lisa Xenix 3.0 for Apple Lisa]
* [http://tenox.pdp-11.ru/xenix/ Tenox Operating Systems Archive] - Includes Xenix documentation in PDF format]
* [https://archive.org/details/Xenix386Ports SCO Xenix and a set of ported software]

====Support Level Supplements for Xenix====

* [http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/vendor/sco/SLS/ SCO Xenix Update PTF/ltr/SLS files.]
* [http://ps-2.kev009.com/ohland/XENIX/XENIX_for_MCA.html SCO Xenix for MCA]
* [https://wdb1.sco.com/kb/showta?taid=102045&qid=1163837384&sid=1299958135&pgnum=1 Actual SCO/Xinous Updates]

===Archaeology===

* [https://museo.freaknet.org/gallery/software/xenix/versions.txt A list of version numbers pulled from disks]
* [http://seefigure1.com/2014/04/15/xenixtime.html A bit of XENIX History] (from a MS Developer '86 ~ '89)
* [http://www.os2museum.com/wp/category/xenix/ Category Archives: Xenix] - precursor to the next group
** [https://www.os2museum.com/wp/the-xenix-386-2-2-3-mystery/ The XENIX 386 2.2.3 Mystery]
** [http://www.os2museum.com/wp/the-xenix-2-2-3-mystery-continued/ The XENIX 2.2.3 Mystery, Continued]
** [http://www.os2museum.com/wp/oldest-surviving-386-pc-os/ Oldest Surviving 386 PC OS?]
* [https://soylentnews.org/search.pl?query=Xenix Searching For: Xenix] - Xenix at SoylentNews
** [https://soylentnews.org/article.pl?sid=17/03/03/1620222 Restoring Xenix 386 2.2.3c, Part 1]
** [https://soylentnews.org/article.pl?sid=17/03/07/1632251 Xenix 2.2.3c Restoration: No Tools, No Problem (Part 2)]
** [https://soylentnews.org/article.pl?sid=17/03/11/2014253 Xenix 2.2.3c Restoration: Damage Mapping (Part 3)]
** [https://soylentnews.org/article.pl?sid=17/03/13/086250 Xenix 2.2.3c Restoration: Xrossing The X (Part 4)] - Includes some extraordinary efforts to get some utilities to run
* [https://www.bell-labs.com/usr/dmr/www/xenix.gif XENIX ad from Dennis Ritchie's home page at Bell Labs]
* [https://www.linux-magazine.com/index.php/Online/Features/Remembering-XENIX Remembering XENIX]
* [https://www.snellman.net/blog/archive/2015-09-01-the-most-obsolete-infrastructure-money-could-buy/ The most obsolete infrastructure money could buy - my worst job ever] - XENIX 286 problem from hell

{{semi-stub}}

{{Nav Unix}}

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