wine-devel April 2004

wine-devel@winehq.org

138 participants
323 discussions

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

Re: WININET: move to Windows sockets
by Dan Kegel 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. And it seems I've managed (via the rant at http://kegel.com/ssl/api.html) to convince Sun to make that the standard way to do ssl with NIO under the next JDK, kinda. So it's not a bad way to go at all. - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

1 0

Re: appdb - improvement in serching out bugs
by tony_lambregts＠telusplanet.net 06 Apr '04

06 Apr '04

Quoting hatky <hatky(a)hatky.myz.info>: > > On Sunday 04 April 2004 06:21, tony_lambregts(a)telusplanet.net wrote: > > The current code can get bugs that have nothing to do with the AppDB. > This > > should fix it. > > > > -- > > > > Tony Lambregts > > I think this is wrong, you are saying the url in bugzilla should be exactly > "appdb #" where it should realy be > "http://bugs.winehq,org/show_bug.cgi?id=#" > > No, no, no... read the patch again. The current code is correct as far as it goes, but it grabs the substring. So when the appdb# is 68 it grabs bugs that for appid 680, 681... 689. It will also grab bugs that just happen to have 68 in the url. My testing with this has been limited somewhat since I have not been able to set up the appdb on my machine but I know enough to know that the code as I have submitted will do what it needs to do. -- Tony Lambregts

2 1

DDraw issues, etc.
by Tim Hentenaar 06 Apr '04

06 Apr '04

Hi all, I've implemented SetClipList and GetClipList in the DirectDraw Clipper, and I'm wondering how I should go about implementing clipping in DirectDraw's Blt() (if it isn't already done somewhere). M$'s documentation isn't too great, so I figured I should ask around. There's a game one of my relatives wants to run under Linux (it's a children's program), and the major problem is that it dosen't seem to handle clipping properly when blitting. (e.g. every time you move the mouse, it calls SetClipList). FYI, the binkw32.dll that came with the program was originally causing it to hang, but I patched the DLL and it works fine. If anyone else has had such problems, I could provide a patch. Also, I'm going to take a look at some of the DirectSound stuff too. The sound isn't very good quality for some reason, but under the WineX 3.3 CVS, sound works perfectly. Tim

3 11

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

06 Apr '04

Hans wrote: > On Monday 05 April 2004 19:24, Alexandre Julliard > wrote: > > There's no real reason that we cannot use Unix > > sockets on Unix and Windows socket on Reactos with > > the same code, it just needs a bit of header magic; > > and this will be useful for Winelib apps too. > > Hmm, I'd like to agree with that. I'd be rather nervous about the mixing of OpenSSL with the use of Winsock, at least as is. OpenSSL is itself using socket read/write calls, and it expects them to be the correct ones: in particular, the UNIX ones. I believe the only way to do this correctly is to write a new OpenSSL BIO that uses the same read/write/open/close calls as the rest of netconnection.c, and this can be combined with the aforementioned header magic to get what you're after. Copying and pasting an existing OpenSSL BIO would probably suffice. --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

2 1

Re: wineserver: correctly free the debug ctx
by Alexandre Julliard 05 Apr '04

05 Apr '04

Eric Pouech <pouech-eric(a)wanadoo.fr> writes: > when a debugging thread is attached to several processes, the debug > context (shared across all processes) is destroyed when the first > process terminates. This patch destroys it when the last process > attached terminates. 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? -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: WININET: move to Windows sockets
by Steven Edwards 05 Apr '04

05 Apr '04

Hello Hans, --- Hans Leidekker <hans(a)it.vu.nl> wrote: > > This makes wininet build on MinGW. > > Changelog: > Move to Windows sockets. > I asked Alexandre about a patch to move Wininet to Winsock and he said it took to much of a performance hit to merge. Is there a way we can bench mark it to show how much of a hit Winsock vs Unix sockets is going to give us? He suggested that we find a way to make Wininet use Unix sockets on Unix and Winsock on Windows. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

6 7

Re: appdb - improvement in serching out bugs
by hatky 05 Apr '04

05 Apr '04

On Sunday 04 April 2004 06:21, tony_lambregts(a)telusplanet.net wrote: > The current code can get bugs that have nothing to do with the AppDB. This > should fix it. > > -- > > Tony Lambregts I think this is wrong, you are saying the url in bugzilla should be exactly "appdb #" where it should realy be "http://bugs.winehq,org/show_bug.cgi?id=#" -- Hatky, Worshiper of wine (http://www.winehq.org/), Impossible is only an opinion.

1 0

CryptoAPI
by "Jacek [KRunch] Chałupka" 05 Apr '04

05 Apr '04

Has anybody started implementing CryptoApi in WINE?? If no mayby someone can give me some clues how to start... I am not bad i C++ I think, but I have never make thing like that. I don't promise I will do that, but I can try... :)

3 2

Re: CryptoAPI
by Juan Lang 05 Apr '04

05 Apr '04

Jacek wrote: > Has anybody started implementing CryptoApi in WINE?? > If no mayby someone can give me some clues how to > start... I am not bad i C++ I think, but I > have never make thing like that. I don't promise I > will do that, but I can try... :) Hi Jacek, take a look at Wine's rsabase.dll, that DLL doesn't do very much yet. All its functions (CPAcquireContext, etc) are described here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/s… If you have access to a Windows box it's easier: you can load the DLL itself and call all the functions and try to reproduce what it's doing. Good luck, --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

1 0

Re: Fwd: Re: appdb - improvement in serching out bugs
by tony_lambregts＠telusplanet.net 05 Apr '04

05 Apr '04

Quoting hatky <hatky(a)hatky.myz.info>: >> No, no, no... read the patch again. > Ok, sorry wasn't what I tought you are trying to do, this patch is ok > p.s. I didn't think someone actually changed the urls in bugzilla. sweet :). I have been going through them 100 at a time. I've got 1-400 done at this time. I figure I will be done sometime before Christmas :P. If anyone wants to help with this I would be glad to have the help... Check out http://bugs.winehq.org/show_bug.cgi?id=560 for more more on this. -- Tony Lambregts

1 0

NtPulseEvent
by Robert Lunnon 05 Apr '04

05 Apr '04

What is the status of NtPulseEvent it emits a diagnostic messages fixme:ntdll:NtPulseEvent (7c,0) yet it looks to me that NtPulseEvent is implemented but the fixme is bogus Anyone know about this ? BTW Has anyone experience with the Skype application under linux, does it work there ? Bob b

2 1

Should winemaker be able to handle this
by Bill Medland 05 Apr '04

05 Apr '04

I haven't been following the winemaker stuff so I don't know whether it is supposed to be able to handle this (and is broken) or not. I am having to play with the "build a builtin dll to wrap a linux so" concept again after a year or so since the last time, as discussed in the Winlib manual, chapter 5. I see that winemaker has changed since then. In particular the bit that is not working for my case is the -D, -I, -L and -l options. What I want is to run winemaker to generate the build environment and then do the build. What I used toi have was: #! /bin/bash # Run this script in order to pass the correct arguments to winemaker so that # it can set up the build environment winemaker --nosource-fix --nogenerated-specs --dll --single-target mytarget --nomfc -DMY_SETTING -I$MY_INC_DIR -L$MY_LIB_DIR -lmylinuxso . I see that we don't bother with generating spec files any longer. However I see that the -D, -I, -L and -l options don't find their way into the Makefile these days. Is that by design or a bug? (i.e. do I have to fix winemaker or do I need to look at a different way of doing it) -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

4 5

RE: Handling dialogs created without using templates
by Santosh Siddheshwar 05 Apr '04

05 Apr '04

Hi, Thanks. Would you be able to share details of the changes you did for handling MDI windows? Regards Santosh > -----Original Message----- > From: Dmitry Timoshkov [SMTP:dmitry@baikal.ru] > Sent: Tuesday, March 30, 2004 7:40 PM > To: Santosh Siddheshwar > Cc: wine-devel(a)winehq.com > Subject: Re: Handling dialogs created without using templates > > "Santosh Siddheshwar" <santosh.s(a)sonata-software.com> wrote: > > > Yes attached is a sample which is pretty similar to what I described > > below. > > Thanks. Now I see where the problem is. We have to hook dialog creation > code into common window creation code, something similar to what I've done > recently for MDI. Alexandre, are my thoughts correct? > > -- > Dmitry. ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

Re: Re: dbghelp
by Pouech Eric DMI AEI CAEN 05 Apr '04

05 Apr '04

> UnDecorateName is still a stub, while our winedump has some a good > framework for UnDecorateName, also translating into a GCC way and not in a > VC++ way. How should these things go together? See the comment in dbghelp.c !! My first thouhgt would be to make a .a lib out of winedump code, and use it in winedump and msvcrt and / or dbghelp. I haven't studied yet the best way to share the code between msvcrt and dbghelp A+

1 0

Re: appdb - improvement in serching out bugs
by tony_lambregts＠telusplanet.net 04 Apr '04

04 Apr '04

1 0

Re: dbghelp
by Uwe Bonnes 04 Apr '04

04 Apr '04

>>>>> "Eric" == Eric Pouech <pouech-eric(a)wanadoo.fr> writes: Eric> Eric Pouech a écrit : >> This is a first (and incomplete) shot at implementing the dbghelp >> DLL. Eric> forgot to say that: - this patch must be applied before the ones Eric> on imagehlp & taskmgr - code is highly derivated from winedbg Eric> current code Eric> I'm also working on a winedbg version based on this DLL, but it Eric> isn't ready yet (as dbghelp seems to get a bit more mature, I Eric> thought some people might be interested in testing it) UnDecorateName is still a stub, while our winedump has some a good framework for UnDecorateName, also translating into a GCC way and not in a VC++ way. How should these things go together? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Personal tree with interesting patches
by Mike Hearn 04 Apr '04

04 Apr '04

Hi, As I'm pretty busy right now and won't have time to work on the various misc projects I've been working on up until recently for the foreseeable future, I'm checking them into my personal arch archive for people to play with and maybe work on themselves. My archive co-ordinates: http://navi.cx/~mike/archive/2004 mike(a)navi.cx--2004 so, you'd use: $ tla register-archive http://navi.cx/~mike/archive/2004 There are currently only two interesting branches: wine--mainline--0.9: misc patches that were never applied for whatever reason, debug delay, lockwindowupdate (disabled), that sort of thing as i find more patches around my system i'll check them in for safekeeping wine--loadarea-reserve--0.9 execshield/prelink work, see the log message in patch-1 for details on what remains to be done Have fun! thanks -mike

2 2

installation program
by Brian Vincent (C) 04 Apr '04

04 Apr '04

On the To Do List (c.4) is an item for having a new graphical Wine install program. Anyone ever looked at Frank Hendrickson's WineTools program? http://franksworld.net/winetools.html It used to be written in some funky language, now it's all shell script. Anyway, if you look at the script (wt210) you'll notice he uses xdialog ( http://thgodef.nerim.net/xdialog/ ) for the GUI. So here's what I'm wondering.. How feasible would it be for Wine to create a new Winelib program (say, wdialog) and use a similar concept as Frank? wdialog would simply replicate the functionality of xdialog. We could potentially fail gracefully into shell mode if Wine can't start. It might be a cheap and simple way to get a GUI front-end. Of course, all this requires sane defaults so Wine can actually run wdialog. Any thoughts? --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Microsoft SDK samples
by Jonathan Wilson 04 Apr '04

04 Apr '04

Has anyone given thought to using the Microsoft SDK samples (e.g. DirectX samples) to improve WINE? i.e. take a particular sample and work away at it untill what you get in WINE matches what you get in Windows. Although I suspect that there are things that the MS samples dont cover :)

2 1

winapi_stats
by Tom 03 Apr '04

03 Apr '04

Hi, http://www.winehq.org/site/winapi_stats Is incorrect as it shows Total 19640 100% 100% would be nice but its incorect! Tom

3 6

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