wine-devel

wine-devel@winehq.org

3 participants
84471 discussions

Patch: winemaker-options
by Martin Wilck 06 Sep '02

06 Sep '02

This patch fixes winemaker's annoying habit to insist on --mfc even if --nomfc was specified, and adds an option to not add any DLLs automatically. Patch: winemaker-options.diff Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> Modified files: tools: winemaker - fix --nomfc option which is currrently broken - add --nodlls option for small apps This patch is incremental over Francois Gouget's latest winemaker patch: http://www.winehq.com/hypermail/wine-patches/2002/09/0028.html and my previous patch (winemaker-bugs.diff) --- CVS/wine/tools/winemaker Fri Sep 6 17:35:39 2002 +++ TMP/wine/tools/winemaker Fri Sep 6 17:36:46 2002 @@ -234,6 +234,14 @@ my $TF_MFC=4; ## +# User has specified --nomfc option for this target or globally +my $TF_NOMFC=8; + +## +# --nodlls option: Do not use standard DLL set +my $TF_NODLLS=16; + +## # Initialize a target: # - set the target type to TT_SETTINGS, i.e. no real target will # be generated. @@ -436,23 +444,37 @@ push @{@$target[$T_LIBRARY_PATH]},$option; } elsif ($option =~ /^-l/) { push @{@$target[$T_LIBRARIES]},"$'"; - } elsif (@$target[$T_TYPE] != $TT_DLL and $option =~ /^--wrap/) { - @$target[$T_FLAGS]|=$TF_WRAP; - } elsif (@$target[$T_TYPE] != $TT_DLL and $option =~ /^--nowrap/) { - @$target[$T_FLAGS]&=~$TF_WRAP; - } elsif ($option =~ /^--mfc/) { - @$target[$T_FLAGS]|=$TF_MFC; + } elsif ($option =~ /^--wrap/) { if (@$target[$T_TYPE] != $TT_DLL) { @$target[$T_FLAGS]|=$TF_WRAP; + } else { + print STDERR "warning: option --wrap is illegal for DLLs - ignoring"; + }; + } elsif ($option =~ /^--nowrap/) { + if (@$target[$T_TYPE] != $TT_DLL) { + @$target[$T_FLAGS]&=~$TF_WRAP; + } else { + print STDERR "warning: option --nowrap is illegal for DLLs - ignoring"; } + } elsif ($option =~ /^--mfc/) { + @$target[$T_FLAGS]|=$TF_MFC; + @$target[$T_FLAGS]&=~$TF_NOMFC; } elsif ($option =~ /^--nomfc/) { @$target[$T_FLAGS]&=~$TF_MFC; - @$target[$T_FLAGS]&=~($TF_MFC|$TF_WRAP); + @$target[$T_FLAGS]|=$TF_NOMFC; + } elsif ($option =~ /^--nodlls/) { + @$target[$T_FLAGS]|=$TF_NODLLS; } else { print STDERR "error: unknown option \"$option\"\n"; return 0; } } + if (@$target[$T_TYPE] != $TT_DLL && + @$target[$T_FLAGS] & $TF_MFC && + !(@$target[$T_FLAGS] & $TF_WRAP)) { + print STDERR "info: option --mfc requires --wrap"; + @$target[$T_FLAGS]|=$TF_WRAP; + } return 1; } @@ -543,7 +565,7 @@ } elsif ($dentry =~ /\.c$/i and $dentry !~ /\.spec\.c$/) { push @sources_c,"$dentry"; } elsif ($dentry =~ /\.(cpp|cxx)$/i) { - if ($dentry =~ /^stdafx.cpp$/i) { + if ($dentry =~ /^stdafx.cpp$/i && !(@$project_settings[$T_FLAGS] & $TF_NOMFC)) { push @sources_misc,"$dentry"; @$project_settings[$T_FLAGS]|=$TF_MFC; } else { @@ -553,7 +575,7 @@ push @sources_rc,"$dentry"; } elsif ($dentry =~ /\.(h|hxx|hpp|inl|rc2|dlg)$/i) { push @sources_misc,"$dentry"; - if ($dentry =~ /^stdafx.h$/i) { + if ($dentry =~ /^stdafx.h$/i && !(@$project_settings[$T_FLAGS] & $TF_NOMFC)) { @$project_settings[$T_FLAGS]|=$TF_MFC; } } elsif ($dentry =~ /\.dsp$/i) { @@ -779,7 +801,11 @@ # which we don't have in Wine. Also I add ntdll which seems # necessary for Winelib. my @std_dlls=qw(advapi32.dll comdlg32.dll gdi32.dll kernel32.dll ntdll.dll odbc32.dll ole32.dll oleaut32.dll shell32.dll user32.dll winspool.drv); - @$target[$T_DLLS]=\@std_dlls; + if (@$target[$T_FLAGS] & $TF_NODLLS == 0) { + @$target[$T_DLLS]=\@std_dlls; + } else { + @$target[$T_DLLS]=[]; + } push @{@$project[$P_TARGETS]},$target; # Ask for target-specific options @@ -2169,7 +2195,7 @@ print STDERR "Usage: winemaker [--nobanner] [--backup|--nobackup] [--nosource-fix]\n"; print STDERR " [--lower-none|--lower-all|--lower-uppercase]\n"; print STDERR " [--lower-include|--nolower-include]\n"; - print STDERR " [--guiexe|--windows|--cuiexe|--console|--dll]\n"; + print STDERR " [--guiexe|--windows|--cuiexe|--console|--dll|--nodlls]\n"; print STDERR " [--wrap|--nowrap] [--mfc|--nomfc]\n"; print STDERR " [-Dmacro[=defn]] [-Idir] [-Pdir] [-idll] [-Ldir] [-llibrary]\n"; print STDERR " [--interactive] [--single-target name]\n"; @@ -2182,9 +2208,6 @@ exit (2); } - -project_init(\@main_project,""); - while (@ARGV>0) { my $arg=shift @ARGV; # General options @@ -2245,11 +2268,13 @@ $opt_flags&=~$TF_WRAP; } elsif ($arg eq "--mfc") { $opt_flags|=$TF_MFC; - $opt_flags|=$TF_MFC|$TF_WRAP; $needs_mfc=1; } elsif ($arg eq "--nomfc") { - $opt_flags&=~($TF_MFC|$TF_WRAP); + $opt_flags&=~$TF_MFC; + $opt_flags|=$TF_NOMFC; $needs_mfc=0; + } elsif ($arg eq "--nodlls") { + $opt_flags|=$TF_NODLLS; # Catch errors } else { @@ -2264,6 +2289,11 @@ usage(); } } + + if ($opt_flags & $TF_MFC && $opt_target_type != $TT_DLL) { + print STDERR "info: option --mfc requires --wrap\n"; + $opt_flags |= $TF_WRAP; + }; } if (!defined $opt_work_dir) { @@ -2279,6 +2309,8 @@ print_banner(); } +project_init(\@main_project,""); + # Fix the file and directory names fix_file_and_directory_names("."); -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

1 0

Winelib apps containing upper case letters don't run
by Martin Wilck 06 Sep '02

06 Sep '02

The patch below fixes a problem introduced August 14 (process.c 1.196): Names of "builtin" apps (into which category fall also Winelib apps) aren't found if they aren't lowercase-only. Explanation: Create a directory "Test" and there a file foo.cpp like this: #include <iostream.h> int main (void) { cout << "Hello world!" <<endl; return 0; } In the "Test" directory, run $ winemaker --cuiexe .; ./configure; make; ./Test => error. This fails because the "Test" shell script (aka "wineloader") calls "wine Test.exe", and this ends up searching "test.exe.so" in the DLL path. My patch below fixes that, but I'm not sure if it is the right thing to do. Perhaps wineloader should simply look for "Test.exe.so" rather than for "Test.exe". This is only one of several problems I have with the current winelib/winemaker. Martin Patch: process.diff Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> scheduler: process.c open_builtin_exe_file(): Allow running Winelib apps whose names contain upper case letters. Index: scheduler/process.c =================================================================== RCS file: /home/wine/wine/scheduler/process.c,v retrieving revision 1.198 diff -u -r1.198 process.c --- scheduler/process.c 27 Aug 2002 01:13:59 -0000 1.198 +++ scheduler/process.c 6 Sep 2002 12:05:17 -0000 @@ -265,11 +265,15 @@ { char exename[MAX_PATH], *p; const char *basename = get_basename(name); + void *dll = NULL; if (strlen(basename) >= sizeof(exename)) return NULL; strcpy( exename, basename ); for (p = exename; *p; p++) *p = FILE_tolower(*p); - return wine_dll_load_main_exe( exename, error, error_size, test_only ); + dll = wine_dll_load_main_exe( exename, error, error_size, test_only ); + if (!dll) + dll = wine_dll_load_main_exe( basename, error, error_size, test_only ); + return dll; } -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

1 0

Re: Comctrl generic notification support
by Andreas Mohr 06 Sep '02

06 Sep '02

Hi, On Thu, Sep 05, 2002 at 01:54:50PM -0400, Dimitrie O. Paun wrote: > ChangeLog > Add generic notification support to comctl32 > > Index: dlls/comctl32/comctl32.h > =================================================================== > RCS file: /var/cvs/wine/dlls/comctl32/comctl32.h,v > retrieving revision 1.16 > diff -u -r1.16 comctl32.h > --- dlls/comctl32/comctl32.h 31 May 2002 23:25:43 -0000 1.16 > +++ dlls/comctl32/comctl32.h 5 Sep 2002 17:33:49 -0000 > @@ -4,6 +4,7 @@ > * > * Copyright 1999 Thuy Nguyen > * Copyright 1999 Eric Kohl > + * Copyright 2002 Dimitrie O. Paun > * > * This library is free software; you can redistribute it and/or > * modify it under the terms of the GNU Lesser General Public > @@ -23,6 +24,8 @@ > #ifndef __WINE_COMCTL32_H > #define __WINE_COMCTL32_H > > +#include "commctrl.h" > + > extern HMODULE COMCTL32_hModule; > extern HBRUSH COMCTL32_hPattern55AABrush; > > @@ -125,4 +128,132 @@ > #define WINE_FILEVERSION 5, COMCTL32_VERSION_MINOR, 0, 0 > #define WINE_FILEVERSIONSTR "5.00" > > +/* Notification support */ > + > +inline static LRESULT __send_notify(HWND hwnd, UINT code, NMHDR *hdr) Isn't using double underscore for such non-system functions rather pretty weird ? (or IOW: even strongly discouraged ?) -- Microsoft Licensing 6.0: "Pay us now in advance, so that we can own you later."

4 3

Re: Atom test fix
by Dmitry Timoshkov 05 Sep '02

05 Sep '02

"Francois Gouget" <fgouget(a)free.fr> wrote: > Conformance tests must not use Wine-specific headers (like > wine/unicode.h) otherwise they will not compile on Windows. > > wine/test.h is the only exception. > > Changelog: > > * dlls/kernel/tests/atom.c > > Do not include wine/unicode.h > Duplicate strlenW I would suggest to simply replace it by lstrlenW, instead of duplicating code. -- Dmitry.

1 0

Re: VersionNumber reg. key
by Jeff Smith 05 Sep '02

05 Sep '02

My $0.02: I say don't create, and dynamically 'lie' about it's value. I'm sure it's easier said than done, but that's my thoughts, anyway. -- Jeff S >From: Ender <winedev(a)admdev.com> >To: wine-devel(a)winehq.com >Subject: VersionNumber reg. key >Date: Wed, 4 Sep 2002 21:28:32 -0500 (CDT) >read the HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\VersionNumber >key. And of course, as this is a 'required' key in Windows, there was no >code to cope with failure :) >whether or not Wine should dynamically 'lie' about this registry key, >depending what winver the current thread is running in. > - Ender _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

3 2

[Bug 448] - need help debugging 16-32-bit parameter passing
by Martin Wilck 05 Sep '02

05 Sep '02

Included below are my latest results for Bug 448. The problem there is that winsock connects to port 512 although a service at port 5557 was specified. The winsock functions seem to work correctly: -> getservbyname16 returns port 0x15b5 = 5557 -> connect16 receives port 512 (!) directly after that. (the only thing that happens in between is a socket() call). The interesting part is that 512 in network byte order is 0x0002, i.e. the same as the protocol family (0x0002=AF_INET). Is it possible that something gets overwritten here when connect() is called? My problem is that I have no clue hall the magic relaying between 16 and 32 bit code in wine works. Perhaps someone can give me a hint? Martin ------- Additional Comments From martin.wilck(a)fujitsu-siemens.com 2002-09-05 07:58 ------- I finally got some time to look into this. It does not seem to be a winsock error. By inserting some TRACES, I can clearly see that getservbyname() correctly returns port 5557 (hex 0x15b5): trace:winsock:WINSOCK_getservbyname16 "ctsql", "tcp" trace:winsock:__ws_getservbyname name ctsql proto tcp flag 2 i 6 trace:winsock:WS_dup_se s_name ctsql s_port 15b5 s_proto tcp trace:winsock:WS_dup_se 16 s_port 15b5 trace:winsock:__ws_getservbyname s_name ctsql s_port 15b5 s_proto tcp [ ... ] But when "connect" is called, it is passed port 512 (hex 0200): trace:winsock:WINSOCK_connect16 socket 0048, ptr 0x40c493d6, length 16 sockaddr_in: family 2, address 172.25.186.5, port 512 02 00 02 00 ac 19 ba 05 00 00 00 00 00 00 00 00 Interestingly, (since the port is in network byte order) the hex patterns for address family and port are both 0x0002. This looks as if either - the app is assigning the family to the port number (?) (This would mean that the shouldn't be able to run on Windows either, since you say all was fine in 20011108, there must be another reason) - something goes wrong when the argument is passed from the 16- to 32bit layer. Have to look further. -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

1 0

Trying to debug Paradise Poker client
by Per Nystrom 05 Sep '02

05 Sep '02

Hi, I filed bug 1007 (kernel32.dll.Heap32* functions unimplemented) on this, but I'm not even sure that's the real problem. One thing that I'm seeing is retval=00000000 (FALSE) from all the calls to advapi32.CryptAcquireContextA() -- since this application relies *heavily* on encryption, I wonder if this is a good place to start. If I run it with the advapi32 dll overridden to use native, I get a different error and the App seems to crash even earlier in its execution. The following is what I got using the native advapi32 dll: fixme:file:VxDCall_VMM Unknown service 00010029 08070158:Ret kernel32.VxDCall4() retval=ffffffff ret=bfe81d8d fs=008f eax=ffffffff ebx=00000000 ecx=4011faa8 edx=405c6a00 esi=00000064 edi=00000001 ebp=405c6d5c esp=405c6d40 ds=002b es=002b gs=0ac7 flags=00000202 08070158:Call kernel32.CreateEventA(00000005,00000064,00000001,71467c2a "\205\300u\020h\024$EqSj\001S\377\327\243LPJqU\350\304\262\377\377;\363t\007V\377\025<\022Eq_^][\303\203=LPJq") ret=00000001 err:win32:CreateEventW Bad security attributes pointer 0x5 08070158:Ret kernel32.CreateEventA() retval=00000000 ret=00000001 wine: Unhandled exception, starting debugger... I'm attaching the entire relay trace (compressed) from running with the builtin advapi32 dll; it's much larger but probably more useful for fixing the problem. Any help is greatly appreciated! Per Nystrom System specifics: wine was built from the very latest in the CVS repository as of tonight Pentium II, 128Mb RAM and 1+ Gb swap running Red Hat 7.1 with updated X (4.2.0) glibc-2.2.4-29 gcc-2.96-81 -- "When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl."

2 1

Re: [PATCH] winsock-test.diff
by Alexandre Julliard 05 Sep '02

05 Sep '02

Martin Wilck <Martin.Wilck(a)Fujitsu-Siemens.com> writes: > Rationale: > - Make it easier to add new unit tests. > - Conform better to the usual wine unit testing scheme > (instead of running different tests from the same file, > run separate files testing different functionality) That's not really the usual scheme. It may look that way because we have few tests at the moment, but we can't put each test in a separate file, or we will end up with thousands of them. The right approach is to follow more or less the layout of the source files, that is if two APIs are implemented in the same source file they should be tested in the same test file; so I think the current winsock tests are OK as they are. And in any case #including .c files is strongly discouraged. -- Alexandre Julliard julliard(a)winehq.com

2 1

Tab Controls without name
by Fabian Cenedese 05 Sep '02

05 Sep '02

Hi I found something that would be easy to fix in case it really should be fixed. Working with tab controls I have the case where I set the tab name to empty because it's too big to be shown. In the TCITEM structure I set the text pointer to NULL instead of a "". Thus Wine stopped at some point doing a strlen on a NULL pointer. Obvious. Then I checked MSDN if this is allowed or not. It always says string pointer, never is a NULL pointer a possible value. Ok, so my code is wrong, easy to change. But still (the often cited sentence): It used to work in Windows. So now I don't know if Wine should be clean (and NULL pointer in tab name is not allowed) or if it should behave as Windows (no matter what docs say) and a NULL pointer is just an empty name... bye Fabi

2 2

VersionNumber reg. key
by Ender 05 Sep '02

05 Sep '02

Hi all, A few weeks ago I was setting up a fake-windows install, and ran across a few pieces of software that just crashed.. like the Visual Studio installer. After a little bit of investigation, I discovered these were trying to read the HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\VersionNumber key. And of course, as this is a 'required' key in Windows, there was no code to cope with failure :) At the very least this should be added to the default registry with a dummy value (oh yeah, values are like: "4.90.3000"). But my question is whether or not Wine should dynamically 'lie' about this registry key, depending what winver the current thread is running in. Thoughts? - Ender

1 0

Re: Partial implementation of NotifyRegister notifications
by Alexandre Julliard 05 Sep '02

05 Sep '02

Joshua Thielen <thielen(a)netprince.net> writes: > I expect there to be problems with this patch (some of it is probably > a bit over my head) so eyes are requested, please! I already know that > the number and order of the segment messages (NFY_LOADSEG and FREESEG) > doesn't exactly match those sent in Windows, and I'm not totally sure > of the affect this patch will have on 16-bit memory and threading > details in wine. You should really have some kind of TOOLHELP_SendNotification function instead of calling wine_call_to_16_regs all over the place. Also the handling of segmented pointers (especially the lpstrModuleName) doesn't look right. Apart from that, it looks quite reasonable. -- Alexandre Julliard julliard(a)winehq.com

1 0

Catching MFC exception
by Fabian Cenedese 04 Sep '02

04 Sep '02

Hi I found one of the wrong behaviours though I don't know where to solve it. For creating an ocx one can give a window title. I gave a "" to the CreateControl function. But this poses a problem to MFC, it's only prepared for valid strings or NULL pointers. That's why it generates the exception: void AFXAPI AfxThrowOleException(SCODE sc){ #ifdef _DEBUG TRACE1("Warning: constructing COleException, scode = %s.\n", AfxGetFullScodeString(sc)); #endif COleException* pException = new COleException; pException->m_sc = sc; THROW(pException); } In Windows this is caught by another function in MFC and doesn't do any harm: BOOL AFX_CDECL COleControlSite::SafeSetProperty(DISPID dwDispID, VARTYPE vtProp, ...) { va_list argList; // really only one arg, but... va_start(argList, vtProp); BOOL bSuccess; TRY { SetPropertyV(dwDispID, vtProp, argList); bSuccess = TRUE; } CATCH_ALL(e) { DELETE_EXCEPTION(e); bSuccess = FALSE; } END_CATCH_ALL va_end(argList); return bSuccess; } Now it seems that the exception handling inside (or wherever) the MFC.dll doesn't work if running in Wine or the MFC exceptions are different and the exception comes right through. I can overcome this problem by giving a valid window title but that solves it only for me. I have no idea how and if this can be solved but maybe this description gives a hint to a programmer with more insight. Thanks Fabi

2 1

Re: LsaNtStatusToWinError implementation
by Andriy Palamarchuk 04 Sep '02

04 Sep '02

--- Andriy Palamarchuk <apa3a(a)yahoo.com> wrote: > Changelog: > Implemented LsaNtStatusToWinError, conformance > tests, added definitions of the error and status > constants, used by the function. Please ignore this patch. I just found out that I should call RtlNtStatusToDosError from this function instead of implementing the mapping myself. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

1 0

Wine error codes
by Sylvain Petreolle 04 Sep '02

04 Sep '02

hi, having problem with IE 6 exiting immediately using a patched shdocvw, I would know if wine exit codes are documented somewhere ? ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 1

Problem with regression tests getting stuck
by Paul Millar 04 Sep '02

04 Sep '02

Hi everyone, I've had the regression tests freeze on me again (see [1] for previous report). Sylvain has reported problems with the wininet regression tests (described in [2]). The symptoms are the same, but for me the problem is only intermittent. This time I caught the problem with gdb and obtained the following info: [...] Loaded symbols for /lib/libresolv.so.2 0x402e7744 in __libc_close () at __libc_close:-1 -1 __libc_close: No such file or directory. in __libc_close (gdb) bt #0 0x402e7744 in __libc_close () at __libc_close:-1 #1 0x400ec9a4 in __DTOR_END__ () from /home/paulm/WINE-cvs/wine/dlls/libntdll.dll.so #2 0x400b3df5 in WaitForMultipleObjectsEx (count=0, handles=0x0, wait_all=0, timeout=100, alertable=0) at ../../scheduler/synchro.c:257 #3 0x400b3b88 in Sleep (timeout=100) at ../../scheduler/synchro.c:178 #4 0x40358747 in winapi_test (flags=268435456) at tests/http.c:121 #5 0x40358b36 in func_http () at tests/http.c:184 #6 0x40358f9d in run_test (name=0xbffffc63 "http.c") at wtmain.c:244 #7 0x40357037 in __wine_exe_main () at wininet_test.exe.spec.c:133 #8 0x400aff84 in start_process () at ../../scheduler/process.c:528 #9 0x400b3f3f in call_on_thread_stack (func=0x400afd2c) at ../../scheduler/sysdeps.c:108 So, to summarise (with some extra bits of information): The problem occurs when wininet/tests/http.c is testing asynchronous HttpSendRequest(), so flags > 0. The problem is triggered at line 121 of http.c, i.e.: 120 while ((flags)&&(!goon)) 121 Sleep(100); Sleep(), in turn, just calls WaitForMultipleObjectsEx(). From scheduler/synchro.c: 176 VOID WINAPI Sleep( DWORD timeout ) 177 { 178 WaitForMultipleObjectsEx( 0, NULL, FALSE, timeout, FALSE ); 179 } WaitForMultipleObjectsEx() has problems when it gets to 257: 256 SERVER_END_REQ; 257 if (ret == STATUS_PENDING) ret = wait_reply( &cookie ); 258 if (ret != STATUS_USER_APC) break; ret is 1079729528, btw. AFAIK, __DTOR_END__ (see near bottom of stack) is the destructor for a function call in ntdll. I'm probably missing something obvious, but I don't see the connection between scheduler/synchro.c:257 and ntdll. The closest is wait_reply() (in scheduler/client.c) calls wait_reply_data (in same file), which calls NtCurrentTeb(), which is commented as an NTDLL function. But there doesn't seem to be an implementation of NtCurrentTeb in ntdll. Any ideas? Cheers, Paul. [1] http://www.winehq.com/hypermail/wine-devel/2002/08/0006.html [2] http://www.winehq.com/hypermail/wine-devel/2002/07/0386.html PS, I'll create a bugzilla in a bit. ---- Paul Millar

2 4

Re: Implements shdocvw.101
by Eric Pouech 04 Sep '02

04 Sep '02

Sylvain Petreolle a écrit : > > Changelog: > Implements shdocvw.101, which is a call to shlwapi.PathRemoveBackslashW wouldn't a forward in the spec file be more appropriate ? 1+

2 2

Help solving Bug 434
by Rick Romero 03 Sep '02

03 Sep '02

Hello all, I'm taking yet another look at bug 434, where a left mouse click won't release in Visual FoxPro. Alexandre applied a patch on 6/13/02 that fixed the issue for the opener of the bug, but is general issue still exists for me, I havn't heard from the submitter of the Illustrator 8 report. First question: Since the original report has been resolved, should a new report be opened? Second: I feel like the solution is pretty close, but I'm probably treading water in deep fog, FEELING like I'm getting close to shore :) The one weird thing that I can't figure out is why I can run wine --debugmsg +scroll,+event,+toolbar,+gdi,+heap /mnt/windows/DevStu dio/vfp/vfp.exe and have the button up WORK for a few clicks. If I hold the button down, then release, the issue occurs. Since the mouse issue started when input functions were moved into the wine server, it makes sense to me that there might be some issue related to synchro.c as shown below in gdb output. ------- Additional Comments From rick(a)havokmon.com 2002-08-31 21:22 ------- Ok - ivanovich(a)menta.net determined the fix for Flash 5 to be patch at: http://www.winehq.com/hypermail/wine-cvs/2002/06/0098.html from 6/14/02. This patch does not affect the mousebutton issue in Visual FoxPro, but his posts on using gdb now make sense to me.. Using Wine-20020804. wine test.exe (using vfp5test.zip - Installer works now!) - available from Bug Report Here's my output of GDB: (gdb) bt #0 0x402ddfe4 in read () from /lib/i686/libc.so.6 #1 0x40102130 in __JCR_LIST__ () from /usr/local/lib/libntdll.dll.so #2 0x400c6cac in WaitForMultipleObjectsEx (count=1095856128, handles=0x0, wait_all=0, timeout=220, alertable=0) at ../../scheduler/synchro.c:265 #3 0x400c69e1 in Sleep (timeout=220) at ../../scheduler/synchro.c:178 #4 0x10001011 in ?? () #5 0x400c704e in SYSDEPS_StartThread (teb=0x41517000) at ../../scheduler/sysdeps.c:158 (gdb) n Single stepping until exit from function read, which has no line number information. wait_reply (cookie=0x41506e58) at ../../scheduler/synchro.c:96 96 if (ret == sizeof(reply)) (gdb) n 98 if (!reply.cookie) break; /* thread got killed */ (gdb) n 99 if (reply.cookie == cookie) return reply.signaled; (gdb) n 0x400c6cac in WaitForMultipleObjectsEx (count=259, handles=0x0, wait_all=0, timeout=220, alertable=0) at ../../scheduler/synchro.c:265 265 ret = WAIT_FAILED; (gdb) n 258 if (ret != STATUS_USER_APC) break; (gdb) n 262 if (HIWORD(ret)) /* is it an error code? */ (gdb) n 267 return ret; (gdb) n 268 } (gdb) n Sleep (timeout=220) at ../../scheduler/synchro.c:179 179 } (gdb) n Here, just like ivanovich(a)menta.net's post, the gdb hangs and the wine process takes 100% cpu. If the scheduler is not working properly with FoxPro, that might explain the weird 'Slowness Solution' I described above, with extra debug info delaying the button up issue. If I ctrl-C and detach from that process, and attach to a second wine process, I get: (gdb) bt #0 0x402de024 in write () from /lib/i686/libc.so.6 #1 0x40997d48 in _XlcPublicMethods () from /usr/X11R6/lib/libX11.so.6 #2 0x4092122f in _X11TransWrite () from /usr/X11R6/lib/libX11.so.6 #3 0x40904bc2 in _XScreenOfWindow () from /usr/X11R6/lib/libX11.so.6 #4 0x40902717 in _XReply () from /usr/X11R6/lib/libX11.so.6 #5 0x408f881b in XQueryPointer () from /usr/X11R6/lib/libX11.so.6 #6 0x40893452 in TSXQueryPointer (a0=0x809e030, a1=70, a2=0x405a5cbc, a3=0x405a5cc0, a4=0x405a5cc4, a5=0x405a5cc8, a6=0x405a5ccc, a7=0x405a5cd0, a8=0x405a5cd4) at ts_xlib.c:846 #7 0x4086e1a8 in X11DRV_GetCursorPos (pos=0x405a5d20) at mouse.c:514 #8 0x406a55a8 in GetCursorPos (pt=0x8) at ../../windows/input.c:476 #9 0x10008fc7 in ?? () #10 0x101aa657 in ?? () (gdb) n Single stepping until exit from function write, which has no line number information. 0x40922050 in _X11TransGetConnectionNumber () from /usr/X11R6/lib/libX11.so.6 (gdb) n Single stepping until exit from function _X11TransGetConnectionNumber, which has no line number information. 0x4092122f in _X11TransWrite () from /usr/X11R6/lib/libX11.so.6 (gdb) n Single stepping until exit from function _X11TransWrite, which has no line number information. 0x40904bc2 in _XScreenOfWindow () from /usr/X11R6/lib/libX11.so.6 (gdb) n Single stepping until exit from function _XScreenOfWindow, which has no line number information. 0x40902717 in _XReply () from /usr/X11R6/lib/libX11.so.6 (gdb) n Single stepping until exit from function _XReply, which has no line number information. 0x408f881b in XQueryPointer () from /usr/X11R6/lib/libX11.so.6 (gdb) n Single stepping until exit from function XQueryPointer, which has no line number information. TSXQueryPointer (a0=0x809e030, a1=70, a2=0x405a5cbc, a3=0x405a5cc0, a4=0x405a5cc4, a5=0x405a5cc8, a6=0x405a5ccc, a7=0x405a5cd0, a8=0x405a5cd4) at ts_xlib.c:847 847 wine_tsx11_unlock(); (gdb) n 846 r = XQueryPointer(a0, a1, a2, a3, a4, a5, a6, a7, a8); (gdb) n 847 wine_tsx11_unlock(); (gdb) n 849 } (gdb) n X11DRV_GetCursorPos (pos=0x405a5d20) at mouse.c:518 518 update_key_state( xstate ); (gdb) n 519 TRACE("pointer at (%d,%d)\n", winX, winY ); (gdb) n 520 pos->x = winX; (gdb) n 521 pos->y = winY; (gdb) n 522 } (gdb) n 0x406a55a8 in GetCursorPos (pt=0x40887b03) at ../../windows/input.c:476 476 } (gdb) n 475 return 1; (gdb) n 476 } (gdb) n Here, just like ivanovich(a)menta.net's post, the gdb hangs and the wine process takes 100% cpu. I tried putting a while loop in synchro.c, so that it would loop until !(HIWORD(ret)), but I did something wrong: --- synchro.c line 231 int ret, cookie,testparm; struct timeval tv; testparm = 0; while (testparm == 0){ testparm = 1; if (count > MAXIMUM_WAIT_OBJECTS) ... ... if (HIWORD(ret)) /* is it an error code? */ { SetLastError( RtlNtStatusToDosError(ret) ); ret = WAIT_FAILED; testparm = 0; } } return ret; --- I don't know if something like that would actually work, but my last gdb step through showed testparm set to 0 before returning ret ;) - so I whatever I did, I didn't do it right. ------- End Comments From rick(a)havokmon.com 2002-08-31 21:22 ------- Any direction to take would be greatly appreciated. Thanks Rick -- -- Rick Romero IT Manager Valeo, Inc. ph: 262.695.4841 Sussex, WI. fax: 262.695.4850 Rick(a)valeoinc.com

1 0

current wine status pr-1
by tom 03 Sep '02

03 Sep '02

Hello, I would like to thank everyone who has re-plied so far about the current wine status. I have a pre-1 hacked together and request any feed back that you can give. My main goal is the info I put up be as accurate as possiable . And since i'm not a Developer I have to bug/spam you guy's for the info :) So please bear with me .......... Known ToDo's will be next on my list after ** WE ** get this up to date.. Tom Wine status changes from 9-29-01 untill 9-01-02 pre-1 reply to : twickline2(a)triad.rr.com ( Aspect or Component ) Wine's fundamental architecture Documentation = workers = Alexandre Julliard % = 85% Process/Address Space model Documentation = workers = Alexandre Julliard % = 100% Threading model Documentation = workers = Alexandre Julliard % = 100% Scheduling and synchronization Documentation = workers = Alexandre Julliard % = 100% Supervisory process (wineserver) Documentation = workers = Alexandre Julliard % = 90% Windows binary loader Documentation = workers = Alexandre Julliard % = 100% Memory management Documentation = workers = Alexandre Julliard % = 90% Wine DLL infrastructure Documentation = workers = Alexandre Julliard % = 95% Need to ADD --- DLL separation Documentation = workers = AJ % = 75% Message passing/queues Documentation = workers = Alexandre Julliard % = 95% Window management Documentation = workers = ? % = 95% Disk drive emulation Documentation = workers = ? % = 100% CD-ROM emulation Documentation = workers = Eric Pouech eric.pouech(a)wanadoo.fr % 90% Native DLL overrides Documentation = workers = ? % = 95% X11 display/window driver Documentation = workers = ? % = 90% X11 font mapper Documentation = workers = ? % = 70% Registry handling Documentation = workers = ? % = 90% Clipboard handling Documentation = workers = ? % = 90% File I/O Documentation = workers = Mike McCormack % = 100% TrueType support Documentation = workers = Huw D M Davies % = 80% National Language Support (NLS) Documentation = Dmitry Timoshkov, Alexandre Julliard workers = % = 90% Unicode support Documentation = workers = Dmitry Timoshkov, Alexandre Julliard % = 80% Dynamic Data Exchange (DDE) Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 80% Standard Windows Controls Documentation = workers = ? % = 95% Serial/parallel ports 16-bit 95% 32-bit 90% Documentation = workers = Mike McCormack I/O port access Documentation = workers = ? % = 100% VxDs Documentation = workers = ? % = 5% General printer setup Documentation = workers = Huw D M Davies % = 70% Internal PostScript printer driver Documentation = workers = Huw D M Davies, Ian Pilcher % = 60% Native Windows printer drivers 16-bit 50% 32-bit 0% Documentation = workers = ? Win32 Console Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 75% DOS application support Documentation = workers = Ove Kåven, Alexandre Julliard % = 60% CPU emulation Documentation = workers = ? % = 5% Multi-user support Documentation = workers = ? % = 20% ( DLLs ) crtdll&msvcrt: Standard C runtime library Documentation = workers = CodeWeavers % = 60% comctl32: Common Controls Documentation = workers = CodeWeavers % = 95% Note-- Is Macadamian still working on Wine ??? comdlg32: Common Dialogs Documentation = workers = ? % = 75% riched32: Rich Text Control Documentation = workers = ? % = 20% shell32: Shell interface Documentation = workers = CodeWeavers % = 80% tapi32: Telephony API (TAPI) Documentation = workers = ? % = 0% rasapi32: Dial-Up Networking (DUN) and Remote Access Service (RAS) Documentation = workers = ? % = 0% wsock32: Windows Sockets (WinSock) 1.1 Documentation = workers = Macadamian ???????? % = 90% ws2_32: WinSock 2 Documentation = workers = Macadamian ???????? % = 20% wininet: Internet application protocols Documentation = workers = CodeWeavers % = 50% winmm: Multimedia architecture Documentation = workers = Eric Pouech eric.pouech(a)wanadoo.fr % = 80% ( Eric has this changed ??? ) Multimedia wave audio Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 100% for OSS Multimedia MIDI audio Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 100% for OSS **Preliminary ALSA support 10% Multimedia joystick driver Documentation = workers = Eric Pouech eric.pouech(a)wanadoo.fr % = 80% ( Eric has this changed ??? ) Multimedia CD audio Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 100% MCI (Media Control Interface) drivers Documentation = workers = Eric Pouech eric.pouech(a)wanadoo.fr % = 60% ( Eric has this changed ??? ) msacm32: Audio Compression Manager (ACM) Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 60% msvfw32: Video for Windows (VFW) Documentation = workers =Eric Pouech eric.pouech(a)wanadoo.fr % = 30% ddraw: DirectDraw Documentation = workers = TransGaming % = 85% Direct3D Documentation = workers = TransGaming % = 30% dinput: DirectInput Documentation = workers = TransGaming % = 40% dplayx: DirectPlay Documentation = workers = Peter Hunnisett % = 25% dsound: DirectSound Documentation = workers = TransGaming % = 80% quartz: DirectShow core Documentation = workers = In TransGaming cvs ?? % = 0% wing: WinG 16-bit game library Documentation = workers = ? % = 50% rpcrt4: RPC/DCOM subsystem Documentation = workers = ? % = 0% ole32: OLE/COM core Documentation = workers = CodeWeavers % = 60% oleaut32: OLE Automation core Documentation = workers = CodeWeavers % = 60% olecli32: OLE client library Documentation = workers = ? % = 5% olesvr32: OLE server library Documentation = workers = ? % = 5% oledlg: OLE user interface Documentation = workers = ? % = 5% opengl32: OpenGL interface Documentation = workers = Lionel Ulmer, TransGaming % = 90% odbc32: ODBC Database Manager Documentation = workers = Corel % = 100% wnaspi32: Advanced SCSI Peripheral Interface Documentation = workers = ? % = 85% ( Tools ) Wine Resource Compiler Documentation = workers = Bertho Stultiens ??? % = 95% Wine Message Compiler Documentation = workers = Bertho Stultiens ??? % = 75% Wine Debugger Documentation = workers = Eric Pouech eric.pouech(a)wanadoo.fr % = 85% Wine Porting Tool (winemaker) Documentation = workers = CodeWeavers % = 70% Wine Installer (wineinstall) Documentation = workers = Andreas Mohr % = 90% Wine Installation Checker (winecheck) Documentation = workers = Andreas Mohr % = 30% Wine Setup Tool (winesetuptk) Documentation = workers = CodeWeavers % = 50% Wine Launcher Documentation = workers = CodeWeavers % = 60% Wine Regression Test Suite Documentation = workers = CodeWeavers % = 10% ( No-Windows installation issues ) Initial registry contents Documentation = workers = ? % = 25% Initial directory structure Documentation = workers = ? % = 90% Initial INI files Documentation = workers = ? % = 40% DLL placeholder files Documentation = workers = CodeWeavers % = 100% ( Instructions ) How to install Wine Documentation = workers = Andreas Mohr % = 90% How to debug Documentation = workers = Andreas Mohr % = 80% How to create a useful bug report Documentation = workers = Andreas Mohr % = 80% How to become a Wine developer Documentation = workers = Andreas Mohr % = 80% How to use Winelib Documentation = workers = Andreas Mohr % = 90% How to compile MFC with Winelib Documentation = workers = Andreas Mohr % = 80% ( Miscellaneous ) Wine 1.0 Release Plan Both link's are dead !! I did find this link: http://www.winehq.com/news/?view=118#Road%20to%200.9 Ove- do you plan to do a updated Road to 1.0 ? The History of the Wine Project MS has got nervous and released junk API's What a MS breakup might mean to Wine ? Remove as there not going to get BROKE -UP!!!! ): ??? WineHQ and Corel relationship CodeWeavers is the host of WineHQ now ? ----------------- Need to ADD BiDi Documentation = workers = Shachar Shemesh contact = wine-devel(a)sun.consumer.org.il % = 5% individual control status Documentation = workers = Dimitrie O.Paun contact = dimi(a)bigfoot.com % = ?%

8 14

current wine status pre-2
by Thomas Wickline 03 Sep '02

03 Sep '02

Hello, Here is Pre-2 I have made changes from the feedback that I recieved from Pre-1 From now on I will just send a diff from Pre-2 to cut back on Bandwith. Please take a minute and look over it and send me any corrections that may be needed. Bad info is worse than NO info at all.. I know this is a estimate of work done... I would just like for it to be as close as possiable.. Many Thanks to everyone Thomas Wickline Wine status changes from 9-29-01 untill 9-03-02 pre-2 reply to : twickline2(a)triad.rr.com ( Aspect or Component ) Wine's fundamental architecture Documentation = workers = Alexandre Julliard % = 85% Process/Address Space model Documentation = workers = Alexandre Julliard % = 100% Threading model Documentation = workers = Alexandre Julliard % = 100% Scheduling and synchronization Documentation = workers = Alexandre Julliard % = 100% Supervisory process (wineserver) Documentation = workers = Alexandre Julliard % = 90% Windows binary loader Documentation = workers = Alexandre Julliard % = 100% Memory management Documentation = workers = Alexandre Julliard % = 90% Wine DLL infrastructure Documentation = workers = Alexandre Julliard % = 95% Need to ADD --- DLL separation Documentation = workers = AJ % = 75% Message passing/queues Documentation = workers = Alexandre Julliard % = 95% Window management Documentation = workers = ? % = 95% Disk drive emulation Documentation = workers = ? % = 100% CD-ROM emulation Documentation = workers = Eric Pouech % 90% Native DLL overrides Documentation = workers = ? % = 95% X11 display/window driver Documentation = workers = ? % = 90% X11 font mapper Documentation = workers = Huw D M Davies % = 70% Registry handling Documentation = workers = ? % = 90% Clipboard handling Documentation = workers = ? % = 90% File I/O Documentation = workers = Mike McCormack % = 100% TrueType support Documentation = workers = Huw D M Davies % = 80% National Language Support (NLS) Documentation = workers = Dmitry Timoshkov, Alexandre Julliard % = 90% Unicode support Documentation = workers = Dmitry Timoshkov, Alexandre Julliard % = 80% Dynamic Data Exchange (DDE) Documentation = workers =Eric Pouech % = 80% Standard Windows Controls Documentation = workers = ? % = 95% Serial/parallel ports 16-bit 95% 32-bit 90% Documentation = workers = Mike McCormack I/O port access Documentation = workers = ? % = 100% VxDs Documentation = workers = ? % = 5% General printer setup Documentation = workers = Huw D M Davies % = 70% Internal PostScript printer driver Documentation = workers = Huw D M Davies, Ian Pilcher % = 60% Native Windows printer drivers 16-bit 65% 32-bit 65% Documentation = workers = Huw D M Davies Win32 Console Documentation = workers = Eric Pouech % = 75% DOS application support Documentation = workers = Ove Kåven, Alexandre Julliard % = 60% CPU emulation Documentation = workers = ? % = 5% Multi-user support Documentation = workers = ? % = 20% ( DLLs ) crtdll&msvcrt: Standard C runtime library Documentation = workers = CodeWeavers % = 60% comctl32: Common Controls Documentation = workers = Macadamian % = 95% comdlg32: Common Dialogs Documentation = workers = ? % = 75% riched32: Rich Text Control Documentation = workers = ? % = 20% shell32: Shell interface Documentation = workers = CodeWeavers % = 80% tapi32: Telephony API (TAPI) Documentation = workers = ? % = 0% rasapi32: Dial-Up Networking (DUN) and Remote Access Service (RAS) Documentation = workers = ? % = 0% wsock32: Windows Sockets (WinSock) 1.1 Documentation = workers = Martin Wilck % = 90% ******** http://www.winehq.com/news/?view=121#Winsock2%20Patches also news in #108 ws2_32: WinSock 2 Documentation = workers = Martin Wilck % = 70% ******** http://www.winehq.com/news/?view=121#Winsock2%20Patches also news in #108 wininet: Internet application protocols Documentation = workers = CodeWeavers % = 50% winmm: Multimedia architecture Documentation = workers = Eric Pouech % = 80% Multimedia wave audio Documentation = workers =Eric Pouech % = 100% for OSS Multimedia MIDI audio Documentation = workers =Eric Pouech % = 100% for OSS **Preliminary ALSA support 10% Multimedia joystick driver Documentation = workers = Eric Pouech % = 80% Multimedia CD audio Documentation = workers =Eric Pouech % = 100% MCI (Media Control Interface) drivers Documentation = workers = Eric Pouech % = 60% msacm32: Audio Compression Manager (ACM) Documentation = workers =Eric Pouech % = 60% msvfw32: Video for Windows (VFW) Documentation = workers =Eric Pouech % = 30% ddraw: DirectDraw Documentation = workers = TransGaming % = 85% Direct3D Documentation = workers = TransGaming % = 30% dinput: DirectInput Documentation = workers = TransGaming % = 40% dplayx: DirectPlay Documentation = workers = Peter Hunnisett % = 25% dsound: DirectSound Documentation = workers = TransGaming % = 80% quartz: DirectShow core Documentation = workers = % = 0% wing: WinG 16-bit game library Documentation = workers = ? % = 50% rpcrt4: RPC/DCOM subsystem Documentation = workers = ? % = 0% ole32: OLE/COM core Documentation = workers = CodeWeavers % = 60% oleaut32: OLE Automation core Documentation = workers = CodeWeavers % = 60% olecli32: OLE client library Documentation = workers = ? % = 5% olesvr32: OLE server library Documentation = workers = ? % = 5% oledlg: OLE user interface Documentation = workers = ? % = 5% opengl32: OpenGL interface Documentation = workers = Lionel Ulmer, TransGaming % = 90% odbc32: ODBC Database Manager Documentation = workers = Corel % = 100% wnaspi32: Advanced SCSI Peripheral Interface Documentation = workers = ? % = 85% ( Tools ) Wine Resource Compiler Documentation = workers = Bertho Stultiens ??? % = 95% Wine Message Compiler Documentation = workers = Bertho Stultiens ??? % = 75% Wine Debugger Documentation = workers = Eric Pouech % = 85% Wine Porting Tool (winemaker) Documentation = workers = CodeWeavers % = 70% Wine Installer (wineinstall) Documentation = workers = Andreas Mohr % = 90% Wine Installation Checker (winecheck) Documentation = workers = Andreas Mohr % = 30% Wine Setup Tool (winesetuptk) Documentation = workers = Martin Pilka, CodeWeavers % = 100% Wine Launcher Documentation = workers = CodeWeavers % = 60% Re-name to = Wine Unit Testing Framework Wine Regression Test Suite Documentation = workers = Andriy Palamarchuk % = 70% ( No-Windows installation issues ) Initial registry contents Documentation = workers = ? % = 25% Initial directory structure Documentation = workers = ? % = 90% Initial INI files Documentation = workers = ? % = 40% DLL placeholder files Documentation = workers = CodeWeavers % = 100% ( Instructions ) How to install Wine Documentation = workers = Andreas Mohr % = 90% How to debug Documentation = workers = Andreas Mohr % = 80% How to create a useful bug report Documentation = workers = Andreas Mohr % = 80% How to become a Wine developer Documentation = workers = Andreas Mohr % = 80% How to use Winelib Documentation = workers = Andreas Mohr % = 90% How to compile MFC with Winelib Documentation = workers = Andreas Mohr % = 80% ( Miscellaneous ) Wine 1.0 Release Plan update link to: http://www.winehq.com/about/index.php?contrib#active remove WWN #45 Known Remaining: Window management rewrite Wine Unit Testing Framework More DLL Separation Documentation Quality assurance The History of the Wine Project MS is definitely getting nervous What a MS breakup might mean to Wine ? Remove as there not going to get broke up ?? WineHQ and Corel relationship CodeWeavers is the host of WineHQ now should this be removed ???? ----------------- Need to ADD BiDi Documentation = workers = Shachar Shemesh contact = wine-devel(a)sun.consumer.org.il % = 5% individual control status Documentation = workers = Dimitrie O.Paun % = 80% Rolling cvs testing Documentation = workers = Paul Millar % = 90% **Side note... The test its self is 90% done.

1 0

Compiling Wine gdi dlls under cygwin
by David Fraser 03 Sep '02

03 Sep '02

I have been trying to compile the wine gdi dll under cygwin. I am using the 20020804 snapshot This is part of an attempt to get native Windows applications to display themselves in cygwin's X Windows. I have seen several posts from Steven Edwards and others about compiling wine under cygwin So far I have managed to link in all required object files, but still receive the error below: fu000001.o(.idata$3+0xc): undefined reference to `libwine_a_iname' fu000003.o(.idata$3+0xc): undefined reference to `libwine_a_iname' fu000005.o(.idata$3+0xc): undefined reference to `libwine_a_iname' fu000007.o(.idata$3+0xc): undefined reference to `libwine_a_iname' fu000009.o(.idata$3+0xc): undefined reference to `libwine_a_iname' fu000011.o(.idata$3+0xc): more undefined references to `libwine_a_iname' follow Some other unresolved references are resolved by auto-import (wine_main_argc etc) and enable-stdcall-fixup (_RELAY_DoCallFrom32Regs) but I can't work out where libwine_a_iname comes from. Basically as I only need the gdi dll I have linked in a whole lot of object files: /graphics/*.c, /objects/*.c, /files/*.c, /loader/*.c, /loader/ne/*.c, /relay32/*.c, /memory/*.c /library/ldt.c, /dlls/ntdll/*.c, unicode/*.c, scheduler/*.c, msdos/*.c, win32/*.c, misc/*.c, if1632/*.c as well as everything in dlls/gdi and subdirs. This is probably a bit ambitious as it's my first attempt at wine development, but any advice?

2 1

Re: ANSI_CHARSET
by Jeff Smith 03 Sep '02

03 Sep '02

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

1 0

Ignoring exceptions
by Fabian Cenedese 03 Sep '02

03 Sep '02

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

2 1

Quartz DLL
by tom 03 Sep '02

03 Sep '02

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

6 6

ANSI_CHARSET
by Jeff Smith 03 Sep '02

03 Sep '02

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

5 5

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

02 Sep '02

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

1 0

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