wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Window refresh problem with GroupBox and Tabs
by George Marshall 21 Oct '03

21 Oct '03

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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

>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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

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 20 Oct '03

20 Oct '03

>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

Asprotected programs crash with current wine-cvs
by Oleg Prokhorov 20 Oct '03

20 Oct '03

Hello Alexandre , current CVS version has regression. All Asprotected (probably) programs crash due to the fact that Asprotect assumes that executables are being loaded from kernel32.dll, so stack return address passed to executable entry (in the other words executable entry was called from kernel32.dll) points to somewhere inside kernel32.dll. Later Asprotect uses this return address to detect kernel32.dll export section and dig it for required kernel32.dll function (LoadModule, VirtualAlloc etc). The problem is that now executable entry loaded under wine is being started from somewhere inside ntdll.dll, so Asprotected kernel32.dll function finding routines fail with crash. I'm not sure what's the best way to solve it, is some ntdll.dll process startup code relocating to kernel32.dll good enough ? -- Best regards, Oleg mailto:xolegpro@rbcmail.ru

1 0

RE: WWN: wn20031017_192.xml
by Brian Vincent (C) 20 Oct '03

20 Oct '03

> Test these lines > BEGIN { FS = "\"" } > { A+=$2 } > { B+=$4 } > END { print "<person posts=\""A"\""" size=\"" B"\""" > who=\""$6"\" />" } Works like a charm! Thanks! --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Re: S3 texture compression patent
by Ivan Leo Murray-Smith 19 Oct '03

19 Oct '03

>But what would that mean for the developers in the US? Just because the >sources are hosted in EU would still render them useless for US developers. No, if you're in the US and publish something in the EU, you aren't violating any US law, as you aren't publising anything in the US. If this isn't the case, the US constitution must have a few bugs in it. This would also mean moving the mailing list archives and the CVS to the EU, but I don't think this will happen, unless you show that there is a patent violation and that wine will never work without violating that patent.

2 1

Re: Setupapi Win16/32 (Again) and PSDK porting fixes
by Gregory M. Turner 19 Oct '03

19 Oct '03

On Saturday 18 October 2003 01:57 pm, Steven Edwards wrote: > With this > patch all of the objects for setupapi.dll can be built on > MS_VC with the PSDK. There are a few minor issues but nothing > to major doesn't this: -typedef struct _CABINET_INFOA { +typedef struct _CABINET_INFO_A { PCSTR CabinetPath; PCSTR CabinetFile; PCSTR DiskName; USHORT SetId; USHORT CabinetNumber; -} CABINET_INFOA, *PCABINET_INFOA; +} CABINET_INFO_A, *PCABINET_INFO_A; -typedef struct _CABINET_INFOW { +typedef struct _CABINET_INFO_W { PCWSTR CabinetPath; PCWSTR CabinetFile; PCWSTR DiskName; USHORT SetId; USHORT CabinetNumber; -} CABINET_INFOW, *PCABINET_INFOW; +} CABINET_INFO_W, *PCABINET_INFO_W; mean we should do this: -DECL_WINELIB_TYPE_AW(CABINET_INFO); -DECL_WINELIB_TYPE_AW(PCABINET_INFO); +DECL_WINELIB_TYPE_AW(CABINET_INFO_); +DECL_WINELIB_TYPE_AW(PCABINET_INFO_); ? -- gmt "class 'SfxPoolCancelManager' only defines a private destructor and has no friends" -- gcc, resorting to unnecessary character attacks

2 3

Re: What does "still could not load module" mean?
by Ivan Leo Murray-Smith 19 Oct '03

19 Oct '03

>Anybody got ideas? You have winealsa.drv in your lib path and artsd is stoped, right?

1 0

Re: S3 texture compression patent
by Ivan Leo Murray-Smith 19 Oct '03

19 Oct '03

>hell, if MS can get a patent on NTFS they can get a >patent on anything. I do remember reading that the WTO decided that APIs aren't patentable.

1 0

PATCH: dlls/x11drv/wineclipsrv.c
by Gerald Pfeifer 19 Oct '03

19 Oct '03

This fixes another problem on my automatic tester's radar. The only user of this array is commented/disabled, so I suggest to either move the array or completely yank it. Gerald ChangeLog: Move event_names[] into EVENT_ProcessEvent(). Index: wineclipsrv.c =================================================================== RCS file: /home/wine/wine/dlls/x11drv/wineclipsrv.c,v retrieving revision 1.4 diff -u -3 -p -r1.4 wineclipsrv.c --- wineclipsrv.c 5 Jul 2002 21:22:09 -0000 1.4 +++ wineclipsrv.c 19 Oct 2003 20:04:32 -0000 @@ -174,20 +174,6 @@ static PCACHEENTRY g_pClipboardCache = N static unsigned long g_cPrimaryTargets = 0; /* Number of TARGETS reported by PRIMARY selection */ static unsigned long g_cClipboardTargets = 0; /* Number of TARGETS reported by CLIPBOARD selection */ -/* Event names */ -static const char * const event_names[] = -{ - "", "", "KeyPress", "KeyRelease", "ButtonPress", "ButtonRelease", - "MotionNotify", "EnterNotify", "LeaveNotify", "FocusIn", "FocusOut", - "KeymapNotify", "Expose", "GraphicsExpose", "NoExpose", "VisibilityNotify", - "CreateNotify", "DestroyNotify", "UnmapNotify", "MapNotify", "MapRequest", - "ReparentNotify", "ConfigureNotify", "ConfigureRequest", "GravityNotify", - "ResizeRequest", "CirculateNotify", "CirculateRequest", "PropertyNotify", - "SelectionClear", "SelectionRequest", "SelectionNotify", "ColormapNotify", - "ClientMessage", "MappingNotify" -}; - - /* * Prototypes */ @@ -805,6 +791,18 @@ void EmptyCache(PCACHEENTRY pCache, int void EVENT_ProcessEvent( XEvent *event ) { /* + static const char * const event_names[] = + { + "", "", "KeyPress", "KeyRelease", "ButtonPress", "ButtonRelease", + "MotionNotify", "EnterNotify", "LeaveNotify", "FocusIn", "FocusOut", + "KeymapNotify", "Expose", "GraphicsExpose", "NoExpose", "VisibilityNotify", + "CreateNotify", "DestroyNotify", "UnmapNotify", "MapNotify", "MapRequest", + "ReparentNotify", "ConfigureNotify", "ConfigureRequest", "GravityNotify", + "ResizeRequest", "CirculateNotify", "CirculateRequest", "PropertyNotify", + "SelectionClear", "SelectionRequest", "SelectionNotify", "ColormapNotify", + "ClientMessage", "MappingNotify" + }; + TRACE(" event %s for Window %08lx\n", event_names[event->type], event->xany.window ); */

1 0

tests for shlfileop.c xp comparsion was done
by Dietrich Teickner 19 Oct '03

19 Oct '03

Hello fellows, Rolf Kabermater (from wine) and I (from Odin) need help. Rolf has written a nice test-programm for many many test-cases (round (45*4+40*2)*8*4) for shlfileop, based on my test-scripts with a one-case test-program for shlfileop. With this faster program we had tested many more cases in w98se and w2k. The problem is, the output is different between w98se and w2k. I had rewritten the shlfileop, and we can simulate shlfileop.c as w98se or w2k. We will mad this test also with w-Me and w-Xp. Some test are also done with nt40 sp6, there works shfileoperation only in simpy cases without confusions. We will not emulate the many errors. We need one testoutput from Rolf's testshfop.exe produced in a w-Me and one in a w-Xp environment. The testprogamm is round 50k big and the log about stdout will be 2,1mb. for the test we need 2 drive-letters, Rolf assumed C:\t\ and D:\t\ for his tests. If anyone will know more about, he can mail me. I can send him\her the (w98se,w2k) logs and the progam, with a short description. I Runs this w-program also in Odin-environment. We need only the wMe log. Regards Dietrich

1 0

Re: Partially implement advapi.ReportEvent
by Dimitrie O. Paun 19 Oct '03

19 Oct '03

On October 19, 2003 07:58 am, Mike Hearn wrote: > This implementation is obviously not complete, but it prints out the > event log strings using MESSAGE, which is good enough for now. Another option is to create a new debug channel (call it eventlog) and output to it. This way we give people a bit more control over it, and it fits a bit better with the rest of the messages. -- Dimi.

1 0

soldat
by Pavel S. Khmelinsky 19 Oct '03

19 Oct '03

Hi! I try to run Soldat by wine and failed ( strange isn't it? :) ) U can found this game at http://www.soldat.prv.pl/ . Thats some listing: --------------------------------------------------------------- $ winedbg --debugmsg +loaddll Soldat.exe fixme:win32:PE_CreateModule Unknown directory 15 ignored trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\kernel32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\advapi32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\user32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\rpcrt4.dll' : native trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\ole32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\oleaut32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\comctl32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\shlwapi.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\shell32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\winspool.drv' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\comdlg32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\ddraw.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\d3d8.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\Soldat\D3DX81ab.dll' : native trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\winmm.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\msacm32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\msvcrt.dll' : native trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\Soldat\fmod.dll' : native trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\ws2_32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\winnt\system32\wsock32.dll' : builtin trace:loaddll:MODULE_LoadModule16 Loaded module 'krnl386.exe' : builtin trace:loaddll:MODULE_LoadModule16 Loaded module 'system' : builtin trace:loaddll:MODULE_LoadModule16 Loaded module 'wprocs' : builtin trace:loaddll:MODULE_LoadModule16 Loaded module 'GDI.EXE' : builtin err:font:AddFontFileToList Unable to load font file "/usr/sto/wine/winnt/Fonts/desktop.ini" err = 55 err:font:AddFontFileToList Unable to load font file "/usr/sto/wine/winnt/Fonts/modern.fon" err = 2 err:font:AddFontFileToList Unable to load font file "/usr/sto/wine/winnt/Fonts/roman.fon" err = 2 err:font:AddFontFileToList Unable to load font file "/usr/sto/wine/winnt/Fonts/script.fon" err = 2 trace:loaddll:MODULE_LoadModule16 Loaded module 'USER.EXE' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\WINNT\SYSTEM32\x11drv.dll' : builtin trace:loaddll:MODULE_LoadModule16 Loaded module 'display' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\WINNT\SYSTEM32\WINEPS.dll' : builtin fixme:psdrv:PSDRV_BITMAP_SelectObject stub fixme:psdrv:PSDRV_BITMAP_SelectObject stub fixme:psdrv:PSDRV_BITMAP_SelectObject stub trace:loaddll:MODULE_LoadModule16 Loaded module 'commdlg.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\WINNT\SYSTEM32\d3dgl.dll' : builtin wine: Unhandled exception, starting debugger... --------------------------------------------------------------- This is that I cut from listing when try +relay: --------------------------------------------------------------- 08075ee8:Call(1) kernel32.VirtualAlloc(019f0000,00010000,00001000,00000004) ret=779bd4e5 08075ee8:Ret (1) kernel32.VirtualAlloc() retval=019f0000 ret=779bd4e5 08075ee8:Call(1) kernel32.InitializeCriticalSection(77a39098) ret=779bd60a 08075ee8:Ret (1) kernel32.InitializeCriticalSection() retval=00000000 ret=779bd60a 08075ee8:Call(1) kernel32.InitializeCriticalSection(77a390c8) ret=779bd613 08075ee8:Ret (1) kernel32.InitializeCriticalSection() retval=00000000 ret=779bd613 08075ee8:Call(1) kernel32.InitializeCriticalSection(77a390b0) ret=779bd61c 08075ee8:Ret (1) kernel32.InitializeCriticalSection() retval=00000000 ret=779bd61c 08075ee8:Call(1) kernel32.InitializeCriticalSection(77a39080) ret=779bd624 08075ee8:Ret (1) kernel32.InitializeCriticalSection() retval=00000000 ret=779bd624 08075ee8:Call(1) kernel32.TlsAlloc() ret=779bd5a3 08075ee8:Ret (1) kernel32.TlsAlloc() retval=00000002 ret=779bd5a3 08075ee8:Call(1) ntdll.RtlEnterCriticalSection(77a390b0) ret=779bcf26 08075ee8:Ret (1) ntdll.RtlEnterCriticalSection() retval=00000000 ret=779bcf26 08075ee8:Call(1) ntdll.RtlLeaveCriticalSection(77a390b0) ret=779bd059 08075ee8:Ret (1) ntdll.RtlLeaveCriticalSection() retval=00000000 ret=779bd059 08075ee8:Call(1) kernel32.TlsSetValue(00000002,019f0100) ret=779bd5d4 08075ee8:Ret (1) kernel32.TlsSetValue() retval=00000001 ret=779bd5d4 08075ee8:Call(1) kernel32.GetCurrentThreadId() ret=779bd5eb wine: Unhandled exception, starting debugger... --------------------------------------------------------------- Does it mean that expeption is generatated by any command in GetCurrentThreadId() or not? Then I try to debug it I see someting like that: --------------------------------------------------------------- WineDbg starting on pid 8072568 Unhandled exception: page fault on read access to 0x00000076 in 32-bit code (0x0021b960). In 32-bit mode. 0x0021b960 (KERNEL32.DLL.SetComputerNameA+0x2c): arpl 0x75(%edi),%bp --------------------------------------------------------------- Is it mean that I should to search problem in SetComputerNameA or not? Can you give me some advice how to gather some more information and there I should to search in wine source to solve my problem. And I want to learn how to debug wine may be you can advice me some articles, that I should to read? P.S.: Sorry for my English, I try to state understandable.

2 1

a proposal that will affect MingW-Runtime, w32api, ReactOS and WINE
by Jonathan Wilson 19 Oct '03

19 Oct '03

Currently, we have 3 different projects that are working towards windows "compatibility". We have ReactOS We have WINE and We have MingW-Runtime and w32Api (refered to as just MingW from now on) The 3 projects have different goals but the same target. Microsoft Windows and the Microsoft SDK, DDK and compiler. All 3 projects are working in some way to be compatible with those. All 3 projects have their own set of header & library files including windows SDK headers like windows.h, MSVCRT headers like stdlib.h or stdio.h and (to some extent) ddk headers like ntddk.h The first part of what I am proposing is that the 3 sets of headers be "merged" to create a new "SDK/DDK" for building windows apps. This SDK would contain: 1.a new set of windows headers and libraries (windows.h and friends) built up from a combination of ReactOS headers, WINE headers and w32api headers. They would be (with the help of MSDN) designed to be as close to the microsoft headers as possible (in so far as where things are declared e.g. if abc is in def.h on MS SDK, put it in def.h in this new SDK). This set of headers and libraries would be used: A.by MingW users for windows programming and development B.by the reactos team to build ReactOS C.by the WINE team to build WINE and D.by people building apps with WINELIB. 2.same as 1 but for MSVCRT.dll/MSVCRT.lib and would be used by WINE, MingW and ReactOS. It would endevour to provide 100% coverage of what the MS runtime provides in its MSVCRT.dll as well as all the glue code in MSVCRT.lib (like the Thread Local Storage stuff I made) It would be used by MingW developers to write for win32, by ReactOS to build their OS and their clone of msvcrt.dll and by WINE to build WINE and its clone of msvcrt.dll (which would be the same one as the ReactOS clone, see below) 3.same as 1 but for winddk.h & friends (i.e. kernel mode ddk). Would be used by MingW for kernel-mode development should anyone want to do that. Also, it would be used by WINE for anything kernel-mode that is needed And by ReactOS to build the kernel and kernel drivers. In addition, there would be additions to the libraries plus new header files for all 3 items (SDK, MSVCRT and DDK) that would include any "undocumented by MS but documented by someone else" functions. One thing to remember is that just because they are undocumented doesnt mean that Microsoft (or even 3rd parties that have documentation/headers/code that isnt "genreally available) hasnt used them. The new "SDK" could contain features designed with the different projects in mind. For example, ReactOS core modules could be built with a flag that would tell the headers not to define the "generic" versions of ansi/unicode functions. But application developers could build with this flag off. And so on. A specific "ReactOS SDK" wouldnt exist since this new SDK would do it all. The 3 existing sets of header/library files (i.e. WINE headers, MingW-Rintime/W32api and ReactOS headers) would be thrown away and replaced with this new SDK. Internal stuff (i.e. stuff thats internal to ReactOS or internal to WINE and is not visible to userland apps or to kernel drivers) would go in their own internal header files, as needed by each project. Also, Now on to the other part of my proposal, code sharing between ReactOS and WINE. Basicly, ReactOS (and to some extent WINE) is divided up into 5 parts: 1.kernel (ntoskrnl.exe, hal.dll, win32k.sys etc) 2.kernel drivers (mouclass.sys, ndis.sys, vga.sys, videoprt.sys etc) 3.userland core (user32.dll, gdi32.dll, kernel32.dll, ntdll.dll and any other userland dll that makes calls to kernel-mode without going via one of those 4 dlls) 4.support components (the system services etc) and 5.other dlls and apps (like comctl32.dll, comdlg32.dll, shell32.dll, msvcrt.dll, crtdll.dll, ole32.dll etc) My view is that: A.where possible components 2 and 4 should be designed to work on windows as well as on ReactOS B.sharing parts of component 3 (specificly some of the user32 stuff) does make sense and should be done in a way thats clean in that the "shared" code doesnt rely on any of the internals of WINE or ReactOS and only calls "published" APIs (i.e. regular user32 or gdi32 calls). For example, the MessageBox code can be implemented on top of the Dialog Box api and so on. C.as for component 5, we should implement one and only one copy of those dlls. They should only use published APIs and should work "out of the box" on Windows, ReactOS and WINE when compiled with the new "SDK" mentioned above. DLLs that talk to kernel mode (such as winmm talking to the sound driver or winsock talking to networking) should certainly be implemented so that they will work OOB on both windows and ReactOS (since we are supporting 3rd party drivers in ReactOS anyway we need to implement the "glue" between e.g. winmm and the driver in the same way MS did). WINE is a different issue, mabie they can just implement something in their kernel/ntdll that "appears" to e.g. winmm like the sound driver, I dont know. Ideally, WINE, ReactOS and w32api/MingW-Runtime should be designed to be as alike to Windows and Microsoft SDK as possible. (including those bits of code that are shared between the projects)

3 3

Re: [ros-kernel] Proposed ReactOS headers and code sharing policy
by Eric Kohl 19 Oct '03

19 Oct '03

"Vizzini" <vizzini(a)plasmic.com> wrote: > Executive Summary > ----------------- > - Use MinGW for all public interface headers, i.e. everything that > MinGW supports > - Use non-OS-specific Wine libraries unmodified > - Use portions of OS-specific Wine libraries (e.g. user32) > - Keep it all straight with CVS vendor branches > > Details > ------- > For headers, we will use MinGW as our external interface in all cases > that MinGW supports, including kernel-mode code (i.e. the DDK). We will > submit patches to MinGW when we find problems with the public > interfaces. There is the added benefit of having a compatibility check > against our public interface. One important detail was missing from the discussion. Kernel-mode and native code (ntdll, smss, etc.) does _not_ know about Win32 types, like BYTE, WORD, DWORD, INT, UINT or the LP* types. Unfortunately, the use of these types does not cause any trouble because of the braindead mix of SDK and DDK headers. Actually, we need three different sets of headers: Kernel-mode headers which include all definitions used in ntoskrnl and drivers, native-mode headers which include only the Nt/Zw/Rtl functions used in ntdll and other native components and finally Win32 headers which include the remaining stuff. > We will continue to maintain our own internal headers for anything that > doesn't belong in the public headers. We will begin to port our > kernel-mode code to use the MinGW DDK headers, maintaining our internal > headers for non-public things. Component-internal headers should be moved into the component directory (<component_path>/<header_name>.h) or into a component-specific include directory (<component_path>/include/<header_name>.h). They should always be added to a .c file by using '#include "..."'. Non-public headers which are shared by components (the csrss-subsystem communication protocol for example) should be treated as public headers, they become part of the SDK, DDK or native headers but are not shared between projects. > The first class of libraries is more difficult. Some chunks of code > will be used unmodified, ideally on a file-by-file basis. Other chunks > of code will have to be ReactOS-specific, and we will maintain those in > our local tree. If Wine ever chooses to merge our changes, that's fine > too, but it certainly won't be required. If code is ported from Wine to ReactOS, we have to make sure it will be adjusted to the ReactOS/MS style. I do not like to see any Wine-isms/Unix-isms in ntdll/ntoskrnl or a driver because this will become a portability issue sooner or later. Another issues are licenses and copyrights. IMO, public headers and import libraries should not be licensed or copyrighted at all. They should be in the public domain, so anybody can use them the way they want. Wine code is published under the LGPL, which is important because of Winelib. ReactOS on the other hand should use a clean mix of licenses: GFDL for the documentation, public domain for public headers and import libraries and GPL for the internal code. We should establish a GPL/LGPL dual-license agreement so that shared code automatically changes its license when it is moved from ReactOS to Wine or vice versa. Regards, Eric Kohl

2 1

Re: [ComCtl32] Fix ownerdraw tab width
by Maxime Bellengé 19 Oct '03

19 Oct '03

Alexandre, please don't apply this patch (but you can apply my previous one). After talking with Vitaliy, it seems this patch is not the right fix. I'll send a new one later. Max On Sat, 2003-10-18 at 11:57, Maxime Bellengé wrote: > This patch fixes a regression introduced by last Vitaliy Margolen patch. > The ownerdraw tabs were no longer sized correctly. > > Changelog: > * Fix ownerdraw tabs sizing. -- Maxime Bellengé <maxime.bellenge(a)laposte.net>

1 0

Fwd: Re: [ros-kernel] Re: WINE porting templates
by Steven Edwards 18 Oct '03

18 Oct '03

So are you interested in helping to implement this? The WINE project has started a uxtheme.dll It would be nice if we could agree on a common theme system for both projects. Thanks Steven Note: forwarded message attached. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 0

International settings for language resources
by Rolf Kalbermatter 18 Oct '03

18 Oct '03

I want to test the loading of non-english string resources in some Wine application and just started to wonder what I have to change in which configuration file to cause LoadString() to attempt to load another language resource first before it eventually resolves to loading the english one? Anyone can help here? Rolf Kalbermatter

2 1

Jump to page:

2025

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