I'm noticing that the self heal is gone...

# via iPhone

I just spent like 2 full days hacking Adobe Reader to deploy it, and it works now as is. I am sure not going to be pushing out any updates that may undo all that hard work, ha! So, sorry I have not noticed that.

9.3.4 breaks the Self Heal fix. We've been keeping everyone on 9.3.3

-- Gregory Stamper
Macintosh Application Engineer

175 Fifth Avenue
New York, NY 10010
646-307-5156 (office)
646-918-0414 (cell)

Visit our new web-site: http://www.macmillan.com

*please consider our environment before printing this email*


As an FYI, I have reported this to the appropriate folks in the Acrobat team. I'll let this list know if I hear of a resolution to this issue.

Cheers,

Jody Rodgers | Product Manager| Enterprise & Volume Creative Suite | Adobe Systems

Jody, you da man!

P.S. Not at all related to Aaron Rodgers...

Craig E

Hi Steve,

This useful tip was forwarded to me a while back on the Mac Enterprise
List by Dan Ball:

"All I do is edit out this line in each .app/Contents/MacOS/
SHInit.xml with these comments -- --> :
-- <key>selfhealingfilename</key><string>AcroEFGPro90SelfHeal.xml</
string> -->

So far its worked for me with Reader since 10.3.x and I just moved
over to Acrobat about 2 years ago or so and luckily the same thing
works for it for me so far."

I do this edit in the Acrobat Pro and Distiller applications. I no longer
edit the SelfHeal.xml files.

Usually on the machine I build the Composer package on, I will open
Acrobat once and let it attempt to self heal and all the other garbage it
does at launch, then make the change I listed above, and also copy over
~/Library/Preferences/com.adobe.acrobat.90.sh.plist do be added to the
User Template and installed users when it's deployed with Casper. I'm
pretty sure this method is still working for me, even with 9.4.0.

Thanks,

-- Ted August
Salve Regina University