Won't save to DV-AVI

[Bill Brandenstein]

After a fresh rebuild of Windows XP I have lost the
ability to export even a simple, transitionless project to
DV-AVI, while exporting to other lesser and unsuitable
formats work fine, including WMV. That's no good -- it
HAS to be DV-AVI. I have added several Windows Media
utilities, including the Encoder, re-installed DirectX,
and checked PapaJohn and John Kelly's websites for help,
all in hopes I'll stumble onto some little file that
needed repairing. All to no avail.

What happens is that saving to file begins normally, then
fails when the first DV-AVI input clip is reached with the
classic message in the "Cannot Complete the Save Movie
Wizard:"
"Windows Movie Maker cannot save the movie to the
specified location. Verify that the original source files
used in your movie are still available, that the saving
location is still available, and that there is enough free
disk space available, and then try again." Of course,
none of these are a problem, and changing the output type
bypasses the error.
When I exit the wizard, then WMM2, the following error
message appears:
"Microsoft Visual C++ Runtime Library
Runtime Error!
Program: D:\Program Files\Movie Maker\moviemk.exe

R6025
-pure virtual function call"

That's it folks. Any help would be appreciated.

 

[John Kelly]

Hi there Bill,

After a fresh rebuild of Windows XP I have lost the
ability to export even a simple, transitionless project to
DV-AVI, while exporting to other lesser and unsuitable
formats work fine, including WMV. That's no good -- it
HAS to be DV-AVI. I have added several Windows Media
utilities, including the Encoder, re-installed DirectX,
and checked PapaJohn and John Kelly's websites for help,
all in hopes I'll stumble onto some little file that
needed repairing. All to no avail.

What happens is that saving to file begins normally, then
fails when the first DV-AVI input clip is reached with the
classic message in the "Cannot Complete the Save Movie
Wizard:"
"Windows Movie Maker cannot save the movie to the
specified location. Verify that the original source files
used in your movie are still available, that the saving
location is still available, and that there is enough free
disk space available, and then try again." Of course,
none of these are a problem, and changing the output type
bypasses the error.
When I exit the wizard, then WMM2, the following error
message appears:
"Microsoft Visual C++ Runtime Library
Runtime Error!
Program: D:\Program Files\Movie Maker\moviemk.exe

R6025
-pure virtual function call"

That's it folks. Any help would be appreciated.

Wow!!! Looks like you have a good one here....I did some checking and found
some info.....I will put it below my sig line.
Although the info found seems to indicate that the actual cause is due to
some program code in Movie Maker not being as robust as it should be I
doubt if it is. It looks to me that what you probably have is some executed
routine that has failed in an unexpected way resulting in the error message
you got.....
Even though you have installed DirectX etc, I would re-boot the computer
and before running any other program download and install DirectX version
9.0b, then reboot again and then download and install the codec's from
Microsoft or download and install Windows Media Player 9....I can not
remember now, but, if you get the option to download the full package so
that you can install it later then that's the option I would suggest you go
for (This assumes of course you have a good connection speed)

If this fails...

The AVI structure is actually a container rather than a method. The
container can use any one of a number of codec's to create the data within
the container......So, it is not impossible that a codec from some other
package is causing the problem. If it is one of the known problem causing
codec's then you can download a program written by myself to deal with that
issue. Its called "Rename Codec's" I have to say though that if that turns
out to be your solution that it would not be a good enough solution for
me.....I think I would have to consider whether the program that installed
the codec concerned really had a future on my system.

Its not much I know, but hope it helps.

Best Wishes.....John Kelly
www.the-kellys.org

SYMPTOMS
The C++ program fails, and reports the following run-time error:
runtime error R6025
- pure virtual function call
CAUSE
This error occurs when your application indirectly calls a pure virtual
member function in a context where a call to the function is not valid. In
most cases, the compiler detects this and reports the error when building
the application. But depending on how your code is written, sometimes the
problem is detected only at run-time.

The error occurs when you indirectly call a pure virtual function within the
context of a call to the constructor or destructor of an abstract base
class. This is illustrated in the sample code below, along with some more
description.
RESOLUTION
Calling a pure virtual function is a programming error, so you need to find
the call to the pure virtual function and rewrite the code so it is not
called.

One way to find a call to a pure virtual function is to replace the pure
virtual function with an implementation that calls the Windows API function
DebugBreak(). When using the debugger, DebugBreak() will cause a hard-coded
breakpoint. When the code stops running at this breakpoint, you can view the
callstack to see where the function was called.
STATUS
This behavior is by design.