possibly the issue you are having are
due low resources, ie, memory/ram and
or virtual memory.
if we take a look at the above from
a different perspective; a similar scenario
could occur if for example your background
image(s) are a high definition at file size
of 20 megabytes (for example).
this is an extreme example, but the
point is that a large images such
as the above and replicated in a multitude
of slides would overwhelm your resources
by managing 20 megabytes backgrounds
and then overlaying text boxes.
so it might seem reasonable that
the graphical issues are a result
of resources.
--------------------
i would suggest the following:
a) examine the background image(s)
size and ensure they are of a reasonable size,
something like 200 kb and not 2 megs.
also, if i recall the backgrounds can
be inserted into each slide or linked.
using the link feature would reduces
the file. However, using links require
special considerations based on the
method of your presentation. Therefore,
if you are not familiar with linking the
images, then you should not use this
advanced feature.
b) try to work in your presentations without
backgrounds. That way you can focus
on building the slides with your important
data first. Then save several copies of it.
afterwards and using one of the copies, insert your
background images as the final process
with building your slideshow. If it crashes
then you have the other copies and the crash
will confirm the backgrounds might be the
issue.
c) ensure your virtual memory is at
a fixed size. Eventhough windows
can automatically adjust the virtual
memory size, this process requires
resources that may not be available
to your system while fiddling with
your presentation. I set all my
machines at a fixed custom size
of min = 2 and max=1152. these
are reasonable for a variety of applications
and can be adjusted later if the pc
seems sluggish.
d) one thing i like to do before
opening a presumably large and
complex file is to flush out the
memory with:
http://www.amsn.ro/
the way i use it is that i open it,
run it once or twice then
close it before working on any large
file that are hungry for resources
like my photoshop images where some
of my drafts images are around 80 megs.
most people reject the use of the
above program. However, i have used
it with success and the windows o.s.
benchmark proves the results from the above.
-------------
other than the above, i cannot think of
any other considerations for an issue like
this. My perspective of your issue suggests
low resources. But there may be other
considerations as well....
- db
