[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

1823.0. "Problems creating DECterms" by NITMOI::PESENTI (JP) Thu Nov 30 1989 15:13

One of the folks in my group cam to me with an unusual problem.  He is running 
VMS/DECwindows V5.3 on his VS2000.  Currently, he has been using a DECW$LOGIN
command procedure that creates his decterms using CHILD.  Today he wanted one
more decterm, and tried to create it using the standard applications menu in
the session manager.  He has not changed the definition of the decterm startup
at all (CREATE/TEMINAL=DECTERM/DETACH).  What happens is that he gets a process
with the id = <username>_SM, but no window and no icon.  In addition to the
DECW$TE_1 process that was there already, he now has a DECW$TE_1A process.
If you kill all the processes with the <username>_SM id, and create another
decterm, you get a DECW$TE_1B.

Any ideas as to where we can look to figure out this problem?

By  the way, his system manager account has the same DECW$LOGIN.COM, but does
not display this problem.  His user account has some privileges, and setprv,
and hefty quotas.

T.R	Title	User	Personal Name	Date	Lines
1823.1	Try not using CHILD	AGBEAR::HORNER	A.G.Bear, Old fashion teddy bear	`Thu Nov 30 1989 17:41`	9
	Although the absolute latest version of CHILD is supposed to be compatible, I have had this problem on several of our systems here when mixing CHILD and CREATE/TERMINAL. The solution was to stop using CHILD. In fact, I found that it is best to clear out all of our V1 workarounds for doing what AUTOSTART will do in V2. After doing this, all problems completely disappeared. I suspect the same will work for you. Dave
1823.2	See hannah::decw$disk:[public]decterm, note 508	HANNAH::MESSENGER	Bob Messenger	`Thu Nov 30 1989 17:50`	13
	Re: .0 This was discussed in note 508 in the DECterm conference (KP7 to select). The workaround suggested there was to use CREATE/TERMINAL instead of CHILD. Another possible workaround is to make sure there are no SET DISPLAY commands in your LOGIN.COM. One thing that's different in your situation is that you say that a DECW$TE_1A process gets created, which nobody mentioned in the DECTERM note. This may not be important, though: they may not have noticed the additional process. -- Bob
1823.3	Note collision	HANNAH::MESSENGER	Bob Messenger	`Thu Nov 30 1989 17:52`	5
	Re: .1 Oops, you beat me to it. -- Bob
1823.4	Thanks	NITMOI::PESENTI	JP	`Tue Dec 05 1989 07:33`	5
	Wel,, I still don't know what specifically caused the problem to happen in the user account and not the system account, but AUTOGEN fixed the problem. Thanks -JP
1823.5		PRNSYS::LOMICKAJ	Jeffrey A. Lomicka	`Thu Dec 07 1989 12:17`	2
	Do you still get two terminal emulator processes?
1823.6	I don't know...	NITMOI::PESENTI	JP	`Fri Dec 08 1989 08:06`	2
	After he solved the problem, he took a day and updated his startup files to use the customization available in V5.3. He no longer runs CHILD.