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

Re: Winelib and documentation

by Andriy Palamarchuk

Steve, --- steve_lustbader(a)hsgmed.com wrote: > I've been having some trouble using winelib (with > spec files) following the documentation on the web > site. A few people in the IRC channel were under > the impression that winelib had changed and the docs > aren't really relevant anymore. Wine is a quickly moving target and often some portions of documentation are outdated. I think one can't say that Winelib User Guide is not relevant anymore. Big part of information there is still valid. > Is the > documentation going to be updated to the current > status of the source? Yes, but I do not know when. As far as I know nobody is working on the guide right now. If you provide information which part of the guide is outdated somebody may want to fix it. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com

July 23, 2002

RE: wine/dlls crtdll/crtdll.spec crtdll/crtdll_mai ...

by Patrik Stridvall

> Modified files: > dlls/crtdll : crtdll.spec crtdll_main.c > dlls/msvcrt20 : msvcrt20.spec > dlls/shell32 : shell32.spec > > Log message: > Fixed broken forwards reported by Patrik Stridvall. Much better. No broken forwards reported by winapi_check any longer. However I don't think your fix was 100% correct. winapi_check now says dlls/msvcrt/string.c:52: <>: char * _strdec(char *,char *): documentation: _strdec (MSVCRT.@) wrong dlls/msvcrt/string.c:75: <>: char * _strinc(char *): documentation: _strinc (MSVCRT.@) wrong dlls/msvcrt/string.c:83: <>: unsigned int _strnextc(char *): documentation: _strnextc (MSVCRT.@) wrong dlls/msvcrt/string.c:93: <>: char * _strninc(char *,unsigned int): documentation: _strninc (MSVCRT.@) wrong dlls/msvcrt/string.c:143: <>: unsigned int _strncnt(char *,unsigned int): documentation: _strncnt (MSVCRT.@) wrong dlls/msvcrt/string.c:152: <>: char * _strspnp(char *,char *): documentation: _strspnp (MSVCRT.@) wrong The problem is not what the error messages suggest though, winapi_check is far from prefect. :-) Anyway, the real problem seems to be that the the functions you implemented in crtdll_main.c were already implemented in msvcrt. However they were not exported. Examining the msvcrt.dll on my Windows 98 computer indicates that this is correct they shouldn't be exported. crtdll.dll does exactly as Wine does though. So I guess the implementation of the functions above should only be in CRTDLL and not in MSVCRT. Will you fix it or should I?

July 23, 2002

Winelib and documentation

by steve_lustbader＠hsgmed.com

I've been having some trouble using winelib (with spec files) following the documentation on the web site. A few people in the IRC channel were under the impression that winelib had changed and the docs aren't really relevant anymore. Is the documentation going to be updated to the current status of the source? ****************************** Steve Lustbader Philips Medical Systems E-mail: steve_lustbader(a)hsgmed.com 3000 Minuteman Road, MS 0105 Voice: 978 659 3713 Andover, MA 01810

July 23, 2002

Re : Coded breakpoints

by Max

Never mind, if WAS a stupid question :-) For who needs it too, just add __asm__("int $0x03\n\t") ; at the required point, maybe inside an huge if(....) Regards Max

July 23, 2002

Coded breakpoints

by Max

Maybe it's a stupid question, but... is there a way to hard-code a breakpoint ? I need to check a bit of code that gets called too many times and I'd like to put a conditional breakpoints compiled in code; no way to use winedbg built-in conditional breaks, the condition is too complicated..... Regards Max hmmm... BTW, somebody knows what's the meaning ow window message # 0x1018 ? :-)

July 23, 2002

Problem with wineconsole

by DanteAliegri

I'd suggest the following patch as an easy way to tell that something in wineconsole is going wrong. All I was getting was that the backend had failed - no indication of why. --Dante --- user.c Tue Jul 23 09:29:23 2002 +++ newuser.c Tue Jul 23 09:29:54 2002 @@ -550,7 +550,7 @@ fc.data = data; fc.done = 0; EnumFontFamilies(PRIVATE(data)->hMemDC, NULL, get_first_font_enum, (LPARAM)&fc); - if (!fc.done) WINE_WARN("Couldn't find a decent font, aborting\n"); + if (!fc.done) WINE_ERR("Couldn't find a decent font, aborting\n"); return fc.done; }

July 23, 2002

Dinput - Keyb Bug

by Kristoffer Ericson

I'm trying to get StarSiege Tribes (1) to work, and from what i gather is it suffering from a quite common wine-gaming-problem (both wine & winex). The game starts smoothly enough but keyboard is dead. When i press any key it will instantly drop out and quit. No error message or breaks. Considering the keyboard makes you move it basicly leaves you jumping up and down shooting at everything that comes..=) Other than the keyboard error tribes runs fine. I daily run updates from winex & wine but been working at this problem for about 2 weeks. I've read all the info i could find on the subject and from what i can gather is that tribes used to work on older wine. So can anyone give me some futher info about where i could find older wine-archives or if the dinput (i guess the problem is due to dinput) problem is about to be solvedŽ, tweaks, patches, ideas.. With respect Ken _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

July 23, 2002

Re: Threading on Solaris

by Gregg Mattinson

Threads on Solaris are a big issue for Sun, so I will start tackling this problem today. Thanks for telling me all the issues Francois. I have a hack-ish version implemented, and now I can create a real solution to the problem. Gregg Mattinson Co-op Developer Sun Microsystems of Canada >From: Francois Gouget <fgouget(a)codeweavers.com> >To: wine-devel(a)winehq.com >CC: Gregg Mattinson <gm138242(a)opcom-mail.canada.sun.com> >Subject: Threading on Solaris >Date: Tue, 23 Jul 2002 00:35:09 -0700 > >Hi, > > >Some time ago I did some tests of Wine on Solaris x86 and found that >there is a problem with the way we handle threads due to the differences >between the Linux and Solaris threading models. These differences are >also relevant for Solaris Sparc and probably many other Unices. > >Unfortunately I don't have time to work on it anymore so I created a bug >report in Bugzilla where I tried to dump the relevant information, >including a patch to illustrate the issues and the start of a fix. I >hope it will be useful to someone... maybe Gregg who has been doing a >lot of Solaris work recently. > >http://bugs.winehq.com/show_bug.cgi?id=904 > > >-- >Francois Gouget >fgouget(a)codeweavers.com

July 23, 2002

Re: [Q] CreateProcess for Batch files

by us＠the-edmeades.demon.co.uk

>I don't think we want to check extensions this way. We should simply >hand off all command lines we cannot execute another way to the >command interpreter (which could be made configurable so you can use >native cmd.exe if you have it). Isnt this what Windows uses the COMSPEC env var for? Surely we should (by default) set the COMSPEC env var to wcmd, and if someone wants to change it to the real cmd.exe then they can. If I remember rightly, a simple C pgm which issues system("fred.bat") fails, (cant remember what happens if you system a .exe though). This would then leave a change to the CreateProcess and varients to recognize bat pgms to launch the program defined in comspec by. Interestingly windows2000 seems to honour comspec, and .bat extensions are registered as 'batfile' (in registry) which in turn has a default handler of %1 %* which means internally it must recognize .bat extensions itself. Jason

July 23, 2002

Threading on Solaris

by Francois Gouget

Hi, Some time ago I did some tests of Wine on Solaris x86 and found that there is a problem with the way we handle threads due to the differences between the Linux and Solaris threading models. These differences are also relevant for Solaris Sparc and probably many other Unices. Unfortunately I don't have time to work on it anymore so I created a bug report in Bugzilla where I tried to dump the relevant information, including a patch to illustrate the issues and the start of a fix. I hope it will be useful to someone... maybe Gregg who has been doing a lot of Solaris work recently. http://bugs.winehq.com/show_bug.cgi?id=904 -- Francois Gouget fgouget(a)codeweavers.com

July 23, 2002