"Bernard" <> wrote in message
news:6F80884C-26A7-4FA2-8603-...
> Well thanks for the hint Robert, but if I look in the .inf file in that
> directory it mentions version 2.0.0.3xxx rather than 2.1.4026.0 so I'm not
> totally convinced this is going to give me the latest version. My second
> machine has the 2.1.4026.0 version.
I also have a moviemk.inf under %windir%\ServicePackFiles\i386\
Perhaps you could try the same idea with it?
BTW have you seen this (from another search):
http://www.microsoft.com/windowsxp/u...reate/faq.mspx
(Live Search for
"Movie Maker" AND XP AND (install OR installed OR installing) site:support.microsoft.com
)
Notice that there is a Windows Movie Maker newsgroup and other
information resources? Perhaps you would find a solution in them.
The FAQ also mentions a problem with completing the install of
Movie Maker under XP + MUI. Apparently there are some extra
components available at the download center.
Hmm... that newsgroup seems to have moved on from this issue
(judging by searching on the web interface) but Google Groups
shows that it was once known to it. E.g. here's an article which seems
to validate my suggestion about using the ServicePackFiles in a
reinstall attempt. Link courtesy of John Inzer.
http://blogs.msdn.com/deanro/archive...18/355050.aspx
(Google Groups search for
XP "movie maker" (install OR installing OR installed) group:microsoft.*
)
On a different tack perhaps you should try diagnosing why the package
did not install with your XPsp2 install. The above FAQ implies that it should.
So then what I would do is search for files which reference moviemk.
Unfortunately you can't do this with Search Companion since it won't
search all the files when you ask it to do a text search. Also, it won't
find any files which have the equivalent strings in doublebyte characters
(such as Unicode). Therefore, I use findstr /s /m /i instead.
Findstr allows us to specify strings using regular expressions so it can
also help us work around the doublebyte string problem too. E.g. interlace
the characters in the word you want to find with the period, "match any character"
pattern. Fortunately, a guess of where the string might be found works:
findstr /s /m /i "moviemk" *.log
starting from %windir% returned two files:
setupapi.log
svcpack.log
They aren't quite as useful as I would have hoped.
I think the most use you might be able to get from them
is compare the ones from your two systems, if one
installed Movie Maker correctly and the other didn't.
HTH
Robert
---
> --
> Bernard
>
>
> "Robert Aldwinckle" wrote:
>
>> "Bernard" <> wrote in message
>> news:5A348586-D8EF-4A14-97EF-...
>> >I have exactly the same problem - 2 machines both with SP2 installed and both
>> > Genuine. Each one came with XP pre-installed by IBM/Lenovo - one has MM2 and
>> > one does not. Both machines use Auto Update and are up to date in terms of
>> > Microsoft mandatory and optional updates. I really would appreciate some help
>> > from Microsoft on how to get MM2 for the second machine.
>>
>>
>> Try a search?
>>
>> <title>Movie Maker does not upgrade to Movie Maker 2 in Windows XP</title>
>> http://support.microsoft.com/kb/825229
>>
>> (Live Search for:
>> intitle:movie intitle:maker intitle:XP site:support.microsoft.com
>> )
>>
>>
>> HTH
>>
>> Robert Aldwinckle
....
Similar Threads
Linear Mode
