May 2001 - wine-devel

Finding (or not) the exact number of args
by Gaël de Chalendar 01 Jun '01

01 Jun '01

Hi, I'm trying to implement stubs for some missing ordinal functions in shlwapi. Reading the NOTES comment in dlls/shlwapi/ordinal.c I don't know if it is a good idea, but it allows explorer.exe (Win 98) to show its desktop and it is what I'm testing (just for fun. I do not hope to be able to use it right now). Anyway, it uses at a moment or another unimplemented ordinal functions. To implement their stubs, I begins with a lot of args, reducing this number until the function is passed. It seems to work but I wonder if I do not add only problems with this strategy. If I left the stack in a corrupted state, maybe the problem will become visible a lot later... I was not able to find in docs, mails archives or google groups any useful tip to find (simply) the right number of args. Particularly, the URL http://www.ece.cmu.edu/afs/ece/usr/dacut/www/src is dead. So, do I continue ? If yes, in this way or differently ? Thanks for your advices. Gael. PS: I will not read my mail until monday 28.

3 4

Re: critical section blocking
by Duane Clark 01 Jun '01

01 Jun '01

Aric Stewart wrote: > > Working with QuickTime5 I found a situation where mouse messages could > lockup wine. This leaving and entering the critical section resolves > that bug. > > -aric > > ------------------------------------------------------------------------ > Index: windows/message.c > =================================================================== > RCS file: /home/wine/wine/windows/message.c,v With this patch, Myst locks up solid as soon as the mouse is moved into the Myst window. Without it, Myst works fine. Duane

3 2

Re: wineps include fix.
by Ian Pilcher 01 Jun '01

01 Jun '01

David Hammerton wrote: > > hi, seems you have done some updating on it.. but now it still doesnt compile, > im not sure if your trying to include something that is defined elsewhere or > you made a typo, but it seems to bawk on: > > gcc -c -I. -I. -I../../include -I../../include -I/usr/include/freetype2 -g -O2 > -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_REENTRANT > -I/usr/X11R6/include -o truetype.o truetype.c > truetype.c:13: `#include' expects "FILENAME" or <FILENAME> > truetype.c:14: `#include' expects "FILENAME" or <FILENAME> > I give up. You're getting the error because FreeType's macros are not being defined by your include files. This is supposed to be the way to work around the fact that the FreeType guys rename their include files with every minor release. freetype/freetype.h should either define the macros or include another file that does so. If you can figure out why that isn't happening, let me know. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

5 9

Re: set_thread_buffer
by Marcus Meissner 31 May '01

31 May '01

On Thu, May 31, 2001 at 01:12:14PM -0400, =?iso-8859-1?Q?G=E9rard_Patel_=3Cgerard.patel=40nerim.net=3E?=(a)tourian.nerim.net wrote: > At 01:24 30/05/2001 +0200, you wrote: > (yet another self followup) > > >Since the commits of last night, every app I have tried only says : > > > >wine client error:0x80675a8: set_thread_buffer failed with status c000000d Hmm, can you do 'nm file/file.o|grep stat64' and see if we are including stat64 there? > >with apps that usually work fine. > I have still the problem; I have downloaded a fresh tree from winehq > to make sure it was not a random event. > > I don't have much time to debug until next weekend, but I have done > a bit of searching : this does not happen on my newest computer, a > Mandrake 8 with glibc 2.2. It happens with my other box, a Suse 6.1 > with a manually upgraded glibc 2.1.3 (I use it without this problem since > months) > > The problem occurs in the mmap call in the server subroutine, the parameters > being > size=8192, fd=8,offset=0. > > Has anyone compiled cvs since 3 days with glibc 2.1.3 ? I have build RPMs for OpenLinux eDesktop 2.4, which is kernel 2.2.14 and glibc 2.1.3, and sol.exe still works. You can try them from http://www.lst.de/~mm/wine.html if you want to. Ciao, Marcus

2 1

Re: set_errno patch
by Alexandre Julliard 31 May '01

31 May '01

Francois Gouget <fgouget(a)free.fr> writes: > MSVCRT__set_errno should be able to set errno to 0. It's called at > least once explicitly with 0 in dir.c, but many other times it is > called with a GetLastError() that may return 0. I don't think it is ever correct to set errno to 0. Code that does that should be fixed to provide a valid error code instead. -- Alexandre Julliard julliard(a)winehq.com

1 0

FreeType autoconf checks - please test
by Ian Pilcher 31 May '01

31 May '01

This works on my system (Red Hat 7.1 with FreeType 2.0.1). Please try it on other variants and let me know if it works. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ======================================================================== diff -urN ../wine-20010529cvs/configure.in ./configure.in --- ../wine-20010529cvs/configure.in Thu May 31 09:16:57 2001 +++ ./configure.in Thu May 31 09:19:41 2001 @@ -402,8 +402,21 @@ wine_cv_msg_freetype=yes else AC_DEFINE(HAVE_FREETYPE) - FREETYPELIBS=`$ft_devel --libs` - FREETYPEINCL=`$ft_devel --cflags` + FREETYPELIBS=`$ft_devel --libs` + FREETYPEINCL=`$ft_devel --cflags` + ft_incl_dir=${FREETYPEINCL#-I} + old_c_include_path="$C_INCLUDE_PATH" + C_INCLUDE_PATH="$ft_incl_dir:$C_INCLUDE_PATH" + export C_INCLUDE_PATH + ft_incl_dir=$ft_incl_dir/freetype + AC_CHECK_HEADER($ft_incl_dir/freetype.h,AC_DEFINE(HAVE_FREETYPE_H)) + AC_CHECK_HEADER($ft_incl_dir/ftglyph.h,AC_DEFINE(HAVE_FTGLYPH_H)) + AC_CHECK_HEADER($ft_incl_dir/tttables.h,AC_DEFINE(HAVE_TTTABLES_H)) + AC_CHECK_HEADER($ft_incl_dir/ftnames.h,AC_DEFINE(HAVE_FTNAMES_H)) + AC_CHECK_HEADER($ft_incl_dir/ftsnames.h,AC_DEFINE(HAVE_FTSNAMES_H)) + AC_CHECK_HEADER($ft_incl_dir/ttnameid.h,AC_DEFINE(HAVE_TTNAMEID_H)) + C_INCLUDE_PATH="$old_c_include_path" + export C_INCLUDE_PATH wine_cv_msg_freetype=no fi fi diff -urN ../wine-20010529cvs/dlls/wineps/truetype.c ./dlls/wineps/truetype.c --- ../wine-20010529cvs/dlls/wineps/truetype.c Thu May 31 09:17:26 2001 +++ ./dlls/wineps/truetype.c Thu May 31 09:17:56 2001 @@ -9,11 +9,30 @@ #ifdef HAVE_FREETYPE +/* + * These stupid #ifdefs should work for FreeType 2.0.1 and 2.0.2. Beyond that + * is anybody's guess. + */ + +#ifdef HAVE_FREETYPE_H #include <freetype/freetype.h> -#include FT_NAMES_H -#include FT_TRUETYPE_NAMES_H -#include FT_TRUETYPE_TABLES_H -#include FT_GLYPH_H +#endif +#ifdef HAVE_FTGLYPH_H +#include <freetype/ftglyph.h> +#endif +#ifdef HAVE_TTTABLES_H +#include <freetype/tttables.h> +#endif +#ifdef HAVE_FTNAMES_H +#include <freetype/ftnames.h> +#endif +#ifdef HAVE_FTSNAMES_H +#include <freetype/ftsnames.h> +#endif +#ifdef HAVE_TTNAMEID_H +#include <freetype/ttnameid.h> +#endif + #include <sys/types.h> #include <dirent.h> #include <string.h> diff -urN ../wine-20010529cvs/include/acconfig.h ./include/acconfig.h --- ../wine-20010529cvs/include/acconfig.h Tue May 29 18:16:35 2001 +++ ./include/acconfig.h Thu May 31 09:17:56 2001 @@ -129,3 +129,11 @@ /* Define if FreeType 2 is installed */ #undef HAVE_FREETYPE + +/* Define if various FreeType headers are present */ +#undef HAVE_FREETYPE_H +#undef HAVE_FTGLYPH_H +#undef HAVE_TTTABLES_H +#undef HAVE_FTNAMES_H +#undef HAVE_FTSNAMES_H +#undef HAVE_TTNAMEID_H

2 1

[Fwd: autoconf help needed [was wineps include fix.]]
by Ian Pilcher 31 May '01

31 May '01

Ian Pilcher wrote: > > Marcus Meissner wrote: > > > > Add here: > > > > CFLAGS="$CFLAGS -I$ft_incl_dir" > > > > Works great. Thanks! > I spoke too soon. It's finding /usr/include/freetype/freetype.h (from FreeType 1.x). The test is not paying any attention to the CFLAGS variable. So how does one get the autoconf tests to look in a non-standard directory for header files? -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Re: WINE server messages
by Alexandre Julliard 31 May '01

31 May '01

David Howells <dhowells(a)redhat.com> writes: > I'm having a little trouble deciding exactly how to emulate the "module > registration" functionality in my kernel module. It occurs to me that this > might be easier to accomplish with a change to the current wine server message > set. My idea is: > > * Have the server only deal with NT Section objects and views of Sections. > > * Have no separate module table attached to a process. > > * Implement NtQuerySectionInformation/NtSetSectionInformation calls (or > whatever they're called) as wineserver messages. > > * Add an extra Wine-specific information class for the purpose of recording > the extra module information. > > * The wineserver process structure can then be changed so that rather than > keeping a separate list of process_dlls, they can just keep a list of > section views, some of which will be images/modules. Maintaining a section list in the server is certainly something we could do, but I don't really see why you want to get rid of the modules list. What would you gain by doing that?> -- Alexandre Julliard julliard(a)winehq.com

2 1

PathGetCharType/PathGetCharTypeA
by Dax Kelson 31 May '01

31 May '01

I'm having a failure with a windows app. The application starts, and it asks me to name my project and pick a directory to store it in. When I do so, I get errors such as: fixme:shell:PathGetCharTypeA d fixme:shell:PathGetCharTypeA f fixme:shell:PathGetCharTypeA d fixme:shell:PathGetCharTypeA t And apps reports "such such character isn't valid", and doesn't continue (each time I try again, it generates another fixme message). According to MSDN: http://msdn.microsoft.com/library/psdk/shellcc/shell/SHLWAPI/Path/PathGetCh… PathGetCharType/PathGetCharTypeA part of shlwapi.h returns one or more of the following values that define the type of character: GCT_INVALID The character is not valid in a path. GCT_LFNCHAR The character is valid in a long file name. GCT_SEPARATOR The character is a path separator. GCT_SHORTCHAR The character is valid in a short (8.3) file name. GCT_WILD The character is a wildcard character. This is the current Wine code: /************************************************************************* * PathGetCharTypeA [SHLWAPI.@] */ UINT WINAPI PathGetCharTypeA(UCHAR ch) { FIXME("%c\n", ch); return 0; } I'm a perl guy, but I'm learning C. Maybe I'm naive, but fleshing out the Wine version of this function shouldn't be too hard it seems. You'd have to go track down the rules. Can some point me in the right direction on fixing this up? Can someone give me a quick hack to make my application work? Many thanks, Dax

2 3

autoconf help needed [was wineps include fix.]
by Ian Pilcher 31 May '01

31 May '01

Alexandre Julliard wrote: > > Basically do a > > AC_CHECK_HEADERS(freetype/freetype.h freetype/foo.h freetype/bar.h) > Unfortunately it's not that simple, because the FreeType include files won't always be in /usr/include/freetype. On Red Hat 7.1, for example, they're in /usr/include/freetype2/freetype, to distinguish them from the FreeType 1.x headers. The required compiler flag to include the proper directories is in the FREETYPEINCL variable. For example, on my Red Hat system it is set to '-I/usr/include/freetype2'. I tried the following: ft_incl_dir=${FREETYPEINCL#-I} AC_CHECK_HEADER("$ft_incl_dir/freetype/freetype.h",AC_DEFINE(HAVE_FREETYPE_H)) When I run autoconf, autoheader, and configure, I get the following: checking for FT_Init_FreeType in -lfreetype... yes checking for freetype-config... freetype-config checking for /usr/include/freetype2/freetype/freetype.h... no So the AC_CHECK_HEADER macro isn't finding the file, even though it is right there. Anyone have any idea why? -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

2 1

Re: wineps include fix.
by Alexandre Julliard 31 May '01

31 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > Did you read somewhere that they're getting rid of freetype.h? > > I've looked at 2.0.1 and 2.0.2: > > * In 2.0.1, the header macros are defined in > freetype/config/ftbuild.h, which is included in freetype/freetype.h. > > * In 2.0.2, the header macros are defined in ft2build.h, which is > included in freetype/freetype.h. > > So as long as they keep freetype/freetype.h around, we can include that > and get the macro definitions. The page at http://freetype.sourceforge.net/freetype2/docs/tutorial/step1.html says that you have to include ft2build.h and use macros to include freetype.h, and that other inclusion schemes will get broken in 2.1. I have no idea if this page is up-to-date or if the recommendations have changed again. > We still have to test which macros are defined and only include the ones > that exist, but it does save the work of adding extra autoconf checks. Except with the autoconf checks we control what macros are being defined, we don't have to guess which file to include to get the proper macros. Frankly this idea of defining macros to specify include file names is hopelessly brain-damaged, and the less we have to do with that the happier I will be. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: PATCH: Version 2, GetX11WindowId
by Alexandre Julliard 30 May '01

30 May '01

Nikolas Zimmermann <wildfox(a)kde.org> writes: > ah > i mean, this feature would _only_ be used in kdenonbeta/activexproxy > and it would be great to have this in CVS until you've done this rewrite-task. > > Do you think that's a good, short-term, solution for me? For you certainly. But it doesn't have to be in CVS for you to use it, does it? These kinds of quick hacks have a way of staying around much too long, especially when external packages depend on them, and the best way to avoid that is to not put them in CVS the first place. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: wineps include fix.
by Alexandre Julliard 30 May '01

30 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > I *believe* that <freetype/freetype.h> should always include the header > that defines the macros. If not, it's going to be a nightmare checking > for 2.0.1, 2.0.2, 2.0.3, etc. -- let alone every intermediate snapshot > that a rawhide/cooker distribution might use. It seems the rule is now to use ft2build.h instead of freetype.h. And this will certainly change in the next release again... so yes, it will be a nightmare if we actually try to use the silly macros. But if we simply bypass them and do autoconf checks like we do for every other package, I think it should work, and be harder to break (though I'm sure the freetype guys will manage to do it ;-) Basically do a AC_CHECK_HEADERS(freetype/freetype.h freetype/foo.h freetype/bar.h) and then #ifdef HAVE_FREETYPE_FREETYPE_H #include <freetype/freetype.h> #endif #ifdef HAVE_FREETYPE_FOO_H #include <freetype/foo.h> #endif etc. Then when they change all the header names again in the next release we can simply add the new names to the list. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: wineps include fix.
by Alexandre Julliard 30 May '01

30 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > FT_SFNT_NAMES_H doesn't appear anywhere in the 2.0.1 headers. It > appears to be impossible to be source code compatible between 2.0.1 and > 2.0.2. How about doing autoconf checks for all the possible header names variations, and including the ones we find? This would be a lot more robust than trying to find the header that defines the macros that define the headers that define what we need... -- Alexandre Julliard julliard(a)winehq.com

3 2

Problems with large file support.
by Ludovic LANGE 30 May '01

30 May '01

Hello, A few days ago (15 or 16) the support for large files / 64bits was added to Wine ( files/files.c, server/file.c, win32/file.c). Since that modification, my Wine installation isn't functional any more, and wine throws an exception while setting up the SystemHeap. The exception occurs in heap.c, function HEAP_InitSubHeap, just at the instruction : "subheap->heap = heap;" while the subheap pointer is valid. It seems as if the protection of this memory areay was set to read-only, and that the mprotect() call did not succeed in setting it to read/write. I don't know where the real problem is, but since I found no record of such problem in the lists archive, it may be a configuration problem of mine. However, having not found the solution, I'd like some advices. I also think it could be a problem with my glibc not functionning with 64bits functions. My system is a Linux 2.4.4 / RedHat 7.0 / redhat's glibc 2.2-12 Here is a working trace, before the support for 64bits functions was added : ============================================================================== 0806cb00:trace:virtual:CreateFileMappingA (ffffffff,(nil),08000004,0000000000110000,"__SystemHeap") 0806cb00: create_mapping( size_high=0, size_low=1114112, protect=67, inherit=0,file_handle=0, name=L"__SystemHeap" ) 0806cb00: create_mapping() = 0 { handle=32 } 0806cb00: get_mapping_info( handle=32 ) 0806cb00: get_mapping_info() = 0 { size_high=0, size_low=1114112, protect=67, header_size=0, base=(nil), shared_file=0, shared_size=0 } 0806cb00: get_handle_fd( handle=32, access=00000000 ) 0806cb00: *fd* 32 -> 9 0806cb00: get_handle_fd() = 0 { fd=-1 } 0806cb00: set_handle_info( handle=32, flags=0, mask=0, fd=6 ) 0806cb00: set_handle_info() = 0 { old_flags=0, cur_fd=6 } 0806cb00:trace:virtual:MapViewOfFileEx handle=20 size=110000 offset=0 0806cb00: dup_handle( src_process=-1, src_handle=32, dst_process=-1, access=00000000, inherit=0, options=2 ) 0806cb00: dup_handle() = 0 { handle=36, fd=-1 } View: 65430000 - 6553ffff 36 65430000 - 6553ffff c-rW- 0806cb00:trace:virtual:VirtualAlloc 65430000 00110000 1000 00000040 0806cb00:trace:virtual:VIRTUAL_SetProt 65430000-6553ffff c-rWx View: 65430000 - 6553ffff 36 65430000 - 6553ffff c-rWx 0806cb00: create_semaphore( initial=00000000, max=00000001, inherit=0, name=L"") ============================================================================== Here is the stack trace with support for 64 bits functions (more debug traces of mine.) ============================================================================== 0806cb40:trace:virtual:CreateFileMappingA (ffffffff,(nil),08000004,0000000000110000,"__SystemHeap") 0806cb40: create_mapping( size_high=0, size_low=1114112, protect=67, inherit=0, file_handle=0, name=L"__SystemHeap" ) 0806cb40: create_mapping() = 0 { handle=32 } 0806cb40:trace:heap:HEAP_CreateSystemHeap LLA 0806cb40: get_mapping_info( handle=32 ) 0806cb40: get_mapping_info() = 0 { size_high=0, size_low=1114112, protect=67, header_size=0, base=(nil), shared_file=0, shared_size=0 } 0806cb40: get_handle_fd( handle=32, access=00000000 ) 0806cb40: *fd* 32 -> 9 0806cb40: get_handle_fd() = 0 { fd=-1 } 0806cb40: set_handle_info( handle=32, flags=0, mask=0, fd=6 ) 0806cb40: set_handle_info() = 0 { old_flags=0, cur_fd=6 } 0806cb40:trace:virtual:MapViewOfFileEx handle=20 size=110000 offset=0 0806cb40: dup_handle( src_process=-1, src_handle=32, dst_process=-1, access=00000000, inherit=0, options=2 ) 0806cb40: dup_handle() = 0 { handle=36, fd=-1 } View: 65430000 - 6553ffff 36 65430000 - 6553ffff c-rW- 0806cb40:trace:heap:HEAP_CreateSystemHeap LLA - after MapViewOfFileEx : 1077 0806cb40:trace:heap:HEAP_CreateSystemHeap LLA - line 1081 0806cb40:trace:heap:HEAP_InitSubHeap LLA address = 65430000 - line 478 0806cb40:trace:heap:HEAP_InitSubHeap LLA - line 482 0806cb40:trace:virtual:VirtualAlloc 65430000 00110000 1000 00000040 0806cb40:trace:virtual:VIRTUAL_SetProt 65430000-6553ffff c-rWx View: 65430000 - 6553ffff 36 65430000 - 6553ffff c-rWx 0806cb40:trace:virtual:VirtualAlloc LLA 65430000 00110000 1000 00000040 VIRTUAL_SetProt : base= 65430000 0806cb40:trace:heap:HEAP_InitSubHeap LLA - line 491 0806cb40:trace:heap:HEAP_InitSubHeap LLA subheap = 65430000 - line 518 0806cb40:trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 0806cb40: queue_exception_event( first=1, record={context={flags=00000000,eax=00000047,ebx=4012c0ec,ecx=65430000,edx=65430000,esi=40128e05,edi=00110000,ebp=00000000,eip=400bb7eb,esp=40626dd0,eflags=00010212,cs=0023,ds=002b,es=002b,fs=008f,gs=0000,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000}},rec={code=c0000005,flags=0,rec=(nil),addr=0x400bb7eb,params={1,65430010} ) 0806cb40: queue_exception_event() = 0 { handle=0 } ============================================================================== Any clues are welcome. Best regards, Ludovic LANGE

1 0

Re: PATCH: Version 2, GetX11WindowId
by Alexandre Julliard 30 May '01

30 May '01

Nikolas Zimmermann <wildfox(a)kde.org> writes: > Hi there, > > andrewl (#winehq) advised me to remove > the winuser.h dependencies > > here is the new patch > > Any comments? The main problem is that this requires linking the application to x11drv, which is not a good idea. x11drv is an internal driver that should only be loaded by user/gdi. There needs to be a way to do that without loading x11drv, for instance by using window properties. This is somewhere on my todo list for the new window management code that I'm currently working on. -- Alexandre Julliard julliard(a)winehq.com

2 1

PATCH: Version 2, GetX11WindowId
by Nikolas Zimmermann 30 May '01

30 May '01

Hi there, andrewl (#winehq) advised me to remove the winuser.h dependencies here is the new patch Any comments? Bye Bye Niko -- Nikolas Zimmermann wildfox(a)kde.org

1 0

some unimplemented COM stuff
by Malte.Starostik＠t-online.de 30 May '01

30 May '01

Hello, I have started implementing a small winelib-program that shall eventually add ActiveX support to the Konqueror web browser. For testing I'm using the Shockwave Flash OCX and experienced some problems due to unimplemented functions and features in winelib. First thing is typelib registration, which doesn't work yet as the debug output tells. Okay, did that manually. Then, for setting the control's properties, I tried the easy way via IDispatch::Invoke(), which calls ITypeInfo::Invoke() and that's only a stub :( I worked around this via evil assembler hacks to call the interface's members as given by the vtable offsets in the FUNCDESC using stdcall convention - unfortunately g++ doesn't support specifying a calling convention for method pointers like HRESULT (IDispatch::*setProp)(BSTR). After getting this to work, I hit the next problem: unimplemented urlmon.RegisterBindStatusCallback and when I use a native urlmon.dll it tries to call shlwapi.154, with native shlwapi it still doesn't work somehow, but that's a different story. Anyway, what I'd basically need to get this to work properly is - typelib registration - IDispatch::Invoke() - RegisterBindStatusCallback() and probably asyncronous bind contexts - probably a "real" URL Moniker, not just CreateURLMoniker() using a File Moniker What I'd like to know is if anyone is already working on any of these and if so what's the status and how I could help getting these implemented. if no one started yet, I'd still like to give it a try. Thanks, -Malte PS: the attached patch fixes urlmon.h not being C++-safe. -- Wars don't determine who's right, only who's left.

5 9

WINE server messages
by David Howells 30 May '01

30 May '01

Hello Alexandre, I'm having a little trouble deciding exactly how to emulate the "module registration" functionality in my kernel module. It occurs to me that this might be easier to accomplish with a change to the current wine server message set. My idea is: * Have the server only deal with NT Section objects and views of Sections. * Have no separate module table attached to a process. * Implement NtQuerySectionInformation/NtSetSectionInformation calls (or whatever they're called) as wineserver messages. * Add an extra Wine-specific information class for the purpose of recording the extra module information. * The wineserver process structure can then be changed so that rather than keeping a separate list of process_dlls, they can just keep a list of section views, some of which will be images/modules. David

1 0

set_thread_buffer
by gerard patel 29 May '01

29 May '01

Since the commits of last night, every app I have tried only says : wine client error:0x80675a8: set_thread_buffer failed with status c000000d with apps that usually work fine. Gerard

1 0

PATCH: GetX11WindowId()
by Nikolas Zimmermann 29 May '01

29 May '01

Hi there, this is my first wine patch. it allows the coder to get the X11 Window Id of a HWND. People ask me why this belongs into x11drv and why i need it. ActiveX support for Konqueror, Malte Starostik (who will post some oleaut and urlmon patches soon) and me are working on this. I need to embed the created window, therefore i need this window id. Thank you in advance Bye Bye Niko -- Nikolas Zimmermann wildfox(a)kde.org

1 0

Re: Small fixes in controls/menu.c
by gerard patel 28 May '01

28 May '01

At 10:46 PM 25/05/2001 +0200, you wrote: >I downloaded ftp://ftp.supermemo.com/ftp/sm8zip.exe and managed to >reproduce the bug. (WINE version 20010510) >The way: >1) Using mouse chose File>SuperMemo >2) When app changes its mode click at capition of window >"Contents: E:\SM8\SYSTEMS\SUPERMEMO" >And now main menu is inaccesible (using mouse) >When you force wine to repaint all windows (eg. switch to linux console >and back to X-Window ) you can see menu is drawn up 10-20 pixels than >it should. All right, I still can't see this bad redrawing , but I can see the menu not accessible behaviour now. I'll try to understand something in this problem this week. Btw, this app does not work at all for me in managed mode, it hangs after displaying the splash screen. (but sm7.exe - version 7.5 and sm99.exe - version 9 both load). I think it's an unrelated problem though since it happens with my oldest wine version (20000801) and it's not fixed by your patch. Gerard

2 1

a tool: simple C++ interface definition -> ICOM_ macro converter.
by TAKESHIMA Hidenori 28 May '01

28 May '01

This program may help creating ICOM_ macro. (but this code doesn't have portability, so some modification may be required.) for example, if give the following codes to stdin, we gets ICOM_ macros for IPersist. class IUnknown { public: HRESULT QueryInterface( REFIID riid, LPVOID *ppvObj) ; ULONG AddRef() ; ULONG Release() ; }; export interface IPersist : public IUnknown { virtual HRESULT STDMETHODCALLTYPE GetClassID( CLSID *pClassID ); };

1 0

Wrc patch
by kenon＠go2.pl 28 May '01

28 May '01

Hi, This patch is an answer for "Call for volunteers". I hope it fixes : "wrc fails on preprocessed files" #115: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=115 Maciek Changelog * tools/wrc/ppy.y Maciek Kaliszewski <kenon(a)go2.pl> Added better GCC-style #line directive handling. --

1 0

Enabling backing store
by David Hagood 27 May '01

27 May '01

Has any thought been given to enabling backing store on Wine's windows? As it stands now, when you obscure a Wine window, it forces the Windows app to redraw the screen. Many times this is not needed. Perhaps a configuration option to allow certain apps to have backing store on would be useful. I know that up until a few months ago, it was possible to go into wnd.c and change the default from NotUseful to WhenMapped and things seemed to work well. However, the structure of the X driver has changed, and a simple patch is no longer possible.

1 0

Re: X Error with latest Wine and Notes
by Ian Pilcher 27 May '01

27 May '01

David.Goodenough(a)dga.co.uk wrote: > > I have noticed that with the latest Wine (May drop) I have started to get X > Errors. This typically happens as a dialog is being dismissed. > > The latest of these errors read:-- > > X Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 12 (X_ConfigureWindow) > Resource if in failed request: 0x1c24350 > Serial number of failed request: 9920 > Current serial number in output stream: 9922 > > I get the feeling, although I can not prove it, that this may be timing > related, as it tends to happen when I am a bit quick completing the dialog. > The other odd thing that happens when this occurs is that a second copy of > the window, not the detail face of the window, just the window and its > frame controls, is drawn slightly down and right of the original window, > then it blows and Notes hangs. > > I had not noticed this behaviour before switching to the May drop. There > are no other console messages that are out of the ordinary set that I have > been reporting for a while. > > Is this a known problem? David - I have also seen this problem, but I have no idea what causes it. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Q: anybody using Exceed on NT4 as X server for wine?
by Heiko Nardmann 26 May '01

26 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there anybody out there who uses Exceed on NT4 as the X server to display wine applications (like winemine from examples) which have been started on Linux? If yes are did you try 20010510 snapshot (or CVS) to run your applications? If yes could you provide me with your configuration files? I am still not able to start winemine since snapshot 20010418 (20010326 works fine). - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7DgpMpm53PRScYygRAn6cAKDaQl3Tm4l/sIe9cQoRbdwo7vf7bwCg8gm5 38OwXBWHUxJVc1ZV91iywRY= =CjPM -----END PGP SIGNATURE-----

2 1

Re: AFM files no longer required
by Alexandre Julliard 25 May '01

25 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > Here's a thought. How about creating a data subdirectory for the Post- > Script driver (i.e. dlls/wineps/data). The data could then be put in > separate files in that directory without confusing things. (The data > isn't interdependent from a build point of view, just from a main- > tenance point of view.) > > I don't know the Makefile magic necessary to do this, but if someone > could step forward with that piece, I suspect it would address both of > our concerns. > > What do you think? That's certainly a viable solution yes. If you send me a patch implementing the separate files I'll do the Makefile magic. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: AFM files no longer required
by Alexandre Julliard 25 May '01

25 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > I actually gave quite a bit of thought to the large file issue before > submitting it, and I would agree with you if there were any functional > code in the file. Because it's entirely data, and it's heavily > interdependent, I really think that one file is better. I disagree. If the data is so interdependent that you cannot split the file, you are doing something wrong IMO. And in fact splitting it will help enforce a clean data structure, which is a major advantage. > From a build point of view, gcc has no problem at all with the file. In > fact it compiles much faster than many of Wine's functional files. I know some older versions of gcc had problems with large data structures, using exponential memory to compile them or something like that. > If a > target compiler (does Wine build with anything other than gcc?) does have > a problem with it, I will yield to necessity. Until that happens, how- > ever, I believe that the practical benefit of maintainability outweighs > stylistic concerns. (After all, it's not like anyone will ever need to > read all the way through the file to understand it, as is the case with > functional code.) You may not need to read every single line, but you still need to go through it if you want to understand the structure (this is how I noticed it was too large...). So please consider splitting it. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: AFM files no longer required
by Ian Pilcher 25 May '01

25 May '01

Forgot to cc wine-devel. Alexandre Julliard wrote: > > You should really split it into separate files, a 40,000 lines file is > a bit too much. Also all this data must be constant and in a read-only > section, it's eating 400k of data space right now. I actually gave quite a bit of thought to the large file issue before submitting it, and I would agree with you if there were any functional code in the file. Because it's entirely data, and it's heavily interdependent, I really think that one file is better. (As the person most likely be tweaking the data in the near future, I can tell you that having a single file to edit, albeit a long one, will be heck of a lot easier than having 39 separate files, and isn't that really the point?) >From a build point of view, gcc has no problem at all with the file. In fact it compiles much faster than many of Wine's functional files. If a target compiler (does Wine build with anything other than gcc?) does have a problem with it, I will yield to necessity. Until that happens, how- ever, I believe that the practical benefit of maintainability outweighs stylistic concerns. (After all, it's not like anyone will ever need to read all the way through the file to understand it, as is the case with functional code.) I would like to make the data constant, but that would require major surgery to afm.c, which is more than I can take on at this point. Keep in mind that the same amount of memory is being used currently; it's just dynamically allocated as the AFM files are read in. > > I'm guessing that you have a script to generate all this; could you > please consider submitting it? This way other people can make changes > too. > I have attached the two programs I use to generate agl.c. I have always intended to submit them, but didn't know where in the source tree to put them. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Re: Small fixes in controls/menu.c
by gerard patel 25 May '01

25 May '01

At 03:42 AM 22/05/2001 +0200, you wrote: >In attachement WIN.3_11 you can see listing generated under windows 3.11. >( Borland WinSight ) (If you want get a listing generated under win98/95 - no >problem , but I'll have to format&reinstall ,because this copy of windows >stopped functioning about 6 months ago ) >WINE_SETWINPOS ,WINE_NCALC- under wine with first and second version of >patch. >I think WINE_NCALC is more similar to WIN.3_11 . There is nothing looking like a SetWindowPos call between WM_INITMENU and WM_INITPOPUPMENU, yes. But as Alexandre Julliard was pointing, it does not mean that something like calling NC_HandleNCCalcSize is done. >I'm wondering why menu->Height == 0. I'll investigate it. height = 0 because at some point the menu has been changed; this is a Wine flag to signal that the menu dimensions have to be calculated again. The problem with my test app without my original patch is that the menu sizes are not calculated at this point so the mouse clicks are ignored Btw, I have downloaded several of the availables app on your web site and I don't see anything wrong with menus; IIRC I have tried 7.5 for Win3.11, and trial versions 8 and 9 (32 bits). Is it with the main menu that you see this problem ? Gerard

2 1

Re: Unused OPTIONS variable in configure.in
by Alexandre Julliard 25 May '01

25 May '01

Fran=E7ois Gouget <fgouget(a)codeweavers.com> writes: > I noticed that OPTIONS is not used anymore in 'configure.in'. I > believe it may have been used to store the --enable-* stuff at one ti= me > but AFAIU this is now stored in 'config.h'. So I propose to remove it > altogether. Or is it set as a side effect of some standard autoconf > macro on some exotic system? It's here so that you can specify extra flags that configure doesn't know about, by doing OPTIONS=3D-Dfoo ./configure. This can be useful in some cases. --=20 Alexandre Julliard julliard(a)winehq.com

1 0

Re: AFM files no longer required
by Alexandre Julliard 25 May '01

25 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > I decided to put all of the data into dlls/wineps/agl.c, since changing > the glyph list data without regenerating the font metrics data would > cause things to break in extremely bizarre ways. (Well, it will once I > actually use the glyph names.) You should really split it into separate files, a 40,000 lines file is a bit too much. Also all this data must be constant and in a read-only section, it's eating 400k of data space right now. I'm guessing that you have a script to generate all this; could you please consider submitting it? This way other people can make changes too. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Strange Wine Problems
by r.maurizzi＠gvs.it 25 May '01

25 May '01

That's the same kernel problem that plagues Lotus Notes (If I've understood correctly the message in German ;-) Lotus Notes will die with the same problem if you use a SuSE 7.0 with SuSE kernel 2.2.18 (Mandrake kernels have the same problem, according to other people here) If you compile the kernel yourself starting from ftp.kernel.org's sources, all is well (at least for Notes). I didn't try SuSE Kernels 2.2.19 / 2.4.2 however. Ciao, Roberto.

1 0

Re: PATCH: mirc dcc send
by Dmitry Timoshkov 25 May '01

25 May '01

"Marcus Meissner" <marcus(a)jet.franken.de> wrote: > + /* This might be a DOS device we do not handle yet ... */ > + FIXME("(%) not detected as DOS device!\n",devname); ^^^ Seems a typo to me.

1 0

Strange Wine Problems
by Josef.Wegner＠t-online.de 25 May '01

25 May '01

Hi, I have some strange errors with wine the last few weeks. Everytime I try to start an application (mainly Ultima Online and Baldur's Gate) wine crashes (stops) with this errors: >wine client.exe For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE Protocol error:0x8071580: read : Die Ressource ist zur Zeit nicht verfügbar fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403938fc,00000138,3):stub fixme:pthread_kill_other_threads_np For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE Protocol error:0x8067660: read : Die Ressource ist zur Zeit nicht verfügbar Beendet Protocol error:0x8075258: read : Die Ressource ist zur Zeit nicht verfügbar I don't know what the problem is. My first thought was that I have problems with my sound drivers (Alsa 0.5.11) , so I tried the kernel emu10k1 driver and after that I loaded no sound module. All with the same result. The only other thing I did with my linux installation was upgrading to a 2.2.18 kernel. My system specs: Latest wine cvs SuSE Linux 7.0 All updates from Suse.com (new glibc 2.1.3) Kernel 2.2.18 (SMP) Alsa 0.5.11 KDE 2.1.1 Xfree86 4.0.3 (Ximera on) Dual PIII 500Mhz 384 MB Ram Adaptec AIC-7880 Ultra SCSI host adapter Matrox G400 Max Dualhead SoundBlaster Live! Value Regards -Josef Wegner

1 0

Re: More wine beginner questions
by Alexandre Julliard 23 May '01

23 May '01

Francois Gouget <fgouget(a)free.fr> writes: > So according to the dll separation rules we must not make msvcrt > depend on an API not exported by a regular windows dll. But in the case > of ntdll I'm not sure. Can we use native ntdll in Wine? I don't think so > since it also exports things like 'wine_dbgstr_[aw]n?'. So maybe we can > bend the rules a little and export _vsnwprintf anyway. A better solution would be to put the *wprintf functions inside libwine_unicode. -- Alexandre Julliard julliard(a)winehq.com

1 0

More wine beginner questions
by Mike Bond 23 May '01

23 May '01

I was just perusing through msvcrt and noticed that in wcs.c there is an implementation of _vsnwprintf, which also exists, verbatim, in it's entirety, in ntdll/wcstring.c. Unless I am misunderstanding the .spec files there appears to be a method of "forward"ing a symbol to an external implementation, such as: @ forward -noimport wcslen ntdll.wcslen Is there any particular reason this was not done for _vsnwprintf as well? There is even a comment in the wcs.c copy saying to mirror any fixes in the ntdll copy. Also, on perhaps a style note, I've noticed some implementations are prefixed by the dll name in all caps, such as MSVCRT_vfprintf, and some are not, such as _wmkdir. Is this just personal style or is there more to these differences? -- TTFN MikeB

2 1

Configuration/Announce
by eric pouech 23 May '01

23 May '01

with today's CVS commit (for those who stay up to date with the latest developments), you'll have to modify your Wine configuration to reflect the changes. First of all, your Wine configuration file now needs a WinMM section containing the following: [WinMM] "Drivers" = "wineoss.drv" "WaveMapper" = "msacm.drv" "MidiMapper" = "midimap.drv" Not adding this will print the following message > You didn't setup properly the config file for the Wine multimedia modules. > Will use the hard-coded setup, but this will disapear soon. > Please add a WinMM section to your Wine config file. Note that the above configuration will be shortly required, so don't wait before setting your configuration up Next, you have also to add a key to your registry. To do so, create a sample file (let's call it foo) containing the following text: [HKEY_LOCAL_USER\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap] 989041554 "AutoScheme"=dword:00000000 "CurrentInstrument"="#0" "UseScheme"=dword:00000000 then goto the <wine>/programs/regapi and compile the program the run: regapi setValue < foo that's it Not applying the key in the registry will result in various errors in MIDIMAP_ functions (mainly if Wine is set up to use a native Windows system) Maintainers are welcome to update theirs packages accordingly (default values are in documentation/samples/config & winedefault.reg) Detailed information is available in documentation/multimedia.sgml. A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

3 3

Re: Configuration/Announce
by Alexandre Julliard 22 May '01

22 May '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > First of all, your Wine configuration file now needs a WinMM section > containing the following: > [WinMM] > "Drivers" = "wineoss.drv" > "WaveMapper" = "msacm.drv" > "MidiMapper" = "midimap.drv" > > Not adding this will print the following message > > You didn't setup properly the config file for the Wine multimedia modules. > > Will use the hard-coded setup, but this will disapear soon. > > Please add a WinMM section to your Wine config file. > Note that the above configuration will be shortly required, so don't > wait before setting your configuration up Please keep the defaults. There is no reason to force people to update their configuration file when there are workable defaults that we can use. Ideally Wine should behave reasonably even with an empty configuration file; this is not entirely possible because things like paths don't have reasonable defaults, but forcing people to specify things that we could guess is not user-friendly. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Small clean up
by Francois Gouget 22 May '01

22 May '01

On Tue, 22 May 2001, Dmitry Timoshkov wrote: > Hello. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Small clean up. > > diff -u cvs/wine/dlls/kernel/comm.c wine/dlls/kernel/comm.c > --- cvs/wine/dlls/kernel/comm.c Sun Apr 22 07:54:54 2001 > +++ wine/dlls/kernel/comm.c Thu May 17 14:21:58 2001 > @@ -535,7 +535,7 @@ > return IE_HARDWARE; > } else { > unknown[port] = SEGPTR_ALLOC(40); > - bzero(unknown[port],40); > + memset(unknown[port], 0, 40); > COM[port].fd = fd; > COM[port].commerror = 0; > COM[port].eventmask = 0; Checking for other instances of this problem I found one in 'misc/comm.c'. But CVS claims that: cvs server: misc/comm.c is a new entry, no comparison available Yet I'm pretty sure I did not create such a file. But when a file is deleted CVS should not give me such a message. Is it because I made changes to these files (probably traces) that CVS did not dare delete them? But shouldn't it say 'was removed, no comparison available'? I also have this message for: cvs server: dlls/ddraw/ddraw/dga.c is a new entry, no comparison available cvs server: dlls/ddraw/ddraw/x11.c is a new entry, no comparison available cvs server: dlls/winspool/winspool.spec is a new entry, no comparison available cvs server: misc/comm.c is a new entry, no comparison available -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Broadcast message : fin du monde dans cinq minutes, repentez vous !

2 1

Re: Anybody know int-31?
by Alexandre Julliard 22 May '01

22 May '01

Bob Goodwin <goodie1(a)pacbell.net> writes: > When calling the save/restore handler function, the only parameter > passed is a byte in AL to indicate whether to save the current context > or restore a saved context. My question is, are there multiple copies of > the save/restore function or at least multiple entry points? It seems > that this would be the only way of having multiple unique context saves. No, the app is supposed to allocate a buffer of the right size (as returned by the int31 call) and pass it to the save/restore function in ES:EDI. Anyway, I'm not sure you need this functionality at all, the current implementation should work OK (except that it needs a dummy protected mode entry point). -- Alexandre Julliard julliard(a)winehq.com

1 0

vxd support?
by Osvaldo Fornaro 22 May '01

22 May '01

Hi, I were far from the project for a while, so sorry if this topic is trivial, but I wish to use a parallel port scanner with wine. Under Windows, appears a device to treat the parallel port as a SCSI port, but is based on a VxD archive, and wine don't find it. Is there any solution to deal with VxD or not yet? Thanks in advance. -- Dr. Osvaldo Fornaro <ofornaro(a)exa.unicen.edu.ar> Universidad Nacional del Centro de la Provincia de Buenos Aires Instituto de Física de Materiales Tandil - CICPBA Pinto 399 (B7000GHG) Argentina

3 3

Question on exposing non-windows functions from dlls...
by Mike Bond 22 May '01

22 May '01

I just submitted a patch to wine-patches that provides the implementation of spawnl and spawnlp. I had been hoping to implement execl and execlp as well but found that the underlying functionality that I would need is not exposed outside scheduler/process.c. My question is what guidelines are there, if any, are there to exposing non-win functions, such as exec_wine_binary in scheduler/process.c? Also, from just a cursory glance at exec_wine_binary that I may need to wrap it to do some of the work that fork_and_exec and PROCESS_Create are doing, such as calling DOSFS_GetFullName. I'm not sure what, if anything, the server would need to know about this. -- TTFN MikeB

3 5

Re: Patch for a bug in server/select.c
by Alexandre Julliard 22 May '01

22 May '01

Bang Jun-Young <bjy(a)mogua.org> writes: > It has been observed that poll always returns POLLNVAL without waiting > when fd is -1. Then we cannot use the current code on NetBSD, otherwise we'll be eating 100% CPU as soon as an fd becomes -1. You'll probably need to do a poll() wrapper that removes the invalid fds before calling the real poll. Or you could ask the NetBSD folks to fix their implementation. -- Alexandre Julliard julliard(a)winehq.com

2 1

history of CVS files?
by Heiko Nardmann 22 May '01

22 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How can I see the history of files in CVS? Is there a WebCVS access provided? Reason: I have a 20010112 version of wine running fine but current CVS version does not start any windows application. - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7CiQypm53PRScYygRAuZsAKDhwkJRltKTFWU8Dtmg4DHIOGkYMwCgsusj Izxj4GqmLT7dYzVkEpZVHjA= =DzY7 -----END PGP SIGNATURE-----

3 2

problem starting winword 97SR2
by Heiko Nardmann 22 May '01

22 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then. So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain? BTW: I use wine 20010112 since the last snapshot 20010418 does not work on my machine (unhandled exception). Here is the last line from the logfile when starting wine with '+reg': trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6d10) - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7COAjpm53PRScYygRAibvAKCXFuh51LK3S//Ber6iQSjgjvrmNwCffRTy MRUAdaCXrhST+oDmu5WHjtg= =2kDj -----END PGP SIGNATURE-----

3 6

Re: Small fixes in controls/menu.c
by gerard patel 22 May '01

22 May '01

At 10:20 AM 20/05/2001 -0700, you wrote: >gerard patel <gerard.patel(a)asi.fr> writes: > >> (patch using NC_HandleNCCalcSize instead of SetWindowPos) >> >> IMO it's better and it solves my problem as well. > >I think the SetWindowPos one was better. If the app handles >WM_NCCALCSIZE we shouldn't try to bypass it. But does Windows send this message in this case ? From what I can see in the traces, I don't think so. Maybe Maciek could look at the behaviour of his app under Windows. Or I could download it and try to solve the problem myself (I'd better not :-/) Gerard

2 1

Re: Wine build failure in tools/winebuild/spec16 due to recent change
by Ove Kaaven 21 May '01

21 May '01

On Mon, 21 May 2001, Marcus Meissner wrote: > Changelog: > In case our stat already supports 64bit operations (like FreeBSD > stat does), we don't need to stub them, we can just define the > x64 functions to x. You know, glibc would also have such an interface if you used the -D_FILE_OFFSET_BITS=64 compilation option. Wouldn't it be simpler to unify the 64-bit interface code by using that?

1 0

Re: warning fixes
by Francois Gouget 21 May '01

21 May '01

On Mon, 21 May 2001, eric pouech wrote: > ChangeLog: fixed a couple of warnings This does not fix the warnings, it just hides the bug. As the comments say, the assignments are plain wrong in the first place. /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__environ = GetEnvironmentStringsA(); + MSVCRT__environ = (char**)GetEnvironmentStringsA(); MSVCRT___initenv = MSVCRT__environ; /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__wenviron = GetEnvironmentStringsW(); + MSVCRT__wenviron = (WCHAR**)GetEnvironmentStringsW(); MSVCRT___winitenv = MSVCRT__wenviron; -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Avoid the Gates of Hell - use Linux.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel May 2001