"Please insert the disk: Untitled CD" error message

[jheilman]

I've had this problem for a couple weeks. With Quark 4.0 on Mac OS 9.2 I began having the error message in the subject (Please insert the disk: Untitled CD) pop up on launch. I have the option to "cancel" the message and after hitting it about 15 times it goes away. Occasionally during operations in Quark it will pop up again forcing me to hit cancel numerous times.

So, I upgraded to Quark 4.1. The problem went away for a few days. But tonight, it resurfaced. I have deleted "finder preferences", "appleshare prep" and "xpress preferences" to no avail. Do I have a virus? Is there another preference file I need to delete? Help!

 

[MarcusStringer]

I have that problem when I try to open fonts which I have loaded into suitcase straight from the cd (because I'm lazy) and then removed the cd. and when I go to open a document with the fonts in it I get that message...it's frustrating....isn't it

Marcus

http://www.midlandtypesetters.com.au

 

[jheilman]

I have had that font problem, but this is different. Simply opening Quark elicits this error message.

 

[jheilman]

So, anyone else know how to eliminate this problem??

 

[bigbabich]

I am having the same exact issue. The machine is also dual booted for 9.2.2 and OSX (just wondering if yours is). I believe I have localized it to a font issue. I have deleted some of the fonts that I use, and the Insert Disk error has gone away along with some wierd window errors (toolbars disolving, Quark disappearing into the desktop). The files I access are now without the fonts but everything is working ok, and I'm going to reinstall the fonts, hopefully everything will be cool. Please post back if this works for you. Thanks

 

[jheilman]

Woohoo...it's gone!!

Thanks for pointing to fonts.

I used to use Suitcase to manage fonts then switched to ATM Deluxe. Well somehow, Suitcase was made active again and was apparently conflicting with ATM. Once Suitcase was given the boot, the error disappeared.

I never would have considered looking at font issues for that message. Thanks again.