I upgraded to wine-1.1.31
now I get this:
Code:
Warning: program compiled against libxml 207 using older 206
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 180, std (d/m/y): 21/02/2010, dlt (d/m/y): 17/10/2010
err:ole:CoGetClassObject class {9a5ea990-3034-4d6f-9128-01f3c61022bc} not registered
err:ole:CoGetClassObject no class object {9a5ea990-3034-4d6f-9128-01f3c61022bc} could be created for context 0x1
fixme:win:EnumDisplayDevicesW ((null),0,0x448df88,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x448de84,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x448f2e4,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 1280070990 (as fourcc: NULL) WINED3DFORMAT!
fixme:d3d:getFormatDescEntry Can't find format unrecognized(1280070990) in the format lookup table
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x170a80,0x170f30): stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
and about the bug report, the existent one is a very similar situation, but the code is different. Should I report a new bug?
