Hi Mike,
It may start being the same bits of code pasted into the two sections, however the output is that the code in the main section of a wiki page is getting mangled as it is being interpretted as wiki text.
Since the allowScriptAccess param is being changes from always to never, then I suspect that it is based on the different options which are being used to call lib/htmlpurifier on the text being processed.
The key to the problem seems to be trying to embed a flash object which has a separate loader "bootstap.swf", and a data file listed in the flashvars parameter - content=http://content.screencast.com/users/DoorCountySolar/folders/900%20-%20Marketing%20Plan/media/e91f54cd-f049-4694-a773-479e5ad68253/gfgdfgdfgdfgfdg.swf.
The flashvars param seems to be working the the summary area, but disappearing when the code is included in the main body of the wiki.
There might be a way to sidestep all of this complexity. If you have swf option turned on in the moodle media filters, have you tried just including a simple link to the content of the screencast:
<a href="http://content.screencast.com/users/DoorCountySolar/folders/900%20-%20Marketing%20Plan/media/e91f54cd-f049-4694-a773-479e5ad68253/gfgdfgdfgdfgfdg.swf">Screencast 1</a>
With any luck, the moodle filter should write out a flash object to embed the swf file. You can also specify the height and width by adding ...fdg.swf?d=640x320"
With screencast.com, be careful to use the file specified by the content= variable hidden in the flashvars instead of the bootstrap.swf file.
You may lose some of the advantages of using a the bootstap loader and having a nice poster image while loading, but it might work for the situation you describe.
--
Sean Farrell
Edinburgh, Scotland