# @(#)22 1.41 src/cde/README, desktop, cde720 11/10/04 10:44:41 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # cde720 src/cde/README 1.41 # # Licensed Materials - Property of IBM # # COPYRIGHT International Business Machines Corp. 1994,1995 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG # # COMPONENT_NAME: desktop # # FUNCTIONS: README # # ORIGINS: 27 # Common Desktop Environment # # (C) Copyright Hewlett-Packard Company 1993, 1994. # (C) Copyright International Business Machines Corp. 1993, 1994. # (C) Copyright Sun Microsystems, Inc. 1993, 1994. # (C) Copyright Unix System Labs, Inc., a subsidiary of Novell, Inc. 1993, 1994. # # # RESTRICTED RIGHTS LEGEND # # Use, duplication, or disclosure by the U.S. Government is subject to # restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in # Technical Data and Computer Software clause in DFARS 252.227-7013. Rights # for non-DOD U.S. Government Departments and Agencies are as set forth in # FAR 52.227-19(c)(1,2). # # Hewlett-Packard Company, 3000 Hanover Street, Palo Alto, CA 94304 U.S.A. # International Business Machines Corp., Route 100, Somers, NY 10589 U.S.A. # Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, CA 94043 U.S.A. # Unix System Labs, Inc., 190 River Road, Summit, NJ 07901 U.S.A. # ############################################################################## This file includes information that was not included in the AIX Common Desktop Environment (CDE) 1.0 documentation and known defects in the desktop that have the most impact on desktop users. The defects are grouped by desktop component. This README contains the following: o Migration o Internationalization Overview for CDE 1.0 o Known Defects and Helpful Hints o For more information ============================================================================== Migration from AIXwindows Desktop on AIX 4.1.1 or AIX 4.1.2 to the new AIX Common Desktop Environment (CDE) 1.0 on AIX 4.1.3 and beyond ============================================================================== If you are migrating to the new AIX CDE from any previous AIXwindows Desktop AIX 4.1 or AIX 3.2, be sure to review the Help Volume "Welcome to AIX CDE 1.0," selectable from the subpanel of the Help Manager on the front panel. This help volume describes what you can expect to encounter after migration. If you used the AIXwindows Desktop on AIX 4.1.1 or AIX 4.1.2, then you may need to have the X11.Dt.compat fileset installed. The "Welcome to AIX CDE 1.0" help volume describes particular instances in which the X11.Dt.compat fileset is required. If errors are being recorded in your $HOME/.dt/errorlog file, then you should install X11.Dt.compat fileset. Any active users can execute "dtaction ReloadActions" after X11.Dt.compat is installed to load new actions into their desktop database. If other unexpected errors are encountered, review the "Welcome to AIX CDE 1.0" help volume for further information. ============================================================================== Internationalization Overview for CDE1.0 on AIX 4.1.3 and beyond ============================================================================== General - Font Alias( -dt- font alias ) A set of -dt font aliases is provided for each locale supported by AIX. Refer to /usr/lib/X11/fonts/font.alias* for a mapping of the -dt- alias name to the respective locale specific font. In detail, see man page of DtStdInterfaceFontNames and DtStdAppFontNames. - How to change the setting of the system wide default font /usr/dt/config/$LANG/sys.resources defines which sys.font file should be used. If you want to change the default font, do the following - Modify /usr/dt/config/$LANG/sys.resources file to include the appropriate sys.font file. - Modify that sys.font file to use your preferred font. For details, refer to the "Common Desktop Environment 1.0: Advanced User's and System Administrator's Guide". Individual users can configure fonts using the Style Manager, dtstyle. - How to setup the keyboard map. The appropriate keymap is set by either /usr/dt/config/Xsetup or /usr/dt/bin/Xsession. You can configure it via /usr/dt/config/Xconfig file. Refer to /usr/dt/config/Xsetup file and the "Common Desktop Environment 1.0: Advanced User's and System Administrator's Guide". For example: How to setup Xstation keyboard/locale settings a. cp /usr/dt/config/Xconfig /etc/dt/config/Xconfig b. cp /usr/dt/config/Xsetup /etc/dt/config/Xsetup_keyboard_XXX c. modify /etc/dt/config/Xconfig's *setup resource to: Dtlogin*host_domain_name_0*setup: /etc/dt/config/Xsetup_keyboard_XXX d. modify /etc/dt/config/Xconfig's *language resource to: Dtlogin*host_domain_name_0*language: e. modify /etc/dt/config/Xsetup_keyboard_XXX's KBD_MAP[0] to: KBD_MAP[0]=":0 " f. restart dtlogin should be substituted with your locale name, e.g. ja_JP should be substituted with your Xstation hostname - Mnemonic - This issue is for only Asian countries: In some cases, a mnemonic may not function even if the labels are translated with the mnemonic like: (X) - This issue is also for only Asian countries: In some cases, a mnemonic may function even if the label is translated without the mnemonic like: - Individual components - dtcalc - Under some languages, dtcalc'c buttons are truncated. If you see this problem, you can resize dtcalc's window to see whole button labels. - dtmail - DO NOT ... - Use sendmail.cf's Ob and OO. dtmail converts any language e-mail body to the appropriate codeset via iconv. - Use the multibyte character in the "From" field. - Select SunMailTool option if you are going to send non English e-mail. You can see this option at In New Message Window, "File -> Send As" - Print The current dtmail prints out the e-mail as is. So that if you get multibyte e-mail, you need to do "Message -> Save As Text" to save the e-mail as text then print it. - How to customize the conversion table for dtmail. - Send First, dtmail converts the current locale to CDE Character Set Name by refering to /usr/dt/config/svc/AIX.lcx file. Next, it converts CDE Character Set Name to CDE interchangeCodeset Name. Third, it converts CDE interchangeCodeset Name to the codeset name which can be used for iconv(). For example, if the locale is ko_KR, locale CDE Character Set Name -------------------------- --------------------------- ko_KR ==> EUC-KR CDE Character Set Name CDE interchangeCodeset Name --------------------------- --------------------------- EUC-KR ==> ISO-2022-KR CDE interchangeCodeset Name codeset for iconv --------------------------- --------------------------- ISO-2022-KR ==> fold7 and dtmail knows that it should convert the string from ko_KR's codeset(IBM-eucKR) to fold7. You can change only the last conversion (from ISO-2022-KR to fold7)'s "fold7". It is defined in /usr/dt/config/svc/AIX.lcx file: AIX.320+.iconv1,iconv3.>.?.: In the above example, you can modify AIX.320+.iconv1,iconv3.>.?.ISO-2022-KR: - Receive First, dtmail picks up "charset" parameter. Next, it converts it to CDE interchangeCodeset Name. Third, it converts CDE interchangeCodeset Name to the the codeset name which can be used by iconv(). Forth, it converts CDE interchangeCodeset Name to CDE Character Set Name. Fifth, it converts CDE Character Set Name to the codeset name which can be used by iconv(). For example, if "charset" is ISO-2022-KR, charset CDE interchangeCodeset Name --------------------------- --------------------------- ISO-2022-KR ==> ISO-2022-KR CDE interchangeCodeset Name codeset for iconv --------------------------- --------------------------- ISO-2022-KR ==> fold7 CDE interchangeCodeset Name CDE Character Set Name --------------------------- --------------------------- ISO-2022-KR ==> EUC-KR CDE Character Set Name codeset for iconv --------------------------- --------------------------- EUC-KR ==> IBM-eucKR and dtmail knows that it should convert the string from fold7 to IBM-eucKR. You can change only the second conversion (from ISO-2022-KR to fold7)'s "fold7". It is defined in /usr/dt/config/svc/AIX.lcx file: AIX.320+.iconv1,iconv3.>.?.: In the above example, you can modify AIX.320+.iconv1,iconv3.>.?.ISO-2022-KR: - dtcm - The current dtcm cannot process the different codeset Calendar data correctly. For example: If the Calendar data is saved with zh_CN ( Simplified Chinese(EUC) ), the date cannot be read by dtcm correctly if LANG is set to ZH_CN( Simplified Chinese(UTF) ). - The date format in the dtcm's window does not conform to various language cultural convention. (By Options dialog, you can change this format with Category set to Date Format. But this is not enough for supporting all language's cultural conventions.) The following date formats can be configured by app-defaults file. 1. The month/year name in DayView window. It can be configured by /usr/dt/app-defaults/$LANG/Dtcm's value of "Dtcm*XmMonthPanel.titleFormat:" 2. The month name in YearView window. It can be configured by /usr/dt/app-defaults/$LANG/Dtcm's value of "Dtcm*yearForm.XmMonthPanel.titleFormat:" 3. The date format in the weekview and dateview using the following resources: Dtcm.dateFormatMDY /* this resource should be used for MM/DD/YY format */ Dtcm.dateFormatDMY /* this resource should be used for DD/MM/YY format */ Dtcm.dateFormatYMD /* this resource should be used for YY/MM/DD format */ For information about the format string, refer to the man page of strftime function. - dtwm - This is an issue only for Traditional Chinese 101 keyboard: Ctrl + Alt + 1 Ctrl + Alt + 0 Shift + Esc keys which should be used by the Input Method conflict the dtwm's special functions. - dtterm - The current dtterm doesn't support BiDi. By default, aixterm is launched from the FrontPanel for those locales. - dthelpview/libDtHelp.a - If you'd like to use your preferred font, set up the following resources for the font. *pitch.size.slant.weight.style.lang.char-set: font-name : where: pitch: p(propotional) or m(monospace) size: 6, 8, 10, 12, 14 slant: roman(upright letter) or italic(slanted letter) weight: medium or bold style: serif or sans_serif lang: CDE Languate/Territory name examples: *.6.*.*.*..: *.8.*.*.*..: *.10.*.*.*..: *.12.*.*.*..: *.14.*.*.*..: As for CDE Language/Territory name and CDE CharacterSet name, refer to the CDE 1.0 Help System Author's and Programmer's Guide (ISBN 0-201-48955-4). These definitions can be added to the /usr/dt/app-defaults/$LANG/Dt application default file, or they can be added to a session using the EditAppResources action from the SampleClients folder of the Application Manager. ============================================================================== Known Defects and Helpful Hints ============================================================================== Login Manager ~~~~~~~~~~~~~ It is recommended that the desktop login manager (dtlogin) be started via /etc/inittab. By default, dtlogin is started via inittab, but should it be necessary to add it, the '/usr/dt/bin/dtconfig -e' command can be issued as root to do so. The portmapper subsystem must be active for users to be able to start the desktop. By default, portmapper should be active, but if it is necessary to restart portmapper, do the following as root: stopsrc -s inetd startsrc -s portmap startsrc -s inetd To have Xsession execute your $HOME/.xsession file rather than dtsession for a single user (comparable to the system-wide "Dtlogin*xdmMode" resource described in the dtlogin manpage), follow these steps : 1) login to dtlogin for the user requiring this change 2) cp $HOME/.dtprofile $HOME/.dtprofile.orig 3) Edit $HOME/.dtprofile and add the following variable: SESSIONTYPE=xdmMode If you enter a user name longer than 19 characters on the CDE Desktop login screen, only the first 16 characters will be displayed on the next screen on which the password is entered. But, the entire name entered will be used during the login authentication process. To indicate that a user name has been truncated on the password screen, the truncated user name will be displayed with "..." at the end. During startup, the Login Manager checks the Xservers file (either in /usr/dt/config or /etc/dt/config) to determine how to start the Xserver on the local display. By default, the Xservers file is configured so that Login Manager will attempt to start the Xserver on a local display and to display a login screen on the local display. If your system has no graphics adapter and the DT_NO_DISPLAY_CHECK environment variable is not set, Login Manager will ignore the default local line from the Xservers file and will not attempt to start an Xserver on the local display. If, for any reason, you do not want Login Manager to make this check and ignore the line from the Xservers file if your system has no graphics adapter, you will need to set the DT_NO_DISPLAY_CHECK environment variable before starting login manager. This variable can be set in the /etc/environment file. Using Loadable Authentication Modules with Login Manager ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you are using Loadable Authentication Modules, you must stop and restart Login Manager (dtlogin) when you have modified /usr/lib/security/methods.cfg or the load module program referenced in this file. If dtlogin is not stopped and restarted, login may fail or it may not use the authentication method specified in /usr/lib/security/methods.cfg. To stop and restart dtlogin, 1. Have all users exit from the CDE desktop. 2. Perform the following steps as root. It is recommended that these steps be performed when logged in at the console. 3. As root, kill the CDE and X processes: /usr/dt/bin/dtconfig -kill 4. If needed, log back in as root. 5. Determine if there are any remaining dtlogin processes: ps -ef |grep dtlogin 6. If a dtlogin process remains, then manually kill it: kill -9 7. Remove any currently unused modules in kernel and library memory: slibclean 8. Restart the CDE login manager and return to the login screen: sh /etc/rc.dt ; exit dtdbcache files ~~~~~~~~~~~~~~~ When desktop is started in the default manner via dtlogin, dtdbcache files needed by the desktop are created during the session startup process. These files are then automatically removed by both the Xstartup and Xreset configuration scripts. If desktop is not started in the default manner via dtlogin and if the Xstartup and Xreset configuration scripts are not executed, then you must manually remove the dtdbcache files after you exit desktop. These files are located in /var/dt/tmp and are created for each display. If these files are not manually removed, another user from the same display may not be able to login. Session Manager ~~~~~~~~~~~~~~~ If your .dtprofile sources a non-existent file or contains some other syntax error, then you will be unable to login. After login is attempted, you will be returned to the login screen and an error will be logged in $HOME/.dt/startlog. The following is an example of the information that would be logged to $HOME/.dt/startlog if a sourced file could not be found: --- sourcing /home/user/.dtprofile... /usr/dt/bin/Xsession[389]: /bad_file: not found If you have enabled Session Manager to source your .profile and your .profile sources a non-existent file, then you will be unable to login. After login is attempted, you will be returned to the login screen and an error will be logged in $HOME/.dt/startlog. The following is an example of the information that would be logged to $HOME/.dt/startlog: --- execing /usr/dt/bin/dtsession using /home/user/.profile... /usr/bin/ksh: /bad_file: not found With other errors in your .profile, you may still be allowed to login. But, errors will be logged to your $HOME/.dt/startlog. After modifying your .profile, you should check your $HOME/.dt/startlog after logging into the desktop to determine if any errors were detected. During the start of your desktop session, dtappgather is run to gather application files for presentation by the Application Manager. As part of this process, dtappgather attempts to create a directory in /var/dt/appconfig/appmanager. The name of the directory will be the value of the DTUSERSESSION environment variable. If dtappgather is unable to create this directory during the session startup, a MakeDirectory error will be logged to $HOME/.dt/startlog. The default setting for DTUSERSESSION is a concatenation of your user name and display name. For example, if you are logged into the desktop as user test1 on display 0 of host machine2, the DTUSERSESSION environment variable would default to: test1-machine2-0 Because the length of a file or directory name is limited by the system to 255, dtappgather will be unable to create the directory if the value of the environment variable DTUSERSESSION is longer than 255. This could occur if you are using a long user name or display name. If the default setting for the DTUSERSESSION is too long and you wish to use Application Manager, you can set DTUSERSESSION in your $HOME/.dtprofile. For example, to indicate that dtappgather would gather your application files in directory /var/dt/appconfig/appmanager/test1_appfiles, add the following to your .dtprofile: export DTUSERSESSION=test1_appfiles This value must not be used by another user on the same system. This value will not used until the next time you login to the desktop. ToolTalk ~~~~~~~~ The ToolTalk messaging transport mechanism is based on RPC. If the system is misconfigured as to where it cannot communicate on the network or in "loopback", then the desktop login process will fail. To correct a possibly misconfigured system, then try: 1) "smitty tcpip" (Follow the directions in the menu driven screen). 2) If you are running a "nameserver" check that the file "/etc/resolv.conf" exists and that you can contact the nameserver host described in the file (ping ). If you can't contact the nameserver host, then check with your network administrator to resolve this problem. Additionally, you might want to check if you have read access to this file. If you do not, then this problem needs to be corrected so that you will be able to successfully login in to your session. 3) check "/etc/hosts" If you are not running a nameserver, the file /etc/resolv.conf will not exist. However, you must make sure that your workstation tcpip address is listed in /etc/hosts. Otherwise, you will not be able to login in. rpc.ttdbserver ~~~~~~~~~~~~~~~ In order to prevent a user from overwriting a system file, the ToolTalk database server daemon, rpc.ttdbserver, will not allow the use of a transaction log file that is a symbolic link. If a user attempts a database operation that writes entries to a transaction log file and the log file is a symbolic link, the operation will fail, the symbolic link will be removed and an error message will be displayed on standard error for rpc.ttdbserver. The transaction log file is named log_file and is placed in the database directory. In order to debug applications that use ToolTalk databases, /usr/dt/bin/rpc.ttdbserver can be started with the "-S" option. When started from a command line with this option, error messages will be displayed on the console on which rpc.ttdbserver was started. These error messages can also be redirected to a file. /usr/dt/bin/rpc.ttdbserver can only be executed by a user with root authority. File Manager (dtfile) ~~~~~~~~~~~~~~~~~~~~~ On a multi-screen display, the Trash view will display on the default screen, regardless of any specified screen. Any file manager view activated through an action on a directory which is actually a link will use the fully resolved directory. For example, /u is a symbolic link to /home; a file manager view activated through an action on /u/guest will actually show /home/guest. If you are using the Permissions dialog of the File Manager and the owner and/or group name of the file is longer than 19 characters, the file type icon will not be displayed. This icon would normally indicate the type (e.g. DATA file or FOLDER) of the file or folder for which the permissions are being changed. Drag and drop on multi-screen display ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you are using a multi-screen display, it may not be possible to drag an object from a client (e.g. Mailer) running on one screen and drop that object on a client (e.g. File Manager) running on another screen. If you need to drag and drop objects, you may need to have both clients running on the same screen. Front Panel ~~~~~~~~~~~ If you are running on a system with two graphics adapters and the first (primary) adapter is a 24-bit adapter, icons will not appear on the Front Panel. Icon Editor ~~~~~~~~~~~ The Icon Editor will not run on Skymono graphics adapters (4-bit color) when the desktop is set to use the default color mode. To change the color mode to black and white do the following: 1) Start the Style Manager 2) Click on the "Color" icon 3) Click on the "Color Use..." button 4) Change the option from "Default" to "Black and White" 5) Exit the session and start it up again. Dticon should work now. Content-based Object Typing ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Some of the data type definitions that are loaded when you start your desktop session may define content-based object typing. With content-based object typing, desktop will need to open a file and search for the existence of a particular string or number in order to determine the type of the file (when the file type can not be determined from the name or location of the file). If a desktop application (for example, File Manager) is required to perform content-based object typing on a large number of files, the performance of the application can be affected. If you are using another tool (e.g. Tivoli Storage Manager) other than the AIX Operating System to manage your files, the performance will be even slower if the files that need to be opened have to first be recalled from another media (e.g. tape) to disk. To improve performance, you can set the environment variable DT_SKIP_CONTENT_TYPING. When this environment variable is set, desktop will not open files to determine their types. This setting can be made for a single user (e.g. in the user's $HOME/.dtprofile file), for all users (e.g. in the /etc/environment file) or for a particular application when starting from the command line (e.g. DT_SKIP_CONTENT_TYPING=1 /usr/dt/bin/dtfile). Screen Savers in Style Manager ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The CDE Style Manager allows the capability to select multiple screen savers and to specify the time that each screen saver should run before switching to the next saver. When the system switches from one screen saver to the next, the previous screen saver process should die. On some display configurations, there is an intermittent problem which prevents the previous screen saver process from terminating when starting the next screen saver. A symptom of this problem will be that multiple dtscreen processes are running for a single user login into the desktop. Over time, these processes may build up to the point that a new process can not be started. This problem can occur even if only one screen saver is selected but the "Time Per Saver" is not 0. If you encounter this problem on your configuration, you can disable switching screen savers for an individual user using the following steps: 1. Start CDE Style Manager. 2. Choose the "Screen" option. 3. Select more than one screen saver from the list. "Time Per Saver" will not be active unless more than one screen saver is selected. 4. Change "Time Per Saver" to 0. 5. Select one and only one screen saver from the list. 6. Press "OK" to save these changes. If you are using a Home Session, you will need to set a new Home Session from the "Startup" option in the Style Manager. To ensure that you are using the new screen saver selections, you should logout and log back into the desktop. After logging back into the desktop, restart Style Manager, select "Screen" and check that "Time Per Saver" is 0 and that one and only one screen saver is selected. A system administrator can also disable the switching between one screen saver and another for all users on a system by setting the DISABLE_SCREEN_SAVER_SWITCH environment variable using the following technique: 1. Create a new script file in /etc/dt/config/Xsession.d containing the following: #!/bin/ksh export DISABLE_SCREEN_SAVER_SWITCH=True 2. The permissions of this file should allow it to be read and executed by all users on the system. After this script is created, the next time a user logins into the CDE desktop, regardless of the Screen settings in Style Manager, the system will not switch from one screen saver to another unless that user has overridden the setting of DISABLE_SCREEN_SAVER_SWITCH. If the Screen settings in Style Manager specify that screen saver switching should occur but was disabled via the DISABLE_SCREEN_SAVER_SWITCH environment variable, an informational message will be logged to $HOME/.dt/errorlog the first time the screen saver is activated for this session. If a user wishes to override the system setting of DISABLE_SCREEN_SAVER_SWITCH, DISABLE_SCREEN_SAVER_SWITCH can be set to False in the profile for their shell. Session Manager ~~~~~~~~~~~~~~~ The -norestore option of the dtsession command is not supported. Color Server ~~~~~~~~~~~~ Some applications which have their own colormaps and which also use desktop component (including Motif widgets) will not have default colors calculated correctly for those components. This problem can be circumvented by turning off the "useColorObj" resource for the application. You will need to know the class name of your application before you begin. This can usually be found in the application's documention. For an application with the classname "MyAppClass", to turn off the "useColorObj" resource for your session only, add the line: *MyAppClass*useColorObj: False to $HOME/.Xdefaults. The next time you log in, and start the application, the problem will be corrected. To correct the problem for your running session, type: dtaction ReloadResources from the command line and re-start the application. For an application with the classname "MyAppClass", to turn off the "useColorObj" resource for all users on the system, add the line *MyAppClass*useColorObj: False to /etc/dt/config/$LANG/sys.resources. The next time any user logs in, and starts the application, the problem will be corrected. To correct the problem for a user's current session, have the user type: dtaction ReloadResources from the command line and re-start the application. Dtterm ~~~~~~ If you use the desktop terminal emulator (dtterm) to access a remote system which is not running the desktop you will need to install the terminfo description for dtterm on that system. You can use the following steps to accomplish this for an AIX system. 1. Log into the remote system as the root user. 2. Copy /usr/lib/terminfo/dtterm.ti from the desktop system to /usr/lib/terminfo/dtterm.ti on the remote system. 3. Compile the terminfo file: 'tic /usr/lib/terminfo/dtterm.ti'. Calendar Manager APIs ~~~~~~~~~~~~~~~~~~~~~ The csa_restore() and csa_save() APIs for the calendar manager are not supported at this time. There are empty stubs in the library for compatibility purpose, but they do nothing but return to the caller. Application Manager Actions ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The package X11.samples.apps.clients is needed for the following actions: Action: binary needed: Edit Bitmap /usr/lpp/X11/Xamples/bin/bitmap Clipboard Contents /usr/lpp/X11/Xamples/bin/xclipboard System Load /usr/lpp/X11/Xamples/bin/xload Font Preview /usr/lpp/X11/Xamples/bin/xfd Window Information /usr/lpp/X11/Xamples/bin/xwininfo X Server Information /usr/lpp/X11/Xamples/bin/xdpyinfo To make these actions fully functional, install the X11.samples.apps.clients fileset. Dtmail ~~~~~~ The AIX version of Dtmail uses the /tmp file system to store temporary files during normal processing. System adminstrators will want to ensure that there is sufficient free space in the /tmp file system. Space requirements will vary depeding on the number of users and the size of the mailboxes opened. Dtmail will post an error dialog if any needed filesystem has insufficient space. Migration Tool ~~~~~~~~~~~~~~ When using the "Find objects below" widget on the "Find Objects" dialog manually, to type in your path, remember to leave a "/." at the end of your path. Failure to do so will result in turning off the "Start search" button, which will render it unusable. When migrating xdt objects that include iconmenu.objscr files in the object directory, xdt2cde will complain about these files and eventually result in unsuccessful migration. Since these files are not supported directly, they need not be present for a successful migration and should be removed from the object directory prior to the migration of that object. Dtsearchpath ~~~~~~~~~~~~ The MANPATH variable can be set in the /etc/environment file the following way MANPATH=$MANPATH:NEW PATH dtsearchpath substitutes the value of MANPATH in the above expression. For more details on how dtsearchpath evaluates MANPATH, see dtsearchpath(1). If however, the statement in the /etc/environment file reads like MANPATH=$MANPATH:NEW PATH:$MANPATH etc., i.e., multiple $MANPATH appear in the statement, dtsearchpath will evaluate only one of them. Subsequent instances will not be evaluated. In such a case, a user will not be able to login using cde, as libDtSvc will hang. Motif User Interface Language Compiler ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In AIX 5.0.0 and above the User Interface Language compiler /usr/dt/bin/uil refers to the X11R6 Motif2.1 version of the uil. X11R5 Motif1.2 version of the uil is available at /ust/dt/bin/uil.12. Miscellaneous ~~~~~~~~~~~~~ Setting the hostname on the desktop normally occurs as part of system configuration immediately after installing AIX. If the hostname is subsequently changed, the desktop must be restarted. Using Uncompress in the UnixUtilities Toolbox requires a file name with a suffix of ".Z". If very large fonts are selected for the desktop, some dialogs may contain information that is not viewable. To view this information, resize the window or change the font to a smaller size. In AIX 4.1.3 and beyond, the sh command is now equivalent to ksh, whereas in AIX 4.1.1 and AIX 4.1.2, it was equivalent to bsh. This change was made to conform to standards. This change may result in some peculiar desktop behavior, depending on how you've set up your environment. ksh sources .kshrc. If you get unexpected errors or warnings, check to make sure the .kshrc file does not set the PATH environment variable. With the enhanced security features that were added to AIX 4.1.5 and beyond, users can no longer share home directories. These changes were in apar IY03847 for aix 4.1, apar IY03848 for aix 4.2, and apar IY03849 for aix 4.3 . ttsession and security problems ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From 4.3, CDE (and tooltalk) has been changed to incorporate some changes to fix the security problems. The changes are made such that a user on a current system requesting to use any of desktop clients on a remote system will have to be authenticated by the remote system. The way to do is, for example: A user 'test' on host 'A' is requesting 'tooltalk' services on 'B', then the user running 'ttsession' on 'B' (currently logged in user) will run a command /usr/dt/bin/ttauth and add host 'A'. The use of 'ttauth' is available in the man page for 'ttauth'. This situation might also arise, when user 'test' on 'A' telnets to 'B' and exports the DISPLAY back to 'A:0.0' and runs a 'dtpad' or dtmail or some other CDE client. The same above fix will take care of this problem. There is another way to do is by disabling authentication,i.e., edit the 'XSession' file in /usr/dt/bin/ and change 'ttsession -s' to 'ttsession -s -a none' on both the systems that are in the picture. Calendar Manager (dtcm and rpc.cmsd) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Users with a name longer than 248 characters will not be able to start Calendar Manager because the name for the calendar file would exceed the maximum length allowed by the system. After booting the system, if the first user to attempt to start the Calendar Manager (dtcm) has a user name longer than 248 characters, subsequent users may encounter problems starting Calendar Manager. If subsequent users who do not already have a calendar file attempt to start Calendar Manager, they may receive an error message indicating that the calendar manager server daemon (rpc.cmsd) is not responding for that user name. A workaround for this problem is for the user to logout of the CDE desktop and for a root user to manually kill the running rpc.cmsd process. Then, users with names of 248 characters or shorter can login into the CDE desktop and successfully start Calendar Manager. As stated above, users with a name longer than 248 characters will still not be able to start Calendar Manager. Desktop Script (dtscript) ~~~~~~~~~~~~~~~~~~~~~~~~~ You will be unable to run Desktop Script (dtscript), if you are logged with a long user name (greater than approximately 80 characters). Desktop KornShell (dtksh) ~~~~~~~~~~~~~~~~~~~~~~~~~ Because Desktop KornShell (dtksh) is based on ksh-93, you may encounter some problems when running dtksh scripts when logged in with a user name longer than 8 characters. Help Viewer ~~~~~~~~~~~ When viewing a help topic, ascii text file or man page using the CDE Desktop Help Viewer (dthelpview), a problem viewing the entire page may occur when the help viewer window is resized. If the help viewer window is made narrow enough that horizontal scroll bars are required and you then scroll to the right so that the text on the left is no longer displayed in the window, the left portion of the text will not be displayed if you then maximize the window or resize it so that scroll bars are no longer required. In order to avoid this problem, you will need to scroll all the way to the left before maximizing or resizing the window. ============================================================================== For More Information ============================================================================== For more information about the CDE desktop refer to the IBM CDE home page at "http://www.ibm.com/servers/aix/cde/". Additionally, for help with basic desktop customization, such as how to start an aixterm how to setup a mailer signature file, how to source your profile, and so on, see the "Basic Desktop Customization" help volume located in the "Help" subpanel.