B
bk
Does this show on everyone's update all the time?
Is the update not working?
Thanks
Is the update not working?
Thanks
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
T
Tedd Riggs
I have never gotten that one, it was fixed in a fair number of SP's for the
various OS's as this is a DirectX update that could be in almost any version
of Windows. What version are you running ?
Here is the write-up on what the patch is for
http://support.microsoft.com/default.aspx?scid=kb;en-us;819696
various OS's as this is a DirectX update that could be in almost any version
of Windows. What version are you running ?
Here is the write-up on what the patch is for
http://support.microsoft.com/default.aspx?scid=kb;en-us;819696
B
bk
I am on Win98.
Thanks
Thanks
Tedd Riggs said:I have never gotten that one, it was fixed in a fair number of SP's for the
various OS's as this is a DirectX update that could be in almost any version
of Windows. What version are you running ?
Here is the write-up on what the patch is for
http://support.microsoft.com/default.aspx?scid=kb;en-us;819696
R
Robert Aldwinckle
What version are you running ?
Notice that the article gives a table, showing that besides the Windows
version the current version of DirectX is significant.
It also tells you to use the dxdiag tool to discover that information.
You could also use that tool after installing the patch to find out how much
was changed and how much is left to do.
Other clues could be obtained by doing a search of your harddrive
for any diagnostic files (e.g. patterns such as *.log) which contain
819696
BTW this is off-topic for this newsgroup. A better choice would be:
or perhaps
(FWIW I don't use that last one. I just found it by pressing Ctrl-w
in OE and typing public.directx .)
In any case try using Google Groups before posting again so you can
at least refer to other variations of this problem that there have been
if you don't find a solution that way for yours.
Good luck
Robert Aldwinckle
---
....
I am on Win98.
Notice that the article gives a table, showing that besides the Windows
version the current version of DirectX is significant.
It also tells you to use the dxdiag tool to discover that information.
You could also use that tool after installing the patch to find out how much
was changed and how much is left to do.
Other clues could be obtained by doing a search of your harddrive
for any diagnostic files (e.g. patterns such as *.log) which contain
819696
BTW this is off-topic for this newsgroup. A better choice would be:
or perhaps
(FWIW I don't use that last one. I just found it by pressing Ctrl-w
in OE and typing public.directx .)
In any case try using Google Groups before posting again so you can
at least refer to other variations of this problem that there have been
if you don't find a solution that way for yours.
Thanks
Good luck
Robert Aldwinckle
---
....
....
A
Anonymous
Robert Aldwinckle said:Notice that the article gives a table, showing that besides the Windows
version the current version of DirectX is significant.
It also tells you to use the dxdiag tool to discover that information.
You could also use that tool after installing the patch to find out how much
was changed and how much is left to do.
Other clues could be obtained by doing a search of your harddrive
for any diagnostic files (e.g. patterns such as *.log) which contain
819696
BTW this is off-topic for this newsgroup. A better choice would be:
or perhaps
(FWIW I don't use that last one. I just found it by pressing Ctrl-w
in OE and typing public.directx .)
In any case try using Google Groups before posting again so you can
at least refer to other variations of this problem that there have been
if you don't find a solution that way for yours.
Good luck
Robert Aldwinckle
---
...
...
See Microsoft's solution here:
http://support.microsoft.com/?kbid=829778