Eusti
2002-07-17, 17:21:18
Meldung von: http://www.theinquirer.net/?article=4474
__________
Microsoft admits Win XP DirectX problems on AMD platforms
AMD-specific code a right mess
__________
MICROSOFT HAS IDENTIFIED a problem with running DirectX 8.1 on AMD processor-based systems. Some DirectX 8.1 programs may simply stop working on AMD PCs, says the Vole, and it has come up with a patch to fix the problem.
The problem applies to DirectX programs running under Windows XP on AMD platforms. Intel processors are unaffected, the posting on Microsoft's support site here says.
According to the posting, "the DrawIndexedPrimitive function stops working without displaying an error or debug message". Microsoft fesses up and says the error occurs because of "a code error in the AMD-specific optimized code. This code error may lead to heap corruption," it says.
So Microsoft, not AMD, messed up, in case you were wondering.
To fix the problem you'll have to call Microsoft.
__________
Microsoft admits Win XP DirectX problems on AMD platforms
AMD-specific code a right mess
__________
MICROSOFT HAS IDENTIFIED a problem with running DirectX 8.1 on AMD processor-based systems. Some DirectX 8.1 programs may simply stop working on AMD PCs, says the Vole, and it has come up with a patch to fix the problem.
The problem applies to DirectX programs running under Windows XP on AMD platforms. Intel processors are unaffected, the posting on Microsoft's support site here says.
According to the posting, "the DrawIndexedPrimitive function stops working without displaying an error or debug message". Microsoft fesses up and says the error occurs because of "a code error in the AMD-specific optimized code. This code error may lead to heap corruption," it says.
So Microsoft, not AMD, messed up, in case you were wondering.
To fix the problem you'll have to call Microsoft.