April 2002 - Wine-Devel - list.winehq.org

cool font viewer... might make good test case

by Dan Kegel

FYI... My wife is a Windows user who loves fonts. She never found good free font viewing utilities until today; now she's raving about 'font xplorer lite'. Since it's a free download, it might make a good testcase for Wine's font support. It's at http://www.moonsoftware.com/freeware.asp but I haven't tried it yet. - Dan

April 4, 2002

posting wineconf info to slashdot?

by Michael Cardenas

Now that we have the video feeds, some of the presentations, and some pictures, does anyone think we should post links to slashdot so everyone who couldn't attend can see what went on?

April 4, 2002

Crossover/WINE Test In Large Rollout

by Dave Richards

All- I am not on this list, so if you would like to respond to me you will have to reply to me directly. This is a real world situation where WINE could be used for a massive sever rollout (hundreds of users) and is having some problems in our environment. The City of Largo, Florida is a large Linux and thin client shop that has deployed a PC-less network for running out software. We are currently doing some R&D into options for running Lotus Notes in our environment. Our first choice obviously would be a native client running on Linux---it doesn't exist. We haven't looked at WINE in about 2 years and today the kind folks at CodeWeavers allowed us to test their new release with the Lotus Client. Here are the problems--> 1) Endian Bug. WINE is not able to detect that the runtime Endian order might be different than the server. Our Xterminals are RISC based and obviously WINE is running on Intel. All of the colors display incorrectly because of this. 2) Performance. On remote displays WINE is *much* slower than it is on the console. The Lotus Notes client took over 5 minutes to run remotely whereas on the console it comes up in about 20 seconds. I am assuming that it is making use of some of the XFree extensions for performance and that perhaps they have to timeout and drop through code in order to run on our Xservers. Once it is running, performance is much better, but the initial startup make it undeployable. We are thankful for everyone that has gotten WINE this far and that it works as well as it does considering the complexity of this task. If these areas are ever addressed, we would be happy to explore the product again! Dave Richards City of Largo, FL Systems Administrator

April 4, 2002

Re: ReadFile and WriteFile in overlapped mode

by Tony Bryant

On Fri, 05 Apr 2002 06:01, Jacques Gelinas wrote: > I have been looking at those two functions and some specs. My understanding > is that those function do not work at all in overlapped (async mode). > Currently (latest stuff in CVS), both function handle overlap mode like > this > > a) Give it a try in synchronous mode using a combination > of pread/read and pwrite/write. > > b) If not enough bytes were read or written, a request > is sent to wineserver to perform and asynchronous > operation. This request always fail. (don't know why yet). > > There is two problem here. If step a succeed, no event will ever be > generated since step be is not performed. Application doing the following > sequence > > ReadFile > .. > WaitOnSingleObject > > will wait forever. Some borland Builder classes do this > > My understanding is that step a should never be done and only step b. > Is that correct ? > > Now, why step b is failing is another story. > I fixed this a while ago, but never finished submitting the patch. The problem is that wine uses async callbacks to signal the event in the overlapped structure, which is a problem, because async callbacks can only happen when WaitOnSingleObjectEx specifically allows them. The solution is to have the wine directly trigger the event without going through the async callback system.

April 4, 2002

Re: ReadFile and WriteFile in overlapped mode

by Mike McCormack

Hi, > I have been looking at those two functions and some specs. > My understanding is that those function do not work at all I haven't tested the current CVS lately, but i can assure you that ReadFile and WriteFile did work at some fairly recent time :-) You may be correct that they do not work in *exactly* the right way, but for most cases they do work. > ever be generated since step be is not performed. Application > doing the following sequence > ReadFile > .. > WaitOnSingleObject > > will wait forever. Some borland Builder classes do this No, it won't because asynchronous reads can be processed during on-alertable waits. The application must call WaitForSingleObject eventually to see f the overlapped operation has finished. > My understanding is that step a should never be done and only > step b. Is that correct ? We need to check if data is pending before returning RROR_IO_PENDING because some applications do this: WaitCommEvent(hComm,&ev,&ov); WaitForSingleObject(ov.hEvent); ClearCommError(hComm,NULL,&cs) len = cs.cbInQue; if(!ReadFile(hComm,buf,len,&count,&ov)) FATAL() You're right that the way wine currently handles this is not erfect, but it will only fail if multiple overlapped operations re done at the same time. Martin Wilck is currently fixing this. > Now, why step b is failing is another story. > > Comments ? It's not perfect, and you're welcome to fix it if you want. Mike ------------------------------------------ mailto:Mike_McCormack(a)start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

April 4, 2002

Re: SetCooperativeLevel

by Tels

-----BEGIN PGP SIGNED MESSAGE----- Moin, On 04-Apr-02 Dimitrie O. Paun carved into stone: > On April 4, 2002 12:55 pm, Tels wrote: > >> wine-devel-patches? wine-devel? winex-devel? Under what license would it >> fall? Or does that not matter? > > Patches for the public tree go to wine-patches and fall under LGPL unless > you relicense them with another license. Okay. LGPL for these parts then. Fine by me. > The transgaming tree is proprietary, > and no code from it can go to the public tree unless transgaming > donates it. Okay. But that doesn't really answer my qustion, since it that case *I* am writing the code and not Transmeta (well, not sure if this matters ;). Does my code fall automatically under the transgaming licence when I patch insise their CVS tree? Can arrange that my code goes automatically public, or do I just have to hope that someday transmeta will release stuff (meaning that I work for free for transmeta, and they just hold on to my patches/work?) Thanx in advance! >> * Also, since I am a bit CVS challanged (newbie, I told you ;), is it [snip] > If you just modify some file, simply modify them in place, then do a Thank you for your explanations! Cheers, Tels - -- "Why do you go so slowly? Do you think this is some kind of game?" PGP key available on http://bloodgate.com/tels.asc or via email. perl -MDev::Bollocks -e'print Dev::Bollocks->rand(),"\n"' vitalistically harness industry-wide e-business -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. iQEVAwUBPKzIhncLPEOTuEwVAQGsXwf+PL1QL/WwnaDdytdLROjEyCcHRB+J6N1t w2AlSOepo3AyN8VWYws9p5eZb/5zVkSaLcscmI0PruTndHKnJ/qhDoKrwFtuLjZM Ox6JfKW8Aw6eVsTRXxBP17HckETwMaUHrs7u/GYzOwfOKLBZ20i4Rh1iSuCavvEP kK9Aji/UF/ztDhLjXezPouGj7O4F9Kgz4wy29tuacFNUxbNntv4+l827HccB2i0D 9RXcfCM9Teg+f+1ebZet7iwtokkyUYdYRL3MgBItYjCbzMZM/oKOCMj+XEwpzHhn deRHKZF71un44EorpXdP8fFIIJWbTywOzScv4I5kcezaabhmulLdFQ== =xL49 -----END PGP SIGNATURE-----

April 4, 2002

Re: Review - Winnt.h warning patch for mingw32

by Francois Gouget

On Fri, 5 Apr 2002, Dmitry Timoshkov wrote: > "Steven Edwards" <Steven_Ed4153(a)yahoo.com> wrote: > > > diff -u -r1.104 winnt.h > > --- winnt.h 2 Apr 2002 19:37:15 -0000 1.104 > > +++ winnt.h 4 Apr 2002 08:15:55 -0000 > > @@ -80,9 +80,11 @@ > > #ifndef __WINE__ > > #define pascal __stdcall > > #define _pascal __stdcall > > +#if ! defined(__WINE__) && !defined(__MINGW__) > > #define _stdcall __stdcall > > #define _fastcall __stdcall > > #define __fastcall __stdcall > > +#endif > > #define __export __stdcall > > #define cdecl __cdecl > > #define _cdecl __cdecl > > Why don't you use something like this: > > +#if !defined(_stdcall) > #define _stdcall __stdcall > #define _fastcall __stdcall > #define __fastcall __stdcall > +#endif Is _stdcall going to be a macro? I would rather expect it to be a reserved keyword like in Visual C++. Steven's patch looks good to me. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Advice is what we ask for when we already know the answer but wish we didn't -- Eric Jong

April 4, 2002

Re: [PATCH] async IO APCs call check_async_list() directly

by Mike McCormack

Hi Martin, I think this is a better way to do things, but it might be better to submit this patch against the current CVS rather than against CVS+previous patch. Mike Original message from: Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> > > >PATCH: async-func.diff > >This is an improvement over my previous patch (async-struct.diff) >in that it does not need the static function check_async_lists >in several source files anymore and still achieves DLL separation. > >The idea is that all async I/O requests use check_async_list as callback function >anyway, so that there is no need to pass a function pointer. >I discussed the idea with Mike, and he seemed to like it. > >Patch against: Wine CVS 2002/04/04, with my async-struct patch applied. >Test status: Compiles warnings. > Tested regular file async IO (ok). > Serial port async IO: a test would be desirable. > ------------------------------------------ mailto:Mike_McCormack(a)start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

April 4, 2002

Re: [PATCH] async IO APCs call check_async_list() directly

by Mike McCormack

Hi Martin, I think this is a better way to do things, but it might be better to submit this patch against the current CVS rather than against CVS+previous patch. Mike Original message from: Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> > > >PATCH: async-func.diff > >This is an improvement over my previous patch (async-struct.diff) >in that it does not need the static function check_async_lists >in several source files anymore and still achieves DLL separation. > >The idea is that all async I/O requests use check_async_list as callback function >anyway, so that there is no need to pass a function pointer. >I discussed the idea with Mike, and he seemed to like it. > >Patch against: Wine CVS 2002/04/04, with my async-struct patch applied. >Test status: Compiles warnings. > Tested regular file async IO (ok). > Serial port async IO: a test would be desirable. > ------------------------------------------ mailto:Mike_McCormack(a)start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

April 4, 2002

Re: DeviceIoControl

by Laurent Pinchart

> > I'll add a check for the 0x10000 and 0x20000 bits, and will dispatch the > > call to either a VxD or a device handler. Is that ok ?Can I use the same > > VxD list as for (HIWORD(dwIoControlCode) == 0 ) ? > > I don't follow you, you only need the VxD list when the hiword is 0 I'm trying to implement support for a WDM driver (.sys). The driver registers itself by calling IoCreateDevice with DeviceType set to 0xef00. The user program calls CreateFile( "\\\\.\\MyDriver", ... ) and uses the returned handle in the call to DeviceIoControl, with dwIoControlCode set to 0xef002407. The dwIoControlCode higword is not 0. Shouldn't we have a handler list, similar to the VxD list in this case ? Laurent Pinchart

April 4, 2002