Force re-install of windows movie maker, other stuff?

[Guest]

Well something got corrupted this morning. I assume its one of the .dll's in
the video common code. All of a sudden, I can't open new videos (.mpg) in
movie maker, nor can I play or export a video with quicktime pro.

In the case of movie maker, simply clicking on "import video" causes an
immediate terminate of the program. No "pick file window", the main window
just closes, and thats that. In the case of Quicktime, I get a more
"graceful" exit, it pops up a "buffer overflow forces exit" and then it goes
away.

I was able to do a forced re-install of quicktime, and directX. Can't find
a way to do likewise for windows movie maker. (apparently it came as part of
SP-2).

Norton claims the machine is free of viri, and all the mpg's and .mov's I
have been playing with came from my very own camera, so its a touch unlikely
that I got passed an infected video file. I assume a bit got flipped on the
disk, hence the forced re-instals, and the desire to do more.

Anything else I should be trying to update? Any way to capture more
information about where things are faceplanting?

Anyone know where I can get my paws on an install for movie maker? The only
one on the ms download center is a special update for Vista machines.

 

[Guest]

Seems MM came with xp,if that's the case,install xp cd,exit the info
page,go to
run,type:cmd In cmd type:Sfc /Scannow Type:CHKDSK C: /F When its thru,
Agree,type:EXIT Restart PC Remove xp cd.I would run 1st,then back in xp,
simply install xp SP2 cd,reinstall A reinstall of SP2 wont/shouldnt remove
anything.

 

[Guest]

Thanks for the info. Of course this happens on a machine that didn't ship
with media. Will try to get the SP standalone download, and re-install that.
What would help is something that would cough up a backtrace, that
identifies which DLL the fault occurred in. Any tricks there?

(I am spoiled by lisp systems, where should such a fault happen, a single
key chord would bring you to the editor, with the source of the offending
function opened, and the cursor on the line of code that fired the trap)

 

[Peter Foldes]

Andrew go away. You are causing more harm than good. You are giving very bad advice and help. No need to touch the OS and the SP

 

[Peter Foldes]

Try and delete the Movie maker from Add\Remove and then re-install

http://www.microsoft.com/windowsxp/downloads/updates/moviemaker2.mspx