Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ames!dftsrv!jagubox.gsfc.nasa.gov!jim From: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) Newsgroups: comp.unix.aux Subject: Re: Font for CommandShell Message-ID: <3796@dftsrv.gsfc.nasa.gov> Date: 2 Nov 90 16:37:36 GMT References: <3784@dftsrv.gsfc.nasa.gov> Sender: news@dftsrv.gsfc.nasa.gov Reply-To: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) Organization: NASA/Goddard Space Flight Center Lines: 28 In article <3784@dftsrv.gsfc.nasa.gov> jim@jagubox.gsfc.nasa.gov (Jim Jagielski) writes: > > stuff about adding a "hacked" version of Courier for CommandShell > deleted > Well, never mind about this... for some reason CommandShell (but not CommandShell24) doesn't like this. It works fine, until you try to select Page Setup under FILE... then it bombs with a System Error of 33... Actually, the "new font" was the 4th font to show up under FONT, the first two are Monaco and Courier and the 3rd is Belmont, which is used for MathType. When these 3 are available, all is okay. When a 4th is added, then stuff starts happening. By the way, my root account had Courier, Monaco and CSfont available (NO Belmont) and it worked fine... so if the total number of fonts available under FONT is 3, then you may be okay. If Apple, or anyone else, has any other ideas or suggestions, please let me know. -- ======================================================================= #include =:^) Jim Jagielski NASA/GSFC, Code 711.1 jim@jagubox.gsfc.nasa.gov Greenbelt, MD 20771 "Kilimanjaro is a pretty tricky climb. Most of it's up, until you reach the very, very top, and then it tends to slope away rather sharply."