Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: VWS - PSI incompatibility.
Message-ID: <880105131720.04e@CitHex.Caltech.Edu>
Date: 5 Jan 88 22:07:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23


 > I noticed that I confused some people with  my  remark  that  the  VWS  and
 > PSI(-ACCESS) products are incompatible.  I was referring to VWS 3.2 and PSI
 > 4.1.
 > 
 > Page 2-8 of the PSI installation manual:
 >         VAX P.S.I.
 >         (Packetnet Systems Interface)
 >         Installation Procedures
 > tells you to change the SYSGEN parameter TTY_CLASSNAME to "TP".
 > 
 > When we changed the TTYCLASSNAME this way on a VAXstation 2000 on which VWS
 > had  been  installed, we had severe problems with interactive windows, like
 > terminal emulators, HELP windows and some  SETUP  windows.   These  windows
 > were  never  deleted  anymore.   Some attempts to delete these windows even
 > crashed the system.  Does this mean that PSI(-ACCESS) cannot be run from  a
 > VAXstation on which VWS is running?

I'm not sure.  First of all, you have to set the SYSGEN parameter TTY_CLASSNAME
to "TP" only if you want X29 support, if I recall correctly; I didn't check to
see what would happen if you didn't set the parameter, and I can't bring
down my system right now to find out.  I've got hardware maintenance scheduled
for Thursday, and I'll try to make the experiment then.