Hi again
Unfortunately, if they copy to their own hard drives there is little you can do other than to advise that things won't work until Flash Player security has been massaged. I think there is actually a way to supply some form of an XML file that configures the player to allow a specific location to behave, but you would have to know the location beforehand. And short of simply advising that they place content in a specifically named folder, that doesn't seem feasable. If you are supplying via CD-ROM, you may also install a small "Web Sever" that runs on the CD. This tricks the Flash Player into believing the content is in that safe zone and the security restrictions aren't enforced.
In the event you want to try that route, below is an article I constructed that lists the steps you need to take:
Placing Captivate content on CD/DVD media
So here you are. You have your Captivate movie(s) finalized and ready to go. Your goal at this point is to copy the content to CD-ROM or DVD for distribution.
What next? Are there special considerations I need to think about? Anything in particular I can do to make things easier?
First we will examine a bit about the media.
If you intend to use CD-ROM, you have roughly 650 to 700 megs of space available to store your content. Is that enough? If your Captivate content is larger than this, you will have to either consider ways of paring it down so it fits within that size restriction or you will need to consider using DVD. DVD has a much larger storage capacity.
You may elect to exploit the autorun feature available. It's worth noting that autorun is far from foolproof. For example, in some organizations, the IT staff will routinely disable autorun. You may wonder why. They often view autorun as a security vulnerability they would rather avoid. If autorun is left enabled, and someone has constructed a CD with a virus or other malware that automatically runs and installs or otherwise damages the computer, the IT staff would like to prevent this. Hence the reason for routinely disabling the feature.
Assuming autorun has not been disabled, there are other reasons it could fail. For example, the autorun.inf file needs to reference the file to run. If this file name is very long and contains spaces, autorun will often fail. One way around that is to surround the file name with quotes inside the autorun.inf. Unfortunately Captivate doesn't do this for you, so if you wish to use a long file name, you will need to amend the autorun.inf yourself after Captivate creates it. Another approach is to simply change the name of the Captivate file you are autorunning so it conforms to the older DOS 8.3 naming convention. For example, instead of using a file name of My Most Wonderful Captivate Movie in the whole wide word, the name would perhaps be MyMovie.
Adobe Captivate does offer a feature that will create the autorun.inf for you. Even though the cons have been issued above, it's still a good idea to configure an autorun.inf in case it will be used.
Media File Structure
If the amount of information on the CD/DVD is substantial (meaning you have a potentially confusing array of files) it is often useful to create a folder and place all the content inside the folder. You would then keep only the file(s) pertinent to starting your application in the root folder of the media. This simplifies things dramatically for your end user.
Web Based Content
Captivate is capable of outputting a few different formats. The main two formats are known as Standalone and Flash SWF.
If your output is Flash SWF (Captivate SWF with HTML page) you have special considerations. Later versions of the Flash Player have security built into them. This means that when you try to run content on your local drives (CD or DVD would be considered local drives in this case) the Flash Security model will often block certain operations. Things such as JavaScript calls and links to web sites fall into this category of blocked items.
What is at issue is the fact that you are operating on the local file system. That's dangerous territory to allow anything to happen. After all, if an application that normally runs on the web has access to the local file system, some nasty things could result. Hence the security restrictions imposed. For testing purposes, you may wish to configure the Flash Player to acknowledge the folder where you are running the location as being safe. The problem here is that with CD or DVD distribution, the CD or DVD is considered as being part of the local file system. This means that unless the location has been marked as safe, some of the content will refuse to work.
You might wonder why this doesn't happen with content that comes from a Web Server. The reason is simple. Content that has been served by a Web Server is automatically in a restricted zone from the security perspective. Because it is already within a security zone, the Flash Player has no need to restrict or inhibit any actions.
Fooling the Flash Player
Fortunately there is a way to work past this. What you can do is to trick the Flash Player into believing the content it is playing is actually coming from a web server. The manner in which this is done is by installing a very lightweight web server that starts and runs before your content runs.
Fortunately one is available in the open source arena. (Read free to use at no additional expense to you)
The name of the software is Server2Go.
You will need to follow the steps below to install Server2Go.
Download the Server2Go software from http://www.server2go-web.de/download/download.html
Choose the Micro package
This should result in receiving a zip file named distribute_apache1.3_micro.zip
Unzip the contents of the zip file to the root of your hard drive ( C:\ )
This should create a folder named distribute_apache1.3_micro
Open this folder and delete the following files and folders inside:
Files:
splash.bmp
logo.ico
readme.txt
Folders:
dlls
dbdir
cgi-bin
Open the htdocs folder and delete all files and folders inside.
Copy all of your Captivate output files to the htdocs folder
Rename the HTML page Captivate created to index.htm
Copy the contents of the distribute_apache1.3_micro folder to the CD-ROM and test!
Hopefully this helps... Rick 
Button_Prop.jpg (51.6 K)
Dir_Struct.jpg (25.3 K)
