HP Neoware c50 TeemTalk® 5.0 for Unix User's Guide - Page 29
Testing The Installation
View all HP Neoware c50 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 29 highlights
Installing TeemTalk On UNIX Based Products Testing The Installation TeemTalk should now be run up and work perfectly - if however you get the error message, Cannot Load Font..., then the font installation has failed. The following tips may be useful: - The installation is designed to load the fonts in the format required by the workstation that TeemTalk is being loaded onto. If TeemTalk is to be run from another display (workstation or X terminal), then a different version of bdftosnf (supplied with the other display) or the standard bdftosnf but with different parameters may need to be used. Most X terminals usually look in different directories for the fonts so the installation script will need modifying to reflect this. - Some workstations/X terminals require the fonts to have both read and surprisingly write permission for them to able to be loaded by the server. - Try restarting the X server. If xset fp rehash failed then this is a sure way to make sure the server is aware of additions to the fonts. - Check that the correct version of bdftosnf is being used. It is possible that someone has loaded a version with different defaults (for another workstation). It is unlikely that the original will have been overwritten but it is possible that the wrong version is being picked up by the OS first. - xlsfonts is a useful way of listing fonts known to the server. Check that the TeemTalk fonts are listed (e.g. xlsfonts | grep tis). If they are listed but TeemTalk cannot load them then check the protections as described above. - Check that the directory in which the fonts have been installed is part of the server font path. The font path that the server is using is easily found by looking at the font path reported by xset q. Make sure when running xset that it is done from the display where TeemTalk is going to be run. - If all the above fail, re-run the installation paying careful attention to any error messages which may have been missed first time around. 2-11