Xref: utzoo comp.os.vms:22815 comp.windows.x:18742
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!quanta.eng.ohio-state.edu!kcgl1.eng.ohio-state.edu!DAVISM
From: DAVISM@kcgl1.eng.ohio-state.edu (Michael T. Davis)
Newsgroups: comp.os.vms,comp.windows.x
Subject: Question re: (VMS) DECwindows Session Manager
Message-ID: <4290@quanta.eng.ohio-state.edu>
Date: 21 Feb 90 14:52:08 GMT
Sender: news@quanta.eng.ohio-state.edu
Organization: Ohio State University
Lines: 27


[Just in case you hadn't noticed, this is being cross posted to comp.os.vms
and comp.windows.x, since there doesn't seem to be a newsgroup which is (VMS)
DECwindows specific.]

	Our site's System Programmer and myself are in the process of porting
the twm window manager to VMS DECwindows.  We have it working, for the most
part.  One thing I haven't been able to figure out is that when I call on the
Session Manager to Quit (LOGOFF), even if I haven't made any customization
changes via the Session Manager, it asks me if I want to save the changes I've
made to the customizations before quitting.  Apparently, the use of the twm
window manager is corrupting something in memory that the Session Manager
examines to determine the "correctness" of the Session Manager customizations.
Does anyone out there know what this "resource" is and/or how to keep twm from
corrupting it.

							Thanks,
							 Mike

    ________________________________________________________________________
   |   InterNet> davism@{kcgl1.eng|rcgl1.eng|osu-20.ircc}.ohio-state.edu    |
   |                                  -or-                                  |
   |                       davis-m@eng.ohio-state.edu                       |
   |                         CompuServe> 73667,541                          |
   |************************************************************************|
   |                      These thoughts, they be mine                      |
    ------------------------------------------------------------------------