PDF-to-PDF link works online, fails on CD

Question

We publish multi-part PDF docs on the web and on CD. Inside them are occasional placeholder pages for large maps, with the text CLICK HERE TO VIEW linked to an external file, also a PDF. We make the links with AA's Link tool. (Draw a rectangle around the text, Open File, browse to the map file, etc., you know the drill.) We’ve done this for years, but recently:
- Clicking the link from the local file finds the map just fine.
- Posting the doc and map to the web, opening the doc online (IE), and clicking the link in it for the map works fine.
- Burning the webpage, doc, and map to a CD in the exact same configuration puts up a Security Warning box when we click the map’s link inside the document. The box says the doc is trying to connect to [map's path (correct path)] and offers responses of Help, Allow, or Block. Clicking the obvious ‘Allow’ has no effect!
The CD setup has worked fine for years but now suddenly fails. Is there some parameter in IE that's wound too tight?
I've posted a sample of how it works. To see it, open the first doc linked on http://www.speakeasy.org/~mtangard/test/example.htm and click the red CLICK HERE.. link on page 5 or page 7.
Using Acrobat 9 Pro and IE 8.0.6. Grateful for any clues....
Mark

Answer 1

Dump the web page.
For deployment of PDF collections on optical storage media (OSM) avoid "entry" to the collection(s) from an HTML file on the OSM.
Rather, always provide a "start" PDF that is on the root of the OSM.
This avoids having to rely on the end-user's browser or browser version or one software house's updates gobbering another house's application.
Provided the PDFs are not PDF Packages, Acrobat 9 Portfolios, or Acrobat X Portfolios end-users with Adobe Reader / Acrobat back to version 5.x can use the PDFs in a reliable manner.
n.b., if a Cataloged Index or tiered indices are utilized users of version 5.x are 'locked out' as the licensed search engine/index builder was changed in version 6.x
Create a staging "burn zone" on a local machine's HDD.
Identified the common "parent" directory/folder that exists on the web deployment.
At the provided web space example this would be directory/folder "fier".
--| feir
.... file: exec_summ.pdf
.... --| figs
....  .... file: fig_es-1.pdf
~
~
When a link path traverses through directories/folders on its passage to a target file this very specific "path" must be maintained when a file collection is transfered.
True for a transfer of files to other web space, network space, other local machines, USB device, or OSM (any format - PDF, HTML, whatever).
~
~
So, with the parent "feir" and its child content present in the 'burn zone' what goes to OSM will contain functional links.
A Windows autorun file on the OSM root affords the possibility of calling Adobe Reader from the local machine to render the "start" PDF.
If, for the PDFs in the 'burn zone, a Catalog Index has been created then associate the PDX file to the 'start' PDF.
With it all on an OSM, the user has a mounted PDX as soon as the 'start' PDF is opened. This supports "anytime" use of Advanced Search.
n.b., newer releases of Acrobat / Adobe Reader can be expected to provide a security dialog when the PDX is accessed.
Be well...