>>> I don't think you have corrupted fonts. I thing the program is getting >>> bogged down. Try allocating more memory >> I have 768MB of RAM, and OSX gives each application all the memory it wants, >> on the fly, depending on whether the application is resting or working. So I >> doubt that I have a memory problem. > You may be right, but I'm not familiar with native OS X software. ... > Another thing you can look at is, compare the number of fonts to the > number of lines in the Font menu. Maybe that will give you a clue to > what's going on.
Memory There is no way to allocate memory in OSX unless you can work "under the hood". Pogue's manual says the memory is allocated dynamically, and in the past year I have not heard of or found a way to allocate memory myself. I have a little program called Gmem that shows how much memory OSX is giving to the open programs. It is interested to see that a program that is open but doing nothing is given almost no memory. Then when you open a lot of documents, pictures, windows, etc., the program is given a lot more memory. It is really nice not to have to worry about memory, and you can run a lot more programs with a lot less memory, because each program does not lock up a fixed allocation. They just wait there, using just a little memory until you call on them to do some work. Then they get only what they need for the task, moment by moment. Fonts My problems with Word were almost certainly due to fonts, but I don't know if it was because certain fonts were corrupted or just unsupported. I could see the bad fonts in Word's WSYWIG pull down menu, because their names were distorted and illegible. Since Word X was unable to display the fonts legibly, I guess that means they were unsupported. I was able to compare the pull down menu to the contents of my four font folders (one in the OS9 System Folder and three in OSX's various Library Folders). Then by using alphabetic order, I figured out the bad fonts in the folders and trashed them. The bad fonts were all odd-balls that nobody would ever use. That cleaned up the pull down menu, and now the font that I select is the font that I get. That was only yesterday, so I can't yet say for sure that those fonts were also causing Word to quit now and then, but there are no quits so far so I am optimistic. Allan Atherton The next meeting of the Louisville Computer Society will be November 26 For more information, see <http://www.aye.net/~lcs>. A calendar of activities is at <http://www.calsnet.net/macusers>.
