(my 2nd reply!)

From that Doc you referenced, "Your computer may not...
DirectX...MS05-050...", and that table it gives a page down: I do fall into
that first category.

The line following the table: "After you identify the name of the yadda..."
go to the MS05-050 asp web catelog area and find it. I'm sure what that is
saying exactly.

I went there, and found a command line version of the update in question
(KB907406, Dx9, W2K). This file named: Windows2000-KB904706-DX9-x86-ENU.exe,
by the way.

My confusion is the "fourth" column in that doc above "Name of the correct
update that must be installed" is the column title. and I read "Microsoft
DirectX 9.0, 9.0a, 9.0b, 9.0c when they are installed on Windows 2000 Service
Pack 4".

The latter I already have (I believe), 9.0c. Or is it saying a new (re)
install of the appropriate DX 9's ? Ugh.

I'll keep that command line update for now.
This is all kind of weird when there isn't really any problem (that I know
of)!

The tools you mention, not sure about those. FileMon, "Process Explorer from
SysInternals". (Remember Win 2000...)

Thanks again
Michael

"Robert Aldwinckle" wrote:

> "Michael W" <michaelj_SPAMME_waltrip@hot_NOT_mail.com> wrote in message
> news:A0FFA35C-B36F-4B7C-9883-28B0CB4F88C5@microsoft.com
> ....
> > Hello,
> > I have had an error with K904706 since it came out in Oct. Had 10 or so
> > updates that were wanted to do, and from Win Upd web, let them all installl.
> >
> > All downloaded fine, by during install. when 904706 (DirectX 9. Win 2000
> > mine says), it quickly advances 50% and stops. Since then, have managed to
> > remove the download for this (no uninstall appears), and let it attempt all
> > by itself. Same result.
> ....
> > I've tried various things,
> ....
>
>
> Have you seen this article
>
> <title>Your computer may not be updated when you install one of the DirectX
> security updates that is associated with security bulletin MS05-050
> on a computer running Windows Server 2003, Windows XP, or Windows 2000</title>
>
> http://support.microsoft.com/default...b;en-us;909596
>
> (MSKB search for
> K904706
> )
>
>
> or more particularly done the diagnosis it suggests?
> What are the results?
>
> Notice that your log does not include the most important detail
> or at least is very vague about the current version of quartz.dll
>
> > 0.321: FileVersion of C:\WINNT\system32\quartz.dll is Greater or Equal To 6.5.1.900
>
>
> The article ends with a link to the relevant TechNet Security Bulletin.
> There you can find instructions for doing a command line invocation
> which apparently allows you to specify a /verbose option.
> That might allow you to get more insight on those "FileInUse" messages.
> BTW I would make sure that all other programs are closed before
> trying an install, in particular Windows Media Player which I think is the
> only one which should be using quartz.dll.
>
> If you have stopped Media Player and still get that particular symptom
> in your log with no apparent explanation I would try using tasklist
> (or Process Explorer from SysInternals) to try to understand why it
> would be showing as in use (assuming the message means what it implies.)
> Other tools from SysInternals could be really helpful here too.
> E.g. both FileMon and RegMon could add insight.
> Tip: when FileMon includes writes to the install log you can use
> the length of the writes to infer which messages are being written
> and thus correlate other file and registry accesses to supplement
> what the log is showing. The correlation with a RegMon trace is
> helped also by using the options Clock Time and Show Milleseconds
> on both tools.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>