We're demoing EWS (Eln Window System?) here, it's the software that
    runs on a VT1300.
    
    The VAXstation 2000s we have here (6MB memory) absolutely *scream* with
    this software installed!  Performance is at least equal to my
    VAXstation 3200 with 16MB memory, definitely outruns a VAXstation 3100
    with 8MB.
    
    The drawback (and that's why this is a demo) is the question "What sort
    of load do X-terminals put onto their server node?"  We boot the
    cluster from a pair of 8820s, and I don't want to sink them into the
    dirt.  So we're moving cautiously, though I must say the three people
    whose VS2000s have been converted into EWS terminals will put up one
    hell of a squawk if I decide to change 'em back.
    
    It appears only the VT1300 (not the VT1200) comes with EWS.  If the
    1200 is anything like the VT1000 we have here, then forget it.  This
    seems rather odd, since the 8820 is the server node for the
    VT1000/VT1200/EWS2000, and the EWS-running VAXstation 2000 runs circles
    around the others...?
    
    Quote I've seen is for a distribution kit, and VAXstation 2000 and
    microVAX 2000 licenses (can't figure out the latter...).  You need to
    purchase a VAXeln license for the units you run this software on, and
    they require a minimum 6MB for the VAXstation 2000.  Part numbers are:
    
    	VAXeln runtime license for MV2000 (?!)		QL-376AP-FA
    	VAXeln runtime license for VS2000		QL-376AR-FA
    	VAXeln/EWS VMS - TK50				QA-YWRAA-H5
    
    (I can't imagine what you'd do with a MV2000 license, maybe I
    misunderstand the info...?)
    
    List price for my initial configuration of three VAXstation 2000s and
    distribution media is under $2200.  Lots cheaper than throwing them out
    and replacing them with VT1300s, and lots faster than I've seen running
    on VT1000s and heard of running on VT1200s.
    
    	-gus