- Wine-devel - list.winehq.org

Re: ANSI_CHARSET
by Jeff Smith 03 Sep '02

03 Sep '02

>From: Marcus Meissner <meissner(a)suse.de> >To: Francois Gouget <fgouget(a)free.fr> >CC: Jeff Smith <whydoubt(a)hotmail.com>, wine-devel(a)winehq.com >Subject: Re: ANSI_CHARSET >Date: Tue, 3 Sep 2002 09:02:20 +0200 >MIME-Version: 1.0 >Received: from Cantor.suse.de ([213.95.15.193]) by >mc4-f10.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Tue, 3 Sep >2002 00:02:24 -0700 >Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201])by >Cantor.suse.de (Postfix) with ESMTPid A471C142DA; Tue, 3 Sep 2002 09:02:20 >+0200 (MEST) >Message-ID: <20020903090220.C30897(a)suse.de> >References: <F155awoeMTVNcBklFJN00020b3e(a)hotmail.com> ><Pine.LNX.4.43.0209022354330.31721-100000(a)amboise.dolphin> >In-Reply-To: <Pine.LNX.4.43.0209022354330.31721-100000(a)amboise.dolphin> >User-Agent: Mutt/1.3.22.1i >Return-Path: meissner(a)suse.de >X-OriginalArrivalTime: 03 Sep 2002 07:02:24.0593 (UTC) >FILETIME=[DB273C10:01C25317] > >On Mon, Sep 02, 2002 at 11:56:49PM -0700, Francois Gouget wrote: > > On Mon, 2 Sep 2002, Jeff Smith wrote: > > > > > ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in >include/wingdi.h), > > > but I have some doubts about the details. > >They are already defined there: > >#define ANSI_CHARSET (BYTE)0 /* CP1252, ansi-0, iso8859-{1,15} >*/ >#define DEFAULT_CHARSET (BYTE)1 >#define SYMBOL_CHARSET (BYTE)2 > >Why arent they in your wingdi.h file? > >Ciao, Marcus _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

1 0

Ignoring exceptions
by Fabian Cenedese 03 Sep '02

03 Sep '02

Hi I still try to find the reason for the exception in my app while loading an ocx. But I don't seem to make much progress. Here is a new trace: 08153fd8:Call kernel32.lstrlenA(40791300 "") ret=5f587c81 08153fd8:Ret kernel32.lstrlenA() retval=00000000 ret=5f587c81 08153fd8:Call kernel32.MultiByteToWideChar(00000000,00000000,40791300 "",ffffffff,405c45fc,00000001) ret=5f5010de 08153fd8:Ret kernel32.MultiByteToWideChar() retval=00000001 ret=5f5010de 08153fd8:Call kernel32.GetProcAddress(65340000,00000002) ret=5f54db21 08153fd8:Ret kernel32.GetProcAddress() retval=65341408 ret=5f54db21 08153fd8:Call kernel32.IsBadReadPtr(405c469c,00000020) ret=40c27bce 08153fd8:Ret kernel32.IsBadReadPtr() retval=00000000 ret=40c27bce 08153fd8:Call kernel32.IsBadReadPtr(405c467c,00000004) ret=40c27bce 08153fd8:Ret kernel32.IsBadReadPtr() retval=00000000 ret=40c27bce 08153fd8:Call ntdll.RtlSizeHeap(40360000,00000000,403c0850) ret=65f019c3 trace:heap:RtlSizeHeap (40360000,00000002,403c0850): returning 00000020 08153fd8:Ret ntdll.RtlSizeHeap() retval=00000020 ret=65f019c3 08153fd8:Call kernel32.IsBadReadPtr(41986f50,00000020) ret=10214168 08153fd8:Ret kernel32.IsBadReadPtr() retval=00000000 ret=10214168 08153fd8:Call kernel32.IsBadWritePtr(41986f50,00000020) ret=10214180 08153fd8:Ret kernel32.IsBadWritePtr() retval=00000000 ret=10214180 08153fd8:Call kernel32.OutputDebugStringA(405c2154 "Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003).\r\n") ret=10215139 08073540:Ret kernel32.ContinueDebugEvent() retval=00000001 ret=404c3ee2 08073540:Call kernel32.WaitForDebugEvent(40615e0c,ffffffff) ret=404c3ef8 08073540:Ret kernel32.WaitForDebugEvent() retval=00000001 ret=404c3ef8 08073540:Call kernel32.ReadProcessMemory(0000002c,405c2154,40615cf4,00000100,40615cc4) ret=404c2e27 08073540:Ret kernel32.ReadProcessMemory() retval=00000001 ret=404c2e27 08073540:Call kernel32.ContinueDebugEvent(08153f20,08153fd8,00010002) ret=404c3ee2 08153fd8:Ret kernel32.OutputDebugStringA() retval=00000000 ret=10215139 08153fd8:Call kernel32.RaiseException(e06d7363,00000001,00000003,405c45b4) ret=10209499 It used to stop right after the RtlSizeHeap function. I don't know why it's later now, but leads me to thinking that it's just accidentally at this place and the reason is much earlier. Anyway, I now have a new message stating an exception (DISP_E_MEMBERNOTFOUND). After looking into MSDN to find out what it means I found this little article: <MSDN> Debugging Output You Can Safely Ignore -- snip -- Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003). First-chance exception in TSTCON32.EXE (MFCO42D.DLL): 0xE06D7363: Microsoft C++ Exception. -- snip -- The last two lines are notification that an exception has been thrown because the test container didn't provide a Color property to be read. This is okay, because we've provided a default value for the property. You won't get this error if you use a container that provides the property, such as a Visual Basic application. In Visual C++ version 4.1, the only line I got was a warning about the exception for properties that couldn't be loaded from the container. First-chance exception in TSTCON32.EXE (MFC40.DLL): 0xE06D7363: Microsoft C++ Exception. Depending on how your container handles threads, you may also get occasional messages about threads exiting. You don't need to worry about these, either. </MSDN> It seems to me that it's probably this exception that stops my app. Somehow it is better handled in Windows than in Wine as my app runs in Windows. I also tried a pure VB-app with just my ocx in it. Output looks quite similar. Can anybody with more insight in this matter give me some hints? Thanks (for helping and for reading my long mails :) Fabi

2 1

Quartz DLL
by tom 03 Sep '02

03 Sep '02

Hello, I was looking at the WineX cvs version on sourceforge and it looks as if they have a quartz.dll based on ffmpeg. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/winex/wine/dlls/quartz/ What are the odd's of this work being put into the main wine tree ? As the old quartz.dll got pulled........ Tom

6 6

ANSI_CHARSET
by Jeff Smith 03 Sep '02

03 Sep '02

ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in include/wingdi.h), but I have some doubts about the details. SYMBOL_CHARSET should be defined as (BYTE)2, I believe. If the current value of DEFAULT_CHARSET as (BYTE)1 is correct, then I suspect ANSI_CHARSET should be (BYTE)0. I question the current value of DEFAULT_CHARSET, and suspect it should be the reverse (DEFAULT:0 ANSI:1). DEFAULT defines tend to be 0 except for a few special cases (and this one does not fit as one of in my book). I'm sure someone out there is more familiar with this than I am, and I would appreciate their feedback. Notes: There is a function in shell32.dll as distributed in Win95-OSR-2.1, that uses the LOGFONT structure. In this function, the structure is used for three fonts: "Times New Roman", "Arial", and "Wingdings". The lfCharSet member for each case is 0, 0, and 2, respectively. -- Jeff Smith _________________________________________________________________ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com

5 5

Mono / winforms + Winelib
by Steven Edwards 02 Sep '02

02 Sep '02

I have started some discussion with the Mono developers on how to better share our work and they have sent these directions for anyone that is interested in testing Mono with Winelib. There is also a Mono build for Win32 if you want to test it under Wine/ReactOS. I will try and find some free time in the next few weeks to see if I can help with documenting problems or areas our projects can work together better. Note: forwarded message attached. __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

1 0

ALSA 0.9 sound problems
by TJ 02 Sep '02

02 Sep '02

Hi =) I have ALSA 0.9 with OSS compat modules. I recently got DeusEx to run (on Wine w/ openGL, not talking about WineX) However using winealsa.drv sound is very laggy and lots of nasty clicks and hissing occurs, but if I use wineoss.drv sound is fine?? (note OSS driver will be talking to ALSA via the snd-pcm-oss compat module) Also when using the wineoss module and the game (not just DeusEx but most games I got working) is setting up sound it seems to freeze, all i do then is ctrl+z, fg, in controling term and things run fine from then on. -TJ

3 4

Creating ocx
by Fabian Cenedese 02 Sep '02

02 Sep '02

Hi I have a problem with an ocx (not with WineDbg this time :). To create it I do: CreateControl(GetClsid(), lpszWindowName, dwStyle, rect, pParentWnd, nID,pPersist, bStorage, bstrLicKey); which works fine in windows (NT4), but in Wine-20020804 I get the following: First chance exception: e06d7363 in 32-bit code (0x400d5ee5). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:0000 EIP:400d5ee5 ESP:405c4e18 EBP:405c4e70 EFLAGS:00000246( - 00 I Z- -P1 ) EAX:405c4e20 EBX:4010ca04 ECX:00000000 EDX:405c4e34 ESI:405c4f4c EDI:00000000 Stack dump: 0x405c4e18 (_end+0x265cf4): 4010ca04 400ca2f2 e06d7363 00000001 0x405c4e28 (_end+0x265d04): 00000000 400d5e70 00000003 19930520 0x405c4e38 (_end+0x265d14): 405c4f84 5f4bb5d8 405c4ecc 400fbc9c 0x405c4e48 (_end+0x265d24): 405c4e74 00000400 405c4f58 405c4e80 0x405c4e58 (_end+0x265d34): 4010ca04 400da28a 00000002 40123a68 0x405c4e68 (_end+0x265d44): 00000058 40129d48 405c4e90 400ca303 0x405c4e78 (_end+0x265d54): 0011: sel=008f base=401225c0 limit=00000fff 32-bit rw- Backtrace: =>0 0x400d5ee5 (RaiseException+0x75(code=0xe06d7363, flags=0x1, nbargs=0x3, args=0x405c4f4c) [except.c:81] in libntdll.dll.so) (ebp=405c4e70) 1 0x400ca303 (call_stdcall_function+0xc3(func=0x400d5e70, nb_args=0x4, args=0x405c4f20) [relay386.c:327] in libntdll.dll.so) (ebp=405c4e90) 2 0x400ca6e8 (RELAY_CallFrom32+0x148(ret_addr=0x7800ac4e) [relay386.c:400] in libntdll.dll.so) (ebp=405c4f14) 3 0x4076fed5 (KERNEL32.DLL.TryEnterCriticalSection+0x2b59 in kernel32.dll.so) (ebp=405c4f58) 4 0x5f47d5b1 (MFC42.DLL.1269+0x4d in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c4f7c) 5 0x5f48ceab (MFC42.DLL.2464+0x11c in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c5004) 6 0x5f423445 (MFC42.DLL.4035+0x51 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c502c) 7 0x5f42348d (MFC42.DLL.6095+0x43 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c5054) 8 0x5f423520 (MFC42.DLL.5719+0x28 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c5088) 9 0x5f42375d (MFC42.DLL.6198+0x14 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c50f0) 10 0x5f421996 (MFC42.DLL.6621+0x86 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c5148) 11 0x5f42168b (MFC42.DLL.6623+0x3f in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c5184) 12 0x5f421647 (MFC42.DLL.2135+0x59 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=405c51d8) 13 0x3001e1ad (CIXOutWinView::Create+0x43(lpszWindowName=0x406cb3f0, dwStyle=0x50300000, rect=0x405c5244, pParentWnd=0x41568c60, nID=0x1320, ExtStyle=0x200, pPersist=0x0, bStorage=0x0, bstrLicKey=0x0) [N:\IMD\Imex\Src\IXOutWin.cpp:167] in C:\IMD\BIN\IMEX.DLL) (ebp=405c520c) (here is the above mentioned CreateControl) 0x400d5ee5 (RaiseException+0x75 [except.c:81] in libntdll.dll.so): leal 0xffffffa8(%ebp),%esp 81 RtlRaiseException( &record ); It finds the .ocx so that shouldn't be a problem. The registry should be correct too as other ocx's I have work fine, all installed with the same setup. This is also the reason why I believe it's something inside the ocx code. The exception code e06d7363 means float inexact result or so, but I never used float or double or any 64 bit integer. The OnCreate and OnFontChanged of the ocx are called and left successfully. I traced it down to this (shortly after OnFontChanged is left, maybe some painting done): 08153fd8:Call kernel32.lstrlenA(405c5062 "\016") ret=5f418414 08153fd8:Ret kernel32.lstrlenA() retval=00000001 ret=5f418414 08153fd8:Call kernel32.lstrlenA(406cb3f0 "") ret=5f4184ce 08153fd8:Ret kernel32.lstrlenA() retval=00000000 ret=5f4184ce 08153fd8:Call kernel32.MultiByteToWideChar(00000000,00000000,406cb3f0 "",ffffffff,405c4f88,00000001) ret=5f4184f9 08153fd8:Ret kernel32.MultiByteToWideChar() retval=00000001 ret=5f4184f9 08153fd8:Call kernel32.GetProcAddress(65340000,00000002) ret=5f405724 08153fd8:Ret kernel32.GetProcAddress() retval=65341408 ret=5f405724 08153fd8:Call kernel32.IsBadReadPtr(405c4f98,00000020) ret=42622bce 08153fd8:Ret kernel32.IsBadReadPtr() retval=00000000 ret=42622bce 08153fd8:Call kernel32.IsBadReadPtr(405c4fd8,00000004) ret=42622bce 08153fd8:Ret kernel32.IsBadReadPtr() retval=00000000 ret=42622bce 08153fd8:Call ntdll.RtlSizeHeap(40360000,00000000,403c0738) ret=65f019c3 trace:heap:RtlSizeHeap (40360000,00000002,403c0738): returning 00000020 08153fd8:Ret ntdll.RtlSizeHeap() retval=00000020 ret=65f019c3 08153fd8:Call kernel32.RaiseException(e06d7363,00000001,00000003,405c4f4c) ret=7800ac4e 65340000 is the handle for the OLEAUT32.DLL, function 2 seems to be SysAllocString but it doesn't seem to get there (at least I never see my message in the log file).. Any ideas how I can find out what goes wrong (inside the MFC42.dll)? Thanks Fabi

1 0

Re: SHLWAPI IQueryAssociations helpers
by Jürgen Schmied 02 Sep '02

02 Sep '02

> This patch implements the Assoc* functions for SHLWAPI. We need to > decide whether to duplicate or share the code for the underlying COM > object though (i.e. can I include the c file from the shell dir?). Sharing code is never a good idea. Usually windows implements things on one place and we should do so too. The only reason for some code duplication between shlwapi and shell32 is ms moved some functionality from shell32 to shlwapi over time. All the assoc-stuff belongs to shlwapi now. Shell32 uses only this services. juergen --- juergen.schmied(a)debitel.net

1 0

Opinions about univesal printer driver
by m.kostrzewa＠pentacomp.com.pl 02 Sep '02

02 Sep '02

Greetings to all Wine community! I've been wondering if this is the right place to post it, I belive yes, please forgive me if not :) I'm trying to imagine a method for using windows printer drivers under linux. As far as I know, from gdi's point of view it works like: LoadLibrary(driver) (drv appears to be a dll), some of 24 DDI functions which every printer driver should contain, Initialization = Enable, Control, next goes drawing functions like Output, Pixel. It doesn't have to access paralell ports - it can write to file (when printing under Windows you have this little checkbox, and gdi initializes driver telling this filename I think). Content of this file can be directly sent to port in Linux's way. I know that's not that simple, but I'm very interested in your opinions: what do you think about it having experience in dlling under linux :-) ? I know that wine doesn't run drivers, but it can run win dlls. Is it possible at all? Or this is just a linux-supports-every-printer dream? Perhaps someone tried this already? best regards, Michal Kostrzewa

3 2

Heap overruns
by Shachar Shemesh 02 Sep '02

02 Sep '02

Hi list, I am currently having some problems with a change I am working on, that result in heap corruption as a result of buffer overrun. I was wondering whether there was any builtin debug options to detect and help fix these things. If there aren't, I am perfectly willing to sidetrack a little and write them. Please let me know. Shachar

5 8