Your system's imake configuration is not set up to properly support Motif. To work around this problem, see the INSTALL file and read the comments in the xmcd_d/Imakefile.

Warning: locale not supported by C library, locale unchanged

This message is displayed when you do not have a properly defined LANG environment variable. If you are not using an international character set then you can usually ignore this message.

Error: attempt to add non-widget child "dsm" to parent "xmcd" which supports only widgets

On certain platforms, there appears to be a problem with the vendor shell widget class in the shared Motif library. Rearranging the order of the Motif and X libraries linked may alleviate this problem, and re-linking with the static Motif library instead of the shared version usually solves this problem.

Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing 'osfActivate: BulletinBoardReturn()'
Warning: translation table syntax error: Unknown keysym name: osfCancel
Warning: ... found while parsing 'osfCancel: BulletinBoardCancel()'
etc...

The LIBDIR/XKeysymDB file is not installed on your system (where LIBDIR is typically /usr/lib/X11). A XKeysymDB file is supplied with the xmcd release. When the XKeysymDB is installed in the proper location this problem should go away.

The LIBDIR/app-defaults/XMcd file cannot be located, or is the wrong version. A correct version of this file must be present in the appropriate directory in order for xmcd to run. Please check your xmcd installation.

Neither the XMcd.libdir resource nor the XMCD_LIBDIR environment is defined!

Your xmcd software may be improperly installed. If you compiled xmcd from the source code, be sure to use "make install" to install the software. Also, make sure that the xmcd_d/XMcd.ad file is installed as LIBDIR/app-defaults/XMcd (where LIBDIR is typically /usr/lib/X11). Check the contents of this file to make sure the XMcd.version parameter exists and matches the version of xmcd you're running. If the XMcd.version field is missing or wrong, do not edit the file to correct it. Install a correct version of the file instead.

If the above doesn't resolve the problem, check to make sure you don't have an old or incorrect version of the XMcd file installed in your home directory, or in any of the directories specified by your XAPPLRESDIR or XFILESEARCHPATH environment variables. Also, check your $HOME/.Xdefaults file.

ld.so.1: xmcd: fatal: libXm.so.2: can't open file: errno=2
Killed

dynamic linker : xmcd : error opening libXm.so.2
Killed

Your xmcd binary was compiled to link with dynamic libraries. On SVR4 and certain other systems, a setuid program such as xmcd will search only the /usr/lib and /usr/ccs/lib for dynamic libraries (for security concerns). However, some of the dynamic libraries that xmcd needs are not in these standard locations. This is notably true for the Motif (libXm), Xt Intrinsics (libXt) and X11 (libX11) libraries.

In the example messages above, libXm.so.2 is not found. You may also run into the same problem with other libraries.

A solution is to create symbolic links such that these needed dynamic libraries are linked to /usr/lib, and thus can be found by xmcd. The xmcd install procedure ("make install" or "install.sh") has built-in support to search for the needed dynamic libraries and to create the links for you.

The install.sh script will only search the following directories for dynamic libraries:

/usr/X/lib
/usr/X11/lib
/usr/X386/lib
/usr/X11R5/lib
/usr/X11R6/lib
/usr/openwin/lib
/usr/X/desktop
/usr/Motif/lib
/usr/Motif1.1/lib
/usr/Motif1.2/lib
/usr/Motif2.0/lib
/usr/dt/lib
/usr/lib/X11

If your xmcd binary needs a shared library that's not in these locations, you must create the symbolic link by hand with the ln(1) -s command.

If you don't like the symbolic link approach, an alternate solution is to recompile xmcd such that the dynamic library locations are specified with the -R option to the ld(1) command. To do this, you must be adept at editing the xmcd_d/Makefile and making the appropriate changes, compile the xmcd sources, and re-installing the binary.

XMCD_LIBDIR environment not defined.

You must set the XMCD_LIBDIR environment variable to run cda. Typically this is set to "/usr/lib/X11/xmcd" (your local set-up may vary). You set the environment variable as follows:

• Bourne Shell, Korn Shell or bash:
  XMCD_LIBDIR=/usr/lib/X11/xmcd; export XMCD_LIBDIR
• C Shell or tcsh:
  setenv XMCD_LIBDIR /usr/lib/X11/xmcd

Warning: Cannot allocate colormap entry for "Grey75"
Warning: Cannot allocate colormap entry for "CadetBlue4"
...

Your X display has run out of colormap entries. Colormap entries are a limited resource, and there are other color-intensive applications running on your X display that has consumed all of of them. This is especially prevalent on X displays that has 8 bit-planes or less (supporting 256 colors or less).

The solution is to start xmcd before running other color-intensive applications, such as web browsers or graphics programs.

If you are using xmcd with the LessTif library (A free Motif clone), this may be the cause of the problems. Earlier versions of LessTif have been known to cause these problems. I suggest using the pre- compiled xmcd binaries that are distributed via the xmcd web site, as these are linked with the real Motif library. Alternatively, you can try a newer version of LessTif.

Check the system for another xmcd or cda process running on the same CD-ROM device. If there are no other xmcd/cda process, then look for a file /tmp/.cdaudio/lock.XXXX where XXXX is the hexadecimal string of the device number. Remove this file and the problem should go away. Normally a new xmcd/cda process will inherit the lock from a previously exited xmcd/cda process, but if the original process ID is now re-used by another process this will not work.

Ensure that the CD-ROM drive is connected and functioning, and that xmcd/cda is properly configured.

If you have one of those unusual OEM SCSI CD-ROM drives that identify themselves as a hard disk (such as the Toshiba CD-ROM XM revision 1971 units OEM'ed by SGI), you will need to add -DOEM_CDROM to the libdi_d/Makefile and recompile.

This tends to occur with some non-SCSI CD-ROM drives. If you have xmcd's closeOnEject parameter set to True, that could be the cause. Try setting it to False. If this still doesn't fix the problem, or cause other problems, send a bug report to the CD-ROM driver's author.

Meanwhile, you can increase the insertPollInterval parameter in xmcd/cda to make this "auto-load" behavior happen later.

This is a "feature". Xmcd and cda cannot issue a "load" command to the drive without having the device open. On many UNIX systems, the CD device cannot be opened until a disc is inserted. Thus, the CD must be loaded manually at the drive the first time around. Subsequently, the Load/Eject control on xmcd/cda should work normally.

This is a problem with some versions of the sbpcd driver on Linux. The sbpcd driver caches the CD's TOC (table of contents) in the driver, but neglects to invalidate this cache when the CD is ejected. There is a workaround: Set the closeOnEject parameter to True in your XMCDLIB/config/DEVICE file and it should work. XMCDLIB is the directory where the xmcd/cda support files are installed.

data write failed: Read only file system

You need to apply a patch to your disk driver. See the README file for details.

Make sure your system has enough memory. X11 programs, especially Motif applications, consume a lot of memory. Xmcd is no exception. Your system may be swapping and paging heavily, causing the performance degradation. Try closing some unneeded windows. Also, the X server may have a memory leak which causes it to grow over time. Try stopping the entire X session and starting a new one.

Run some system performance analysis tools (sar, u386mon, vmstat, crash, etc.) to see if there is a system tuning issue.

Also, setting the xmcd X resource XMcd*mainShowFocus to False may improve performance somewhat.

Click on the label area instead of the thumb. This is a limitation of the Motif scale widget.

The problem occurs when the current keyboard input focus is on the volume control slider. This is a limitation of the Motif scale widget. The work-around is to click another button first to change the keyboard focus to another button, then click the #3 button on the volume control numeric label to bring up the help window.

Make sure you are not running a "demo" version of xmcd. If you see this message when you start xmcd or cda, then you are running the demo version that does not actually work with a real CD-ROM drive:

CD-ROM simulator version x.xx (pid=xxxxx) starting...

You will get the demo mode if you compile and run xmcd/cda on an unsupported OS platform.

Also, make sure your CD-ROM drive audio output is connected to something. You may either connect headphones or amplified speakers to the front jack, or connect the rear audio output to an external amplifier.

Recent Toshiba SCSI CD-ROM drives support two means of software- controlled volume settings. One of these is the SCSI-2 method, using the "mode select" command. The other is via a SCSI-1 Toshiba vendor-unique command, and only gives mute/un-mute functions. Xmcd/cda will use the appropriate method, depending on whether you configured it to operate the drive as a Toshiba SCSI-2 or SCSI-1 unit.

Even though you are using xmcd configured to SCSI-2 mode, the SCSI-1 mode muting may have somehow been activated, thus silencing the audio. To determine if this is the cause, do the following:

1. Run the XMCDLIB/config/config.sh script, and re-configure xmcd/cda to operate the drive as a SCSI-1 Toshiba unit (such as the XM-3201). XMCDLIB is the directory where the xmcd/cda support files are installed.
2. Restart xmcd, play an audio CD, and move the volume control slider around. Note that it will only go to the 0 or 100 settings in this mode. Leave it in the 100 position, then quit xmcd.
3. Configure xmcd/cda back to run as the appropriate SCSI-2 unit.
4. Play a CD. Is there sound? Does the volume control slider work?

A possible cause of this phenomenon, is that some other application that accesses the CD-ROM drive was using the Toshiba SCSI-1 vendor unique command set to control the drive, and left the drive in the muted state when it exited. Xmcd, when configured to run the drive as a SCSI-2 unit, does not issue SCSI-1 vendor-unique commands to re-enable the sound.

To remedy this, you may choose to operate xmcd/cda only in the SCSI-1 mode (as an XM-3201), but you lose some of the features in xmcd/cda. The other option is to avoid using the other application that caused this in the first place. Or, send a complaint to the vendor/author of that application.

Your system must be set up properly to use a CD-ROM drive. A good test is to see if you can mount ISO9660/High Sierra CD-ROM file-systems. If your system does not support ISO9660 but otherwise supports a raw CD-ROM device, you can try typing this command while logged in as the super-user (with a DATA CD loaded in the CD-ROM drive):

dd if=DEVICE of=/dev/null bs=2k count=10

where DEVICE is the CD-ROM device node, such as /dev/rcd0 (SCO ODT), /dev/rcdrom/cdrom1 (SVR4.2/x86) or /dev/rsr0 (SunOS 4.1.x).

If the dd command fails, then either your hardware is not set up properly, or your OS is not configured to support the CD-ROM device. You should fix the problem first before attempting to run xmcd/cda.

Once you have validated basic functionality with data CDs, then make sure xmcd/cda is properly configured. Run the XMCDLIB/config/config.sh script (where XMCDLIB is the directory where the xmcd/cda support files are installed).

Also, be sure that you are running on a supported operating system and hardware platform, and that the minimum OS version requirement is met. Some platforms require special kernel or driver configuration to run xmcd/cda. See the README and INSTALL files for details.

Your CD-ROM drive may not support some of these features. Another possibility is that the software is improperly configured. Run the XMCDLIB/config/config.sh script to re-configure xmcd/cda (where XMCDLIB is the directory where the xmcd/cda support files are installed).

Shuffle mode can only be enabled when the CD is stopped. If your CD is playing, stop the playback and the shuffle button should work. This is a safeguard feature to prevent unintentionally interrupting the playback.

This is the characteristic of the particular CD-ROM device driver and can be considered "normal" (or send bug report to the driver author).

This can be addressed with a wrapper script around the xmcd and cda binaries and adding a symbolic link to the device node.

1. Install xmcd and cda normally, except specify an NFS-mounted location for its BINDIR and XMCDLIB. Since root privilege is not applicable across an NFS-mounted directory, you need to run the installation as a non-root user. Care should be taken to ensure that these directories are writable to you. Also, be sure to fix the permissions of the xmcd and cda binaries to make them setuid root.
2. Rename your xmcd binary as xmcdprog and cda binary as cdaprog (substitute BINDIR with the appropriate path):

   cd BINDIR
   mv xmcd xmcdprog
   mv cda cdaprog

3. Create an xmcd wrapper shell script with the following contents and install with 755 execute permissions in BINDIR:

   #!/bin/sh
   exec xmcdprog -dev /dev/rcdrom.`uname -n` $*

   Similarly, create a cda wrapper as above, but substitute "xmcdprog" with "cdaprog".

4. Create a symbolic link in /dev to link to the appropriate CD-ROM device (substitute DEVICE with the correct device on your system. e.g., /dev/rsr0 on SunOS 4.1.x, and HOSTNAME should be the workstation's host name):

   cd /dev
   ln -s DEVICE rcdrom.HOSTNAME

5. Run the XMCDLIB/config/config.sh script for each workstation (where XMCDLIB is the directory where the xmcd/cda support files are installed). When prompted for the device name, enter "/dev/rcdrom.HOSTNAME" to configure the drive on that workstation host.

I will not give specific brand and model recommendations, but I will recommend a SCSI-2 drive over a non-SCSI one. More features are supported by xmcd on SCSI drives than on non-SCSI units.

Furthermore, SCSI CD-ROM drives are universally supported on the various OS and hardware platforms (whereas non-SCSI units only work on some platforms). This makes a SCSI drive more portable between different systems, and there is less worry about getting obscure device drivers to work.

Note that not all SCSI-2 drives are created equal, some of them implement more of the audio-related commands than others. If you do a careful study of xmcd's libdi_d/cfgtbl/* files, you'll get a good glimpse at the CD-ROM drives' capabilities. Some of xmcd's features will not work unless these commands are fully implemented on the drive. Also, see the README file for specific drive-related notes.

Note that some workstations require special OEM versions of the CD-ROM drives (such as Sun, which requires support of 512-byte block sizes rather than the standard 2048).

This is a common question for users of the FreeBSD, NetBSD, Linux and other platforms that do not come with Motif development and/or run-time environments. No problem, there are answers!

Pre-compiled xmcd binaries with statically-linked Motif library is distributed via this site for most of these platforms. You can just download it, install and run.