wine-devel

wine-devel@winehq.org

9 participants
84458 discussions

Janitorial status?
by Hans Leidekker 09 Apr '03

09 Apr '03

Hi, I was looking for a way to kill some time when I ended up on (WineHQ's version of) Dimi's janitorial page. It seems the page could use an update since as of this moment some of the items seem to have been finished, or nearly so: tools/winapi_check/winapi_check --none --progress --cross-call-win32-win16 [...] loader/module.c: kernel32: WIN32_GetProcAddress16: illegal call to GetProcAddress16 (Win32 -> Win16) scheduler/syslevel.c: kernel32: _KERNEL32_86: illegal call to _LeaveSysLevel (Win32 -> Win16) [...] There must have been some problem converting these? Or were they introduced after the cleanup maybe? I decided to look further: tools/winapi_check/winapi_check --none --progress --cross-call-unicode-ascii [...] dlls/winmm/driver.c: winmm & winmm: OpenDriverW: illegal call to HEAP_strdupWtoA (Unicode -> ASCII) dlls/winmm/driver.c: winmm & winmm: OpenDriverW: illegal call to OpenDriverA (Unicode -> ASCII) [...] What's the story here? I decided to take on the 'Include statements should use <> instead of ""' item, as it seems nobody else is working on that (except Patrick Stridvall who created that useful patch to winapi_cleanup of course). My plan is to supply one patch for each directory in $WINE_SRC/* and $WINE_SRC/dlls/*, in 'ls' sorting order, to keep the patch size down. Is that OK with you? -Hans ----------------------------------------------- Hans Leidekker Vrije Universiteit Dienst IT Systeembeheer Campusnetwerk De Boelelaan 1105 1081 HV Amsterdam +31 (0) 20 444 5385 The Netherlands -----------------------------------------------

2 4

Fw: Wine release 20030408
by BiGgUn 09 Apr '03

09 Apr '03

Extracted from http://source.winehq.org/source/README 4. COMPILATION (...) To upgrade to a new release by using a patch file, first cd to the top-level directory of the release (the one containing this README file). Then do a "make clean", and patch the release with: gunzip -c patch-file | patch -p1 where "patch-file" is the name of the patch file (something likeWine-yymmdd.diff.gz). You can then re-run "./configure", and then run "make depend && make". 5. SETUP (...) Don't forget to uninstall any conflicting previous Wine installation first. Try either "dpkg -r wine" or "rpm -e wine" or "make uninstall" before installing. (...) You should read the entire the useful README to get more details. HTH, Stephan

1 0

warnings in dmusic_segment.c and dmusic_synth.c
by Gerald Pfeifer 09 Apr '03

09 Apr '03

I'm getting the following warnings with the new code in dlls/dmusic: dmusic_segment.c:475: warning: initialization from incompatible pointer type dmusic_segment.c:477: warning: initialization from incompatible pointer type dmusic_synth.c:179: warning: initialization from incompatible pointer type dmusic_synth.c:373: warning: initialization from incompatible pointer type dmusic_synth.c:388: warning: initialization from incompatible pointer type This is both on SuSE Linux 8.1 and FreeBSD 4.8, so it seems like a generic issue; would you mind having a look? Thanks, Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.pfeifer.com/gerald/

1 0

Re: Wine release 20030408
by Oliver Ob [o.b./RSi/TRSi/NSD] 09 Apr '03

09 Apr '03

Alexandre Julliard schrieb: > > This is release 20030408 of Wine, a free implementation of Windows on > Unix. This is still a developers only release. There are many bugs > and unimplemented features. Most applications still do not work > correctly. > > WHAT'S NEW with Wine-20030408: (see ChangeLog for details) > - Some reorganizations of the source tree. > - File change notifications. > - Support for all variants of glibc 2.3. > - Many documentation updates. > - Lots of bug fixes. > > See the README file in the distribution for installation instructions. > > Because of lags created by using mirror, this message may reach you before > the release is available at the ftp sites. The sources will be available > from the following locations: > > http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/Wine-20030408.tar.gz > http://prdownloads.sourceforge.net/wine/Wine-20030408.tar.gz > > It should also be available from any other site that mirrors ibiblio.org. > These locations also hold pre-built documentation packages in various > formats: wine-doc-html.tar.gz, wine-doc-txt.tar.gz, > wine-doc-pdf.tar.gz and wine-doc-ps.tar.gz. > > You can also get the current source directly from the CVS tree. Check > http://www.winehq.com/cvs for details. > > Patches should be submitted to "wine-patches(a)winehq.com". Please > don't forget to include a ChangeLog entry. If you submitted a patch, > please check to make sure it has been included in the new release. > > If you want to receive by mail a patch against the previous release > when a new one is released, you can subscribe to the mailing list at > http://www.winehq.com/mailman/listinfo/wine-releases . > > Wine is available thanks to the work of many people. See the file > AUTHORS in the distribution for the complete list. > > -- > Alexandre Julliard > julliard(a)winehq.com Hi Alexandre. I am new to Linux. Where can I read about how the wine is updated? Deinstall the old one and then put the new one on? Or is there a better way? -- *º¤.,___,.¤º*¨¨¨*¤ =Oliver@home= *º¤.,¸¸¸,.¤º*¨¨*¤ I / __|__ http://www.bmw-roadster.de/Friends/Olli/olli.html I I / / |_/ http://www.bmw-roadster.de/Friends/friends.html I I \ \__|_\ http://groups.yahoo.com/group/VGAP-93 I I \___| mailto:VGAP-93-subscribe@yahoogroups.com I >>> Telek0ma iBBMS - moving house, but online! +49....TRSi1 <<<

1 0

Re: Re: Re: Re: Stuck on threading
by Pouech Eric DMI AEI CAEN 09 Apr '03

09 Apr '03

> Yeah, what I meant was, how do you alter the current thread so you can > move up and down the stack frame as seen in the backtrace of that > thread? current thread is not altered, it's just stopped as long as you don't enter step/cont... commands then up/dn are just indexes to current thread's stack (which doesn't change since it doesn't execute) the up/dn commands are not available on other threads than current A+

1 0

Re: MaskBlt implementation.
by Dan Kegel 09 Apr '03

09 Apr '03

> BYTE SwapROP3_SrcDst(BYTE bRop3) > { > /* swap 1,2 bit and 5,6 bit */ > BYTE bit1 = (bRop3 & 0x04) ? 0x02 : 0; > BYTE bit2 = (bRop3 & 0x02) ? 0x04 : 0; > BYTE bit5 = (bRop3 & 0x40) ? 0x20 : 0; > BYTE bit6 = (bRop3 & 0x20) ? 0x40 : 0; > return (bRop3 & 0x99) | bit1 | bit2 | bit5 | bit6; > } How 'bout BYTE SwapROP3_SrcDst(BYTE bRop3) { /* swap 1,2 bit and 5,6 bit */ BYTE bits44 = (bRop3 & 0x44) >> 1; BYTE bits22 = (bRop3 & 0x22) << 1; return (bRop3 & 0x99) | bits22 | bits44; } -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 1

Re: MaskBlt implementation.
by Dimitrie O. Paun 09 Apr '03

09 Apr '03

On April 8, 2003 05:42 pm, Jaekil Lee wrote: > Now, I'm implementing MaskBlt using BitBlt. > I posted same code in www.codeproject.com as MaskBlt in Windows 9x. Suggestions: -- get rid of the C++ stuff (the ::) -- provide a patch (see http://www.winehq.org/?page=sending_patches) Small nits (IMHO): -- get rid of ROP3FromIndex(), just use ROP3Table directly -- rewrite SwapROP3_SrcDst() (see below) -- this is really picky, but I'd rename {FORE,BACK}_ROP3 to something a little more common like {FOREGND,BKGND}_ROP3 I found BACK a little confusing here. Possible SwapROP3_SrcDst() replacement: BYTE SwapROP3_SrcDst(BYTE bRop3) { /* swap 1,2 bit and 5,6 bit */ BYTE bit1 = (bRop3 & 0x04) ? 0x02 : 0; BYTE bit2 = (bRop3 & 0x02) ? 0x04 : 0; BYTE bit5 = (bRop3 & 0x40) ? 0x20 : 0; BYTE bit6 = (bRop3 & 0x20) ? 0x40 : 0; return (bRop3 & 0x99) | bit1 | bit2 | bit5 | bit6; } -- Dimi.

1 0

Re: PuTTY: server infinite loop
by Dimitrie O. Paun 09 Apr '03

09 Apr '03

Alexandre, Did you get a chance to look at this? http://www.winehq.com/hypermail/wine-devel/2003/04/0109.html Is it a server bug, or my setup busted? I think it's been there for the longest time, since PuTTY freezed like so for at least 2-3 months. Unfortunately, I can't do regression testing since my cvsup is broken. Unfortunately, no one seems to know how to fix it, and I can find only RedHat 6 binaries. Damn Modula 3! :) -- Dimi.

2 2

hi wine team
by Yu Neil 09 Apr '03

09 Apr '03

hello: did the wine team consider construct the win32 support (wine) within a micro-kernel architecture, just like the microsoft`s interix ? Neil Yu _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

2 1

Re: Wine start.exe
by Dan Kegel 08 Apr '03

08 Apr '03

Vilppa Salt wrote: > I posted earlier to the wine-devel about the launching files with params. Now my Wine should be ok. > > In the start.exe the /wait switch doesn't work. If you try to run from wcmd somebatfile.bat file which includes following lines: > > start /wait some-exefile.exe > del some-exefile.exe > > and you have some-exefile.exe in the same directory it fails. This is because the file gets deleted, the wait switch doesn't work. Maybe you could fix it? I would but my c-skills aren't that good. Thanks for the bug report. I'll try to have a look tonight. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

Re: Resend: Implements languagegroups functions
by Alexandre Julliard 08 Apr '03

08 Apr '03

Maxime Bellengé <maxime.bellenge(a)laposte.net> writes: > This patch implements the languagegroups functions. > As I have access to a French and English windows 2k+, I set > the resources accordingly for the kernel32 resources. However, as > I don't know the resources for other languages, I have put English > resources in the other nls files. People will have to change them to the > correct values. You should really implement the A functions by calling the W ones instead of duplicating the code. Also I'm not sure there's much point in looking up the info in the registry, we don't support installing locales dynamically anyway so we might as well have a static table in the code. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: Re: Re: Stuck on threading
by Pouech Eric DMI AEI CAEN 08 Apr '03

08 Apr '03

> See section 2.6.4 in the wine hackers guide, the command reference: > > bt print calling stack of current thread > bt N print calling stack of thread of ID N (note: this > doesn't change the position of the current frame as > manipulated by the up & dn commands) > up goes up one frame in current thread's stack > up N goes up N frames in current thread's stack it doesn't mean (at least it doesn't implement it) that current thread is changed bt N just 1/ stops thread of ID N (if it isn't stopped already) 2/ prints its backtrace but current thread doesn't change in the process (ie, the cont/step... commands still apply to current thread) Mike, BTW, I don't know why, but my ISP seems to have blacklisted the qinetic domain, so I can't reply to you directly (always thru wine-devel) A+

2 1

Re: Re: Stuck on threading
by Pouech Eric DMI AEI CAEN 08 Apr '03

08 Apr '03

> tid as a parameter for instance, and I can't see any way to switch the > current thread, despite the docs mentioning such a concept. which docs... this isn't implemented in winedbg another solution for this would be using gdb thru winedbg (run winedbg -- --gdb) you'll get gdb as a front end, but communicating thru winedbg to the wineserver using gdb commands, you might be able to control a bit more the threads A+

2 1

Re: IP Multicast
by Mike Hearn 08 Apr '03

08 Apr '03

Anything wrong with this one? FYI it uses a different structure to the original (rejected) patch from Marcus. thanks -mike On Tue, 2003-04-01 at 13:54, Mike Hearn wrote: > Hi, > > This patch adds support for IP multicast sockets to winsock. I stole > liberally from a patch from the summer of 2001 from Marcus, so thanks to > him for that: > > http://www.winehq.com/hypermail/wine-patches/2001/07/0009.html > > ChangeLog: > - Map winsock sockopts to the POSIX equivalents for IP multicast > - Remap winsock1 constant values to winsock2 using a forwarder function > - Change a FIXME to a TRACE, it appeared to be simply reporting progress > > thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 2

Stuck on threading
by Mike Hearn 08 Apr '03

08 Apr '03

Hi, I'm a bit stuck. I have a DLL that does a FindWindow on DLL attach, and as part of that it does a GetWindowText which tries to send a message to another thread, using send_inter_thread_message. Other threads then attempt to load a DLL and the loader section prompty deadlocks. In gdb, if I attach at this point I can see a nice backtrace of the thread waiting for the reply to its WM_GETTEXT message, along with the thread ID. I'd quite like to see what the thread it sent the message to is doing, but for some reason in gdb "info threads" doesn't do anything and "thread 18" says, thread ID not known, despite it clearly being there in the backtrace: #5 0x40abd0cf in send_inter_thread_message (dest_tid=18, info=0x4072187c, res_ptr=0x40721874) at message.c:1719 So, I'm wondering if this is due to the funny games Wine plays with threads, I'm on a standard glibc 2.2 system by the way. For some reason I can't use winedbg because it stops with a load of exceptions inside the DLL that seem to be red herrings. Is there any way of switching to a wine thread using gdb to get a backtrace? Is there a sneakier approach I can use to find out why thread 18 has apparently deadlocked? There is probably a race condition here - this program will start some times but not others :( Has anybody got any tips on how to debug this sort of thing? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 2

Building WINE with other headers
by Steven Edwards 08 Apr '03

08 Apr '03

Hello, I know we have discussed this before and Dimi put it on the Janitorial site but I dont think we ever came a conclusion on it and I could not find a easy fix. Last time I tried to change the include path manualy I ran in to lots of problems. I would like to attempt to build parts of WINE with only the mingw headers and exclude the winehq headers so I can: 1. Find out where the mingw w32api package is broken. 2. Impove the Wine headers if they are wrong. 3. Not use the winehq headers for the ReactOS (We wont try this untill 1 and 2 are in sync) BTW thanks for the winsock.h patch, it is nice to not have to have a simple command line now. Sorry for the head-ache <g> Steven

2 1

Visual FoxPro 8 / Wine20030318 crash
by Paul McNett 08 Apr '03

08 Apr '03

I crash when building an EXE in the new version of Visual Foxpro. Any ideas? "windows" = "nt351", all dlls built-in. Here's the output leading up to the crash: fixme:hook:NotifyWinEvent (32769,0x50032,1,0)-stub! fixme:pidl:SHLogILFromFSIL (pidl=0x4032b090) fixme:dc:LockWindowUpdate (0x50033), partial stub! fixme:shell:ISVBgCm_fnGetCommandString unknown command string fixme:shell:ISVBgCm_fnGetCommandString unknown command string fixme:shell:ISVBgCm_fnGetCommandString unknown command string fixme:dc:LockWindowUpdate ((nil)), partial stub! fixme:shell:ReadCabinetState 0x4071e2e0 0x000c stub fixme:hook:NotifyWinEvent (32773,0x30031,7,1)-stub! fixme:hook:NotifyWinEvent (32768,0x90032,1,0)-stub! fixme:hook:NotifyWinEvent (32769,0x90032,256,0)-stub! fixme:hook:NotifyWinEvent (32769,0x90032,1,0)-stub! fixme:ole:DispCallFunc Do not know how to handle pvargResult 0x4071e5cc. Expect crash ... fixme:ole:DispCallFunc Method returned 0 err:ole:TLB_ReadTypeLib Loading of typelib L"E:\\src\\vfp\\sbs\\sbs.exe" failed with error 0 fixme:seh:EXC_RtlRaiseException call to unimplemented function kernel32.dll.BeginUpdateResourceA fixme:process:CreateProcessA (E:\prg\vfp8\dw15.exe,...): NORMAL_PRIORITY_CLASS ignored fixme:process:CreateProcessA (E:\prg\vfp8\dw15.exe,...): CREATE_DEFAULT_ERROR_MODE ignored fixme:win32:PE_CreateModule Security directory ignored fixme:ntdll:NtQuerySystemInformation (0x00000005,0x4028d858,0x00010000,(nil)) stub fixme:win32:PE_CreateModule Security directory ignored fixme:advapi:RegisterEventSourceW ((null),L"Microsoft Visual FoxPro"): stub fixme:advapi:ReportEventA stub fixme:advapi:DeregisterEventSource (0x1): stub fixme:wininet:InternetGetConnectedState always returning LAN connection. -- Paul McNett Liberal Earthling

4 5

NTPL & pthreads locks
by Dimitrie O. Paun 08 Apr '03

08 Apr '03

Alexandre, If I understand correctly, we currently implement the pthreads locks on top on Wine locks because the standard pthreads locks are not powerful enough to support all Win32 locking primitives. Integrating these locks is necessary for integrating Wine with the pthreads Universe. Now, given the new NTPL work, would it be possible/feasible/desirable to implement the Win32 locks on top of NTPL primitives (such as futexes)? At the very least it makes the setup a lot more intuitive, and less likely to break. If we are to follow this path, there are portability problems. But do we support this sort of libc integration of Solaris and *BSD? And it seems to me that it shouldn't be too hard for these systems to provide something that would allow us to implement all Win32 locking primitives, and the end result would be a lot less brittle. -- Dimi.

3 3

Re: Re: cleaning the source tree when compiling outside the source tree
by Pouech Eric DMI AEI CAEN 08 Apr '03

08 Apr '03

> I don't think we should do that. IMO we must not modify the source > tree in any way when building in a separate dir. It depends which files we're talking about I think that *~ (and any editor backup files), *rej* *orig* (patch leftovers), .#* (cvs update leftovers) should be removed from the source tree perhaps we need to seperate the semantics from clean and distclean. but at least, from a distclean point of view, I do think it would be great to remove the hereabove mentionned files from the source tree A+

2 1

re: hi wine team
by Dan Kegel 08 Apr '03

08 Apr '03

> did the wine team consider construct the win32 support (wine) within a > micro-kernel architecture, just like the microsoft`s interix ? "Just like microsoft's Interix"? We have no idea how Microsoft implemented that stuff; it's not bundled with Windows, so not many people see it, and it's closed source, so it's a bit hard to distinguish a microkernel from a regular kernel. Please post some code so we know you're not a troll :-) - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

--with-nptl and RH 8 : unhappy
by Sylvain Petreolle 08 Apr '03

08 Apr '03

Having RH 8.0 with glibc-2.3.2, I tried to compile Wine wiht --with-nptl. Wine compiles fine but doesnt run at all. Every application I try to run calls the debugger in a loop. [syl@snoop c]$ wine --debugmsg +relay notepad trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 [syl@snoop c]$ err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec98 ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 3

winelib/mfc queries
by KK singh 08 Apr '03

08 Apr '03

I am using 20030318 build of wine ... 1. WINE_UNICODE_TEXT is no longer defined anywhere in any of the header files ? What should i do now with OLESTR ? 2. Should i define _AFXDLL while compiling mfc ? Regards kks __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com

2 1

Who is the expert on named_pipe.c
by Bill Medland 08 Apr '03

08 Apr '03

I've found a problem with the named_pipe.c in the server. Is there anyone out there who purports to be an expert or is it up to me to fix it? (Basically the server is creating a named pipe, reading from it, writing back to it, flushing and closing, all before the client has read the reply; the wineserver crashes as the client tries to read because it's copy no longer has an fd) -- Bill Medland ACCPAC International, Inc. medbi01(a)accpac.com Corporate: www.accpac.com Hosted Services: www.accpaconline.com

2 2

why the wine not use the dll binary?
by Yu Neil 08 Apr '03

08 Apr '03

hello: why the wine not use the dll binary? but to rewrite the windows interface? Neil Yu _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

2 1

Re: PATCH: client side SuspendThread() handling when using valgrind
by Dimitrie O. Paun 08 Apr '03

08 Apr '03

On April 7, 2003 10:41 am, Adam Gundy wrote: > the attached patch is a reworking of the previous valgrind patch's > SuspendThread() changes so that the client only suspends threads locally > when running under valgrind. What about: +#ifdef HAVE_VALGRIND_MEMCHECK_H +#include <valgrind/memcheck.h> +#else +#define RUNNING_ON_VALGRIND 0 +#endif so we can eliminate the ugly ifdefs? -- Dimi.

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