- Wine-Devel - list.winehq.org

Window refresh problem with GroupBox and Tabs
by George Marshall Oct. 21, 2003

Oct. 21, 2003

Hi I've already submitted this bug to the wine bugzilla but I'm posting it here as well 'cause... oh well you know. Pls. look at the end of the message for .gifs Bug 1689 follows: I've got an application which purpose is to just reproduce the wine bug I'm gonna explain below. There is, basically, a window, a tab control with four tabs, some GroupBoxes and a few editboxes. (Please, see the attached .gif to get an idea). Here we go with the interesting part... If you run the application you'll realize that some editboxes are not drawn at all and some other not correctly drawn (Expecially if you go through the tabs...) Now if you minimize and then raise this window or drag part of it out of the screen and then back in, everything in it is correctly "painted". The pic tabwin_ok.gif shows the application correctly drawn, while in tabwin_bad.gif you'll see the application in its bad behavior (Like described above). Another interesting thing to note is that if you go through the tabs backward( from the last one to the first one ) the window contents is correctly drawn, not if you go from the first tab to the last one. This is always reproducible. This bug is 100% reproducible with Wine 20030813, 20030709, 20030618 (the versions I could work with...) I'm actually trying to fix this by myself (an ugly workaround will do the job as well) but any help to get me to the right direction will be appriciated. You're more than welcome to ask for any debug or strace log. Thanks. http://bugs.winehq.org/attachment.cgi?id=359&action=view http://bugs.winehq.org/attachment.cgi?id=360&action=view

2 2

Re: will it?
by Ivan Leo Murray-Smith Oct. 20, 2003

Oct. 20, 2003

Wine can't load windows drivers. This may be possible in a very very far future, but it would probably be easier to write native drivers. Probably by the time wine can do such a thing, all hardware vendors will support linux anyway.

1 0

import and export tables
by Dave Miller Oct. 20, 2003

Oct. 20, 2003

A .tar.gz containing HTML tables of imports and exports for windows dlls is now available here: http://24.229.94.2/import_export_tables.tar.gz It is about 1MB but it will decompress to 1000+ html files and 58MB! I have not included empty tables where a dll does not import or export any functions. If you spot a missing windows dll, or a non-windows dll please let me know so I can add/remove as necessary. Of course feature requests are welcome as well. ------------------------------------- So many Right-wing Christians. So few lions.

1 0

Re: [ros-kernel] about headers
by Steven Edwards Oct. 20, 2003

Oct. 20, 2003

This is really the heart of the issue. Can we work out a system that will work for all projects involved? What I am about to bring up is not the same issues that Danny has with GCCisms but it has made me think about our build system again. WINE and Mingw both make use of some of the aspects of the GNU toolchain that ReactOS currently does not. I think I have a more simple solution to our problem but most of the ReactOS will not like it. Currenly the ReactOS project has a bad habit of importing libraries that we need such as zlib and freetype in to our funky build system. Then on top of that you heep on the problems of trying to support the w32api and WINE and you get the current cluster-fu*k we have now. 1. Create vendor branches for w32api, WINE and other projects that ReactOS needs. - Now the question becomes how do we structure this? If we use the w32api with the SDK/DDK then we can import it in to the WINE source tree just as we have done with freetype and zlib. 2. Can we import a vendor branch in to CVS under a existing repostory? - If the answer is yes then we do we need to import the whole WINE sourcetree only selected DLL and Programs. 3a. If we can do all of this then do we switch to a GNU configure system so we can configure all of the modules at compile time and dump our funky build system? - I am thinking a layout like this: /CVSROOT /reactos configure /contrib /w32api/configure /freetype/configure /OpenSSL/configure /zlib/configure /WINE/configure /dlls /programs /libs 3b. Or do we leave CVS like it is now? and maybe move the external libs to there own modules where we can Vendor branch them? - Moving to a GNU configure system would still make it easy on us. The only thing is we would need to create a set of import scripts for branching/merging and move the external libs to there own module CVSROOT/ /reactos /rosapps /WINE /support /w32api /freetype /zlib /openssl Ok I am sorry I have taken the discussion beyond headers but we have to find a solution that will work. Is w32api that solution? Does out current build system do everything we need to be able to scale? How does KDE or GNOME handle this? Thanks Steven --- Danny Smith <dannysmith(a)clear.net.nz> wrote: > As far as the mingw runtime headers are concerned, you will have a > hard > time convincing me to remove all the ISO C99 extras. You will also > have > a hard time convincing me that removal of all the POSIX-isms is a > good > thing, since they really assist building of things like binutils, > gcc, > libiconv, gettext, make, etc. > > As someone who has had input into the maintenace of gcc compiler > suppor > for mingw, > the hardest things to maintain are the MS-extensions (dllimport being > the worst because of the ambiguity of the syntax). Adherence to the > MS > "gold standard" has meant that mingw is forced to use sjlj exceptions > rather than DWARF2. > > Personally, I would prefer that mingw gcc/binutils move closer to > theFSF > mainstream > rather than drifting from it. Likewise, I would prefer that mingw > runtime moves in dirction towards ISO C, C++ conformance (eg, make > the C > headers namespace aware when in C++) rather than towards MS > conformance. > > Speaking for myself only. > > Danny __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

3 4

Re: ReactOS GPL vs. proprietary drivers - NTFS Driver under Linux + WINE
by Steven Edwards Oct. 20, 2003

Oct. 20, 2003

Hello Jan, Comments are inline. --- Jan Kratochvil <rcpt-ros-kernel.AT.reactos.com(a)jankratochvil.net> wrote: > Hi, > > As GPLed Linux-NTFS still has no NTFS r/w capability I completed the > project > for reliable r/w access in Wine way by using MS-Windows ntfs.sys > driver. > > Captive-NTFS > http://www.jankratochvil.net/ I have forwarded this reply to wine-devel as they my find captive NTFS interesting > My project is GPL-2.0 and it incorporates ReactOS kernel sources > currently also > carrying GPL-2.0 license. There are rumours GPL may be problem for > linking with > proprietary code (ntfs.sys&ntoskrnl.exe). I interpret it as GPL only > affects > _distribution_ of the program while no proprietary code is > distributed with my > package. Proprietary code is only run-time linked by the end-user. > > > In a GPL-related discussion here two monts ago ReactOS developers > were open for > reusal of existing proprietary drivers for ReactOS as one of the > significant > feature of ReactOS. I would like an affirmation from the major > ReactOS > developers they are not going to try to sue me for releasing Captive > NTFS. I dont think you have to worry about any ReactOS developers filing suit. I would be more worried about one from Microsoft =). In fact I am very happy to see this. I would like to see the interface you have developed evolve in to a a full compatiblty layer addon for WINE so they can support other drivers. I must confess I have not had a chance to look at the code but if it works as you say then this is great news! If you dont distribute Captive NTFS with a Microsoft NTFS driver then you should not have a problem. You are correct the GPL seems to only cover distribution not use. Thanks Steven __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 0

will it?
by John Smith Oct. 20, 2003

Oct. 20, 2003

now that windows drivers will work in linux, can wine run directx easy? with wine on linux, and having windows drivers, the wine shouldn't have any troubles whatsoever acting as windows

1 0

Re: MDI windows, MDIClient and mdiclient
by Fabian Cenedese Oct. 20, 2003

Oct. 20, 2003

>I'm trying to see why a propritery program misbehaves under wine, by comparing it to Windows. When running it under Windows, I don't have the luxury of OutputDebugString. Maybe even better: http://www.codeproject.com/useritems/DLL_Injection_tutorial.asp Already with a sample about logging winsock functions. bye Fabi

1 0

Re: named pipes problem?
by Alexandre Julliard Oct. 20, 2003

Oct. 20, 2003

Daniel Marmier <d.marmier(a)bluewin.ch> writes: > Are you talking about support for TLS in wine? > If so, is that already assigned? No, the problem is TLS support in glibc itself, since that bypasses our pthread wrappers. We don't need to use glibc-style TLS in Wine since we can use the Win32 TLS support instead. -- Alexandre Julliard julliard(a)winehq.com

2 1

named pipes problem?
by Gregory M. Turner Oct. 20, 2003

Oct. 20, 2003

Does everybody's kernel32 named pipes test pass (in wine)? Named pipes are acting very wierd here, lots of segfaults and other wierdness... the test seems to freeze attempting to create the alarmThread in test_NamedPipe_2 (test 3 of 4). The wineserver holds up OK, but the client side looks a mess. This is similar to other behavior I see in other contexts... perhaps, the pattern is, after I create a named pipe, subsequent calls to CreateThread never return or cause segfaults and general instability. Am I the only one? The following is a snippet from "strace -f wine kernel32_test.exe.so pipe" where wine starts to go south.... [pid 28568] write(1, "pipe.c:459:", 11pipe.c:459:) = 11 [pid 28568] write(1, "exercizeServer starting\n", 24exercizeServer starting ) = 24 [pid 28568] write(1, "pipe.c:470:", 11pipe.c:470:) = 11 [pid 28568] write(1, "Client connecting...\n", 21Client connecting... ) = 21 [pid 28568] rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM IO], [RTMIN], 8) = 0 [pid 28568] writev(4, [{"\207\0\0\0\222\0\0\0\0\0\0\0\0\0\0\300\0\0\0\0\0\0\0\0"..., 64}, {"\\\0\\\0.\0\\\0P\0i\0P\0e\0\\\0t\0e\0s\0t\0s\0_\0.\0"..., 146}], 2 <unfinished ...> [pid 28570] <... poll resumed> [{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=13, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN, revents=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=24, events=POLLIN}, {fd=23, events=POLLIN}], 16, -1) = 1 [pid 28570] read(16, "\207\0\0\0\222\0\0\0\0\0\0\0\0\0\0\300\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 28570] read(16, "\\\0\\\0.\0\\\0P\0i\0P\0e\0\\\0t\0e\0s\0t\0s\0_\0.\0"..., 146) = 146 [pid 28570] write(17, "\17\0\0\300\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 28570] poll( <unfinished ...> [pid 28568] <... writev resumed> ) = 210 [pid 28568] read(5, "\17\0\0\300\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 28568] rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 [pid 28568] write(1, "pipe.c:481:", 11pipe.c:481:) = 11 [pid 28568] write(1, "connect failed, retrying\n", 25connect failed, retrying ) = 25 [pid 28568] gettimeofday({1066424342, 296207}, NULL) = 0 [pid 28568] gettimeofday({1066424342, 296363}, NULL) = 0 [pid 28568] select(0, NULL, NULL, NULL, {0, 199844} <unfinished ...> [pid 28575] --- SIGSTOP (Stopped (signal)) @ 0 (0) --- [pid 28574] --- SIGSTOP (Stopped (signal)) @ 0 (0) --- [pid 28575] modify_ldt(17, {entry_number:40, base_addr:0x40af3000, limit:4095, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:0}, 16 <unfinished ...> [pid 28574] modify_ldt(17, {entry_number:39, base_addr:0x408c3000, limit:4095, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:0}, 16 <unfinished ...> [pid 28575] <... modify_ldt resumed> ) = 0 [pid 28574] <... modify_ldt resumed> ) = 0 [pid 28575] sigaltstack({ss_sp=0x408d1000, ss_flags=0, ss_size=1048576} <unfinished ...> [pid 28574] brk(0 <unfinished ...> [pid 28575] <... sigaltstack resumed> , NULL) = 0 [pid 28574] <... brk resumed> ) = 0x3c009000 [pid 28575] rt_sigaction(SIGINT, {0x40081bf2, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] brk(0x3c00a000 <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... brk resumed> ) = 0x3c00a000 [pid 28575] rt_sigaction(SIGFPE, {0x40081b76, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] sigaltstack({ss_sp=0x406a1000, ss_flags=0, ss_size=1048576} <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... sigaltstack resumed> , NULL) = 0 [pid 28575] rt_sigaction(SIGSEGV, {0x40081aa4, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] rt_sigaction(SIGINT, {0x40081bf2, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28575] rt_sigaction(SIGILL, {0x40081aa4, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] rt_sigaction(SIGFPE, {0x40081b76, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... rt_sigaction resumed> NULL, 8) = 0 from there it just degrades into a soup of SIGSEGV and rt_sigprocmask(), like: [pid 28575] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28574] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28575] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28574] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28575] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28574] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28575] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28574] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28575] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28574] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28575] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28574] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28575] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28574] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28575] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> this never ends. Attaching to various threads (when I am so lucky as to be able to) is not very instructive (to me ;)). -- gmt

3 6

Re: S3 texture compression patent
by Ivan Leo Murray-Smith Oct. 20, 2003

Oct. 20, 2003

>Is it a patent for a hrdware solution, or for software? If software then in >Europe, at least in Germany and others, it wouldn't matter because >softwarepatents are not possible (and hopefully never will). Software patents are illegal in all the EU, and it will stay like that thanks to the latest copyright directive, the EUCD. Also, this thread should be on wine-license. It wouldn't be hard to host wine in the EU, codeweavers can just get some host space from any EU hoster, and set up and publish remotely.

3 3