Hanging on a newly recorded project "Save as"

Question

We've just started using Captivate2 (v2.0.0) however we've
already bumped into a repeating serious flaw.
After recording a short web based software simulation (135
slides), we attempted to save the project using the usual "Save As"
option and clicked ok.
The file gets created (~7MB) in the target directory,
Captivate shows it's saving and the save bar gets to the end but
then just hangs using 99% CPU. Using the Task manager process
window with I/O read,write and other shown, we can see that no data
is read, written or "other". After a while windows changes the
title bar to "Not Responding". This doesn't change even after
leaving it for 2 hours.
The only option is to end the application.
On attempting to load the saved project, Captivate states
that the project is corrupt and then closes - no storyboard is
displayed.
The machine is a IBM T42 laptop, 1GB RAM, 10GB free HD space
running Windows XP and IE 6.0. The rest of windows XP patches are
uptodate. Laptop screen as primary at 1024x768x16bit and the
secondary external monitor is at 1280x1024x32bit.
This is repeatable and first occured during a 26MB file
(360slide) recording.
Any one else have this experience?

Answer 1

Lynne, a few notes for clarification.
1) You treat my use of the term "thrashing" as though it were
something I just made up. It is a common term descriptive of rapid
and repeated accessing of the hard drive in its efforts to perform
any disk-intensive task, specifically page swapping. The "rev up"
term that you have chosen to use is called "thrashing" among all PC
technicians. To quote Webopedia, one of the most respected online
"technical dictionaries":
quote:
Disk Thrashing:
In systems that use virtual memory, the resulting condition
of a hard drive being used excessively for virtual memory because
the physical memory (i.e., RAM) is full. (The process of moving
data into and out of virtual memory also is called swapping pages.)
Disk thrashing considerably slows down the performance of a system
because data has to be transferred back and forth from the hard
drive to the physical memory.
A sure sign that your computer is thrashing is when an
application stops responding but the disk drive light keeps
blinking on and off. Thrashing is generally caused by too many
processes competing for scarce memory resources. To temporarily
stop thrashing, you need to terminate one or more applications. To
stop it permanently, you need to install more main memory.
2) My reference to Production Studio's install size was
simply to make the point that 10GB "free" space is really very
little - less than is required to install a large program, and
certainly not enough
contiguous free space to facilitate page swapping as would
be automatically invoked as a function of the OS if physical RAM
were not sufficient for the computer's requirements.
3) Of
course you are being argumentative, but not only do I
not mind ... I encourage differing points of view if they
are supported by logic and reason. That's how we all learn.
4) I am aware of Adobe's system requirements. I am also aware
that there is a difference between resources required to run the
application under optimum conditions (often the marketing
departments' idea of a minimum), and those required to run the
application comfortably in a day-after-day development environment.
The answer to your question "
Why would Adobe only recommend less that half of what (I)
do?" is - well, no offense, but their goal is to sell software,
while mine is to use it and advise on it. Adobe isn't lying to you
(exactly) - but neither am I.
I will be greatly surprised if Adobe's "official" answer to
Nick's problem is substantially different than my own ... but like
all of you, I look forward to seeing their comments.