From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  8-DEC-1989 21:37
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: DECwindows and VWS

Received: From UICVM.UIC.EDU by CRVAX.SRI.COM with TCP; Fri,  8 DEC 89 13:19:50 PDT
Received: from Bitway.Rose-Hulman.Edu by UICVM.uic.edu (IBM VM SMTP R1.2.1MX) with BSMTP id 6377; Fri, 08 Dec 89 15:18:10 CST
Received: from ROSEVC.Rose-Hulman.Edu by Bitway.Rose-Hulman.Edu; Fri, 8 Dec 89
 15:02 EST
Date: Fri, 8 Dec 89 15:02 EST
From: "Jerrod T. Carter, Asst. Manager" <MGRJTC%ROSEVC.Rose-Hulman.Edu@UICVM.uic.edu>
Subject: Re: DECwindows and VWS
To: Info-VAX@SRI.COM
Message-Id: <10AB65C07F9F405368@ROSEVC.Rose-Hulman.Edu>
X-Envelope-To: Info-VAX@SRI.COM
X-Vms-To: IN%"Info-VAX@SRI.COM"

A couple of days ago, I wrote:

>While that is what the VWS server is advertised as doing, it doesn't work
>properly.  If you try to use it under VMS 5.2, it won't work.  VWS 4.2 was
>SUPPOSED to correct to problem, but it didn't.  Also, 4.2 introduced a new

Since that time, I found a little known and little publicized trick.  Remember,
this is not supported, and I accept no responsibility if it causes your VAX to
go up in flames or anything less than that either.  All I'm saying is, it
worked for me; don't count on it working for you.

Apparently, there is just one image that is causing the problem.  All that
needs to be done is to replace the image with the one created fro VMS 5.1
systems.  This is done like so:

$ BACKUP VWSDECW010.B/SAVE/SEL=([*...]DECW$SERVER_DDX_GV.EXE) []/LOG
$ COPY DECW$SERVER_DDX_GV.EXE SYS$SHARE:/PROT=W:RE

I got the file VWSDECW010.B off of my VWS 4.2 tape, although I would guess that
the same file on the VWS 4.1 tape will work also.

BTW, I am running VMS 5.2 and VWS 4.1 on a VAXstation II/GPX.

Jerrod T. Carter, Assistant Networking Manager | I'm a chronic liar. Trust me.
Rose-Hulman Institute of Technology            |
MGRJTC@RoseVC.Rose-Hulman.Edu                  | "May all your faults be soft."