InDesign CS3 crashes upon launch

Renaming the SING folder to SING.bak made it start for me as well.

I'm running a Danish version of XP SP2 and common files is named "Fælles filer" on it.

My printer works fine, and the indesign hang opon start. "Starting up Service Registry"

What should I do...

"Solved the problem, just remove the SING plugin..."

SING is a technology for dynamically adding glyphs to fonts as needed. The CS2/CS3 version only works with East Asian fonts in InDesign (and only CID-keyed OpenType CFF at that). So, if you are unlikely to be working with East Asian documents, you could safely delete it.

Is anything else interesting about your installation? Are there non-ASCII characters in the SING folder path? What language version of InDesign are you running? What language version of Windows?

Regards,

T

-> Mark

You the man!

I works!

Do you know what the Sing folder contains eg. what it is used for?

/Asger

Problem solved if you do this

Delete this folder

%programfiles%\Common Files\Adobe\SING

--
Mark

Hi James

Installing and running Perfectdisk RX Suite did not solve the problem.

/Asger.

My startup problem was not a result of the printer error either. I uninstalled, reinstalled and repaired my installation countless times, with the printers on and off. I cleaned the registry as well as the temp files, but still no success.

Then I installed Perfectdisk RX Suite, ran the basic scans, and was shocked when In Design CS3 started right up!! The Perfectdisk program was a trial program which I then uninstalled after a couple of weeks, and found that InDesign would not start - the error came when the program was almost finished installing - the interface was on the screen, then it would report an error and shut down.
I reinstalled the Perfectdisk RX Suite program, and InDesign started up without a problem!!

No, I do not understand this...but InDesign is working for now.

Deleting those files did not work for me.

Yes i have done all regarding InDesign on Windows XP computers.

/Asger.

Did you look at the KB techdoc?