Project Compression -- Need Help or New Strategy

Question

I have a Captivate project size issue. While the project is
only 156 slides, about 150 of the slides have embedded Flash movies
that average around 10 MB each. Tinkering with quality settings for
the movies, I can get by with medium quality, but anything less to
reduce filesize makes the videos look bad. While previewing the
entire project is no sweat, when I publish as a Windows executable,
the resulting EXE file is ca. 2.5 GB, which is too large for most
PCs to handle memory-wise and fails to load even on a high-powered
Alienware workstation.
So, even though I have "project compression" ticked in the
project preferences, is there a better way to compress the project
so the EXE isn't so big,
OR
is there another strategy I should employ when trying to
reduce the overall output filesize so the project can run on
middle-of-the-road hardware?
Thanks,
Andrew

Answer 1

Hi Andrew
You could create a few smaller projects, then Daisy Chain
them together so that as one finishes it calls the next in the
sequence. This would certainly reduce anything loaded up at a given
moment. But if you are using 10 meg embedded animations, I'm not
sure you have a way around that other than linking out to them from
inside your Captivate projects.
I've made an attempt at explaining the Daisy Chaining process
at
this
link.
Cheers... Rick