home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!decwrl!sdd.hp.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!kcgl1.eng.ohio-state.edu!DAVISM
- From: DAVISM@kcgl1.eng.ohio-state.edu (Michael T. Davis)
- Newsgroups: comp.os.vms
- Subject: VXT2000 and LAT transport
- Message-ID: <1992Jul24.212823.3398@magnus.acs.ohio-state.edu>
- Date: 24 Jul 92 21:28:23 GMT
- Sender: news@magnus.acs.ohio-state.edu
- Organization: The Ohio State University
- Lines: 27
- Nntp-Posting-Host: kcgl1.eng.ohio-state.edu
-
-
- A research group here recently received a VXT2000 X-terminal and a
- DECstation 5000/240. They use the DECstation to boot the X-terminal via MOP.
- The group members would also like to run X-based programs on our VAX using the
- LAT transport, but they aren't having very good luck. Whenever they try to use
- the LAT transport, they get the error associated with the symbol DWT$_DWTABORT
- (03AB8204 hex) when they try to start an X-client. The command to create a
- display that they are using is
-
- $ SET DISPLAY/CREATE/TRANSPORT=LAT/NODE=<lat-node>
-
- where <lat-node> is derived from the terminal TT_ACCPORNAM field. (They
- create a LAT terminal session to the VAX, first.) Security on the X-terminal
- is currently set to allow anyone to access the local display. (Can you specify
- a username with the LAT transport as you can with the DECnet transport?)
-
- I'm hoping that something's just misconfigured. Could someone please
- supply the steps necessary to get things going? I looked at the documentation
- received with the VXT software (esp. the VAX-related information) but it didn't
- provide any obvious fixes.
-
- Thanks,
- Mike
- --
- Internet: davism@KCGL1.eng.ohio-state.edu |
- -or- DAVISM+@osu.edu | These Thoughts, They Be Mine
- BITNET: DAVISM+@OHSTMAIL.BITNET |
-