Difference between revisions of "VAXstation 100"
(→External links: Fix typo in link.) |
m (Rename VAX cat) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
The '''VAXstation 100''' was a programmable [[graphics]] [[terminal]] manufactured by [[Digital Equipment Corporation|DEC]]. It had a [[bit-mapped display]], and could accept, for presentation to the user, text, diagrams or images (when running its usual on-board program, in its [[microprocessor]]). | The '''VAXstation 100''' was a programmable [[graphics]] [[terminal]] manufactured by [[Digital Equipment Corporation|DEC]]. It had a [[bit-mapped display]], and could accept, for presentation to the user, text, diagrams or images (when running its usual on-board program, in its [[microprocessor]]). | ||
| − | It consists of a separate chassis containing a 'display processor module', which is attached remotely to a 'bus window module' in the host computer, which connected | + | It consists of a separate chassis containing a 'display processor module', which is attached remotely to a 'bus window module' in the host computer, which is connected to the other module via [[fiber optic]] cables. The [[VR100 Monochrome Monitor|VR100]] [[display]] (a [[cathode ray tube|CRT]] capable of 1,088x864 [[pixel]]s [[resolution]]) was attached to the display processor module, along with a [[keyboard]] and [[mouse]]. (The chassis contained a separate [[power supply]].) |
| − | The display processor module used a [[Motorola MC68000]]; it had 128K bytes of [[main memory]], in addition to the 512K bytes of memory for the bit-mapped display (only 1/4 of that actually drove the display; the rest could be used to hold data such as [[font]]s). [[Bootstrap]] and [[diagnostic]] code was contained in [[PROM]]s; operating [[object code]] was downloaded over the fiber link once the VAXstation 100 had powered on. A 'Bit Blit Accelerator module' | + | The display processor module used a [[Motorola MC68000]]; it had 128K bytes of [[main memory]], in addition to the 512K bytes of memory for the bit-mapped display (only 1/4 of that actually drove the display; the rest could be used to hold data such as [[font]]s). [[Bootstrap]] and [[diagnostic]] code was contained in [[PROM]]s; operating [[object code]] was downloaded over the fiber link once the VAXstation 100 had powered on. A 'Bit Blit Accelerator module' was attached to the display processor module; it used a separate [[bus]] to get to the screen memory. The BBA off-loaded some laborious low-level tasks (such a copying an area of the display to somewhere else, e.g. in moving a [[window]]) from the microprocessor, and performed them as quickly as possible. |
The only bus window module available, the UNIBUS Window Module, was a [[DEC card form factor|hex]] card, the M7452, which plugged into a standard [[Modified UNIBUS Device|MUD]] slot. Although in theory a VAXstation 100 could be attached to any host with a [[UNIBUS]], DEC only supported them on [[VAX]]en running [[VMS]]. Software in the VAXstation 100 and VMS represented the VAXstation 100 as a series of terminals (one for each open window) to VMS. | The only bus window module available, the UNIBUS Window Module, was a [[DEC card form factor|hex]] card, the M7452, which plugged into a standard [[Modified UNIBUS Device|MUD]] slot. Although in theory a VAXstation 100 could be attached to any host with a [[UNIBUS]], DEC only supported them on [[VAX]]en running [[VMS]]. Software in the VAXstation 100 and VMS represented the VAXstation 100 as a series of terminals (one for each open window) to VMS. | ||
The VAXstation 100 is of some historical note due to its role in the development of the [[X Window System]]. Babara Liskov's [[CLU]] group had acquired a number of VAXstation 100 terminals and needed a [[window]]ing system running on [[BSD|Berkeley Unix]]. Initially the [[W window system]] was used, but Bob Scheifler largely re-wrote it to become X. | The VAXstation 100 is of some historical note due to its role in the development of the [[X Window System]]. Babara Liskov's [[CLU]] group had acquired a number of VAXstation 100 terminals and needed a [[window]]ing system running on [[BSD|Berkeley Unix]]. Initially the [[W window system]] was used, but Bob Scheifler largely re-wrote it to become X. | ||
| + | |||
| + | ==Software support== | ||
| + | |||
| + | * [[4.3 BSD]] comes with a driver for the VAXstation 100 called vs.c. | ||
| + | * VMS has a layered product called ''VAXstation Software''; see below. | ||
| + | * The X Window System supports the VAXstation 100 from the initial version, to X10R4. | ||
| + | * [[Massachusetts Institute of Technology|MIT]] Project Athena had a terminal emulator that handled multiple VAXstation 100's. It was maybe called ''vsterm'', and was possibly written in [[CLU]]. | ||
==See also== | ==See also== | ||
| Line 22: | Line 29: | ||
** [http://www.bitsavers.org/pdf/dec/vax/vaxstation100/VS100_Engineering_Specification_Jun83.pdf VAXstation 100 Engineering Specification] | ** [http://www.bitsavers.org/pdf/dec/vax/vaxstation100/VS100_Engineering_Specification_Jun83.pdf VAXstation 100 Engineering Specification] | ||
** [http://www.bitsavers.org/pdf/dec/vax/vaxstation100/AA-N660A-TE_VAXstation_100_Users_Guide_Jun84.pdf VAXstation 100 User's Guide] (AA-N660A-TE) | ** [http://www.bitsavers.org/pdf/dec/vax/vaxstation100/AA-N660A-TE_VAXstation_100_Users_Guide_Jun84.pdf VAXstation 100 User's Guide] (AA-N660A-TE) | ||
| + | ** [http://www.bitsavers.org/pdf/dec/vax/vaxstation100/Levy_-_Workstation_Graphics_Architecture_preliminary_19831107.pdf Workstation Graphics Architecture] | ||
* [http://www.9track.net/roms/ ROM images] (down the page) | * [http://www.9track.net/roms/ ROM images] (down the page) | ||
* [http://www.9track.net/bits/dec/vs100/ VAXstation Software and VSTA] - layered product for VAX/VMS; see [https://classiccmp.org/pipermail/cctalk/2020-September/055387.html Matt Burke's email] | * [http://www.9track.net/bits/dec/vs100/ VAXstation Software and VSTA] - layered product for VAX/VMS; see [https://classiccmp.org/pipermail/cctalk/2020-September/055387.html Matt Burke's email] | ||
* [https://www.youtube.com/watch?v=3POQ7rvL8_Q VS100 emulator demoing the built-in self tests.] | * [https://www.youtube.com/watch?v=3POQ7rvL8_Q VS100 emulator demoing the built-in self tests.] | ||
| − | [[Category: | + | [[Category: DEC Graphics Terminals]] |
| − | [[Category: | + | [[Category: VAX]] |
Latest revision as of 02:24, 12 August 2024
The VAXstation 100 was a programmable graphics terminal manufactured by DEC. It had a bit-mapped display, and could accept, for presentation to the user, text, diagrams or images (when running its usual on-board program, in its microprocessor).
It consists of a separate chassis containing a 'display processor module', which is attached remotely to a 'bus window module' in the host computer, which is connected to the other module via fiber optic cables. The VR100 display (a CRT capable of 1,088x864 pixels resolution) was attached to the display processor module, along with a keyboard and mouse. (The chassis contained a separate power supply.)
The display processor module used a Motorola MC68000; it had 128K bytes of main memory, in addition to the 512K bytes of memory for the bit-mapped display (only 1/4 of that actually drove the display; the rest could be used to hold data such as fonts). Bootstrap and diagnostic code was contained in PROMs; operating object code was downloaded over the fiber link once the VAXstation 100 had powered on. A 'Bit Blit Accelerator module' was attached to the display processor module; it used a separate bus to get to the screen memory. The BBA off-loaded some laborious low-level tasks (such a copying an area of the display to somewhere else, e.g. in moving a window) from the microprocessor, and performed them as quickly as possible.
The only bus window module available, the UNIBUS Window Module, was a hex card, the M7452, which plugged into a standard MUD slot. Although in theory a VAXstation 100 could be attached to any host with a UNIBUS, DEC only supported them on VAXen running VMS. Software in the VAXstation 100 and VMS represented the VAXstation 100 as a series of terminals (one for each open window) to VMS.
The VAXstation 100 is of some historical note due to its role in the development of the X Window System. Babara Liskov's CLU group had acquired a number of VAXstation 100 terminals and needed a windowing system running on Berkeley Unix. Initially the W window system was used, but Bob Scheifler largely re-wrote it to become X.
Software support
- 4.3 BSD comes with a driver for the VAXstation 100 called vs.c.
- VMS has a layered product called VAXstation Software; see below.
- The X Window System supports the VAXstation 100 from the initial version, to X10R4.
- MIT Project Athena had a terminal emulator that handled multiple VAXstation 100's. It was maybe called vsterm, and was possibly written in CLU.
See also
External links
- VAXstation100 - documents on Bitsavers
- ROM images (down the page)
- VAXstation Software and VSTA - layered product for VAX/VMS; see Matt Burke's email
- VS100 emulator demoing the built-in self tests.
