Difference between revisions of "VAXstation 100"
(→External links: Link to emulator demo.) |
(Role of BBA) |
||
| Line 5: | Line 5: | ||
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 via [[fiber optic]] cables. The [[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]].) | 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 via [[fiber optic]] cables. The [[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' was attached to the display processor module; it used a separate [[bus]] to get to the screen memory. | + | 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', which 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, was attached to the display processor module; it used a separate [[bus]] to get to the screen memory. |
| − | 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 | + | 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. | ||
Revision as of 12:13, 20 February 2023
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 connected it via fiber optic cables. The 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', which 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, was attached to the display processor module; it used a separate bus to get to the screen memory.
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.
See also
External links
- VAXstation100 - documents on Bitsavers
- ROM images (down the page)
- VAXstation Software - layered product for VAX/VMS; see [https://classiccmp.org/pipermail/cctalk/2020-September/055387.html
- VS100 emulator demoing the built-in self tests.
