Odd situation with Adobe Acrobat 7.x as part of CS2 Premier

[Kok-Yong_Tan@adobeforums.com]

Initial installation of the entire suite of Adobe CS2 was fine. It even worked up through the upgrade of my system to 10.4.6. Then I installed Acrobat Reader for PalmOS 3.0.5 and *ONLY* Acrobat Professional 7.0 from the CS2 started crashing upon startup. Odd thing is that Acrobat Professional 6.x that I still have on my system is working fine. And so is the rest of the CS2 suite (e.g. Photoshop, Illustrator, InDesign, GoLive, Distiller, etc). I've a very long crashdump in my Acrobat.crash.log but have no idea how to interpret it. I've done the normal things like remove the AdobeFnt*.lst files, pref files, etc, but Acrobat Pro 7.0 continues to crash on startup. Attempting to upgrade to 7.0.7 results in an error that it cannot upgrade the file (I pointed it to Acrobat Pro 7.0 in the hope that the upgrade would fix my problem but no such luck). Any pointers would be appreciated. I'd rather not have to Archive and Install my whole operating system. That's so, so, Windows. Is there any way to fix my problem without doing that?

[MarkATS@adobeforums.com]

start up Acrobat with the shift key held down to disable plug-ins. Probably some sort of conflict.

[Kok-Yong_Tan@adobeforums.com]

Never mind.

I found the problem. By browsing through the Acrobat 7.0 contents and searching for recently changed folders, I found a plugin named "SendToPalm.acroplugin" in the Plug-Ins folder within the Acrobat 7.0 app. This was causing my startup crash. As soon as I ripped it out, my startup crash went away.

Thank heavens for descriptive naming because that plug-in had creation and modification dates in 2003. I would never have found it if not for the name.

Hope this discovery helps someone else out.

[Kok-Yong_Tan@adobeforums.com]

Thanks, Mark. You were right. It was a plugin problem. As you can see in my other post to myself, I found it the hard way! :-) Good to know that starting up Acrobat with the shift key held down disables plugins.