Debug shuts down wmm.

[andval]

Administrative tools/event viewer gives following detail: "Faulting
application moviemk.exe version 2.1.4926.0 faulting module qedit version
6.5.2600.2180 , fault address 0x0001b2af"

Help is invited with thanks.

 

[walter]

Administrative tools/event viewer gives following detail: "Faulting
application moviemk.exe version 2.1.4926.0 faulting module qedit version
6.5.2600.2180 , fault address 0x0001b2af"

Help is invited with thanks.

Any help here?
http://www.windowsmoviemakers.net/Forums/ShowPost.aspx?PostID=188026

 

[walter]

Specifically, this looks like a/the fix;

Un-register/re-register the qedit.dll file:

1. Close Movie Maker
2. Go to "Start > Run" and enter "regsvr32 qedit.dll /s /u" (but without the
quotes) in the "Open" box and click on "OK".
3. Go to "Start > Run" and enter "regsvr32 qedit.dll /s " (but without the
quotes) in the "Open" box and click on "OK".
4. Open Movie Maker and see what happens

I'd set a restore point first, and then have a go at it.

Good luck
===========

 

[andval]

Many thanks for your willingness to help. Tried out your suggestion but WMM
soon after opening announces that it has a problem and has to close. A debug
facility is given which when activated forces WMM into a non responsive state
and has to be shut down via task manager.

 

[walter]

Many thanks for your willingness to help. Tried out your suggestion
but WMM soon after opening announces that it has a problem and has to
close. A debug facility is given which when activated forces WMM into
a non responsive state and has to be shut down via task manager.

Did you type the commands EXACTLY as written including the spaces and
omitting the quotes?

regsvr32 qedit.dll /s /u

[Note the spaces *after* regsvr32, qedit.dll, and /s]

If you typed that correctly you should have received a "reply" from the
system that the .dll was succesfully *un*registered. Did you?

regsvr32 qedit.dll /s

[Note the spaces after regserv32 and qedit.dll]

If you typed *that* correctly you should have received a "reply" from the
system that the .dll in question was succesfully registered. Did you?

If so, I'm lost. IF not, try again.

Good luck

 

[andval]

I religiously and meticulously followed your suggestions but to no avail on
both issues to unregister and re-register. Many thanks for your support and
interest.
I am prepared to try alternatives if you would have any. I am fast coming to
the conclusion that the movie maker was brilliantly conceived but perhaps
badly put together.

--
SkaliontaAnd

Many thanks for your willingness to help. Tried out your suggestion
but WMM soon after opening announces that it has a problem and has to
close. A debug facility is given which when activated forces WMM into
a non responsive state and has to be shut down via task manager.

Did you type the commands EXACTLY as written including the spaces and
omitting the quotes?

regsvr32 qedit.dll /s /u

[Note the spaces *after* regsvr32, qedit.dll, and /s]

If you typed that correctly you should have received a "reply" from the
system that the .dll was succesfully *un*registered. Did you?

regsvr32 qedit.dll /s

[Note the spaces after regserv32 and qedit.dll]

If you typed *that* correctly you should have received a "reply" from the
system that the .dll in question was succesfully registered. Did you?

If so, I'm lost. IF not, try again.

Good luck

 

[andval]

Walter further investigation on unregistering and re-registrering revealed
that both were indeed happening but the system did not inform at all!
After unregistering I tried to run wmm and this time debug was not alerted.
However, wmm was useless as it couldn't edit at all. On re-registration of
qedit.dll wmm was back to its usual difficulties with debug. Can you perhaps
explain why un- and re-registration are not announced by the system? Does
this reveal another anomaly??
I feel I must thank you again for sharing this quest with me.
--
SkaliontaAnd

I religiously and meticulously followed your suggestions but to no avail on
both issues to unregister and re-register. Many thanks for your support and
interest.
I am prepared to try alternatives if you would have any. I am fast coming to
the conclusion that the movie maker was brilliantly conceived but perhaps
badly put together.

--
SkaliontaAnd

Many thanks for your willingness to help. Tried out your suggestion
but WMM soon after opening announces that it has a problem and has to
close. A debug facility is given which when activated forces WMM into
a non responsive state and has to be shut down via task manager.

Did you type the commands EXACTLY as written including the spaces and
omitting the quotes?

regsvr32 qedit.dll /s /u

[Note the spaces *after* regsvr32, qedit.dll, and /s]

If you typed that correctly you should have received a "reply" from the
system that the .dll was succesfully *un*registered. Did you?

regsvr32 qedit.dll /s

[Note the spaces after regserv32 and qedit.dll]

If you typed *that* correctly you should have received a "reply" from the
system that the .dll in question was succesfully registered. Did you?

If so, I'm lost. IF not, try again.

Good luck

 

[walter]

andval wrote:

Try here on PapaJohn's site.

http://www.papajohn.org/MM2-Modules.html

Scroll down to qedit and have a read.

Walter further investigation on unregistering and re-registrering
revealed that both were indeed happening but the system did not
inform at all!
After unregistering I tried to run wmm and this time debug was not
alerted. However, wmm was useless as it couldn't edit at all. On
re-registration of qedit.dll wmm was back to its usual difficulties
with debug. Can you perhaps explain why un- and re-registration are
not announced by the system? Does this reveal another anomaly??
I feel I must thank you again for sharing this quest with me.

I religiously and meticulously followed your suggestions but to no
avail on both issues to unregister and re-register. Many thanks for
your support and interest.
I am prepared to try alternatives if you would have any. I am fast
coming to the conclusion that the movie maker was brilliantly
conceived but perhaps badly put together.

--
SkaliontaAnd

andval wrote:

Many thanks for your willingness to help. Tried out your suggestion
but WMM soon after opening announces that it has a problem and has
to close. A debug facility is given which when activated forces
WMM into a non responsive state and has to be shut down via task
manager.

Did you type the commands EXACTLY as written including the spaces
and omitting the quotes?

regsvr32 qedit.dll /s /u

[Note the spaces *after* regsvr32, qedit.dll, and /s]

If you typed that correctly you should have received a "reply" from
the system that the .dll was succesfully *un*registered. Did you?

regsvr32 qedit.dll /s

[Note the spaces after regserv32 and qedit.dll]

If you typed *that* correctly you should have received a "reply"
from the system that the .dll in question was succesfully
registered. Did you?

If so, I'm lost. IF not, try again.

Good luck

 

[Liam]

Thank you Walter, I had a similar problem. Using task manager I opened up cmd
prompt and typed in 'regsvr32 qedit.dll /s /u' and that seems to have done
the trick!