My original question:
>I am trying to connect from my Windows NT 4.0 Pentium Pro to my DEC Alpha
>(named hopland) using PC-Xware 5.0 Classic. Everything seems to go okay
>when I connect using XDM (as opposed to telnet), and the CDE comes up.
>However, when I try to run a program called Arc/Info, I get the message
>"FATAL ERROR, Segment Violation." The line in the .arc configuration file
>that seems to cause this is:
>&term 9999 (this line tells Arc/Info that it will be using xterms as the
>data display windows)
>
>If I add the following line to my .cshrc file:
>setenv DISPLAY hopland:0
>then Arc/Info will at least start, but I get the following messages when the
>.arc file tries to set the terminal type:
>Xlib: connection to "hopland:0.0" refused by server
>Xlib: Client is not authorized to connect to Server
>Cannot open channel to XSERVER (hopland:0)
>
I have not been able to fix this problem, but thank you to the 6 people that
responded (their responses are included below). If I have the setenv
DISPLAY hopland:0 line in my .cshrc file, I can almost get everything to
work - but the Arc/Info terminal pops up on my DEC Alphastation instead of
my PC running PC-Xware!!!
I did try the suggestions include below, but haven't been able to get things
to work.
RESPONSES:
From: Brian Parkhurst <brianp_at_u.washington.edu>
Have you entered your alphastation in your trusted host list in PC-Xware?
I had a similar problem with just getting the Xterms to work on the
Version of PC-Xware that ships with Novell Lan WorkPlace Pro 95/NT, until
I fully entered the host name and IP.
From: Tim Medlock <tmedlock_at_hilliary.nosc.mil>
Colin,
I use eval and tset in my .login to set the term type and then evaluate it
against type xterm. I rlogin to HP's and SGI's. Do a man on 'tset' and see if
that maybe what you're looking for. After the login, look at your env. Mine
displays "TERM=xterm" or whatever I set it for.
eval `tset -s -Q -m ':?xterm' `
This will definitely allow you to set your term type, but I don't know about
ARC/INFO running correctly.
From: matthewm_at_voyager.sgate.com (Michael Matthews)
The error you're getting is saying that the machine hopland is not
allowing connections from the machine that's running Arc/Info. I
suspect it's maybe due to Arc/Info running as a separate userid?
If you can something like "xhost +arcinfo-machine" (where
arcinfo-machine is the name of the machine that runs Arc/Info), _on
hopland_, that should fix the problem.
From: "Nagaraja, Raja" <Raja.Nagaraja_at_actew.com.au>
I think it looks like a security issue for the display. In the
Decwindows session, we have to put the server name in the security
option to get a x window display. Perhaps there is a similar thing for
CDE.
From: WOODT_at_ORAU.GOV
This is a fairly wild guess, but change the "setenv DISPLAY hopland:0" to
"setenv
DISPLAY hopland:0.0". My guess is that the ARC/Info software is looking for the
subdisplay (the .0 portion of the DISPLAY variable).
Hope this helps!
Tom Wood
From: rnfrank_at_pierce.llnl.gov
Hello Colin,
I connect to DU4.x machines from my NCD 19c by starting a telnet
session on
the target host and then run this script (WOLFRM is the name of my xterminal).
set DISPLAY WOLFRM:0
export DISPLAY
/usr/dt/bin/Xsession
We use a similar technique from a windoze95 system (Xvision software)
but needed to use rlogin rather than telnet.
rich frank
***END OF RESPONSES****
TTFN,
Colin
****************************************************
Colin Brooks
GIS Program Analyst
Integrated Hardwood Range Management Program
Hopland Research & Extension Center
4070 University Rd.
Hopland, CA 95449
Primary #'s - TEL:(707)744-1270 FAX:(707)744-1040
Work E-mail: cbrooks_at_nature.berkeley.edu
http://danr.ucop.edu/ihrmp
http://www.pacific.net/~cbrooks/gis1.htm
I'm also found at:
ESPM, University of California - Berkeley
160 Mulford Hall
Berkeley, CA 94720-3114
Secondary #'s - TEL: 510-643-1136 FAX: 510-643-5438
****************************************************
Received on Tue Jul 01 1997 - 20:55:51 NZST