Why do I get xset error messages when I try to start the Mathematica front end?

The most common cause of this problem is an outdated maximum font list setting in one of the Mathematica resource files. Originally this maximum was set to 2000. However, there are over 5000 fonts installed on a typical HP-UX system, so resetting this maximum to a safer value of 6000 is strongly recommended. Here are steps that show you how you can update this setting.

Another possiblility is Type1 font support on your X server. The mathematica script calls the xset command twice to add two font directories to your X font search path. The first call is to add *.bdf fonts, which are bitmap fonts. The second call is to add Type1 fonts, which are PostScript fonts.

On some systems, executing the mathematica script generates a font xset error. This can happen if your default X server does not support Type1 fonts. If the front end still starts up and appears to work normally, then the message was probably just a warning.

You can edit your mathematica script and comment out the lines that check and add Type1 fonts to your font path. Find the lines that start with the following.

font=$topdir/SystemFiles/Fonts/Type1 [ $havefonts -lt 2 ] && xset fp+ $font

Insert the pound symbol (#) to comment them out.

# font=$topdir/SystemFiles/Fonts/Type1 # [ $havefonts -lt 2 ] && xset fp+ $font

If you continue to experience font problems, see the following URL.

http://support.wolfram.com/mathematica/systems/unix/interface/unixxserver.html

Download this FAQ as a Mathematica 5.2 Notebook

Questions or comments? Send email to support@wolfram.com.