Cronos Pro Optical (OpenType) Crashing Quark 6.5

We just purchased the Cronos Pro Opticals type family in OpenType for the Mac.

After installing, it continually crashes Quark 6.5 (most of our computers).

I'm personally running the following:

Mac OSX 10.4.7
Quark Xpress 6.52 (same problem in 6.5)
Extensis Suitcase X1 11.0.2

I've tried it on another computer running Mac OSX 10.3, Quark 6.1 and
Suitcase X1, and it worked fine...

I've tried it on another running Mac OSX 10.4, Quark 6.5 and Fontbook, and it
crashes *most* of the time.

Is anyone familiar with how/why this would happen? I have posted a message
on Quark's online forums too, but no response yet.

Thanks for any help,

No idea. There is a known issue with OS X and sets of fonts with optical size
variants, but it just has to do with not all of the fonts showing up in font
menus of some applications. I have not seen a crashing issue like this involving
a properly made OpenType font.

I'll be curious to hear what Quark says.

The font actually does not show up in Photoshop and Illustrator CS. However, on
the computer running OS 10.3, Photoshop will allow you to type in the name of
the font and use it that way. On OS 10.4, Photoshop autocompletes the font name
and thus rejects a name not found in the list...

On OS 10.4 the font menu in MS Word shows a bunch of giberish now, but will let
me select Cronos and use it.

Your comment about "properly made OpenType" is interesting. I would
have assumed that all fonts sold by Adobe.com would be "properly
made".

Aside from that, here's the thread at Quark.com with an interesting note from
Mark Douma: <http://www.quark.com/service/forums/viewtopic.php?t=14224>

Thanks,

I didn't mean to say these fonts weren't properly made - I was trying to suggest
that poorly made fonts (in any format, really) can cause all sorts of weird
problems. However, at Adobe we do test these things pretty carefully.

So, the short version appears to be that the problem is a bug in Mac OS 10.4.7
and 10.4.8, which trips up some applications but not others - specifically
applications that are doing system calls looking for the old-fashioned resource
fork.

Adobe will verify, log and escalate the issue with Apple.

Regards,

Thanks so much!

I hope you guys and Apple can work out the issue. It's not fun spending several
hundred dollars on a type family you can't use.

I guess this issue affects the entire Adobe Font Folio now?