VAX: Difference between revisions
HeyElliott (talk | contribs) |
|||
(9 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|Line of computers sold by Digital Equipment Corporation}} |
{{Short description|Line of computers sold by Digital Equipment Corporation}} |
||
{{ |
{{Redirect|Vax}} |
||
{{Use mdy dates|date=October 2022}} |
{{Use mdy dates|date=October 2022}} |
||
{{Infobox CPU architecture |
{{Infobox CPU architecture |
||
Line 9: | Line 9: | ||
| introduced = {{Start date and age|1977}} |
| introduced = {{Start date and age|1977}} |
||
| design = [[Complex instruction set computer|CISC]] |
| design = [[Complex instruction set computer|CISC]] |
||
| type = Register–register |
| type = {{ubl | Register–register | Register–memory | Memory–memory }} |
||
| encoding = Variable <small>(1 to 56 bytes)</small> |
| encoding = Variable <small>(1 to 56 bytes)</small> |
||
| endianness = Little |
| endianness = Little |
||
Line 23: | Line 23: | ||
}} |
}} |
||
'''VAX''' (an acronym for '''Virtual Address eXtension''') is a series of computers featuring a [[32-bit computing|32-bit]] [[instruction set architecture]] (ISA) and [[virtual memory]] that was developed and sold by [[Digital Equipment Corporation]] (DEC) in the late 20th century. The [[VAX-11/780]], introduced October 25, 1977, was the first of a range of popular and influential computers implementing the VAX ISA. The VAX family was a huge success for |
'''VAX''' (an acronym for '''Virtual Address eXtension''') is a series of computers featuring a [[32-bit computing|32-bit]] [[instruction set architecture]] (ISA) and [[virtual memory]] that was developed and sold by [[Digital Equipment Corporation]] (DEC) in the late 20th century. The [[VAX-11/780]], introduced October 25, 1977, was the first of a range of popular and influential computers implementing the VAX ISA. The VAX family was a huge success for DEC, with the last members arriving in the early 1990s. The VAX was succeeded by the [[DEC Alpha]], which included several features from VAX machines to make [[porting]] from the VAX easier. |
||
VAX was designed as a successor to the [[16-bit computing|16-bit]] [[PDP-11]], one of the most successful [[minicomputer]]s in history with approximately 600,000 |
VAX was designed as a successor to the [[16-bit computing|16-bit]] [[PDP-11]], one of the most successful [[minicomputer]]s in history with approximately 600,000 units sold. The system was designed to offer [[backward compatibility]] with the PDP-11 while extending the memory to a full [[32-bit computing|32-bit]] implementation and adding [[Paging|demand paged]] [[virtual memory]]. The name VAX refers to its ''Virtual Address eXtension'' concept that allowed programs to make use of this newly available memory while still being compatible with unmodified user mode PDP-11 code. The name "VAX-11", used on early models, was chosen to highlight this capability. The VAX ISA is considered a [[complex instruction set computer]] (CISC) design. |
||
DEC quickly dropped the −11 branding as PDP-11 compatibility was no longer a major concern. The line expanded to both high-end [[mainframe]]s like the [[VAX 9000]] as well as to the [[workstation]]-scale systems like the [[VAXstation]] series. [[List of VAX computers|The VAX family]] ultimately contained ten distinct designs and over 100 individual models in total. All of them were compatible with each other and normally ran the [[OpenVMS|VAX/VMS]] [[operating system]]. |
|||
VAX has been perceived as the quintessential CISC ISA,<ref>{{cite web |last1=Bistriceanu |first1=Virgil |title=Computer Architecture – Class notes |url=http://www.cs.iit.edu/~virgil/cs470/Book/chapter3.pdf |publisher=Illinois Institute of Technology |access-date=April 15, 2022}}</ref> with its very large number of [[assembly language]] programmer-friendly [[addressing mode]]s and machine instructions, highly [[orthogonal instruction set]] architecture, and instructions for complex operations such as [[Queue (data structure)|queue]] insertion or deletion, number formatting, and [[polynomial]] evaluation.<ref>{{cite journal |last1=Payne |first1=Mary |last2=Bhandarkar |first2=Dileep |year=1980 |title=VAX floating point: a solid foundation for numerical computation |journal=SIGARCH Computer Architecture News |publisher=ACM |volume=8 |issue=4 |pages=22–33 |issn=0163-5964 |doi=10.1145/641845.641849 |s2cid=15021135|doi-access=free }}</ref> |
VAX has been perceived as the quintessential CISC ISA,<ref>{{cite web |last1=Bistriceanu |first1=Virgil |title=Computer Architecture – Class notes |url=http://www.cs.iit.edu/~virgil/cs470/Book/chapter3.pdf |publisher=Illinois Institute of Technology |access-date=April 15, 2022}}</ref> with its very large number of [[assembly language]] programmer-friendly [[addressing mode]]s and machine instructions, highly [[orthogonal instruction set]] architecture, and instructions for complex operations such as [[Queue (data structure)|queue]] insertion or deletion, number formatting, and [[polynomial]] evaluation.<ref>{{cite journal |last1=Payne |first1=Mary |last2=Bhandarkar |first2=Dileep |year=1980 |title=VAX floating point: a solid foundation for numerical computation |journal=SIGARCH Computer Architecture News |publisher=ACM |volume=8 |issue=4 |pages=22–33 |issn=0163-5964 |doi=10.1145/641845.641849 |s2cid=15021135|doi-access=free }}</ref> |
||
== Name == |
== Name == |
||
[[File:VAX 11-780 intero.jpg|thumb|VAX-11/780]] |
[[File:VAX 11-780 intero.jpg|thumb|VAX-11/780]] |
||
Line 40: | Line 39: | ||
== Instruction set == |
== Instruction set == |
||
The VAX instruction set was designed to be powerful and [[Orthogonal instruction set|orthogonal]].<ref name="Levy">{{Cite book|url=https://books.google.com/books?id=3LijBQAAQBAJ|title=Computer Programming and Architecture: The Vax|last1=Levy|first1=Henry|last2=Eckhouse|first2=Richard|date=June 28, 2014|publisher=Digital Press|isbn=9781483299372|language=en}}</ref> When it was introduced, many programs were written in assembly language, so having a "programmer-friendly" instruction set was important.<ref>{{cite web |
The VAX instruction set was designed to be powerful and [[Orthogonal instruction set|orthogonal]].<ref name="Levy">{{Cite book|url=https://books.google.com/books?id=3LijBQAAQBAJ|title=Computer Programming and Architecture: The Vax|last1=Levy|first1=Henry|last2=Eckhouse|first2=Richard|date=June 28, 2014|publisher=Digital Press|isbn=9781483299372|language=en}}</ref> When it was introduced, many programs were written in assembly language, so having a "programmer-friendly" instruction set was important.<ref>{{cite web |
||
|title=Another Approach to Instruction Set Architecture—VAX |
|title=Another Approach to Instruction Set Architecture—VAX |
||
Line 51: | Line 49: | ||
}}</ref><ref>{{cite web |title=VAX |quote=Esp. noted for its large, assembler-programmer-friendly instruction set --- an asset that|url=http://www.lysator.liu.se/hackdict/split/vax.html}}</ref> In time, as more programs were written in [[high-level programming language]]s, the instruction set became less visible, and the only ones much concerned about it were compiler writers. |
}}</ref><ref>{{cite web |title=VAX |quote=Esp. noted for its large, assembler-programmer-friendly instruction set --- an asset that|url=http://www.lysator.liu.se/hackdict/split/vax.html}}</ref> In time, as more programs were written in [[high-level programming language]]s, the instruction set became less visible, and the only ones much concerned about it were compiler writers. |
||
One unusual aspect of the VAX instruction set is the presence of register masks<ref>{{cite web |url=http://www.openvms.compaq.com/doc/73final/4515/4515pro_020.html#index_x_790 |title=VAX MACRO and Instruction Set Reference Manual |at=9.2.5 Procedure Call Instructions |date=April 2001 |work=OpenVMS documentation |archive-url=https://web.archive.org/web/20020330111145/http://www.openvms.compaq.com/doc/73final/4515/4515pro_020.html#index_x_790 |archive-date= |
One unusual aspect of the VAX instruction set is the presence of register masks<ref>{{cite web |url=http://www.openvms.compaq.com/doc/73final/4515/4515pro_020.html#index_x_790 |title=VAX MACRO and Instruction Set Reference Manual |at=9.2.5 Procedure Call Instructions |date=April 2001 |work=OpenVMS documentation |archive-url=https://web.archive.org/web/20020330111145/http://www.openvms.compaq.com/doc/73final/4515/4515pro_020.html#index_x_790 |archive-date=March 30, 2002 |url-status=dead}}</ref> at the start of each subprogram. These are arbitrary bit patterns that specify, when control is passed to the subprogram, which registers are to be preserved. On most architectures, it is up to the compiler to produce instructions to save out the needed data, typically using the [[call stack]] for temporary storage. On the VAX, with 16 registers, this might require 16 instructions to save the data and another 16 to restore it. Using the mask, a single 16-bit value performs the same operations internally in hardware, saving time and memory.<ref name="Levy"/> |
||
Since register masks are a form of data embedded within the executable code, they can make linear parsing of the machine code difficult. This can complicate optimization techniques that are applied on machine code.<ref name="MCO">{{cite thesis |last=Goss |first=Clinton F. |date=August 2013 |title=Machine Code Optimization: Improving Executable Object Code |type=PhD |orig-date=First published June 1986 |volume=Computer Science Department Technical Report No. 246 |publisher=Courant Institute, New York University |url=http://www.ClintGoss.com/mco/Goss_1986_MachineCodeOptimization.pdf |access-date=August 22, 2013 |arxiv=1308.4815 |bibcode=2013arXiv1308.4815G}} |
|||
*{{cite thesis |degree=PhD |author=Clinton F. Goss |date=2013 |orig-date=1986 |title=Machine Code Optimization – Improving Executable Object Code | publisher=Courant Institute, New York University |url=http://www.ClintGoss.com/mco/}}</ref> |
*{{cite thesis |degree=PhD |author=Clinton F. Goss |date=2013 |orig-date=1986 |title=Machine Code Optimization – Improving Executable Object Code | publisher=Courant Institute, New York University |url=http://www.ClintGoss.com/mco/}}</ref> |
||
== Operating systems == |
== Operating systems == |
||
[[File:VAX VMS logo.svg|thumb|right|Stylized "VAX/VMS" used by Digital]] |
[[File:VAX VMS logo.svg|thumb|right|Stylized "VAX/VMS" used by Digital]] |
||
The |
The native VAX [[operating system]] is Digital's VAX/VMS (renamed to [[OpenVMS]] in 1991 or early 1992 when it was ported to [[DEC Alpha|Alpha]], modified to comply with [[POSIX]] standards, and ''branded'' as compliant with [[XPG4]] by the [[X/Open]] consortium).<ref name="vaxvmsat20">{{Cite web |editor1-last=Rainville |editor1-first=Jim |editor2-last=Howard |editor2-first=Karen |year=1997 |url=http://h41379.www4.hpe.com/openvms/20th/ |title=VAX/VMS at 20 |publisher=Digital Equipment Corporation |access-date=July 20, 2018 |archive-url=https://web.archive.org/web/20180720225439/http://h41379.www4.hpe.com/openvms/20th/ |archive-date=July 20, 2018 |url-status=dead}}</ref> The VAX architecture and VMS operating system were "[[Concurrent Engineering#Concurrent engineering workflow|engineered concurrently]]" to take maximum advantage of each other, as was the initial implementation of the [[VMScluster|VAXcluster]] facility. |
||
During the 1980s, a [[hypervisor]] for the VAX architecture named ''VMM'' (Virtual Machine Monitor), also known as the ''VAX Security Kernel'', was developed at Digital with the aim of allowing multiple isolated instances of VMS and ULTRIX to be run on the same hardware.<ref>{{cite conference|url=https://www.scs.stanford.edu/nyu/04fa/sched/readings/vmm.pdf|title=A VMM security kernel for the VAX architecture|author1=Paul A. Karger|author2=Mary Ellen Zurko|author3=Douglas W. Benin|author4=Andrew H. Mason|author5=Clifford E. Kahnh|date=May 7–9, 1990|conference=Proceedings. 1990 IEEE Computer Society Symposium on Research in Security and Privacy|access-date=2021-01-31|publisher=IEEE|doi=10.1109/RISP.1990.63834}}</ref> VMM was intended to achieve [[Trusted Computer System Evaluation Criteria|TCSEC]] A1 compliance. By the late 1980s, it was operational on [[VAX 8000]] series hardware, but was abandoned before release to customers. |
During the 1980s, a [[hypervisor]] for the VAX architecture named ''VMM'' (Virtual Machine Monitor), also known as the ''VAX Security Kernel'', was developed at Digital with the aim of allowing multiple isolated instances of VMS and ULTRIX to be run on the same hardware.<ref>{{cite conference|url=https://www.scs.stanford.edu/nyu/04fa/sched/readings/vmm.pdf|title=A VMM security kernel for the VAX architecture|author1=Paul A. Karger|author2=Mary Ellen Zurko|author3=Douglas W. Benin|author4=Andrew H. Mason|author5=Clifford E. Kahnh|date=May 7–9, 1990|conference=Proceedings. 1990 IEEE Computer Society Symposium on Research in Security and Privacy|access-date=2021-01-31|publisher=IEEE|doi=10.1109/RISP.1990.63834}}</ref> VMM was intended to achieve [[Trusted Computer System Evaluation Criteria|TCSEC]] A1 compliance. By the late 1980s, it was operational on [[VAX 8000]] series hardware, but was abandoned before release to customers. |
||
Line 65: | Line 64: | ||
== History == |
== History == |
||
[[File:DEC-VAX-8350-front-0a.jpg|thumb|VAX 8350 front view with cover removed]] |
[[File:DEC-VAX-8350-front-0a.jpg|thumb|VAX 8350 front view with cover removed]] |
||
Line 89: | Line 87: | ||
[[File:Microvax 3600 (2).jpg|thumb|MicroVAX 3600 (left) with printer (right)]] |
[[File:Microvax 3600 (2).jpg|thumb|MicroVAX 3600 (left) with printer (right)]] |
||
{| role="presentation" style="font-size:88%;border: 1px solid #a2a9b1; border-spacing: 3px; background-color: #f8f9fa; color: black; margin: 0.5em 0 0.5em 1em; padding: 0.2em; float: right; clear: right;" |
|||
{| class="infobox" style="font-size:88%" |
|||
|- |
|- |
||
|+ DEC VAX registers |
|+ '''DEC VAX registers''' |
||
|- |
|- |
||
| |
| |
||
Line 107: | Line 105: | ||
| style="width:100px; background:white; color:black" | ''(bit position)'' |
| style="width:100px; background:white; color:black" | ''(bit position)'' |
||
|- |
|- |
||
! colspan="10" | General registers |
! colspan="10" style="text-align:left;" | General registers |
||
|- style="background:silver;color:black" |
|- style="background:silver;color:black" |
||
| style="text-align:center" colspan="9"| R0 |
| style="text-align:center" colspan="9"| R0 |
||
Line 157: | Line 155: | ||
| style="background:white; color:black"| Register 15 / Program Counter |
| style="background:white; color:black"| Register 15 / Program Counter |
||
|- |
|- |
||
! colspan="10" | Processor Status Longword |
! colspan="10" style="text-align:left;" | Processor Status Longword |
||
|- style="background:silver;color:black" |
|- style="background:silver;color:black" |
||
| style="text-align:center" colspan="9"| (See adjacent table for bit definitions) |
| style="text-align:center" colspan="9"| (See adjacent table for bit definitions) |
||
Line 165: | Line 163: | ||
=== Virtual memory map === |
=== Virtual memory map === |
||
The VAX virtual memory is divided into four sections. Each is one gigabyte (in the context of addressing, 2<sup>30</sup> bytes) in size: |
The VAX virtual memory is divided into four sections. Each is one gigabyte (in the context of addressing, 2<sup>30</sup> bytes) in size: |
||
Line 187: | Line 184: | ||
=== Privilege modes === |
=== Privilege modes === |
||
The VAX has four hardware implemented privilege modes: |
The VAX has four hardware implemented privilege modes: |
||
Line 219: | Line 215: | ||
=== Processor status longword === |
=== Processor status longword === |
||
The |
The process status longword contains 32 bits: |
||
{|class="wikitable" |
{|class="wikitable" |
||
Line 240: | Line 236: | ||
! width=3% | V |
! width=3% | V |
||
! width=3% | C |
! width=3% | C |
||
|- style="text-align:center" |
|||
|- |
|||
|31 |
|31 |
||
|30 |
|30 |
||
|29 |
|29:28 |
||
|27 |
|27 |
||
|26 |
|26 |
||
|25 |
|25:24 |
||
|23 |
|23:22 |
||
|21 |
|21 |
||
|20 |
|20:16 |
||
|15 |
|15:8 |
||
|7 |
|7 |
||
|6 |
|6 |
||
Line 262: | Line 258: | ||
{|class="wikitable" |
{|class="wikitable" |
||
! Bits || Meaning || Bits || Meaning |
|||
! Bits |
|||
! Meaning |
|||
|- |
|- |
||
| align="center"| 31 || PDP-11 compatibility mode || align="center"| 15:8|| MBZ (must be zero) |
|||
| 31 |
|||
| PDP-11 compatibility mode |
|||
|- |
|- |
||
| align="center"| 30 || trace pending || align="center"| 7 || decimal overflow trap enable |
|||
| 30 |
|||
| trace pending |
|||
|- |
|- |
||
| align="center"|29:28|| MBZ (must be zero) || align="center"| 6 || floating-point underflow trap enable |
|||
| 29:28 |
|||
| MBZ (must be zero) |
|||
|- |
|- |
||
| align="center"| 27 || first part done (interrupted instruction) || align="center"| 5 || [[integer overflow]] trap enable |
|||
| 27 |
|||
| first part done (interrupted instruction) |
|||
|- |
|- |
||
| align="center"| 26 || interrupt stack || align="center"| 4 || trace |
|||
| 26 |
|||
| interrupt stack |
|||
|- |
|- |
||
| align="center"|25:24|| current privilege mode || align="center"| 3 || negative |
|||
| 25:24 |
|||
| current privilege mode |
|||
|- |
|- |
||
| align="center"|23:22|| previous privilege mode || align="center"| 2 || zero |
|||
| 23:22 |
|||
| previous privilege mode |
|||
|- |
|- |
||
| align="center"| 21 || MBZ (must be zero) || align="center"| 1 || overflow |
|||
| 21 |
|||
| MBZ (must be zero) |
|||
|- |
|- |
||
| align="center"|20:16|| IPL (interrupt priority level) || align="center"| 0 || carry |
|||
| 20:16 |
|||
| IPL (interrupt priority level) |
|||
|- |
|||
| 15:8 |
|||
| MBZ (must be zero) |
|||
|- |
|||
| 7 |
|||
| decimal overflow trap enable |
|||
|- |
|||
| 6 |
|||
| floating-point underflow trap enable |
|||
|- |
|||
| 5 |
|||
| [[integer overflow]] trap enable |
|||
|- |
|||
| 4 |
|||
| trace |
|||
|- |
|||
| 3 |
|||
| negative |
|||
|- |
|||
| 2 |
|||
| zero |
|||
|- |
|||
| 1 |
|||
| overflow |
|||
|- |
|||
| 0 |
|||
| carry |
|||
|} |
|} |
||
⚫ | |||
== VAX-based systems == |
== VAX-based systems == |
||
{{See also|List of VAX computers}} |
{{See also|List of VAX computers}} |
||
⚫ | |||
The first VAX-based system was the [[VAX-11/780]], a member of the [[VAX-11]] family. The high-end [[VAX 8600]] replaced the VAX-11/780 in October 1984 and was joined by the entry-level [[MicroVAX]] minicomputers and the [[VAXstation]] workstations in the mid-1980s. The MicroVAX was superseded by the [[VAX 4000]], the VAX 8000 was superseded by the [[VAX 6000]] in the late 1980s and the mainframe-class [[VAX 9000]] was introduced. In the early 1990s, the [[Fault tolerance|fault-tolerant]] [[VAXft]] was introduced, as were the [[DEC Alpha|Alpha]] compatible [[VAX 7000/10000]]. A variant of various VAX-based systems were sold as the [[VAXserver]]. |
The first VAX-based system was the [[VAX-11/780]], a member of the [[VAX-11]] family. The high-end [[VAX 8600]] replaced the VAX-11/780 in October 1984 and was joined by the entry-level [[MicroVAX]] minicomputers and the [[VAXstation]] workstations in the mid-1980s. The MicroVAX was superseded by the [[VAX 4000]], the VAX 8000 was superseded by the [[VAX 6000]] in the late 1980s and the mainframe-class [[VAX 9000]] was introduced. In the early 1990s, the [[Fault tolerance|fault-tolerant]] [[VAXft]] was introduced, as were the [[DEC Alpha|Alpha]] compatible [[VAX 7000/10000]]. A variant of various VAX-based systems were sold as the [[VAXserver]]. |
||
=== SImultaneous Machine ACceSs (SIMACS) === |
=== SImultaneous Machine ACceSs (SIMACS) === |
||
''[[System Industries]]'' developed an ability to give more than one DEC CPU, but not at the same time, write access to a shared disk. They implemented an enhancement named SImultaneous Machine ACceSs ([[SIMACS]]),<ref>{{cite web |url=http://www.atnf.csiro.au/observers/memos/d95f80~1.pdf |title=Computing Requirements for AT Software Development |last1=Wand |first1=R. |last2=Kesteven |first2=M. |last3=Rayner |first3=P. |date=February 24, 1984}}</ref><ref name=SIMACS.HC84>{{cite magazine |last1=Joshi |first1=Prem |last2=Delacroix |first2=Jacques |date=September 1984 |title=New Flexibility For Multiple VAX/VMS |magazine=[[HARDCOPY]] |pages=64–68}}</ref> which allowed their special disk controller to set a [[Semaphore (computing)|semaphore flag]] for disk access, allowing multiple WRITES to the same files; the disk is shared by multiple DEC systems. ''SIMACS'' also existed on PDP-11 [[RSTS/E|RSTS]] systems. |
''[[System Industries]]'' developed an ability to give more than one DEC CPU, but not at the same time, write access to a shared disk. They implemented an enhancement named SImultaneous Machine ACceSs ([[SIMACS]]),<ref>{{cite web |url=http://www.atnf.csiro.au/observers/memos/d95f80~1.pdf |title=Computing Requirements for AT Software Development |last1=Wand |first1=R. |last2=Kesteven |first2=M. |last3=Rayner |first3=P. |date=February 24, 1984}}</ref><ref name=SIMACS.HC84>{{cite magazine |last1=Joshi |first1=Prem |last2=Delacroix |first2=Jacques |date=September 1984 |title=New Flexibility For Multiple VAX/VMS |magazine=[[HARDCOPY]] |pages=64–68}}</ref> which allowed their special disk controller to set a [[Semaphore (computing)|semaphore flag]] for disk access, allowing multiple WRITES to the same files; the disk is shared by multiple DEC systems. ''SIMACS'' also existed on PDP-11 [[RSTS/E|RSTS]] systems. |
||
=== Canceled systems === |
=== Canceled systems === |
||
Canceled systems include the ''BVAX'', a high-end [[emitter-coupled logic]] (ECL) based VAX, and two other ECL-based VAX models: ''Argonaut'' and ''Raven''.<ref>{{cite web |title=Who are the Computer Architects? |url=http://www.cs.clemson.edu/~mark/architects.html |author=Mark Smotherman |date=July 19, 2008 |access-date=September 30, 2008}}</ref> Raven was canceled in 1990.<ref>{{cite web |url=http://simh.trailing-edge.com/semi/raven.html |website=Computer History and Simulation |title=Raven |last=Supnik |first=Bob |date=2007 |access-date=March 1, 2019}}</ref> A VAX named ''Gemini'' was also canceled, which was a fall-back in case the LSI-based ''Scorpio'' failed. It never shipped. |
Canceled systems include the ''BVAX'', a high-end [[emitter-coupled logic]] (ECL) based VAX, and two other ECL-based VAX models: ''Argonaut'' and ''Raven''.<ref>{{cite web |title=Who are the Computer Architects? |url=http://www.cs.clemson.edu/~mark/architects.html |author=Mark Smotherman |date=July 19, 2008 |access-date=September 30, 2008}}</ref> Raven was canceled in 1990.<ref>{{cite web |url=http://simh.trailing-edge.com/semi/raven.html |website=Computer History and Simulation |title=Raven |last=Supnik |first=Bob |date=2007 |access-date=March 1, 2019}}</ref> A VAX named ''Gemini'' was also canceled, which was a fall-back in case the LSI-based ''Scorpio'' failed. It never shipped. |
||
=== Clones === |
=== Clones === |
||
A number of VAX clones, both authorized and unauthorized, were produced. Examples include: |
A number of VAX clones, both authorized and unauthorized, were produced. Examples include: |
||
Line 346: | Line 301: | ||
* The ''SM-1700'' is a Soviet clone of the VAX-11/730, ''SM-1702'' was a clone of MicroVAX II and ''SM-1705'' was a clone of VAX-11/785.<ref>{{cite journal|author1=Laimutis Telksnys|author2=Antanas Zilinskas|title=Computers in Lithuania|journal=IEEE Annals of the History of Computing|volume=21|number=3|pages=31–37|date=July 1999|url=http://www.computer.org/csdl/mags/an/1999/03/00778980.pdf|doi=10.1109/85.778980|s2cid=16240778}}</ref> These systems ran a variety of clone operating systems - [[DEMOS]] (based on BSD Unix), [[OpenVMS#Influence|MOS VP]] (based on VAX/VMS) or MOS VP RV (based on VAXELN).<ref>{{cite journal|url=http://www.swsys.ru/index.php?page=article&id=1480#|journal=Software Systems Journal|volume=1988|issue=3|title=Basic software for 32-bit SM computer models|author1=Prokhorov N.L.|author2=Gorskiy V.E.|language=Russian|access-date=2021-09-15}}</ref> |
* The ''SM-1700'' is a Soviet clone of the VAX-11/730, ''SM-1702'' was a clone of MicroVAX II and ''SM-1705'' was a clone of VAX-11/785.<ref>{{cite journal|author1=Laimutis Telksnys|author2=Antanas Zilinskas|title=Computers in Lithuania|journal=IEEE Annals of the History of Computing|volume=21|number=3|pages=31–37|date=July 1999|url=http://www.computer.org/csdl/mags/an/1999/03/00778980.pdf|doi=10.1109/85.778980|s2cid=16240778}}</ref> These systems ran a variety of clone operating systems - [[DEMOS]] (based on BSD Unix), [[OpenVMS#Influence|MOS VP]] (based on VAX/VMS) or MOS VP RV (based on VAXELN).<ref>{{cite journal|url=http://www.swsys.ru/index.php?page=article&id=1480#|journal=Software Systems Journal|volume=1988|issue=3|title=Basic software for 32-bit SM computer models|author1=Prokhorov N.L.|author2=Gorskiy V.E.|language=Russian|access-date=2021-09-15}}</ref> |
||
* The NCI-2780 Super-mini, also sold as Taiji-2780, is a clone of the VAX-11/780 developed by North China Institute of Computing Technology in Beijing.<ref>{{cite book|url=https://books.google.com/books?id=E0LoOH-GqagC&q=%22NCI-2780%22&pg=PA96|title=Technology transfer to China|author=[[U.S. Congress]], [[Office of Technology Assessment]]|publisher=[[U.S. Government Printing Office]]|date=July 1987|page=96|isbn=9781428922914|id=OTA-USC-340}}</ref><ref>{{cite book|chapter-url=https://books.google.com/books?id=u7HItO03SlwC&q=%22NCI-2780%22&pg=PA244|title=Space Commercialization: Launch Vehicles and Programs|editor1=F. Sharokhi|editor2=J. S. Greenberg|editor3=T. Al-Saud|chapter=Satellite Launch and TT&C Systems of China and Their Roles in International Cooperation|author1=Xia Nanyin|author2=Chan Laixing|year=1990|page=244|publisher=[[American Institute of Aeronautics and Astronautics]]|isbn=0-930403-75-4}}</ref> |
* The NCI-2780 Super-mini, also sold as Taiji-2780, is a clone of the VAX-11/780 developed by North China Institute of Computing Technology in Beijing.<ref>{{cite book|url=https://books.google.com/books?id=E0LoOH-GqagC&q=%22NCI-2780%22&pg=PA96|title=Technology transfer to China|author=[[U.S. Congress]], [[Office of Technology Assessment]]|publisher=[[U.S. Government Printing Office]]|date=July 1987|page=96|isbn=9781428922914|id=OTA-USC-340}}</ref><ref>{{cite book|chapter-url=https://books.google.com/books?id=u7HItO03SlwC&q=%22NCI-2780%22&pg=PA244|title=Space Commercialization: Launch Vehicles and Programs|editor1=F. Sharokhi|editor2=J. S. Greenberg|editor3=T. Al-Saud|chapter=Satellite Launch and TT&C Systems of China and Their Roles in International Cooperation|author1=Xia Nanyin|author2=Chan Laixing|year=1990|page=244|publisher=[[American Institute of Aeronautics and Astronautics]]|isbn=0-930403-75-4}}</ref> |
||
⚫ | |||
⚫ | |||
== References == |
== References == |
||
{{reflist|30em}} |
{{reflist|30em}} |
||
⚫ | |||
⚫ | * {{cite news |last1=Coy |first1=Peter |title=Who Remembers the VAX Minicomputer, Icon of the 1980s? |url=https://www.bloomberg.com/news/articles/2021-01-06/who-remembers-the-vax-minicomputer-icon-of-the-1980s |access-date=January 9, 2021 |publisher=[[Bloomberg News]] |date=January 6, 2021 |language=en}} |
||
== External links == |
== External links == |
||
Line 366: | Line 319: | ||
{{Processor technologies}} |
{{Processor technologies}} |
||
⚫ | |||
⚫ | |||
[[Category:Minicomputers]] |
[[Category:Minicomputers]] |
||
[[Category:32-bit computers]] |
[[Category:32-bit computers]] |
||
⚫ | |||
⚫ |
Revision as of 19:49, 16 February 2024
Designer | Digital Equipment Corporation |
---|---|
Bits | 32-bit |
Introduced | 1977 |
Design | CISC |
Type |
|
Encoding | Variable (1 to 56 bytes) |
Branching | Condition code |
Endianness | Little |
Page size | 512 bytes |
Extensions | PDP-11 compatibility mode, VAX Vector Extensions,[1] VAX Virtualization Extensions[2] |
Open | No |
Predecessor | PDP-11 |
Successor | Alpha |
Registers | |
General-purpose | 16 × 32-bit |
Floating point | not present, uses the GPR |
Vector | 16 × 4096-bit (64 elements of 64 bits each) |
VAX (an acronym for Virtual Address eXtension) is a series of computers featuring a 32-bit instruction set architecture (ISA) and virtual memory that was developed and sold by Digital Equipment Corporation (DEC) in the late 20th century. The VAX-11/780, introduced October 25, 1977, was the first of a range of popular and influential computers implementing the VAX ISA. The VAX family was a huge success for DEC, with the last members arriving in the early 1990s. The VAX was succeeded by the DEC Alpha, which included several features from VAX machines to make porting from the VAX easier.
VAX was designed as a successor to the 16-bit PDP-11, one of the most successful minicomputers in history with approximately 600,000 units sold. The system was designed to offer backward compatibility with the PDP-11 while extending the memory to a full 32-bit implementation and adding demand paged virtual memory. The name VAX refers to its Virtual Address eXtension concept that allowed programs to make use of this newly available memory while still being compatible with unmodified user mode PDP-11 code. The name "VAX-11", used on early models, was chosen to highlight this capability. The VAX ISA is considered a complex instruction set computer (CISC) design.
DEC quickly dropped the −11 branding as PDP-11 compatibility was no longer a major concern. The line expanded to both high-end mainframes like the VAX 9000 as well as to the workstation-scale systems like the VAXstation series. The VAX family ultimately contained ten distinct designs and over 100 individual models in total. All of them were compatible with each other and normally ran the VAX/VMS operating system.
VAX has been perceived as the quintessential CISC ISA,[3] with its very large number of assembly language programmer-friendly addressing modes and machine instructions, highly orthogonal instruction set architecture, and instructions for complex operations such as queue insertion or deletion, number formatting, and polynomial evaluation.[4]
Name
The name "VAX" originated as an acronym for Virtual Address eXtension, both because the VAX was seen as a 32-bit extension of the older 16-bit PDP-11 and because it was (after Prime Computer) an early adopter of virtual memory to manage this larger address space.
Early versions of the VAX processor implement a "compatibility mode" that emulates many of the PDP-11's instructions, giving it the 11 in VAX-11 to highlight this compatibility. Later versions offloaded the compatibility mode and some of the less used CISC instructions to emulation in the operating system software.
Instruction set
The VAX instruction set was designed to be powerful and orthogonal.[5] When it was introduced, many programs were written in assembly language, so having a "programmer-friendly" instruction set was important.[6][7] In time, as more programs were written in high-level programming languages, the instruction set became less visible, and the only ones much concerned about it were compiler writers.
One unusual aspect of the VAX instruction set is the presence of register masks[8] at the start of each subprogram. These are arbitrary bit patterns that specify, when control is passed to the subprogram, which registers are to be preserved. On most architectures, it is up to the compiler to produce instructions to save out the needed data, typically using the call stack for temporary storage. On the VAX, with 16 registers, this might require 16 instructions to save the data and another 16 to restore it. Using the mask, a single 16-bit value performs the same operations internally in hardware, saving time and memory.[5]
Since register masks are a form of data embedded within the executable code, they can make linear parsing of the machine code difficult. This can complicate optimization techniques that are applied on machine code.[9]
Operating systems
The native VAX operating system is Digital's VAX/VMS (renamed to OpenVMS in 1991 or early 1992 when it was ported to Alpha, modified to comply with POSIX standards, and branded as compliant with XPG4 by the X/Open consortium).[10] The VAX architecture and VMS operating system were "engineered concurrently" to take maximum advantage of each other, as was the initial implementation of the VAXcluster facility.
During the 1980s, a hypervisor for the VAX architecture named VMM (Virtual Machine Monitor), also known as the VAX Security Kernel, was developed at Digital with the aim of allowing multiple isolated instances of VMS and ULTRIX to be run on the same hardware.[11] VMM was intended to achieve TCSEC A1 compliance. By the late 1980s, it was operational on VAX 8000 series hardware, but was abandoned before release to customers.
Other VAX operating systems have included various releases of Berkeley Software Distribution (BSD) UNIX up to 4.3BSD, Ultrix-32, VAXELN, and Xinu. More recently, NetBSD[12] and OpenBSD[13] have supported various VAX models and some work has been done on porting Linux to the VAX architecture.[14] OpenBSD discontinued support for the architecture in September 2016.[15]
History
The first VAX model sold was the VAX-11/780, which was introduced on October 25, 1977, at the Digital Equipment Corporation's Annual Meeting of Shareholders.[16] Bill Strecker, C. Gordon Bell's doctoral student at Carnegie Mellon University, was responsible for the architecture.[17] Many different models with different prices, performance levels, and capacities were subsequently created. VAX superminicomputers were very popular in the early 1980s.
For a while the VAX-11/780 was used as a standard in CPU benchmarks. It was initially described as a one-MIPS machine, because its performance was equivalent to an IBM System/360 that ran at one MIPS, and the System/360 implementations had previously been de facto performance standards. The actual number of instructions executed in 1 second was about 500,000, which led to complaints of marketing exaggeration. The result was the definition of a "VAX MIPS", the speed of a VAX-11/780; a computer performing at 27 VAX MIPS would run the same program roughly 27 times faster than the VAX-11/780.
Within the Digital community the term VUP (VAX Unit of Performance) was the more common term, because MIPS do not compare well across different architectures. The related term cluster VUPs was informally used to describe the aggregate performance of a VAXcluster. (The performance of the VAX-11/780 still serves as the baseline metric in the BRL-CAD Benchmark, a performance analysis suite included in the BRL-CAD solid modeling software distribution.) The VAX-11/780 included a subordinate stand-alone LSI-11 computer that performed microcode load, booting, and diagnostic functions for the parent computer. This was dropped from subsequent VAX models. Enterprising VAX-11/780 users could therefore run three different Digital Equipment Corporation operating systems: VMS on the VAX processor (from the hard drives), and either RSX-11S or RT-11 on the LSI-11 (from the single density single drive floppy disk).
The VAX went through many different implementations. The original VAX 11/780 was implemented in TTL and filled a four-by-five-foot cabinet[18] with a single CPU. Through the 1980s, the high-end of the family was continually improved using ever-faster discrete components, an evolution that ended with the introduction of the VAX 9000 in October 1989. This design proved too complex and expensive and was ultimately abandoned not long after introduction. CPU implementations that consisted of multiple emitter-coupled logic (ECL) gate array or macrocell array chips included the VAX 8600 and 8800 superminis and finally the VAX 9000 mainframe class machines. CPU implementations that consisted of multiple MOSFET custom chips included the 8100 and 8200 class machines. The VAX 11-730 and 725 low-end machines were built using AMD Am2901 bit-slice components for the ALU.
The MicroVAX I represented a major transition within the VAX family. At the time of its design, it was not yet possible to implement the full VAX architecture as a single VLSI chip (or even a few VLSI chips as was later done with the V-11 CPU of the VAX 8200/8300). Instead, the MicroVAX I was the first VAX implementation to move some of the more complex VAX instructions (such as the packed decimal and related opcodes) into emulation software. This partitioning substantially reduced the amount of microcode required and was referred to as the "MicroVAX" architecture. In the MicroVAX I, the ALU and registers were implemented as a single gate-array chip while the rest of the machine control was conventional logic.
A full VLSI (microprocessor) implementation of the MicroVAX architecture arrived with the MicroVAX II's 78032 (or DC333) CPU and 78132 (DC335) FPU. The 78032 was the first microprocessor with an on-board memory management unit[19] The MicroVAX II was based on a single, quad-sized processor board which carried the processor chips and ran the MicroVMS or Ultrix-32 operating systems. The machine featured 1 MB of on-board memory and a Q22-bus interface with DMA transfers. The MicroVAX II was succeeded by many further MicroVAX models with much improved performance and memory.
Further VLSI VAX processors followed in the form of the V-11, CVAX, CVAX SOC ("System On Chip", a single-chip CVAX), Rigel, Mariah and NVAX implementations. The VAX microprocessors extended the architecture to inexpensive workstations and later also supplanted the high-end VAX models. This wide range of platforms (mainframe to workstation) using one architecture was unique in the computer industry at that time. Sundry graphics were etched onto the CVAX microprocessor die. The phrase CVAX... when you care enough to steal the very best was etched in broken Russian as a play on a Hallmark Cards slogan, intended as a message to Soviet engineers who were known to be both purloining DEC computers for military applications and reverse engineering their chip design.[20][21] By the late 1980s, the VAX microprocessors had grown in power to be competitive with discrete designs. This led to the abandonment of the 8000 and 9000 series and their replacement by Rigel-powered models of the VAX 6000, and later by NVAX-powered VAX 7000 systems.
In DEC's product offerings, the VAX architecture was eventually superseded by RISC technology. In 1989 DEC introduced a range of workstations and servers that ran Ultrix, the DECstation and DECsystem respectively, using processors from MIPS Computer Systems. In 1992 DEC introduced their own RISC instruction set architecture, the Alpha AXP (later renamed Alpha), and their own Alpha-based microprocessor, the DECchip 21064, a high performance 64-bit design capable of running OpenVMS.
In August 2000, Compaq announced that the remaining VAX models would be discontinued by the end of the year,[22] but old systems remain in widespread use.[23] The Stromasys CHARON-VAX and SIMH software-based VAX emulators remain available. VMS is now developed by VMS Software Incorporated, albeit only for the Alpha, HPE Integrity, and x86-64 platforms.
Processor architecture
|
Virtual memory map
The VAX virtual memory is divided into four sections. Each is one gigabyte (in the context of addressing, 230 bytes) in size:
Section | Address range |
---|---|
P0 | 0x00000000 – 0x3fffffff
|
P1 | 0x40000000 – 0x7fffffff
|
S0 | 0x80000000 – 0xbfffffff
|
S1 | 0xc0000000 – 0xffffffff
|
For VMS, P0 was used for user process space, P1 for process stack, S0 for the operating system, and S1 was reserved.
Privilege modes
The VAX has four hardware implemented privilege modes:
No. | Mode | VMS use | Notes |
---|---|---|---|
0 | Kernel | OS kernel | Highest privilege level |
1 | Executive | File system | |
2 | Supervisor | Shell (DCL) | |
3 | User | Normal programs | Lowest privilege level |
Processor status longword
The process status longword contains 32 bits:
CM | TP | MBZ | FD | IS | cmod | pmod | MBZ | IPL | MBZ | DV | FU | IV | T | N | Z | V | C |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
31 | 30 | 29:28 | 27 | 26 | 25:24 | 23:22 | 21 | 20:16 | 15:8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Bits | Meaning | Bits | Meaning |
---|---|---|---|
31 | PDP-11 compatibility mode | 15:8 | MBZ (must be zero) |
30 | trace pending | 7 | decimal overflow trap enable |
29:28 | MBZ (must be zero) | 6 | floating-point underflow trap enable |
27 | first part done (interrupted instruction) | 5 | integer overflow trap enable |
26 | interrupt stack | 4 | trace |
25:24 | current privilege mode | 3 | negative |
23:22 | previous privilege mode | 2 | zero |
21 | MBZ (must be zero) | 1 | overflow |
20:16 | IPL (interrupt priority level) | 0 | carry |
VAX-based systems
The first VAX-based system was the VAX-11/780, a member of the VAX-11 family. The high-end VAX 8600 replaced the VAX-11/780 in October 1984 and was joined by the entry-level MicroVAX minicomputers and the VAXstation workstations in the mid-1980s. The MicroVAX was superseded by the VAX 4000, the VAX 8000 was superseded by the VAX 6000 in the late 1980s and the mainframe-class VAX 9000 was introduced. In the early 1990s, the fault-tolerant VAXft was introduced, as were the Alpha compatible VAX 7000/10000. A variant of various VAX-based systems were sold as the VAXserver.
SImultaneous Machine ACceSs (SIMACS)
System Industries developed an ability to give more than one DEC CPU, but not at the same time, write access to a shared disk. They implemented an enhancement named SImultaneous Machine ACceSs (SIMACS),[24][25] which allowed their special disk controller to set a semaphore flag for disk access, allowing multiple WRITES to the same files; the disk is shared by multiple DEC systems. SIMACS also existed on PDP-11 RSTS systems.
Canceled systems
Canceled systems include the BVAX, a high-end emitter-coupled logic (ECL) based VAX, and two other ECL-based VAX models: Argonaut and Raven.[26] Raven was canceled in 1990.[27] A VAX named Gemini was also canceled, which was a fall-back in case the LSI-based Scorpio failed. It never shipped.
Clones
A number of VAX clones, both authorized and unauthorized, were produced. Examples include:
- Systime Computers Ltd of the United Kingdom produced clones of early VAX models such as the Systime 8750 (equivalent to the VAX 11/750).[28]
- Norden Systems produced the ruggedized, Military-specification MIL VAX series.[10]
- The Hungarian Central Research Institute for Physics (KFKI) produced a series of clones of early VAX models, the TPA-11/540, 560 and 580.[29]
- The SM 52/12[30] from Czechoslovakia, developed at VUVT Žilina (today Slovakia) and produced from 1986 at ZVT Banská Bystrica (today Slovakia).
- The East German VEB Robotron K 1840 (SM 1710) is a clone of the VAX-11/780 and Robotron K 1820 (SM 1720) is a copy of the MicroVAX II.
- The SM-1700 is a Soviet clone of the VAX-11/730, SM-1702 was a clone of MicroVAX II and SM-1705 was a clone of VAX-11/785.[31] These systems ran a variety of clone operating systems - DEMOS (based on BSD Unix), MOS VP (based on VAX/VMS) or MOS VP RV (based on VAXELN).[32]
- The NCI-2780 Super-mini, also sold as Taiji-2780, is a clone of the VAX-11/780 developed by North China Institute of Computing Technology in Beijing.[33][34]
References
- ^ "VAX MACRO and Instruction Set Reference Manual". OpenVMS documentation. April 2001. 8.1 Basic Architecture. Archived from the original on September 6, 2001.
- ^ DEC STD 032 – VAX Architecture Standard (PDF). Digital Equipment Corp. January 5, 1990. p. 12-5. Retrieved August 1, 2022.
- ^ Bistriceanu, Virgil. "Computer Architecture – Class notes" (PDF). Illinois Institute of Technology. Retrieved April 15, 2022.
- ^ Payne, Mary; Bhandarkar, Dileep (1980). "VAX floating point: a solid foundation for numerical computation". SIGARCH Computer Architecture News. 8 (4). ACM: 22–33. doi:10.1145/641845.641849. ISSN 0163-5964. S2CID 15021135.
- ^ a b Levy, Henry; Eckhouse, Richard (June 28, 2014). Computer Programming and Architecture: The Vax. Digital Press. ISBN 9781483299372.
- ^ "Another Approach to Instruction Set Architecture—VAX" (PDF). Archived from the original (PDF) on June 10, 2017. Retrieved October 3, 2018.
... instruction set architectures, we chose the VAX as programmer-friendly instruction set, an asset
- ^ "VAX".
Esp. noted for its large, assembler-programmer-friendly instruction set --- an asset that
- ^ "VAX MACRO and Instruction Set Reference Manual". OpenVMS documentation. April 2001. 9.2.5 Procedure Call Instructions. Archived from the original on March 30, 2002.
- ^ Goss, Clinton F. (August 2013) [First published June 1986]. Machine Code Optimization: Improving Executable Object Code (PDF) (PhD). Vol. Computer Science Department Technical Report No. 246. Courant Institute, New York University. arXiv:1308.4815. Bibcode:2013arXiv1308.4815G. Retrieved August 22, 2013.
- Clinton F. Goss (2013) [1986]. Machine Code Optimization – Improving Executable Object Code (PhD thesis). Courant Institute, New York University.
- ^ a b Rainville, Jim; Howard, Karen, eds. (1997). "VAX/VMS at 20". Digital Equipment Corporation. Archived from the original on July 20, 2018. Retrieved July 20, 2018.
- ^ Paul A. Karger; Mary Ellen Zurko; Douglas W. Benin; Andrew H. Mason; Clifford E. Kahnh (May 7–9, 1990). A VMM security kernel for the VAX architecture (PDF). Proceedings. 1990 IEEE Computer Society Symposium on Research in Security and Privacy. IEEE. doi:10.1109/RISP.1990.63834. Retrieved January 31, 2021.
- ^ "NetBSD/vax".
- ^ "OpenBSD/vax".
- ^ "Porting Linux to the VAX".
- ^ "OpenBSD 6.0". 2016. Retrieved June 20, 2017.
- ^ "VAX 11/780, The First VAX System (October 1977)".
- ^ Slater, Robert (1987). Portraits in Silicon. MIT Press. p. 213. ISBN 978-0-262-69131-4.
- ^ "VAX 11/780 Computer: CPU". Computer History Museum. Retrieved October 24, 2012.
- ^ "MicroVAX II (1985)". Computer History and Simulation.
- ^ "Steal the best". micro.magnet.fsu.edu. Retrieved January 30, 2008. The Russian phrase was: СВАКС... Когда вы забатите довольно воровать настоящий лучший
- ^ "CVAX (1987)". Computer History and Simulation. Retrieved January 30, 2008.
- ^ "VAX Systems: A letter from Jesse Lipcon". Archived from the original on August 15, 2000.
- ^ "If It Ain't Broke, Don't Fix It: Ancient Computers in Use Today". PCWorld. Retrieved October 11, 2021.
- ^ Wand, R.; Kesteven, M.; Rayner, P. (February 24, 1984). "Computing Requirements for AT Software Development" (PDF).
- ^ Joshi, Prem; Delacroix, Jacques (September 1984). "New Flexibility For Multiple VAX/VMS". HARDCOPY. pp. 64–68.
- ^ Mark Smotherman (July 19, 2008). "Who are the Computer Architects?". Retrieved September 30, 2008.
- ^ Supnik, Bob (2007). "Raven". Computer History and Simulation. Retrieved March 1, 2019.
- ^ "RAL Informatics Report 1984-85". Retrieved October 15, 2007.
- ^ "The TPA story". Retrieved October 15, 2007.
- ^ Dujnic, J.; Fristacky, N.; Molnar, L.; Plander, I.; Rovan, B. (1999). "On the history of computer science, computer engineering, and computer technology development in Slovakia". IEEE Annals of the History of Computing. 21 (3): 38–48. doi:10.1109/85.778981.
- ^ Laimutis Telksnys; Antanas Zilinskas (July 1999). "Computers in Lithuania" (PDF). IEEE Annals of the History of Computing. 21 (3): 31–37. doi:10.1109/85.778980. S2CID 16240778.
- ^ Prokhorov N.L.; Gorskiy V.E. "Basic software for 32-bit SM computer models". Software Systems Journal (in Russian). 1988 (3). Retrieved September 15, 2021.
- ^ U.S. Congress, Office of Technology Assessment (July 1987). Technology transfer to China. U.S. Government Printing Office. p. 96. ISBN 9781428922914. OTA-USC-340.
- ^ Xia Nanyin; Chan Laixing (1990). "Satellite Launch and TT&C Systems of China and Their Roles in International Cooperation". In F. Sharokhi; J. S. Greenberg; T. Al-Saud (eds.). Space Commercialization: Launch Vehicles and Programs. American Institute of Aeronautics and Astronautics. p. 244. ISBN 0-930403-75-4.
Further reading
- Coy, Peter (January 6, 2021). "Who Remembers the VAX Minicomputer, Icon of the 1980s?". Bloomberg News. Retrieved January 9, 2021.
External links
- HP: VAX Systems at the Wayback Machine (archived December 7, 2004)
- DEC Microprocessors
- SimH VAX Open source emulator that supports VAX architecture
- The complete Digital Technical Journals