Path: utzoo!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!uupsi!cai.com!manager
From: manager@cai.com
Newsgroups: comp.windows.x.motif
Subject: Re: Motif and VT 1200's: They won't mix for me
Message-ID: <370.27daa604@cai.com>
Date: 10 Mar 91 21:32:52 GMT
References: <1991Jan11.123804.1@sif.claremont.edu>
Followup-To: comp.windows.x.motif
Organization: Computer Associates International
Lines: 32

In article <1991Jan11.123804.1@sif.claremont.edu>, chris@sif.claremont.edu writes:
>      Has anybody seen the following (and more importantly, found a fix for it!)?
> 
>      Environment:  VMS 5.4-1 (also occured under VMS 5.3-2)
>                    Motif 1.0
>                    VT 1200
> 
>      Problem: The system crashes when it attempts to start the font daemon for
> the VT 1200.  If Motif 1.0 is not installed (virgin VMS), this doesn't happen.
> It appears that once the user on the VT 1200 uses the Motif window manager, the
> next time that the the font daemon is started up the system crashes.
> 
>      Temporary workaround: Disable the loading of the XTERMINAL support.  (This
> is unacceptable.)
> 

Chris,

We had a similar problem here when we first started making Motif 1.0
available generally. It turned out that the Motif startup was defining
the logical name 'XT' in the LNM$SYSTEM_TABLE, and it was doing this
before DECwindows X terminal startup procedure configured the 'XTA0'
device. If you avoid putting XT in the system table, things should
go back to happy normal.

-- 
Todd Aven
Manager, Mid-range Computer Services
Computer Associates International

Internet:	manager@cai.com
UUCP:		uupsi!usgcdh!manager