Dave, I cut this from my original post on page one.
3DMark 03 = 4,140
<A HREF="http://service.futuremark.com/compare?2k3=897633" target="_new">http://service.futuremark.com/compare?2k3=897633</A>
<font color=red>AthlonXP 2100+/Radeon 9500Pro</font color=red>
<font color=red>Folding for Beyond 3D</font color=red>
Pretty much the same thing you just said....They are supplying a faster driver to do the job, yes,....but they are using a method of application detection stored in their drivers to do the swap. Regardless, 3DMark is calling for pixelshader 1.0, not 1.4, or 2.0. I would probably get by with calling it an optimization if they werent using a detection method to achieve it. But they are.
3DMark 03 = 4,140
<A HREF="http://service.futuremark.com/compare?2k3=897633" target="_new">http://service.futuremark.com/compare?2k3=897633</A>
<font color=red>AthlonXP 2100+/Radeon 9500Pro</font color=red>
<font color=red>Folding for Beyond 3D</font color=red>