First things first. Make sure you’re patched to 7.5.2.
Do you run Suitcase?
Thanks for the reply.
I searched for updates and the message I got back told me all the CS5.5 software was up to date.
I should say that I tried to invoke InDesign now by clicking on the shortut on my desktop and nothing happened so I tried again and still nothing happened. However, there appears two entries of InDesign.exe *32 in the list of Task Manager processes.
No, I do not run Suitcase.
How about Q2ID? Any other font manager besides Suitacse?
Kill the InDesign.exe process in task manager. Nothing you try is going to work as long as they are already running. Then try opening ID and suing the File menu to open the doc. If that works, try closing it and double-clicking the file while ID is open, and if that works try the double-click with ID closed. Let us know what happens.
No other font manager.
Kill the InDesign.exe process in task manager. Nothing you try is going to work as long as they are already running.
Then try opening ID and suing the File menu to open the doc.
That does not work. Just another instance of InDesign.exe in the list of processes but no load.
I removed the instance, which also removed another
, and started InDesign from an icon and it loaded as usual. I used the file menu to open the doc and that worked fine.
I closed the document, and with ID open I double clicked the document and that loaded fine.
I then closed ID and double clicked the document and that did not work properly, ID loaded the file but did not display it. However, the document was created by CS4 InDesign, and therefore the present ID had converted it, but I could not close the document because the Window asking whether I wanted to save the conversion cannot be seen!
This is a mess and I am seriously considering giving back InDesign CS5.5.
I have had no problem with CS4 and the indicated running problem highlighted above. That program is IronKey and has never caused a problem with ID before CS5.5
IronKey is banking securtity software, yes?
There was a problem a couple of years ago with another security program, Trusteer. This sounds like a similar situation, a software conflict, and you can probably just terminate IronKey before using ID for the moment, and report the problem to IronKey. Trusteer issued a patch in a matter of days, and hopefully IronKey would do the same.