This makes builds reproducible, and matches the current MIDL behavior
(except that MIDL's string representation will vary with the build machine
timezone).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56590

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56598

This fixes Wine tests compilation with Visual Studio 10.0.
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>

This fixes Wine tests compilation with Visual Studio 10.0 CRT headers.
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>

Those parameters are not supported on multisample textures in the
first place (basically, GL mandates ARB_sampler_objects for those).

The combination COND_NP2 + ARB_texture_multisample is not expected to
happen without wined3d configuration overrides.

In the same vein as e106bbdd.

On Windows this behavior is hardware dependent. Setting instance_count
to 0 makes all our d3d versions consistent in this regard and avoids
triggering the FIXME() in wined3d:draw_primitive_immediate_mode().

Which is really what it means nowadays: resources created by the
CS. It has mostly implications WRT thread safety.

In particular, the flag doesn't mean that the resource doesn't
participate in memory accounting (that was split into
WINED3DUSAGE_VIDMEM_ACCOUNTING by
723cd0a4), nor that it isn't checked
for Reset purposes (we use parent == NULL for that).