wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

Re: Shell32: Reimplement SHGetFolder functions
by Alexandre Julliard 15 Sep '04

15 Sep '04

Juan Lang <juan_lang(a)yahoo.com> writes: > +static void loadShell32(void) > +{ > + if (hShell32) > + { > + if (pMalloc) > + { > + pMalloc->lpVtbl->Release(pMalloc); > + pMalloc = NULL; > + } > + /* until it's really unloaded: */ > + while (FreeLibrary(hShell32)) > + ; I'm not sure what you are trying to do here, but this causes an infinite loop on XP (and it probably should under Wine too, since the test binary imports shell32). Also some tests fail on XP: shellpath.c:433: Test failed: SHGetFolderPath returned 0x00000000, expected 0x80070002 shellpath.c:438: Test failed: SHGetFolderLocation returned 0x00000000, expected E_FAIL shellpath.c:442: Test failed: SHGetSpecialFolderPath succeeded, expected failure shellpath.c:447: Test failed: SHGetFolderLocation returned 0x00000000, expected E_FAIL -- Alexandre Julliard julliard(a)winehq.org

2 3

Re: msvcrt: fill _chsize, _dup, _dup2
by Andreas Mohr 15 Sep '04

15 Sep '04

Hi, On Wed, Sep 15, 2004 at 06:53:28AM +0000, JustFillBug wrote: > > Use the POSIX peer. I don't think this is correct (and if it was, then it would have been done that way already, I guess). I'm not too familiar with our msvcrt, but it looks like these functions should definitely be implemented by means of our msvcrt's file handle management: msvcrt_alloc_fd(), msvcrt_alloc_fp() and many other related functions. Reason being that if you simply dup() an fd, that this properly registered source fd (in msvcrt, that is), would end up with a cloned fd that is NOT being properly registered on the msvcrt side. To make it more obvious: _close() uses msvcrt_fdtoh(), which would most likely fail for an msvcrt-foreign fd. Would be cool if you could implement it the correct way, though. Thanks, Andreas Mohr

1 0

DirectX compatability testing -- RFC results for running a specific program
by Belxjander Serechai 15 Sep '04

15 Sep '04

Ive got a small (can be transported on floppy disk) program that has a major and drastic result effect when run on a "pure" Wine only installation against both Xfree86 4.4.0 + Xorg 6.7.0, "Oh My Goddess - Smash The Bugs" ... I am curious as to anyone else Acquiring and testing this program against another installation. Im honestly not sure whether it is specifically my own setup or some interaction problem as it does a full X system deadlock and I have no response even when attempting to ssh into my own linux system I no longer have an active second machine to SSH from. I would like to confirm whether X alone or whether there is a full kernel level runtime deadlock occuring P.S. have to thank the person who gave such an eloquient reason to ignore trying to debug/test/ find those sections of the Wine "DirectX" implimentation needing work... since I wasn't interested in using the Windows release "DirectX" components for anything more than a compatability test suite to start with... Anyone else wanting to jump in feet first without asking questions? Thanks in advance, Jeremy Sutherland

2 2

Current cvs brokeness...
by James Pellow 15 Sep '04

15 Sep '04

Hi List, Just downloaded the most recent cvs, and noticed it can't run the Office 2000 installer. I haven't tried anything else, but it looks like a general msi failure. I can't spend any time on this (shouldn't be playing with it at the office anyway...) but here is the output: fixme:font:WineEngRemoveFontResourceEx :stub fixme:font:WineEngRemoveFontResourceEx :stub fixme:msi:MsiEnableLogA 00000516 "c:\\windows\\temp\\Office 2000 Professional Setup (0002)_MsiExec.txt" 00000000 fixme:msi:MsiInstallProductW L"/I" L"" fixme:msi:MSI_OpenDatabaseW open failed r = 80004005! Installation of /I () failed. Is the msi system brocken right now? I also noticed that the common file dialog seems to be returning garbage. Try selecting a file in progman-file-execute-browse for example. Just FYI... -- ***************************** James A. Pellow, President Alent Design Solutions www.alentdesignsolutions.com (509) 526-0682 *****************************

3 3

Cryptographic functions
by Alexander Yaworsky 15 Sep '04

15 Sep '04

Hello there is some secret crypto API in 2k and xp. Not so long ago i played with native rsaenh.dll under wine and found that it requires md5 and sha functions exported by advapi32.dll. I don't know where this API really should be. Latest platform SDK is very cryptic itself. Just in case here is a patch. IMHO it worths to be submitted but i'm not sure. Index: dlls/advapi32/advapi32.spec =================================================================== RCS file: /home/wine/wine/dlls/advapi32/advapi32.spec,v retrieving revision 1.55 diff -u -r1.55 advapi32.spec --- dlls/advapi32/advapi32.spec 14 Sep 2004 19:25:35 -0000 1.55 +++ dlls/advapi32/advapi32.spec 15 Sep 2004 11:56:04 -0000 @@ -1,3 +1,6 @@ +@ stub A_SHAInit +@ stub A_SHAUpdate +@ stub A_SHAFinal @ stdcall AbortSystemShutdownA(ptr) @ stdcall AbortSystemShutdownW(ptr) @ stdcall AccessCheck(ptr long long ptr ptr ptr ptr ptr) @@ -169,6 +172,9 @@ @ stdcall MakeAbsoluteSD(ptr ptr ptr ptr ptr ptr ptr ptr ptr ptr ptr) @ stdcall MakeSelfRelativeSD(ptr ptr ptr) @ stub MapGenericMask +@ stub MD5Init +@ stub MD5Update +@ stub MD5Final @ stdcall NotifyBootConfigStatus(long) @ stdcall NotifyChangeEventLog (long long) @ stub ObjectCloseAuditAlarmA

1 0

Re: Shell32: fix DllGetVersion for newer callers
by Robert Shearman 15 Sep '04

15 Sep '04

Juan Lang wrote: >A bit better than my last version, load the version >resource from the file for DllGetVersion, and update >the version of the file to produce the same output as >before. > >ChangeLog: add support for DLLVERSIONINFO2 in >DllGetVersion, and get version info from file > >--Juan > > ... >--- dlls/shell32/Makefile.in 11 Aug 2004 23:59:07 -0000 1.84 >+++ dlls/shell32/Makefile.in 14 Sep 2004 17:16:37 -0000 >@@ -4,7 +4,7 @@ > SRCDIR = @srcdir@ > VPATH = @srcdir@ > MODULE = shell32.dll >-IMPORTS = shlwapi comctl32 user32 gdi32 advapi32 kernel32 >+IMPORTS = shlwapi comctl32 user32 gdi32 advapi32 kernel32 version > DELAYIMPORTS = ole32 > EXTRALIBS = -luuid $(LIBUNICODE) > This is *really* ugly. Create a header file with just the version numbers defined and import it from the resource file and the file that implements the DllGetVersion function and problem solved. Rob

2 2

IUnknown_Release_Proxy leading to exception
by James Hawkins 15 Sep '04

15 Sep '04

This is the final debug output when I run ICQ: wine: Unhandled exception (thread 0023), starting debugger... fixme:console:SetConsoleCtrlHandler (0x405fbab0,1) - no error checking or testing yet WineDbg starting on pid 0x24 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x40ab8695). In 32 bit mode. q0x40ab8695 IUnknown_Release_Proxy [/home/truiken/wine/dlls/rpcrt4/cproxy.c:330] in rpcrt4: movl 0x0(%eax),%edx 330 return IUnknown_Release(This->pUnkOuter); 330 return IUnknown_Release(This->pUnkOuter); Wine-dbg>l syntax error Wine-dbg>list 330 return IUnknown_Release(This->pUnkOuter); 331 #endif 332 } 333 in reading the comments, the interface refcounting is commented out and object refcounting is what is being used. i added a refCount variable to cproxy.c and did refCount++ and refCount-- in IUnknown_Release_Proxy and IUnknown_AddRef_Proxy with additional trace statements that show the value of refCount. right before the exception, a trace shows refCount to be -1. This is the log of trace+relay,ole: 045:Call kernel32.InterlockedDecrement(41277154) ret=00405614 0045:Ret kernel32.InterlockedDecrement() retval=0000000b ret=00405614 0045:Call kernel32.InterlockedDecrement(00637d80) ret=0040561b 0045:Ret kernel32.InterlockedDecrement() retval=00000042 ret=0040561b trace:ole:ObjectStubless (0x4311b3c4)->(5)([4 bytes]) ret=143db323 fixme:ole:RPCRT4_NdrClientCall2 (pStubDec == ^0x2476aa98,pFormat = ^0x2476a626,...): stub 0045:Call rpcrt4.IUnknown_Release_Proxy(4311b3c4) ret=00484779 trace:ole:IUnknown_Release_Proxy refCount: -1 trace:ole:IUnknown_Release_Proxy (0x4311b3c0)->Release() MIBDBCovnert 0045:Call kernel32.UnhandledExceptionFilter(406cdd6c) ret=4090f2b8 Any thoughts? -- James Hawkins

3 2

wine / dlls / itss / itss.c -> ICOM_THIS() macro is defined where ?
by Belxjander Serechai 15 Sep '04

15 Sep '04

I have currently for the last several days been attempting to update my local installation of wine and found that I get blocked by this... Apparently where this macro is used causes errors, is this a possible regression or something was missed at somepoint? Thanks in advance, Jeremy

2 1

include/wine/port.h and socklen_t breakage
by Gerald Pfeifer 15 Sep '04

15 Sep '04

The following change to include/wine/port.h revision 1.58 date: 2004/09/03 18:30:28; author: julliard; state: Exp; lines: +3 -0 Added configure check for socklen_t. +#ifndef HAVE_SOCKLEN_T +typedef unsigned int socklen_t; +#endif causes the following build failure on an old version of FreeBSD 5.1, and probably other systems as well. gmake[1]: Entering directory `/home/gerald/wine/loader' /usr/bin/gcc -c -I. -I. -I../include -I../include -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o kthread.o kthread.c In file included from kthread.c:41: /usr/include/sys/socket.h:77: error: redefinition of `socklen_t' ../include/wine/port.h:65: error: `socklen_t' previously declared here gmake[1]: *** [kthread.o] Error 1 The issue here is that socklen_t is defined in /usr/include/sys/socket.h, but ac_include_default in the configure script does not contain this dir. Which means that HAVE_SOCKLEN_T will be undefined, but once you include /usr/include/sys/socket.h, you'll get the conflict with our port.h. Gerald

1 0

Directx9
by Ann and Jason Edmeades 15 Sep '04

15 Sep '04

Hello, I've spoken with the wine-d3d people and noone is currently doing anything on directx9 support. Originally Raphael was trying to merge things into a new library, wined3d, using an interface which ddraw could also use. This has not happened, and as we stand there is no progress being made. Now, I know nothing about d3d9 support - I have started to see what would be the easiest way to implement this, and have come up with a couple of options, and am after some advice.... 1. (My preference) d3d8 and d3d9 are very similar in lots of respects. I would like to move all the GL code into the wined3d library, effectively factorizing d3d8 and d3d9. However, this would mean extra function call overhead for dx8 and I really dont know how common they will be. Obviously d3d8 will change during such a transition 2. I could implement d3d9 from scratch. This would have the advantage of being a standalone library and wont affect d3d8, but a disadvantage of having to fix anything twice, and probably they will get out of sync really quickly. Also, d3d8 still has parts missing, and I'd prefer a single implementation if possible. If we did this, wined3d could be deleted and a huge code duplication would be required (or 3.... Do nothing, and see if anyone else takes up the gauntlet.) Now, I am not a 3d graphics programmer - I learnt d3d8 as I implemented it (for wine) out of interest to see how things were done. I am happy to try to do the same for d3d9, and would prefer approach (1). I have a few concerns though - Mostly I havent done enough research to know if its possible, and I may end up having a shared library with 2 implementations anyway... I havent found any major stumbling block yet, but I havent researched it far enough either. My other concern is if I start doing it and have to give up due to work or other pressures, I could leave a half migrated setup. I assume its relavitevly easy with cvs to back out changes if this occurs, and I hope it wont, but it is a concern. I'd appreciate thoughts before I start (especially Lionels, AJ's etc) - I'm only just getting back into wine programming again hence my interest. Jason

9 16

Re: Re: Directx9
by brettholcomb＠charter.net 14 Sep '04

14 Sep '04

You're right - even MS can't do it - witness SP 2 for XP <G>. The important apps are core apps - Office, IE, etc., some of the more important apps like the big name games - Half Life <G>. However, it would be nice to know that if I'm running stable release xyz and I upgrade to stable xyz + 1 the apps it would run will still run or at least the chance of breakage is much much less than now. Right now if I run a release, then move to the next many things break. Things will always break to some extent but it seems to have gotten worse lately. I guess what really bothered me is the comment about breaking things and users would just have to live with it until it got fixed whenever. As I said, my objective is to move as much as I can off Windows and I have run wine-cvs and submitted some bugs and data to help debug the regression and I understand wine isn't ready for real use yet. Unfortunately, I don't have the time to do a lot of that so I've essentially dropped Wine and f! igure I'll either wait until someday I can have a release that doesn't break too much between updates or stay with Windows. This is probably what many others have done, too. Don't get me wrong - the Wine team has a very difficult task and has done very well and been responsive but the let 'em use it broke or eat cake approach is not so good. It would help to have a list like you suggest. That would at least let me know that if I have app z which is not on the list and want to run it then it's my problem if the next release breaks. > > From: Lionel Ulmer <lionel.ulmer(a)free.fr> > Date: 2004/09/14 Tue PM 04:32:52 GMT > To: brettholcomb(a)charter.net > CC: wine-devel(a)winehq.com > Subject: Re: Re: Directx9 > > > To be honest, Wine isn't going to be very useful and adopted until > > there is something that a user can install and know that if I have to update > > to a current verson and I pick the stable version that my apps that are > > running will continue to run. > > Well, you perfectly summed up the 'tragedy' of Wine: nobody ever knows what > YOUR applications are... There are so many Win32 applications that Wine > might run one day and so many Win32 APIs and interactions between them that

1 0

Re: Correct ConvertSidToStringSidW with test
by Alexandre Julliard 14 Sep '04

14 Sep '04

Juan Lang <juan_lang(a)yahoo.com> writes: > ChangeLog: fix ConvertSidToStringSidW for all expected > values, and add tests The tests fail for me on XP SP1 (I added some debug output): security.c:85: Test failed: failed to parse sid string S-1-860116326 err 1337 security.c:85: Test failed: failed to parse sid string S-1-16909060 err 1337 security.c:87: Test failed: string sid didn't parse to expected value security.c:85: Test failed: failed to parse sid string S-1-66051 err 1337 security.c:87: Test failed: string sid didn't parse to expected value security.c:85: Test failed: failed to parse sid string S-1-258 err 1337 security.c:87: Test failed: string sid didn't parse to expected value security.c:85: Test failed: failed to parse sid string S-1-2 err 1337 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Re: Directx9
by brettholcomb＠charter.net 14 Sep '04

14 Sep '04

As a user watching this thread here's my comments - Mike is correct. I understand Wine is not to 1.0 yet (close at .9 <G>) but we need something that is stable and that we can run while development is done in the unstable branch. To be honest, Wine isn't going to be very useful and adopted until there is something that a user can install and know that if I have to update to a current verson and I pick the stable version that my apps that are running will continue to run. At one time Wine was like this but in the last year it's gotten so that things that work don't anymore. I have submitted bugs and done some regression testing but let's be honest - most don't have the skills, time or desire to do that but they want to move apps to Linux. If anyone wants to use Wine for serious work to run apps they need then they won't use Wine. Some may go to Crossover, others will just drop it and either go Windows for those systems or forget about Wine or it's derivatives. As a user comments about letting things break and that users just have to put up with ituntil they are eventually fixed scare me! Many projects have stable source that is intended for users and those who want to actually do something useful with the application and then they also have CVS which is for those who want to try out the latest, help fix bugs, etc. > > From: Mike Hearn <m.hearn(a)signal.QinetiQ.com> > Date: 2004/09/14 Tue PM 12:59:45 GMT > I don't think it's about features. It's more about buggyness, and having > popular apps work. Having a stabilisation period where only regression > fixes are allowed on a particular branch could help with that. > > > After all I don't think our Wine CVS is THAT broken/problematic (the > > test suite should help here, too! Why not improve that one for a change?), > > and if people want that extra bit of stability, then they're very > > well-advised to go with CXO (or do you want to deprive CodeWeavers > > of their well-earned money? ;-)). > > Hehe, of course not :) I'm not volunteering to do any of this, at least > not right now! If Jeremy wanted to push Wine 0.9/1.0 forward then yes > I'd be happy to work on it but right now I don't have the time, and what > time I do have all goes on bugfixes and stabilisation for CrossOver. > > Anyway. The fact that CrossOver is a successful product perhaps says > something about the value of stable releases. > > > Even just thinking of the extra 700MB compiled code on my HDD resulting from > > two branches worries me a bit. ;-) > > Nobody is saying you have to use it, I'm sure most kernel developers > don't have both 2.4 and 2.6 installed at once. > > > Not to mention that I believe that the kernel and KDE projects have a > > drastically larger developer audience than Wine, so they can easily afford > > having some people do the branch maintenance. > > No, it's just a matter of willpower. Even small projects can do > stable/unstable releases. Indeed, KDE basically is just a collection of > smaller projects. > > > So at this point in time I still think that doing stable/unstable branching > > would be the entirely wrong thing to do. > > What point in time would it be the right thing to do? > > For me, the right time is "whenever Jeremy says it is" :) But, with my > community hat on, it's something that should be addressed at some point.

2 1

Re: Add IconsDir entry to config
by Marcus Meissner 14 Sep '04

14 Sep '04

On Tue, Sep 14, 2004 at 11:53:53AM -0400, Vincent Béron wrote: > Marcus patch for winemenubuilder has been commited, but for almost all > users the icons will end up in c:\windows\temp for a lack of an IconsDir > entry in config. I don't find that location suitable for long-term > storage of icons. > This is still not perfect as most new users don't use config anymore. wineshelllink will copy them out I guess, won't it? Ciao, Marcus

1 0

Re: MLANG: use Interlocked* in AddRef and Release
by Daniel Remenak 14 Sep '04

14 Sep '04

On Tue, 14 Sep 2004 18:56:40 +0900, Mike McCormack <mike(a)codeweavers.com> wrote: > > ChangeLog: > * use Interlocked* functions in AddRef and Release > <snip> > > static ULONG WINAPI fnIEnumCodePage_Release( > IEnumCodePage* iface) > { > ICOM_THIS_MULTI(EnumCodePage_impl, vtbl_IEnumCodePage, iface); > - ULONG ref = --This->ref; > + ULONG ref = InterlockedIncrement(&This->ref); operator-- changed to InterlockedIncrement instead of InterlockedDecrement. Is that intentional? --Daniel

1 0

Re: Wine and industrial communication like OPC
by Rickard Svensson 14 Sep '04

14 Sep '04

Hallo, sorry I didet awnser in a wile. Some discussion about the company at work on end license per system and so on. License issues isn't fun but ok I can tell you some more. Perhaps someone who knows more about license issues can contribute with something. Our company makes an embedded computer for general use, the first OS that it supported was Linux (an embedded minimum Debian about 10 mb + our app), which we have a customer that uses now. Now a colleague is working on a XP embedded version (is about 70 mb) Our company mostly works with Windows because most of our customers only use Windows. We don't sell any computers with Windows (we don't get bulk deals). We are mostly a software development company. The general industrial application we have made is good, most of our customers doesn't know that it is running Linux, and those who know likes it. But then the demand for OPC increased... In our case the cost of buying a OPC API for Linux perhaps could be economically reasonably, it depends on the amount of Linux computers with OPC we would sell. * 3000-4000$ / numbers of system * A fixed price for Windows licenses to be able to use the Win 98 DCom update. Win License prize * numbers of systems I am now doing some programming task and looking at our options. How does the API we can by from vendors to get OPC on Linux work and cost now. I found the DCom update for Win 98 (Se: http://www.microsoft.com/com/dcom/dcom98/download.asp?SD=GN&LN=SV&gssnb=1) The licens is bad: (Se: http://www.microsoft.com/com/dcom/dcom98/eula.asp) --- --- --- --- 1. GRANT OF LICENSE. This EULA grants you the following rights: * Software License. Microsoft grants you the right to make and use as many copies of the SOFTWARE PRODUCT as you have validly licensed copies of Microsoft® Windows® 98. You may also make copies of the SOFTWARE PRODUCT for backup and archival purposes. * Distribution. You may not redistribute DCOM98. --- --- --- --- The solution that companies like ours that have an interest in OPC collaborates to make a DCom part for Linux through Wine like Mike Hearn and Michael Chang suggested is the one I would go for! But I have to convince my boss... How meny ours do you think it wood take to get DCom to work in Wine? 50 h / 100h / 500h / 1000h ? I'm the one who is mostly for Linux here, as I mentioned XP version is on the way, we have used QT to make or application. So it is easy to migrate and there is a definite risk that all will go towards a XP embedded variant :( From: Mike Hearn <m.hearn(a)signal.QinetiQ.com> Date: Tue, 07 Sep 2004 10:14:50 +0100 To: Rickard Svensson <riq(a)mail.com> Subject: Re: Wine and industrial communication like OPC > > Yyyy! > > I hate license issues! > > I can see that for many people this wouldn't be an issue, because they probably have some old Win 98 CD/Licens somewhere (if they even care). > > But for a company that would like to send it as part of an embedded computer with Linux I can se a lot of problems. > > OK. I don't really know the details of licensing in embedded scenarios > but I can see it would cause problems. > > > But that was per development project, not per system we want to use OPC in. > > Ah, I see. Surely if you depend on Windows though you *already* have to > pay for Windows on a per-system basis? No? Or do you get bulk deals ... > > > That is good ;-) > > In the industry we are a lot of people who really question the total madness of letting the OPC standard be that depended on Windows, when it is supposed to be a "free" organization. > > > > My hope if I can get this to work is to publish a site on the net so all who want to use Linux in the industrial computing can do that quite easy... > > But then we have the license issues to :-( > > Yes. Unfortunately there are (as far as I know) only 4 DCOM > implementations in the world: > > 1) the one in Microsoft Windows > 2) DCOM for UNIX, which is based on Microsofts code > 3) Wines > 4) Cedegas (this is similar to Wines but more advanced, at least for > InstallShield support) > > The only one that is under a liberal license is Wines which is > incomplete. The only way to solve this problem is by having a > free-as-in-speech implementation of DCOM, which means extending and > improving Wine. > > > Ok, now I understand, and also why I got confused before. > > > > And there is a lot of work needed to make DCom to work in Wine? > > Is someone working on it or is it something that not is that important in other cases? > > Yes, it's a fair amount of work. Currently nobody is working on it as > their primary project - Rob Shearman and I did some work on it for > iTunes/InstallShield support lately and most of our code is motivated by > InstallShield. > > It is something that we want to do though, because we currently depend > on native DCOM for a lot of stuff, like installers/office embedding/etc > etc ... so there's interest there at least from CodeWeavers side. But > we're certainly not committed to anything. > > One possible plan is this: if it is true that there is general, > widespread concern over OPC depending on Windows in the industry, > perhaps you could get together with other companies and form a > consortium to fund the development of an LGPLd DCOM implementation in > Wine. This would allow you to write DCOM based software anywhere that > Wine runs and be independent of Microsoft and licensing costs. > > I think if funding was available in the right amounts Jeremy could be > persuaded to have CW at least put some hours into it and I know at least > one guy from ReactOS wants to work on it too. But I can't say for sure. > > Anyway, it was just a thought. > > thanks -mike -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

2 1

Re: resend: patch: shell32.dll - SHELL_ArgifyW expands env-vars
by Alexandre Julliard 14 Sep '04

14 Sep '04

"Jens Collin" <jens.collin(a)lakhei.com> writes: > + { > + TRACE("The env. var can't be found or is bigger than MAX_PATH => useless."); > + res += sprintfW(res, L"%s%%", tmpBuffer); You cannot use Unicode strings constants in Wine, they don't have the right size. -- Alexandre Julliard julliard(a)winehq.org

5 6

Re: Rename keyword variable
by Alexandre Julliard 14 Sep '04

14 Sep '04

Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> writes: > Hi, > > "template" is a keyword on c++, so better rename it to menu_template. We've been through this before; there's absolutely no reason to do that. -- Alexandre Julliard julliard(a)winehq.org

2 1

Why is our OutputDebugString a server request?
by Shachar Shemesh 14 Sep '04

14 Sep '04

Hi all, It seems that OutputDebugString is defined in the Win32 API as a set of client side operations. In wine, however, it is a server request. I have not traced it into the server to see whether they carry out the same operations or not. However, even if they do, I am wondering why we need them? Wouldn't it be better to not do server side things that can be done client side? (http://www.unixwiz.net/techtips/outputdebugstring.html) Shachar P.S. I perfectly understand that obtaining mutexes and waiting on events is a server side operation. However, it was my impression that such things are best carried out by mimicking the Win32 structure as much as possible. Isn't that the case? Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

2 1

Re: Re: Why is our OutputDebugString a server request?
by Pouech Eric DMI AEI CAEN 14 Sep '04

14 Sep '04

> I get the feeling that I misunderstood what you just said. What is the > debug event? where do we do anything with it? debug events are part of the Win32 debug API. A debugger (ie a process using the client side of this API) will get "debug events" (basically the type of the event and some additional information). Such events are process created/terminated, thread created/terminated, thread stopped and so on. One of these "debug events" is the sending of a debug string (by the program being debugged). This means that running a "decent" debugger (decent meaning implementing the support for this debug event) will print all the OutputDebugString calls from the debuggee. A+

1 0

Re: Why is our OutputDebugString a server request?
by Pouech Eric DMI AEI CAEN 14 Sep '04

14 Sep '04

so that debuggers can intercept it (especially ones with GUI) and do what they want with it. A+ > Message du 13/09/04 17:50 > De : "Shachar Shemesh" > A : "Wine Development" > Copie à : > Objet : Why is our OutputDebugString a server request? >

3 3

extern variable question
by Robert Reif 14 Sep '04

14 Sep '04

I'm trying to write a Direct Input regression test and I ran into a problem I can't resolve (and the linker too). dinput.h defines an extern variable: extern const DIDATAFORMAT c_dfDIJoystick; I can't find this variable in dinput.dll but it is in dinput.lib on windows. It looks like I need to generate a dinput.a. How can I generate both a dinput.dll.so and a dinput.a from the same source?

1 0

RE: iostream and msvcrt?
by Scott Snell 14 Sep '04

14 Sep '04

Hi Dimi, Thanks for the offer but I have had the project pulled. Unfortunately I couldnt get a working model in time and the hardware has been recycled to another project ;-(. Basically I needed to compile STLport so I could use iostreams in a project I was converting to wine. I'm going to keep my eye on this list as I hope to have a new round of funding approved late in the year. I may also get an old PC at home working and have another go! thanks, scott. > -----Original Message----- > From: Dimitrie O. Paun [SMTP:dpaun@rogers.com] > Sent: Wednesday, 8 September 2004 0:06 > To: Scott Snell > Cc: Dimitrie O. Paun; Boaz Harrosh; Wine-Devel (E-mail) > Subject: Re: iostream and msvcrt? > > Just got back from vacation. Why is it including a cstdlib? > Anyway, can you send me exactly what you did, so I can try > to reproduce it on my box? > > -- > Dimi.

1 0

Re: Proper finalization in StartServiceW
by Alexandre Julliard 13 Sep '04

13 Sep '04

"Alexander Yaworsky" <yaworsky(a)migusoft.ru> writes: > + if( WAIT_FAILED == r ) > + { > + last_error = GetLastError(); > + CloseHandle( procinfo.hProcess ); > + goto done; > + } > > - ReleaseSemaphore(data, 1, NULL); > - > - if( r == WAIT_FAILED) > - return FALSE; > + /* allright */ > + CloseHandle( procinfo.hProcess ); > + last_error = 0; > + ret = TRUE; > > - return TRUE; > +done: > + CloseHandle( wait ); > + ReleaseSemaphore(data, 1, NULL); > + CloseHandle( data ); > + SetLastError( last_error ); > + return ret; You should never need to do that sort of thing. CloseHandle and ReleaseSemaphore won't change last error if they are called for valid handles, and if they are not you are just hiding a bug. Also, you very probably don't want to set last error to 0 on success, unless you have clear evidence that Windows does it in this case too. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Correct ConvertSidToStringSidW with test
by Alexandre Julliard 13 Sep '04

13 Sep '04

Juan Lang <juan_lang(a)yahoo.com> writes: > @@ -2230,13 +2232,23 @@ > > sz = 14 + pisid->SubAuthorityCount * 11; > str = LocalAlloc( 0, sz*sizeof(WCHAR) ); > - sprintfW( str, fmt, pisid->Revision, > - pisid->IdentifierAuthority.Value[2], > - pisid->IdentifierAuthority.Value[3], > - pisid->IdentifierAuthority.Value[0]&0x0f, > - pisid->IdentifierAuthority.Value[4]&0x0f, > - pisid->IdentifierAuthority.Value[1]&0x0f, > - pisid->IdentifierAuthority.Value[5]&0x0f); > + sprintfW( str, fmt, pisid->Revision ); > + for( i=2; i<=3; i++ ) > + { > + if( pisid->IdentifierAuthority.Value[i] ) > + printingIdent = TRUE; > + if( printingIdent ) > + sprintfW( str + lstrlenW( str ), identAuthFmt, > + pisid->IdentifierAuthority.Value[i] ); > + } That doesn't look right, you'd need something like %02x for the second value if the first was printed. It seems it would be a lot easier to simply build an int from the various values and then format it with a single %x. -- Alexandre Julliard julliard(a)winehq.org

1 0

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