flyingfish182 said:
John I read your reply to Calgovin below. My question pertains to
the fact that every time I open Movie Maker 2.1 it locks up. When
you send the Error Message, the program closes.. Nowhere have I been
able to find a way to repair the problem. Any suggestions?
=========================
Some users have reported problems
after installing IE7. If this applies to your
situation ...uninstalling IE7 may be worth
a try.
(927177) How to uninstall Internet Explorer 7
http://support.microsoft.com/kb/927177/en-us
I've also seen a report that disabling the
ffdshow codec could be the fix. To accomplish
this...open Movie Maker and go to...Tools /
Options / Compatibility tab...Uncheck...
ffdshow / OK.
===
(You can disable ffdshow with this command:
regsvr32.exe /u "C:\Program Files\ffdshow\ffdshow.ax"
After running that command, the regular
DivX/XviD codecs will be used instead of ffdshow.
You can enable ffdshow again with this command:
regsvr32.exe "C:\Program Files\ffdshow\ffdshow.ax" )
===
More info:
Movie Maker 2 Crashes and Hangs
http://tinyurl.com/bqgyx
The following info was previously posted by Dean Rowe:
===
QUESTION:
Whenever I open MM2 it has to close. The problem seems to be related to
qedit.dll . This dll is always mentioned in the event viewer. I'm using
XP
SP2, with the embedded MM2.
ANSWER:
There's a component in Direct Show which
caches the information about the effects and
transitions that are registered upon your system.
Unfortunately there's a bug in that component
which causes it to crash if you have a lot
of transitions and effects installed. MovieMaker
calls this routine on startup which is probably
why you're seeing MovieMaker crash.
Fortunately there is a workaround by doing
something like the following.
1. Find an application which has registered
a bunch of effect filters.
2. Rename the directory that the application
is installed into to something else - which will
temporarily cause those effect filters to fail
to load.
3. Start MovieMaker. As less effects are
successfully created, MovieMaker should
hopefully launch.
4. Rename the directory in step 2 back to
it's original name so the original application
still works.
5. Start MovieMaker again. As everything
was successfully cached in step 3 it shouldn't
try to recache things so it should continue to
work..
As an example of an application for step 1,
I've seen people run into this problem with
applications installed from InterVideo. (This
isn't a bug in InterVideo's application - it's a
Microsoft bug it's just that InterVideo applications
can install a bunch of DirectShow filters). In
this case you would go to your "C:\Program
Files\InterVideo" directory and rename "InterVideo"
to something like "TempInterVideo". Then start
MovieMaker. Once it has launched, close it
down and rename "TempInterVideo" back to
"InterVideo".
Good luck
Dean Rowe
This posting is provided "AS IS" with no
warranties, and confers no rights.
===
--
John Inzer
Digital Media MVP
Notice
This is not tech support
I am a volunteer
Solutions that work for
me may not work for you
Proceed at your own risk
)