George_T said:
No, some of them are quite small, well under 10Mb; it's not a size
issue because I've edited some big files.
If you want, you can try using Sysinternals ProcMon, to trace
the events for the "moviemk.exe" executable.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
How you use this, is you start the program, and a "filter" dialog
box allows you to specify a filter. Otherwise, without filtering,
you would collect way too much data.
I added the filter term
"Process Name is moviemk.exe include"
which means the filter will select events coming from the Movie
Maker program. Once I'm finished with the filter, the program
can start collecting events.
I pulled up a short clip, and attempted a save, so I could get
some events. Windows Movie Maker is a very busy program, so you'll
have a lot of events to go through. What you'd be looking for,
is events related to the named output file. There is a search
function ("binoculars" icon), that allows searching the event
list. The moviemk.exe program may use a temporary file, so it may
not be the actual output file which is failing. There could be a lot
of events to sift through.
In the File menu, is an item that controls capture. You can stop
capture, if you've had a failure in Movie Maker, and you know it is
already captured in Process Monitor. Then, it is a matter of seeing
which operation failed. And looking at the events leading up to
it.
For example, when I used the ProcMon program a couple months ago,
I could see an offending event, and I could see a sequence of
registry operations just before it. Sure enough, I could see
a particular registry event that was consistent with the
symptoms (the registry item in question had been upset when
new hardware was added to the computer). So you need to be a
bit of a "CSI" type, to figure out what went wrong. If you're
lucky, you'll see a file operation fail, and maybe some kind
of error code indicating what kind of failure. The problem is,
the WMM program screws around a lot, and failures (i.e. directory
test probes and the like) are normal events. So not everything
that has "fail" printed on it, is a failure as such. Some are
simply tests that were likely to fail in the first place.
Otherwise, if you Googled, and cannot find similar experiences
somewhere, it may be difficult for others to reproduce the problem.
For example, I have no problem right now, saving my test output.
It ended up in "My Documents:My Videos:test.wmv" and clicking on
it now, I can see my movie. There are no guarantees with ProcMon,
but if someone doesn't manage to find your exact symptoms, you
can do some detective work yourself.
Paul
