ù cISO8859-11¨”Ú o<<ÌŠ &”V»;N Fm 4´ wé #a)…!¯$Ñ Qö4H}LkÝpIºª H ÿ ó ó  (À 3µ ô ª7 ¾ ö  " 6Id ~"‰#$¡+%Í&îÝ'Ì( Ü)*ê*²+,È, õ-Î. Ñ=ò60[g]ÃÊ!>ì8 + d. …& ´2 Û.!$!= R!b 5!µ -!ë""."5";c"C/"YAnother dtsession is currently running - exiting.Screen lock when the screen saver is turned on is not available on this server. Your screen will not be locked when the screen saver is turned on. Invalid display name - exiting.No defaults files exist. No applications will be restarted.No defaults files exist. No applications will be restarted.Unable to remove session directory. Make sure write permissions exist on $HOME/.dt directory. Invalid session files will not be removed.Unable to malloc memory for operation.Unable to lock display. Another application may have the pointer or keyboard grabbed.Unable to open session file. No clients will be restarted.Unable to fork client process.Unable to create DT directories. Check permissions on home directory.Unable to lock display due to security restrictions.Unable to create the temporary file: %s. Make sure write permissions exist for this file. Exiting from Session Manager.Unable to refresh DCE login ticket.Unable to start message server - exiting.The DT message server has exited.Connection to server lost - exiting.Unable to exec process /usr/bin/X11/xrdb. No session resources will be restored.Invalid client settings file. No settings restored.Unable to exec %s.Unable to exec process /usr/dt/bin/dtwm. No window manager will be started.You have reached the maximum allowed number of remote clients. No further remote clients will be restored.Invalid display/language independent resource file. No display/language independent resources will be restored.The wmStartupCommand resource is set to: %s This file does not exist or is not executable. /usr/dt/bin/dtwm will be started instead. An attempt to restore the following command (using the DT remote execution process) on host "%s" failed: %s The following execution string will be tried: %s The following window manager did not start: %s This message indicates you tried to start a window manager that is built into an X terminal. This will only work with X terminals that support this protocol. /usr/dt/bin/dtwm will be started instead. Display locked by user %s.Enter password to unlock.Password: Beginning logout process... Any new data that has not been saved may be lost. Your current session will be saved; however, some applications may need to be restarted after logging in again.Beginning logout process... Any new data that has not been saved may be lost. This session will not be saved. Instead your Home Session will be restored the next time you log in.Logout ConfirmationBeginning logout process... You have two choices for your desktop arrangement the next time you log in: You may save the Current Session to restart as it is now. or You may discard the current session so that your Home Session will be restored. Either way, any new data that has not been saved may be lost.Log out: Save CurrentLog out: Restore HomeLogout Confirmation_DtMessage FailureDisplay locked by user %s.Enter password to unlock.Password: This session was started from an X Window System startup script. No session information will be saved. Use the reset key sequence to log out.Logout _DtMessageThe DT messaging system could not be started. To correct the problem: 1. Choose [OK] to return to the login screen. 2. Select Failsafe Session from the login screen's option menu and log in. 3. Check to see that the hostname is correct in: /etc/hosts Other hostname problems can be corrected by using the command: smit mktcpip For additional information, see the DT User's Guide.Action RequiredMessaging System Inoperative To restart: 1) Save all open data files. 2) Logout. 3) Log in again. Note: The current session will not be saved. When you are ready to begin the restart process, click [OK] and proceed to save your files.Continue logoutCancel logoutThe DT messaging system could not be started. To correct the problem: 1. Choose [OK] to return to the login screen. 2. Select Failsafe Session from the login screen's option menu and log in. 3. Check to see that the hostname is correct in: /etc/hosts Other hostname problems can be corrected by using the command: smit mktcpip 4. Check to see that if a search list is specified in /etc/resolv.conf, it includes the domain your machine is configured on. For additional information, see the DT User's Guide.The ToolTalk message server (ttsession) could not be started within the time specified by the DT_TTSESSION_TIMEOUT environment variable or, if the environment variable is not explicitly set, within the default time, %d seconds. Therefore, the normal session manager could not be started. This Failsafe session has been started instead to allow you to correct the problem. The ToolTalk message server may not start because of various configuration errors. For example, you must have write permission to your home directory ($HOME) and your network must be properly configured and operational. You should check that the hostname is correct in /etc/hosts. Other hostname problems can be corrected by using smitty tcpip. If a search list is specified in /etc/resolv.conf, you should verify that it includes the domain in which your machine is configured. You may want to temporarily rename /etc/resolv.conf in order to isolate whether there is a problem with DNS. Another example of a network misconfiguration problem is that a machine has been moved to another location but the TCPIP subnet information has not been updated. You should also verify that the network cable to your system is securely fastened and look for errors in $HOME/.dt/startlog. If you believe that your system is correctly configured, you can increase the time allowed to start the ToolTalk Message Server (ttsession) by changing or setting the time specified via the DT_TTSESSION_TIMEOUT environment variable in your $HOME/.dtprofile file. For example, add the following line to your $HOME/.dtprofile to change the time to 2 minutes (120 seconds): export DT_TTSESSION_TIMEOUT=120 When you want to return to the CDE login screen, click "Exit Session". This Failsafe session will then terminate. For additional information, you can refer to /usr/dt/README and the CDE books, "Advanced User's and System Administrators's Guide" and "ToolTalk Messaging Overview".ToolTalk Message Server Could Not Be StartedExit SessionThe setting for the DTUSERSESSION environment variable is too long. Your desktop session has started but some applications (for example, Application Manager and Help Manager) may not run or may not run correctly. Refer to /usr/dt/README for details along with corrective action that you can take. When a desktop application does not run properly with a long setting for DTUSERSESSION, you should check for errors in $HOME/.dt/startlog and $HOME/.dt/errorlog.Warning - DTUSERSESSION too longClient message failed. Client information will not be saved.Invalid root window. Can not save client information.Session restoration information not updated for client . Invalid information may be saved.Session restoration information not updated for client %s. Invalid information may be saved.DISABLE_SCREEN_SAVER_SWITCH is set for your environment. Therefore, there will be no switching from one background screen saver to another even though you have enabled this switch in the Style Manager. Color Server Warning: couldn't get ownership of the selection:Color Server Warning, losing ownership of the selection:Should never lose the selection.Warning, found more pixels then are available.Warning, can't allocate enough pixels.Color Server Warning, the size of file is invalid:Color Server Warning, invalid information in '' removing file and starting again. Color Server FatalError, not enough memory to create the structure for a palette. Warning: Color Server system default file is corrupt Color Server Warning, could not read file %s Session Manager HelpPromptErrorMessage@(#)version_goes_here @(#)_DtMessage catalog source $Revision: 1.5 $