COSC1Q0@UHVAX1.UH.EDU ("Lee K. Gleason, Control-G Consultants") (04/21/88)
Anyone out there have any experience with a rather short lived DEC workstation product called the VAXstation 100? I recently acquired most of one, and am trying to put it back on the air. It looks like an interesting product. The piece that is missing is described in the literature as a "UNIBUS window fiber optic transceiver board". Apparently, this hex height board plugged into the host VAX UNIBUS, and downline loaded the workstation software. As I don't even know the module number, it is proving to be a little difficult to find. Any information about that board (especially the DEC module number), or any left over manuals, software, hardware, or wiring diagrams from any now defunct VAXstations would be much appreciated. Leave a message for me here, or call or write... Lee K. Gleason Control-G Consultants 2416 Branard #D Houston TX 77098 Phone 713/528-1859 "The bus came by, and I got on - that's when it all began." -------
PSYDAVE@UBVMSC.CC.BUFFALO.EDU (Dave Straitiff) (05/23/88)
We are currently using a VaxStation 100 in our lab. It gets
used quite extensively for signal processing work. Although it
is rather obsolete, I have found it to be a fairly useful workstation.
Several things to note about it. First and foremost is the fact
that DEC has totally detached from supporting them. ( another one
of DEC's shortlived products ) The last release of the software that
I received was version 1.2. The software is known as VSTA. I believe
version 1.3 exists somewhere. I have been pressing DEC hard, to release
the source code to DECUS. I have had little response, but suspect a
great deal of pressure to work. Version 5 may kill this thing. That
is my greatest concern in getting access to the source code.
The window module is the most critical portion of the link
between the host and the station. The VS100 itself is merely a
display processor based on a 68000. It has micro code loaded across
the fiber optic link via the Unibus window module. After the code
executes, the vax and the VS100 share an area of memory which is
used to communicate.
A few things to note. This thing can really dog a Vax! It
also loves memory (probably more than VMS itself)! I would consider
it using 2-3 meg for average work. The last thing to note is that
it is fairly slow. It takes a great deal of time for it to deal with
occluded windows. It also takes lots of time for it to scroll text.
Finally, on the software side. It is not too difficult to use,
and functions great as a multi job display. It is capable of emulating
tektronix 4014 displays, but functions much better in it's native
VS100 display list code. I have a number a routines written to ease
the pain of native mode programming. I would also recommend avoiding
the Core Graphics Library that comes with it. Slow is giving it credit.
I'd love to hear from anyone still using the VS100. I'd also be
more than happy to share my experiences with anyone who is interested.
Dave...
============================================================================
David M. Straitiff Bitnet: PsyDave@UBvms
Computer Resource Manager Internet: PsyDave@UBvms.cc.buffalo.edu
Phone: (716) 689-8093
Speech Research Laboratory
Department of Psychology
State University of New York at Buffalo
Buffalo, New York 14260
============================================================================