(In reply to comment #9)
> 1) Wine shouldn't use ARB_depth_clamp, but instead it should use an
> extension that exposes CLIP_DISABLE as defined by D3D9 to the user. The
> problem is such an extension doesn't exist.
> 
If ARB_depth_clamp can't be made to work on r300g, that would be my preferred
solution. There may even be some value in that for a hypothetical D3D or
wined3d state tracker, although I still don't see that happening in the short
term, for various reasons.