- Wine-Devel - list.winehq.org

Possible fun project/todo list item?
by Mike Hearn Sept. 6, 2004

Sept. 6, 2004

The OpenSSL library we use in wininet/netconnection.c is a very unstable library, with somewhat odd licensing as well. By unstable I'm talking about the interfaces it exports: unfortunately they break backwards compatibility very frequently with the result that a build of Wine compiled on one system may bail out when using SSL on another, as the soname/abi of OpenSSL it's looking for has changed *yet again*. This also means that some distros deliberately ship older versions and just backport security fixes, as upgrading OpenSSL to newer versions is quite painful. Fedora at least does this. If anybody is looking for work to do then, addressing this problem may be useful. Probably the best way forward is to talk to the GnuTLS people (http://www.gnu.org/software/gnutls/gnutls.html) and see if you can get written confirmation from them that they have a strong commitment to binary compatibility (at least, more than OpenSSL does). It also seems to be a fairly stable project: the new maintainer is more focussed on portability enhancements and a slow release cycle than making huge changes to the code. If so, it might be worth porting wininet over to GnuTLS, or alternatively, rather than remove the OpenSSL code just add code to use GnuTLS and then fall back to OpenSSL if it cannot be found (or vice-versa). One interesting thing about GnuTLS is that it has some OpenSSL compatibility code, but from a look at their website it seems that this is GPLd. Maybe we could get an exemption from them. The downside is that while OpenSSL is frequently going to not be found as it's the wrong version, GnuTLS is also not widely installed by default so it might not get us much in the short term. The good news is that Gaim packages are often built against it, so in any modern distro that packages Gaim (which is a very popular chat client) in its repositories, there's a good chance GnuTLS is packaged as well. thanks -mike

5 11

Battlefield 1942 d3d8 crash
by Robert Reif Sept. 6, 2004

Sept. 6, 2004

I get the following crash when running the Battlefield 1942 single player demo from http://www.3dgamers.com/games/battlefield1942/ fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40361cd8)->(00000000,00000008) trace:d3d:Direct3DCreate8 SDKVersion = dc, Created Direct3D object at 0x40362218 fixme:d3d_caps:IDirect3D8Impl_FillGLCaps found GL_VERSION ("1.5.1 NVIDIA 61.06")->(0x003d17da) fixme:d3d_caps:IDirect3D8Impl_FillGLCaps found GL_RENDERER ("GeForce FX 5200/AGP")->(0x0250) trace:d3d:IDirect3D8Impl_CreateDevice (0x40362218)->(Adptr:0, DevType: 1, FocusHwnd: 0x10022, BehFlags: 80, PresParms: 0x41fc40b8, RetDevInt: 0x41fc409c) trace:d3d:IDirect3D8Impl_AddRef (0x40362218) : AddRef from 1 trace:d3d:IDirect3DDeviceImpl_CreateStateBlock (0x40362498) : Type(1) trace:d3d:IDirect3D8Impl_CreateDevice (0x40362218)->(DepthStencil:(75,D3DFMT_D24S8), BackBufferFormat:(22,D3DFMT_X8R8G8B8)) trace:d3d:IDirect3D8Impl_CreateDevice Context created (HWND=0x10022, glContext=0x43044054, Window=41943042, VisInfo=0x43043de0) fixme:d3d:IDirect3DDevice8Impl_Reset (0x40362498) : stub trace:d3d:IDirect3DDevice8Impl_GetBackBuffer (0x40362498) : BackBuf 0 Type 0 returning (nil) wine: Unhandled exception (thread 0009), starting debugger... fixme:console:SetConsoleCtrlHandler (0x4074a8f8,1) - no error checking or testing yet WineDbg starting on pid 0x8 Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x40df748b). In 32 bit mode. 0x40df748b IDirect3DSurface8Impl_AddRef [/home/wine/wine/dlls/d3d8/surface.c:59] in d3d8: movl 0x4(%esi),%eax 59 return ++(This->ref); 59 return ++(This->ref); Wine-dbg>>bt Backtrace: =>1 0x40df748b IDirect3DSurface8Impl_AddRef+0x23(iface=0x0) [/home/wine/wine/dlls/d3d8/surface.c:59] in d3d8 (0x4081e84c) 2 0x40dd7216 IDirect3DDevice8Impl_GetBackBuffer+0x76(iface=0x40362498, BackBuffer=0x0, Type=0x0, ppBackBuffer=0x41fc40a0) [/home/wine/wine/dlls/d3d8/device.c:577] in d3d8 (0x4081e864) 3 0x00848ec0 (0x00000000) Wine-dbg>

1 0

Re: Wine and industrial communication like OPC
by Rickard Svensson Sept. 6, 2004

Sept. 6, 2004

Thank you, for all your answers! We have one employee who has worked a lot with Windows, and same with OPC. So I can provide same answers. * Mike Hearn - OPC is mostly used for data collection, and to a lesser degree to control industrial machines. * Juan Lang AND Robert Shearman - OPC doesn't use named pipes. OPC uses Dcom over TCP. * Mike Hearn - OPC doesn't need any new Windows (2000, XP) parts, and should work on Win 98 with the added Dcom support (not tested). * Mike Hearn - Price of OPC for Linux was when I looked at it for about a year ago 3000 - 4000$ per project you used their API in. And it only supported one of the OPC versions. Now I guess that the prices has been going down... Now I also got some questions from your answers: * Did I understand correctly. Wine doesn't have a built in support for DCom, to be abel to use Dcom I have to add the DCom support from Windows 98 to the Linux system? And the problem with that is the MS License, it stops me from distribute those XXX.dll with a Linux product (hardware and software in this case.) * We want to make a OPC server, because other computers want to get information from our system. Is there a problem in make a DCOM server, is it the "no user can acsas port under 1024 on a Linux system" problem. * What I have heard I thought DCom uset RPC??? But Juan Lang wrote that Wine doesn't have support for RPC /Rickard -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

2 1

Re: InternetReadFile, FTP and partial buffers
by Uwe Bonnes Sept. 6, 2004

Sept. 6, 2004

>>>>> "Krzysztof" == Krzysztof Foltman <kfoltman(a)portal.onet.pl> writes: Krzysztof> Hi All, In the original WinInet FTP implementation, Krzysztof> InternetReadFile always returns complete buffers, except for Krzysztof> the last block. Some programs (probably ill-behaving ones, Krzysztof> but I wouldn't bet my head on it) rely on that fact, and stop Krzysztof> retrieving the file after the first incomplete block. I met the same problem for the HTTP implementation. The MSG_WAITALL flag sent to recv should always retrieve buffers of the requested size, if possible. Can you please try your problem with the MSG_WAITALL flag instead your patch? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- Index: wine/dlls/wininet/internet.c =================================================================== RCS file: /home/wine/wine/dlls/wininet/internet.c,v retrieving revision 1.95 diff -u -w -r1.95 internet.c --- wine/dlls/wininet/internet.c 19 Aug 2004 19:02:17 -0000 1.95 +++ wine/dlls/wininet/internet.c 4 Sep 2004 22:09:59 -0000 @@ -1632,7 +1632,7 @@ { case WH_HHTTPREQ: if (!NETCON_recv(&((LPWININETHTTPREQW)lpwh)->netConnection, lpBuffer, - dwNumOfBytesToRead, 0, (int *)dwNumOfBytesRead)) + dwNumOfBytesToRead, MSG_WAITALL, (int *)dwNumOfBytesRead)) { *dwNumOfBytesRead = 0; retval = TRUE; /* Under windows, it seems to return 0 even if nothing was read... */

1 0

Re: Wine and industrial communication like OPC
by Juan Lang Sept. 6, 2004

Sept. 6, 2004

Rickard wrote: > * Juan Lang AND Robert Shearman - OPC doesn't use > named pipes. OPC uses Dcom over TCP. > * Mike Hearn - OPC doesn't need any new Windows > (2000, XP) parts, and should work on Win 98 with the > added Dcom support (not tested). Cool! This has a chance of working then. > * Did I understand correctly. Wine doesn't have a > built in support for DCom, to be abel to use Dcom > I have to add the DCom support from Windows 98 to > the Linux system? Yes, that appears to be true. Wine's rpcrt4.dll only works between programs running in the same Wine instance. > * We want to make a OPC server, because other > computers want to get information from our system. > Is there a problem in make a DCOM server, is it the > "no user can acsas port under 1024 on a Linux > system" problem. It's a problem for lots of reasons. They add up to this: this is unimplemented in Wine, and probably won't be implemented any time soon. > * What I have heard I thought DCom uset RPC??? But > Juan Lang wrote that Wine doesn't have support for > RPC Did I? I certainly didn't mean it. But you'd need to install the DCOM98 update to have any chance of success at it for now, at least if I read the code right. --Juan __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

1 0

shell32 unicodefy question
by Vitaliy Margolen Sept. 5, 2004

Sept. 5, 2004

First of all I would like to check if there are any one working on this. Second Q: Some methods of IFSHelper interface defined as taking LPCSTR params. Is this right? I was unable to find any information in regards to this. And because this is exported interface I don't want to brake something that is already working. -- Best regards, Vitaliy

1 0

Re: Compile fix forinclude files from linux 2.6.7
by Marcus Meissner Sept. 5, 2004

Sept. 5, 2004

On Sun, Sep 05, 2004 at 05:38:03PM +0200, Rein Klazes wrote: > Hi, > > Fix for bugzilla bug#2354, compile failure on Slackware 10. > > The include <linux/fd.h> uses since Linux 2.6.7 a macro defined in > <linux/compiler.h>. Compiler.h is new in linux 2.4.4, old but not very > old, so I added an autoconf check for such systems. > > Need to run autoheader & autoconf after applying. No, if it is missing __user, just #define __user at the beginning of the file. Or try not to use linux kernel headers at all. Ciao, Marcus

2 1

Re: Critical Sections Documentation Update
by Hans Leidekker Sept. 5, 2004

Sept. 5, 2004

On Sunday 5 September 2004 13:26, Robert Shearman wrote: > - * Initialise a new RTL_CRITICAL_SECTION. > + * Initializes a new critical section. I'm afraid this critical section from your critical section patch will upset people in the critics' section ;-) -Hans

1 0

Re: weird ?clipping? errors
by Filip Navara Sept. 5, 2004

Sept. 5, 2004

Filip Navara wrote: > James Hawkins wrote: > >>> If the error disappears, then you're dealing with a bug in Wine's >>> comctl32.dll. >>> >> >> >> I used native comctl32.dll and both of the errors disappeared, so I >> will take your advice and search around in comctl32. >> >> > It's regression in dlls/comctl32/propsheet.c that happend between > revision 1.105 and 1.112. To be more specific, it's this patch: Mike McCormack <mike(a)codeweavers.com <mailto:mike(a)codeweavers.com>> Adjust the tab contents to fix the propsheet between PSM_KILLACTIVE and PSM_SETACTIVE. Regards, Fi;lip

3 3

fixme:msi:MsiLocateComponentA installing dotnetredist.exe
by Dan Kegel Sept. 5, 2004

Sept. 5, 2004

I installed wine-20040813 from source, then tried installing http://msdn.microsoft.com/visualc/vctoolkit2003/ (I think this gets a ways further than it did last time I tried it, yay.) Now it fails with the error I: Error installing Microsoft(R) .NET Framework. http://download.microsoft.com/download/e/b/2/eb247c2a-e6b3-4694-98a2-b27111… On the console, I saw only the four warnings/errors: fixme:msi:MsiInstallProductW L"/iH:\\IS3123.tmp\\netfx.msi" L"" fixme:msi:MSI_OpenDatabaseW open failed r = 80004005! Installation of /iH:\IS3123.tmp\netfx.msi () failed. err:dc:DCE_FreeWindowDCE [0x10026] GetDC() without ReleaseDC()! So I downloaded dotnetredist.exe and ran that by hand, and then ran the executable that unpacked. This failed with fixme:msi:MsiLocateComponentA "{A1B926EF-7FD9-11D2-A429-00A0C9E80AFB}" 0x4051ec84 00000105 fixme:msi:MsiLocateComponentA "{173A6EB3-6403-11D4-A53F-0090278A1BB8}" 0x4051ec84 00000105 That function, at least in my tree, is just a pseudostub: INSTALLSTATE WINAPI MsiLocateComponentA(LPCSTR szComponent, LPSTR lpPathBuf, DWORD *pcchBuf) { FIXME("%s %p %08lx\n", debugstr_a(szComponent), lpPathBuf, *pcchBuf); return INSTALLSTATE_UNKNOWN; } Sooo... what's the best way around this? Anyone tackle this before? Thanks, Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

3 2