October 2007 - Wine-Devel - list.winehq.org

Re: wined3d: Allow WINED3DFMT_R32F render targets

by Chris Robinson

On Sunday 14 October 2007 11:34:41 am Stefan Dösinger wrote: > What does a depth texture return for red, green, blue and alpha when > sampled by a pixel shader, or a vertex shader via VTF? Does it work with > fixed function fragment processing? It may be a workable solution if the > returned channels match, since it doesn't have the texture rectangle > restriction. According to the ARB spec, whenever a depth texture is used for color, it behaves like a luminance texture, so I'd assume r, g, and b would be the depth value, and alpha would be 1. I'm just not sure if you can attach a depth texture to a color attachment on fbos..

Oct. 14, 2007

Re: wined3d: Allow WINED3DFMT_R32F render targets

by Stefan Dösinger

Am Sonntag, 14. Oktober 2007 18:24:42 schrieb Chris Robinson: > With some other fixes, it may work better using pbuffers where there are > possibly R32F formats available. Unfortunately, by oversight or design, GL > has no renderable single-component formats* so we have to fall back to > R32G32B32F, which could be a bit harder on the hardware. Most apps seem to > only use it for shadow mapping though, so perhaps using a 32-bit depth > texture would work? And maybe use depth textures for R16F as well. What does a depth texture return for red, green, blue and alpha when sampled by a pixel shader, or a vertex shader via VTF? Does it work with fixed function fragment processing? It may be a workable solution if the returned channels match, since it doesn't have the texture rectangle restriction.

Oct. 14, 2007

Re: Possible WIne regression with Warcraft

by Andrey Turkin

Hi Michael, There are http://bugs.winehq.org/show_bug.cgi?id=9787 for this bug Michael Lothian wrote: > Hi > > I've noticed a problem in wine recently. When I try and join a network > game in Warcraft I can see the game but I'm unable to join it. > > These errors are printing out: > > fireburn(a)tau ~/.wine/drive_c/Program Files/Warcraft III $ wine Frozen\ > Throne.exe > ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 > ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 > err:ole:CoCreateInstance apartment not initialised > fixme:advapi:SetSecurityInfo stub > fixme:win:EnumDisplayDevicesW ((null),0,0x34f3d8,0x00000000), stub! > fixme:win:EnumDisplayDevicesW ((null),0,0x34f7b0,0x00000000), stub! > fixme:win:EnumDisplayDevicesW ((null),0,0x34f3bc,0x00000000), stub! > fireburn(a)tau ~/.wine/drive_c/Program Files/Warcraft III $ > fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (9800000c) > fixme:mswsock:AcceptEx (listen=8552, accept=8564, 0x31100e8, 0, 32, > 32, 0x34f498, 0x31100b8), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8568, 0x3110170, 0, 32, > 32, 0x34f498, 0x3110140), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8572, 0x31101f8, 0, 32, > 32, 0x34f498, 0x31101c8), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8576, 0x3110280, 0, 32, > 32, 0x34f498, 0x3110250), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8580, 0x3110308, 0, 32, > 32, 0x34f498, 0x31102d8), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8584, 0x3110390, 0, 32, > 32, 0x34f498, 0x3110360), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8588, 0x3110418, 0, 32, > 32, 0x34f498, 0x31103e8), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8592, 0x31104a0, 0, 32, > 32, 0x34f498, 0x3110470), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8596, 0x3110528, 0, 32, > 32, 0x34f498, 0x31104f8), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8600, 0x31105b0, 0, 32, > 32, 0x34f498, 0x3110580), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8604, 0x3110638, 0, 32, > 32, 0x34f498, 0x3110608), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8608, 0x31106c0, 0, 32, > 32, 0x34f498, 0x3110690), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8612, 0x3110748, 0, 32, > 32, 0x34f498, 0x3110718), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8616, 0x31107d0, 0, 32, > 32, 0x34f498, 0x31107a0), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8620, 0x3110858, 0, 32, > 32, 0x34f498, 0x3110828), not implemented > fixme:mswsock:AcceptEx (listen=8552, accept=8624, 0x31108e0, 0, 32, > 32, 0x34f498, 0x31108b0), not implemented > fixme:imm:ImmAssociateContextEx (0x30028, (nil), 16): stub > > > I'm going to try rolling back to an old version of Wine, I currently > use the latest git. > > I'll post back if it does work. > > Mike > > > >

Oct. 14, 2007

Possible WIne regression with Warcraft

by Michael Lothian

Hi I've noticed a problem in wine recently. When I try and join a network game in Warcraft I can see the game but I'm unable to join it. These errors are printing out: fireburn(a)tau ~/.wine/drive_c/Program Files/Warcraft III $ wine Frozen\ Throne.exe ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 err:ole:CoCreateInstance apartment not initialised fixme:advapi:SetSecurityInfo stub fixme:win:EnumDisplayDevicesW ((null),0,0x34f3d8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x34f7b0,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x34f3bc,0x00000000), stub! fireburn(a)tau ~/.wine/drive_c/Program Files/Warcraft III $ fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (9800000c) fixme:mswsock:AcceptEx (listen=8552, accept=8564, 0x31100e8, 0, 32, 32, 0x34f498, 0x31100b8), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8568, 0x3110170, 0, 32, 32, 0x34f498, 0x3110140), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8572, 0x31101f8, 0, 32, 32, 0x34f498, 0x31101c8), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8576, 0x3110280, 0, 32, 32, 0x34f498, 0x3110250), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8580, 0x3110308, 0, 32, 32, 0x34f498, 0x31102d8), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8584, 0x3110390, 0, 32, 32, 0x34f498, 0x3110360), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8588, 0x3110418, 0, 32, 32, 0x34f498, 0x31103e8), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8592, 0x31104a0, 0, 32, 32, 0x34f498, 0x3110470), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8596, 0x3110528, 0, 32, 32, 0x34f498, 0x31104f8), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8600, 0x31105b0, 0, 32, 32, 0x34f498, 0x3110580), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8604, 0x3110638, 0, 32, 32, 0x34f498, 0x3110608), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8608, 0x31106c0, 0, 32, 32, 0x34f498, 0x3110690), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8612, 0x3110748, 0, 32, 32, 0x34f498, 0x3110718), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8616, 0x31107d0, 0, 32, 32, 0x34f498, 0x31107a0), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8620, 0x3110858, 0, 32, 32, 0x34f498, 0x3110828), not implemented fixme:mswsock:AcceptEx (listen=8552, accept=8624, 0x31108e0, 0, 32, 32, 0x34f498, 0x31108b0), not implemented fixme:imm:ImmAssociateContextEx (0x30028, (nil), 16): stub I'm going to try rolling back to an old version of Wine, I currently use the latest git. I'll post back if it does work. Mike

Oct. 14, 2007

Re: wined3d: Allow WINED3DFMT_R32F render targets

by Chris Robinson

On Sunday 14 October 2007 02:57:35 am H. Verbeet wrote: > On 14/10/2007, Chris Robinson <chris.kcat(a)gmail.com> wrote: > > May need more work for this to be proper, but we currently allow R16F > > render targets under the same circumstances. It's also enough to make UT3 > > (which requires it) happy. > > Unless the performance problems with R32F have been fixed, this will > cause performance regressions in applications that actually try to use > it. (C&C3 for example). With some other fixes, it may work better using pbuffers where there are possibly R32F formats available. Unfortunately, by oversight or design, GL has no renderable single-component formats* so we have to fall back to R32G32B32F, which could be a bit harder on the hardware. Most apps seem to only use it for shadow mapping though, so perhaps using a 32-bit depth texture would work? And maybe use depth textures for R16F as well. * There is the NV extension which gives 16 and 32-bit Red-only renderable formats, but that has other issues, namely having to use GL_TEXTURE_RECTANGLE_NV which causes the texture's coords to behave differently. Plus it won't work on non-NV hardware.

Oct. 14, 2007

Re: USER32: fix EM_SETLIMITTEXT with zeroed args (with tests)

by Detlef Riekenberg

On Fr, 2007-10-12 at 19:42 -0500, a_villacis(a)palosanto.com wrote: You must use your real name to get a patch accepted. > + /* Maximum limits set by EM_SETLIMITTEXT vary by OS version */ > + osVersion = GetVersion(); > + if (osVersion < 0x80000000) { > + /* WinNT, Win2K, WinXP */ > + limitSingleLine = 2147483646UL; > + limitMultiLine = 4294967295UL; > + } else { > + /* Win9x, WinME */ > + limitSingleLine = 32766; > + limitMultiLine = 65535; > + } The tests should not depend on the OS-Version. Please handle both possible results in the ok() > + /* Test default limit for single-line control */ > + trace("EDIT: buffer limit for single-line\n"); > + hwEdit = create_editcontrol(ES_AUTOHSCROLL | ES_AUTOVSCROLL, 0); > + r = SendMessage(hwEdit, EM_GETLIMITTEXT, 0, 0); > + ok(r == 30000, "Incorrect default text limit, expected 30000 got > %u\n", r); > + SendMessage(hwEdit, EM_SETLIMITTEXT, 0, 0); > + r = SendMessage(hwEdit, EM_GETLIMITTEXT, 0, 0); /* Win9x+ME: 32766; WinNT: 2147483646UL */ ok( (r == 32766) || (r == 2147483646UL), "got limit %u (expected 32766 or 2147483646)\n", r); > + ok(r == limitSingleLine, "Incorrect default text limit, expected > %u got %u\n", limitSingleLine, r); Your looks like a copy&paste error ("default text limit" is wrong here). Change the multiline-test the same way. To allow an easy review, you can split your patch: one patch for the implementation and a second patch for the test. Thanks for helping wine -- By by ... Detlef

Oct. 14, 2007

Re: PulseAudio as a sound output?

by Stéphan Kochen

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 King InuYasha schreef: > I would like to suggest that eventually Wine would support PulseAudio as > a sound output natively. I am already aware of Wine supporting ESD, > which PulseAudio can use, but supporting PulseAudio natively I think > would be much better. This is something I was working on a couple of months ago. I got some beeps out of the driver I wrote, and foobar2000 was even able to play music as long as I didn't touch any of the playback controls. :) But I never got around to finishing it. And in it's current state it can't really do any serious work, afaik. If someone else wants to pick it up, I'd be happy to publicly embarrass myself and post the code here. (If I can still find it. :o) As a side note, the only other driver that seems to work right on top of PulseAudio's emulation is the OSS driver. I play Worms Armageddon using that without too many issues. - -- Stéphan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHEfaacFUq0gzqDwQRAtc5AJ98g/q/U6MMjH8FvUveUkzvpo7AtwCfULCR xH0ZiKKbmQ/gTo5vUHcAyPw= =nGSr -----END PGP SIGNATURE-----

Oct. 14, 2007

Re: [PATCH] wininet: NULL terminate url string passed to InternetCrackUrlW from InternetCrackUrlA.txt (try 3)

by Francois Gouget

On Sat, 13 Oct 2007, Nigel Liang wrote: > Hi, > > InternectCrackUrlW calls strchrW which assumes a NULL-terminated string. Will > crash without NULL termination if you upload/download for long period of time. The MSDN has this to say about InternetCrackUrlW(): dwUrlLength Size of the lpszUrl string, in TCHARs, or zero if lpszUrl is an ASCIIZ string. So if InternetCrackUrlW() assumes that lpwszUrl is zero-terminated then it is buggy. So the fix belong in InternetCrackUrlW(), not in InternetCrackUrlA(). -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ It really galls me that most of the computer power in the world is wasted on screen savers. Chris Caldwell from the GIMPS project http://www.mersenne.org/prime.htm

Oct. 14, 2007

Re: wined3d: Allow WINED3DFMT_R32F render targets

by H. Verbeet

On 14/10/2007, Chris Robinson <chris.kcat(a)gmail.com> wrote: > May need more work for this to be proper, but we currently allow R16F render > targets under the same circumstances. It's also enough to make UT3 (which > requires it) happy. > Unless the performance problems with R32F have been fixed, this will cause performance regressions in applications that actually try to use it. (C&C3 for example).

Oct. 14, 2007

Re: Wine crashes while trying to use Lexmark Network Scanback utility

by King InuYasha

Oops... Sorry... and it just uses a proprietary network protocol to grab a file from the scanner and save it... Nothing more... On 10/14/07, L. Rahyen <research(a)science.su> wrote: > > On Sunday October 14 2007 03:19, King InuYasha wrote: > > Ehh, well, I was trying to use the Lexmark Scanback Utility to operate > my > > Lexmark OptraImage 322 and it crashed after clicking the button to setup > a > > new profile.... Installed original MFC42.DLL in the Scanback program > > folder... > > > > Crash log: > > > > [InuTaisho(a)PIIMMX-GTWE4200 ScanBack]$ wine scanwiz.exe > > wine: Call from 0x40ee68 to unimplemented function MFC42.DLL.6905, > aborting > > wine: Unimplemented function MFC42.DLL.6905 called at address 0x40ee68 > > (thread 0038), starting debugger... > > Unhandled exception: unimplemented function MFC42.DLL.6905 called in > 32-bit > > code (0x602e4d4c). > > Most likely you have wrong (probably too old) version of MFC42.DLL. > You > should try newer version of this DLL. > BTW, if your Lexmark OptraImage 322 is non-ttyUSB USB device (you > don't see > it as ttyUSB in /dev/ directory) then don't even waste your time - it will > not work with Windows programs on WINE. In this case you want try Virtual > Box, QEmu or VMWare instead. WINE currently only support ttyUSB USB > devices > and all other kinds of tty devices (for example bluetooth/IRDA phones). >

Oct. 14, 2007