Posts: 17,885
Threads: 2,316
Joined: May 2025
Reputation:
0
My wifes boss just installed OSX on her machine. Now she is having font problems. She used Suitcase in 9 and grabbed fonts off a server. No problems. They installed OSX, and Suitcase X and now all the fonts appear as generic icons. When dragged into suitcase they don't go. They just bounce back. they are unrecognized by OSX as font files. Won't even open in Font Book.
Also, when she launches Entourage (9 version) it opens Classic and prompts her to create a new account. Even though she already set up an account in OS9.
Probably 2 unrelated problem, but she just called me with both.
Posts: 3,228
Threads: 294
Joined: Nov 2016
Q1: Download the free app Linotype FontExplorer X, and run it to detect conflicts. Much better than Font book.
Q2: ?
Posts: 3,228
Threads: 294
Joined: Nov 2016
Oh, also clear the system font cache w/above app. Restart.
Posts: 17,885
Threads: 2,316
Joined: May 2025
Reputation:
0
I understand there could be a confilct...with a few fonts. But ALl of them? An entire server's worth? And yes, Font Explorer is more robust than Font Book. But Suitcase won't recognize the fonts either. Suitcase X and OSX are both a fresh install btw.
Posts: 16,409
Threads: 1,430
Joined: May 2025
Read this to get a handle on organizing your fonts in OS X. It's very important.
What kind of Server? Suitcase Server? Or are the fonts simply stored on another machine? What version of Suitcase?
Try getting in touch with Extensis tech support.
Posts: 17,885
Threads: 2,316
Joined: May 2025
Reputation:
0
The fonts are simply stored on a file server. Nothing fancy i would imagine. they are stored there b/c they do not store the fonts on the local machine. organization on the server is complete. No orgainization or rearranging necessary on the local machine. the fonts work fine in suitcase (and otherwise) in OS9. after installing OSX the fonts do not work. they are using Suitcase. An OSX version of Suitcase. However, the fonts won't even open in Font Book let alone suitcase, so i don't think its a problem with suitcase. OSX simply isn't recognizing the font files as fonts.
Posts: 1,395
Threads: 19
Joined: Nov 2007
Reputation:
0
What hardware is the font server ? (Apple Macintosh something-or-other?)
What OS does it run ? (MacOS 9 or X or ?)
What filesystem is in use on the font server ? (HFS or HFS+ (with or without journaling) ?)
What is the network protocol used to communicate between the font server and the local (client) system ? (Appletalk (afp) ?)
Whatever the font server is using, the client system should be using a compatible or equivalent. You don't want to use anything that trashes resource forks.
My ill-considered US$0.02,
Posts: 8,279
Threads: 628
Joined: Jan 2009
Reputation:
0
the server is the issue. the fonts should be stuffed under OS9, copied to the server, then unstuffed under OSX.
DH is on track: resource forks are missing.
Posts: 17,885
Threads: 2,316
Joined: May 2025
Reputation:
0
I will see if i can get the info form her. But if it was messing up the resource forks, wouldn't that affect the fonts on OS9 as well? She can boot into OS9 and use the fonts ok.
Posts: 1,395
Threads: 19
Joined: Nov 2007
Reputation:
0
The font server system under (whatever) is not trashing resource forks.
The client system under OS 9 is not trashing resource forks.
The client system under OS X is running something that is trashing resource forks.
You have to look at everything on the client system that stands between the fontserver system and the client application (Suitcase or FontBook).
* network facing : network settings / file sharing / file transfer
* local filesystem : HFS or HFS+ (not UFS)
* client application : OS X native or Classic ? if OS X native, is it compatible with the OS 9-generated data file(s) ? if Classic, are the Classic network and file settings compatible with the font server ?
There may be other possibilities to check out. Paranoia is good.
