User:Vt320/sandbox

VAXstation 100
The VAXstation 100 was an intelligent graphics terminal (also described as a "Display subsystem") introduced by Digital in May 1983 for the VAX-11 line of systems. Design commenced in 1981, prior to the availability of a VLSI VAX CPU necessary to create a standalone VAX workstation. The VAXstation 100 took the approach of attaching a graphics terminal to a VAX-11 (or later Unibus capable VAX) system. Application logic ran on the host's VAX CPU, and the code for displaying graphics was ran on the VAXstation 100's processor. Digital's literature suggested various configurations for the VAXstation 100, such as attaching multiple VAXstation 100s to a large VAX-11/78x system, or attaching a single one to a smaller system such as a VAX-11/725 to create a single user workstation.

The VAXstation 100 consisted of a desk-side unit housing a Motorola 68000 processor, a dedicated bit blit accelerator built from AMD 2901 logic, and a total of 640KB of RAM (128KB for the CPU, and a 512KB frame buffer). Attached to this unit was a 19" monochrome monitor, an LK201 keyboard, a mouse, and optionally a graphics tablet and five-button puck. The VAXstation 100 interfaced with the host VAX system over a 300m fibre optic cable to a Unibus card called the "Unibus Window Module". The VAXstation 100's processor was capable of directly accessing a 256KB window of the host system's memory, which was used to share data and commands between the host and the workstation.

Digital's official software for the VAXstation was the VAX Display Subsystem Software (VDSS) which was installed under VAX/VMS and provided a basic GUI enviornment for the VAXstation 100 with terminal emulation software. Custom GUI applications could be developed using the VAXstation Display Management Library (known as VSTA) and the VAXstation Core Graphics Library. The VAXstation 100 was perhaps best known as the original target of the X Windows Systems.

Digital

VS100:

https://dl.acm.org/doi/pdf/10.1145/61975.66913 http://www.bitsavers.org/pdf/dec/competitiveAnalysis/Engineering_Strategy_Review_Mar82.pdf

notes:
 * http://itpscan.ca/blog/iSeries/iseries_intro_1.php
 * https://www.itjungle.com/2009/01/05/tfh010509-story06/
 * https://www.cs.unm.edu/~crandall/NCSC-FER-95-006.pdf
 * http://www.audentia-gestion.fr/IBM/PDF/sc413735.pdf
 * https://gordonbell.azurewebsites.net/Computer_Structures_Principles_and_Examples/csp0167.htm
 * https://www-01.ibm.com/common/ssi/rep_ca/3/897/ENUS296-023/index.html
 * https://www.semanticscholar.org/paper/Design-Rationale-of-the-AS%2F400-User-Interface-Botterill/ce6ab4c731e530a6f43c2d85b9b4e4139eb4abcc
 * https://www.mcpressonline.com/programming-other/general/create-ibmstyle-rolling-menus-with-uim
 * https://www.mcpressonline.com/programming/rpg/uim-list-panels
 * https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/nls/rbagsuserinterfaceman.htm
 * https://www.mcpressonline.com/programming/rpg/practical-rpg-moving-your-help-to-panel-groups
 * ftp://ftp.software.ibm.com/systems/power/docs/systemi/v5r3/en_US/rzaiq.pdf
 * https://www.yumpu.com/en/document/read/10632250/application-display-programming-v5r4-ibm
 * http://www.hen-sch.de/books/AS400%20System%20Handbook%20V4R4M0.pdf
 * https://www-01.ibm.com/common/ssi/printableversion.wss?docURL=/common/ssi/rep_ca/3/897/ENUS296-023/index.html&request_locale=en
 * http://dhart.<>.info/iseries/5769-SS1%20IBM%20Operating%20System400%20(OS400).htm
 * http://www.audentia-gestion.fr/IBM/PDF/sc414731.pdf
 * http://ftpmirror.your.org/pub/misc/ftp.software.ibm.com/systems/power/docs/systemi/v5r4/fi_FI/sc414730.pdf
 * http://4props.ddns.net/iseries/5763-SS1%20IBM%20Operating%20System400%20(OS400)%20Version%203.htm
 * https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?appname=skmwww&htmlfid=897%2FENUS290-436&infotype=AN&subtype=CA
 * https://www.mcpressonline.com/programming/rpg/a-close-study-of-i5os-machine-interface-mi-pointers
 * https://archive.midrange.com/mi400/200207/msg00078.html


 * http://oldpc.su/lib/gsp/red91.pdf


 * https://books.google.ie/books?id=dPu-_QBrLB4C&pg=PA29&lpg=PA29#v=onepage&q&f=false
 * https://books.google.ie/books?id=7pNVYaQldtkC&pg=PA66&lpg=PA66&dq=Terry+Shannon+Ultrix&source=bl&ots=lF2fRdW00V&sig=ACfU3U1gB7wYXgGirMbrG_BWANL_y9_ZNw&hl=en&sa=X&ved=2ahUKEwjlj8Oxq4v0AhXxQkEAHUJoCh0Q6AF6BAgCEAM#v=onepage&q=Terry%20Shannon%20Ultrix&f=false


 * http://delibra.bg.polsl.pl/Content/22620/Vax.pdf


 * http://www.astradyne.net/manuals/ir007310.pdf
 * https://books.google.ie/books?id=oiB9AqI0GZ4C&pg=PA18&lpg=PA18&dq=System/34+microcode&source=bl&ots=oNSqFRaK7s&sig=ACfU3U3O1FBMMd-wYtZUa4vLZsYfs1dCGw&hl=en&sa=X&ved=2ahUKEwjvzrLOy4z1AhXOYMAKHa8uB08Q6AF6BAgdEAM#v=onepage&q=System%2F34%20microcode&f=false
 * https://archive.midrange.com/mi400/200207/msg00078.html
 * https://archive.midrange.com/c400-l/200008/msg00007.html


 * https://www.mcpressonline.com/programming/rpg/multilingual-in-an-ile-world
 * https://www.mcpressonline.com/programming-other/general/freedom-of-choice-in-ccompilers

IBM i includes compatibility layers for System/36 and System/38 applications and data named the System/36 Environment (or S/36EE) and System/38 Environment (or S/38EE) respectively. These are both implemented inside the XPF. Due to the similarities of the IBM i and System/38 CPF platforms, System/38 applications can run on top of IBM i without recompilation. System/38 applications and object are not entirely forwards compatible with IBM i, as IBM decided to make compatibility-breaking changes during the original development of OS/400. Instead, System/38 objects and programs are "re-encapsulated" transparently by IBM i when restored from a backup or transferred to the system over the network. Certain System/38 programs will not work on IBM i, particularly programs which relied on undocumented interfaces in the System/38 which were removed or hidden from user code during the development of OS/400. The System/38 environment also includes utilities which are no longer included in IBM i, or which were changed in backwards-incompatible ways (for example, IBM i includes a separate implementation of the Control Language for System/38 code due to syntax changes between the two platforms).

stuff

 * May 2020
 * May 2020
 * rowspan=14 | x86-64
 * x86-64 Early Adopter's Kit
 * May 2020
 * June 2020
 * x86-64 Early Adopter's Kit
 * June 2020
 * July 2020
 * x86-64 Early Adopter's Kit
 * July 2020
 * August 2020
 * x86-64 Early Adopter's Kit
 * August 2020
 * October 2020
 * x86-64 Early Adopter's Kit
 * October 2020
 * December 2020
 * x86-64 Early Adopter's Kit
 * December 2020
 * February 2021
 * x86-64 Early Adopter's Kit
 * February 2021
 * April 2021
 * x86-64 Early Adopter's Kit
 * April 2021
 * June 2021
 * x86-64 Early Adopter's Kit
 * October 2020
 * December 2020
 * x86-64 Early Adopter's Kit
 * December 2020
 * February 2021
 * x86-64 Early Adopter's Kit
 * February 2021
 * April 2021
 * x86-64 Early Adopter's Kit
 * April 2021
 * June 2021
 * x86-64 Early Adopter's Kit
 * x86-64 Early Adopter's Kit
 * April 2021
 * June 2021
 * x86-64 Early Adopter's Kit
 * June 2021
 * x86-64 Early Adopter's Kit