wine-devel April 2004

wine-devel@winehq.org

138 participants
323 discussions

Re: Re: wineserver: correctly free the debug ctx
by Pouech Eric DMI AEI CAEN 07 Apr '04

07 Apr '04

> It seems to me this will cause the context to never be freed. I don't > understand the problem with multiple processes, the context is bound > to the debugger thread so it shouldn't make any difference how many > processes are being debugged. Could you please give more details on > the problem? well, problem (sigsev in wineserver) happened when quitting windbg after debugging several processes. I'll try to reproduce it over this weekend. A+

1 0

Re: Game support
by James Perry 07 Apr '04

07 Apr '04

Sorry, meant to send this to the list first time around... >> But I narrowed it down to 3 Wine calls in the >> critical loop: SetEvent, WaitForSingleObject and ResetEvent. >> I tried wrapping each of these functions with >> __asm__("pushfl\n"); at the start and __asm__("popfl\n"); at >> the end to preserve the flags - with this, PECrypt works >> fine and the game gets as far as trying to initialise >> DirectX. Not exactly a neat fix though. > > > Did you have to do all of them, or is it just one function that needs this > treatment? SetEvent definitely needs it. The others possibly don't. But I think it would be more robust to preserve the flag through all of them anyway, in case someone makes a change in future that causes one of the others to clear the direction flag too, which seems quite possible. > Are you sure it's not that we need to set the flag before > jumping to the entrypoint? The flag is normally cleared. PECrypt sets it explicitly, then expects it to remain set across those three API calls. > PECrypt sounds like it should run very early on > in the programs lifetime: how much stuff does it do before hitting this > bug? AFAIK, PECrypt just decrypts and decompresses the executable at startup, then it goes away and the program runs as normal. This bug does happen very early on. > If there is really widespread software that depends on > this behaviour though there is precedent for including a hack for it - see > the DllMain wrapper which preserves %ebx for an example. Certainly anything compressed with PECrypt will depend on the flag being preserved. In general I'd imagine it's quite rare for programs to run with the direction flag set for long periods though. Cheers, James

1 0

ole32.dll_CoRegisterPSClsid
by Paul Ortyl 06 Apr '04

06 Apr '04

Hi, If only ole32.dll.CoRegisterPSClsid() is implemented (empty stub returning '1' is enough) then the application "GeoGeogrid® for Windows©" starts and allows at least some basic operations. (tested with "Baden-Würtemberg AMTLICHE TOPOGRAPHISHE KARTEN" Top50, Version 4) For more info on GeoGrid you may look at: http://swpat.ffii.org/patents/effects/geogrid/index.en.html http://www.eads.net/frame/lang/en/xml/content/OF00000000400004/4/20/534204.… Basically all official topographical maps in Germany are available only through this proprietary application. It would be really useful if ole32.dll.CoRegisterPSClsid() could be implemented in (next) release... TIA Paul Ortyl -- Don't take life too seriously; you will never get out of it alive. -- Elbert Hubbard

1 0

AbiWord on ReactOS
by Steven Edwards 06 Apr '04

06 Apr '04

Note there are still a few minor bugs but for the most part it seems we have a real application working on ReactOS. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

1 0

Re: WININET: move to Windows sockets
by Juan Lang 06 Apr '04

06 Apr '04

> Geoff wrote: > > Or we write our own BIO that wraps up whatever > > glue is desirable on the wine-side. Worst-case > > (and it's not that bad an alternative) is that > > you use a memory-base BIO to encapsulate all I/O > > and worry about moving data to and from "sockets", > > whatever they look like, afterwards. > > That's what I've always done. <snip> > So it's not a bad way to go at all. Yep, in fact the "real" way to do this as far as Wine is concerned is to implement SSL in secur32.dll, since this is where Windows does it. It looks about like this, although as Geoff pointed out to me the API is a bit broken. Doing a BIO inside wininet.dll might be more expedient for Hans, who I think is trying to get as much of Wine as possible ported to MinGW. You guys that know SSL better than I do: patches welcome :) --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

2 1

Re: Game support
by Ivan Leo Murray-Smith 06 Apr '04

06 Apr '04

> btw, are there already any automated tools for parsing Wine logs? There is the examine-relay perl script in the tools directory, but it's only for relay traces. Ivan.

1 0

Re: development speed
by Brian Vincent 06 Apr '04

06 Apr '04

> Check that out - 5mb of patches for the last 3 months running. A meg of > patches just 6 days into the new month already! > > It seems Wine is moving faster than ever before. The website stats are interesting too: Daily Avg | Monthly Totals Hits Pages Visits| Sites KBytes Visits Pages Files Hits Mar 2004 267733 75495 16582 |268931 157346721 514060 2340347 7064537 8299737 Feb 2004 278180 79217 17199 |279399 203400907 498774 2297305 6994822 8067232 Jan 2004 135477 44930 8341 |154109 90054340 258586 1392848 3591136 4199791 Dec 2003 213993 71246 14408 |243882 138401056 446653 2208643 5725553 6633804 Nov 2003 244427 85277 15766 |254363 153748583 472983 2558310 6268477 7332826 Oct 2003 275663 111913 17352 |260400 161803798 537913 3469326 7430846 8545582 Sep 2003 156860 50508 10393 |173365 93441224 311790 1515269 4048260 4705814 Aug 2003 209530 69084 12812 |218040 124270932 397177 2141613 5612004 6495449 Jul 2003 243646 105136 12253 |197296 123038700 379853 3259216 6704428 7553047 Jun 2003 253998 109167 12250 |160468 91985851 306270 2729185 5642823 6349961 May 2003 262218 111683 13764 |207954 105320483 399181 3238809 6336486 7604349 Skipping to the KBytes and Hits columns, things are up. Even more interesting is in Feburary we got Slashdotted and in March we didn't. So it appears people are interested. Generally things begin to taper off as we approach summer. Last year we got some good PR by doing an interview series, so I'm planning on doing that again. Anyone know what happened on October 5th and 6th that generated so many hits? -Brian

1 0

Compiling Wine with BiDi support - instructions
by Shachar Shemesh 06 Apr '04

06 Apr '04

Hi list, Here are the formal instructions for compiling Wine with bidi support. When doing so, it is recommended that you use a fairly recent version of ICU (2.6 and up), or else there is going to be a runtime soft dependancy on some ICU files in the resulting Wine. No big deal - if these files are not there, Wine will work just fine, only without BiDi support. Still, this is not necessary. Instructions: 1. If you use a precompiled package (relatvely rare for ICU, unfortunatly), make sure it has the static libraries as well. ICU does not have these by default. If they are there, you may skip to step 8. Please note, however, that this will add about 7MB to the size of the resulting gdi.dll.so. 2. Grab ICU from the web http://oss.software.ibm.com/icu. 3. Extract the sources file. 4. CD into the ICU directory, and then into the "source" subdirectory. 5. Delete all files with the "mk" extension under icu/source/data. e.g. run "find data -name \*.mk -exec rm \{\} \;". Please trust me on this one, it's ok to do it. This step saves the aforementioned 7MB. 6. ./runConfigureICU LinuxRedHat --enable-static. If you are only building this for use with Wine, you can also add "--enable-shared=no --enable-64bit-libs=no --prefix=~/icuinstall". If not, you may wish to skip the previous step as well. 7. run "make" and "make install". Grab a lunch. Just one will do. 8. If your ICU library files are installed in /usr/lib and /usr/include, compile wine as usual. If they are installed anywhere else, you will need to set the "ICU_LIB_DIR" environment variable to wherever it was that they are installed. You will also have to add the include path. For example, if you compiled and installed icu according to my example above, you will need to set ICU_LIB_DIR to "~/icuinstall/lib", and also CPPFLAGS to "-I~/icuinstall/include". 9. Make sure that including "ubidi.h" and the following linking step passes in "configure". Also check whether include/config.h has "HAVE_ICU" set. 10. To be really sure that your wine supports BiDi, run the program given in this email. A few things to note: * The above assumes that your Wine already has http://www.winehq.org/hypermail/wine-patches/2004/04/0088.html integrated. * If you are compiling Wine on Debian, and want to use the Debian supplied ICU library for whatever reason (for example - because the packaging system pretty much requires you to), the above procedure needs to be slightly altered. ICU changed their static library naming scheme over some recent version. The Debian packaged ICU (2.1) still uses the old scheme. Either use Wine without the aforementioned patch, or set ICUUC_LIB and ICUDATA_LIB to the full path to libicuuc.a and libicudata.a respectively (they are called "libsicuuc.a" and "libsicudata.a" in newer version of ICU). Please note that this means there is a runtime dependancy on some ICU files for BiDi to work, as explained above. Instead of reposting the program for testing whether Win32 supports reordering, the link to the file in the list's archive is at http://www.winehq.org/hypermail/wine-devel/2003/08/att-0175/01-biditest.c. Enjoy -- Shachar Shemesh Lingnu OpenSource Consulting http://www.lingnu.com/

1 0

Re: Dos INT15
by Dmitry Timoshkov 06 Apr '04

06 Apr '04

"Florian Goth" <Captainsifff(a)gmx.de> wrote: > Added some more stubs after examining the dosbox source code Could you please try to stick to the formatting style used in the file in your changes? -- Dmitry.

1 0

development speed
by Mike Hearn 06 Apr '04

06 Apr '04

Hey guys, http://www.winehq.org/hypermail/wine-patches/ Check that out - 5mb of patches for the last 3 months running. A meg of patches just 6 days into the new month already! It seems Wine is moving faster than ever before. To put things in perspective, the Wine source tree is 10mb - that means in only 2 months as many lines of patch were generated as exists in Wine itself! thanks -mike

2 2

← Newer
1
...
25
26
27
28
29
30
31
32
33
Older →

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 April 2004