Here are two notes about resource files: 1) If your RCS account is set up to use the RPI ACM login.profile, your X programs can't see your resource files. This is because their setup creates a variable named XUSERFILESEARCHPATH to point to some ACM directories, and it prevents X from checking your home directory for resource files. To fix it and keep the ACM stuff available, I placed this line in my .bashrc file: export XUSERFILESEARCHPATH=$XUSERFILESEARCHPATH:$HOME/%N It could be further augmented like this: export XUSERFILESEARCHPATH=$XUSERFILESEARCHPATH:$HOME/%N:%N This will make X look in the current directory after checking the user's home directory. This eliminates the need to keep resource files (or copies or symbolic links of them) in the home directory. 2) Someone reported on the newsgroup that a resource file should have an ".ad" extension after the name given in XtVaAppInitialize(). This is apparently a convention adopted by Dr. Franklin in his Computer Graphics class. In his lecture notes he tells students to add this line to their .bashrc file: export XUSERFILESEARCHPATH=%N.ad That makes X look for the application name, with the ".ad" extension tacked on, only in the CURRENT directory (presumably, the one where the program is being run). Since my only X experience is here at RPI, I can't comment on whether or not Franklin's naming convention is a good one or one that is used commonly. I'm going to ask him why he does this; if anyone here knows, please post the reason. For the moment, I can't recommend setting things up to require the ".ad" extension on resource filenames. Rick