wine-devel

wine-devel@winehq.org

2 participants
84471 discussions

Re: I suck...
by Alexandre Julliard 01 Nov '02

01 Nov '02

Greg Turner <gmturner007(a)ameritech.net> writes: > Thanks for catching the first, Alexandre, or > I wouldn't have caught this second... Actually I didn't catch anything, the first one was fixed by Marcus. -- Alexandre Julliard julliard(a)winehq.com

1 0

Warcraft III no go. (probs with 1.03 ?)
by dan carter 31 Oct '02

31 Oct '02

OK, it seems everyone but me is able to play War3 under linux. Current status is i have the 1.03 NoCD patch: ³ Warcraft III: Reign Of Chaos 1.03 Virtual Crack ³ ³ Cracked By : gimpsRus ³ Game Type : Strategy ³ ³ Packaged By: gimpsRus ³ Released On: 10 October 2002 ³ I'm using the 'dataparty' RPMs build "wine-cvs-opengl-102802-1" OpenGL is working and i can still load the warez beta version of war3 that i used to play. Now that i have actually bought the damn thing i can't play :( Here is the error i get: [dantheperson@danski dantheperson]$ wine .wine/fake_windows/Program\ Files/Warcraft\ III/war3.exe -- -opengl wine: Unhandled exception, starting debugger... err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 134692272 8324") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger [dantheperson@danski dantheperson]$ Has anybody had success with the 1.03 patch? Does anyone know where i can get an older NoCD crack that is known to be working under linux? Rgds, dan carter

3 2

RFC: msvcrt _popen/_wpopen/_pclose
by Jaco Greeff 31 Oct '02

31 Oct '02

Hi, I want some comments on the possibility of a _popen/_wpopen/_pclose implementation in Wine. Reference available at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html… The open functions basically operate in the same way as the popen function in Linux, ie. it spawns a process with the command via the command interpreter. Now, unfortionately we don't have our won cmd.exe available, but should people really need this functionality it might not be too much to ask as to copy it from a working Windows installation. In my mind, supporting the Win 95/98 command interpreters might be a nightmare - my gutt feel is that these two rely too much on DOS internals to be sucessfully launched via Wine. No, I haven't tried it, so I might be completely wrong. Either way, something like this might be better implemented via the Win NT/2000/XP cmd.exe. (I'll test my assumptions tomorrow, I don't have access to the command interpreters tonight.) I've hacked (yes, it was quick) a potential implementation of the _popen family of functions. (Haven't compiled, haven't tested, this is just and RFC - if it can work, I'll spend some real time on it.) Anyway, here it is, comments appreciated: --[ inline-ish RFC ]---- #include "config.h" #include "wine/port.h" #include <stdio.h> #include <stdlib.h> #ifdef HAVE_UNISTD_H # include <unistd.h> #endif #include "winbase.h" #include "winnls.h" #include "wine/unicode.h" #include "msvcrt/stdio.h" #include "msvcrt/string.h" #include "wine/debug.h" #define POPEN_FLAG_READ 0x0001 #define POPEN_FLAG_WRITE 0x0002 #define POPEN_FLAG_TEXT 0x0004 #define POPEN_FLAG_BINARY 0x0008 inline CHAR *LPCWSTRToLPSTR(const LPCWSTR lpwstrIn, INT nIn) { INT nLen = WideCharToMultiByte(CP_ACP, 0, lpwszIn, nIn, NULL, 0, NULL, NULL); CHAR *szOut = (CHAR *)malloc((nLen+1)*sizeof(CHAR)); if (szOut) { WideCharToMultiByte(CP_ACP, 0, lpwszIn, nIn, szOut, nLen+1, NULL, NULL); szOut[nLen] = '\0'; } return szOut; } INT POPEN_parseModeFlags(const CHAR *szMode) { INT nFlags = 0; while (szMode && *szMode) { switch (*szMode) { case 'r': { if (nFlags & POPEN_FLAG_WRITE) WARN(": _popen: Cannot set both read and write open flags, ignoring read flag\n"); else nFlags = nFlags & POPEN_FLAG_READ; break; } case 'w': { if (nFlags & POPEN_FLAG_READ) WARN(": _popen: Cannot set both read and write open flags, ignoring write flag\n"); else nFlags = nFlags & POPEN_FLAG_WRITE; break; } case 'b': case 't': { FIXME(": _popen: %c mode flag not implemented, ignoring\n", *szMode); break; } default: { WARN(": _popen: unknown mode flag %c, ignoring\n", *szMode); break; } } } return nFlags; } MSVCRT_FILE *MSVCRT_popen(const CHAR *szCommand, const CHAR *szMode) { MSVCRT_FILE *fProcess = NULL; if (!szCommand || !szMode) return NULL; INT nFlags = POPEN_parseModeFlags(szMode); if (!(nFlags & (POPEN_FLAG_READ|POPEN_FLAG_WRITE))) { ERR("No open mode flag r or w specified\n"); return NULL; } /* _popen/_wpopen executes the required command via the command * processor, either command.com (Win 95/98) or cmd.exe (Win NT/2000/XP). * Wine does not currently have it's own "cmd.exe" hence we cannot * really do anything more at this point. However, we try to lauch it * and hope for the best... */ CHAR *szExec = (CHAR *)malloc(strlen("wine -- C:/cmd.exe -C ")+strlen(szCommand)+1); if (szExec) { sprintf(szExec, "wine -- C:/cmd.exe -C %s", szCommand); fProcess = popen(szExec, (nFlags & POPEN_FLAG_READ) ? "r" : "w"); if (!fProcess) ERR("Execution of C:/cmd.exe via wine failed\n"); else WARN("Launch of %s succeeded, no guarentees of success made\n", debugstr_a(szExec)); free(szExec); } return fProcess; } MSVCRT_FILE *MSVCRT_wpopen(const WCHAR *wszCommand, const WCHAR *wszMode) { MSVCRT_FILE *fProcess = NULL; if (!wszCommand || !wszMode) return NULL; CHAR *szCommand = LPCWSTRToLPSTR(wszCommand, strlenW(wszCommand)); if (szCommand) { CHAR *szMode = LPCWSTRToLPSTR(wszMode, strlenW(wszMode)); if (szMode) { fProcess = _popen(szCommand, szMode); free(szMode); free(szCommand); } free(szCommand); } return fProcess; } int MSVCRT_pclose(MSVCRT_FILE *fProcess) { if (!fProcess) return -1; return pclose(fProcess); }

1 0

Re: So lets say we do it
by Dimitrie O. Paun 31 Oct '02

31 Oct '02

On October 31, 2002 04:18 pm, Andreas Mohr wrote: > Bl**dy b*tch ! :-)) Listen man, I don't like that! I mean, what's up with the stars?!? :))) > First you annoy the h*ll out of people, and then you behave as if nothing > had ever happened and the weather was fantastic... ;-) Oh, Andy dude, you are the toughest guy on Wine-devel, crushing poor newbies without remorse. And now, all of a sudden, you become this sensible, in-touch-with-your-feelings guy?!? ;-) (ROTFL) > (BTW: the weather here is awful :) See, and you blame poor me... :P -- Dimi.

1 0

XBox
by Dirk 31 Oct '02

31 Oct '02

Could someone do something to make the need for this hardware disappear and save the world of people who love proprietrary video game consoles? There is already a tool that converts xpe files into exe. Only the bios and the improved DirectX must be re-engineered and the rest will be done by a Geforce4 (or 5) and a 2Ghz CPU.

4 3

Debugging advice
by Matthew Bloch 31 Oct '02

31 Oct '02

Hi there; I feel like I'm "nearly there" with porting this game to run with winelib, a version checked out from winehq CVS about a week ago. Because I wanted my build system to be cross-platform, and WINE only as a stop-gap, I'm using the Jam build system and so can't directly take advantage of winemaker. Plus I would rather learn and document how the build process works manually, since I can't find this information anywhere else. Anyhow I now have the 400-odd source files compiling happily against my wine header files once I'd excised the need for Direct3D. I have a directory full of object files with external references to Win32 functions and a WinMain function. So to do the final linking step I've used (based on watching the example winemine build process): $WINE/tools/winebuild/winebuild \ -fPIC -DSTRICT -D_REENTRANT \ -exe LSNClient.exe -mgui Builds/native-debug-linux/Source/*.o \ -L$WINE/dlls -luser32 -lgdi32 -ladvapi32 -lkernel32 -lddraw -ldsound \ -lwinmm -ldisplay -ldispdib >Source/LSNClient.exe.c and then compiled & linked LSNClient.exe.c to the rest of the object files with the -shared flag, which leaves me with a shared library. Sideline: am I correct in thinking that winebuild's job is to scan the supplied object files for Win32 dependencies and construct the necessary glue code to load the needed .dll.so files? What's the reason that the linking process can't correspond more closely to "normal" linking, i.e. where I could just supply -lddraw -lwine to my program to produce a final binary? I then run ../wine/wine LSNClient.exe to try to run the game, and get this error: err:module:BUILTIN32_LoadLibraryExA loaded .so but dll display.dll still not found - 16-bit dll or version conflict. err:module:PE_fixup_imports Module (file) display.dll (which is needed by Y:\Work\Nemesis\LSNClient.exe) not found Any idea what might be going wrong, or how I could diagnose it? More generally, the natively compiled .exe runs okay (if grindingly slowly, and with a couple of display glitches) under the binary loader, but I assumed that if I could produce a native version I'd be avoiding a lot of overhead and make my debugging job easier since I could use familiar GNU tools to debug my portability code as I wrote it. What efficiency gains will I make compiling a native "shared library exe" with gcc as opposed to just compiling with Visual C and running it under the normal WINE binary loader? I'm interested in how the latter works efficiently, so any advice in this direction would be appreciated-- I've thought on more than one occasion that maybe I should skip the WINE stop-gap and port it to SDL all at once, but the idea of being able to gradually wean the game off Win32 is appealing. cheers, -- Matthew Bloch Bytemark Computer Consulting Limited http://www.bytemark.co.uk/ tel. +44 (0) 8707 455026

5 6

RE: winapi_check question...
by Patrik Stridvall 31 Oct '02

31 Oct '02

> On Thursday 31 October 2002 09:20 am, Patrik Stridvall wrote: > > Greg wrote: > > > winapi_check tells me: > > > > > > ndr_stubless.c:86: rpcrt4: LONG_PTR WINAPIV > > > NdrClientCall2(PMIDL_STUB_DESC,PFORMAT_STRING,...): argument 1 > > > documentation: \ > > > /* CLIENT_CALL_RETURN */ > > > > This is because winapi_check misparser the line: > > LONG_PTR /* CLIENT_CALL_RETURN */ > > RPCRT4_NdrClientCall2(PMIDL_STUB_DESC pStubDesc, PFORMAT_STRING > > pFormat, va_list args) > > > > Ignore it. > > OK. You promise it won't screw up the actual documentation bot? Promise? Hmm. All code have bugs you know and winapi_check is designed to be ad hoc and thus inherently buggy... :-) But seriously, I wouldn't worry about it. Anyway. A real fix to the code you be nice. Presumable the type CLIENT_CALL_RETURN haven't been declared properly. > > > how shall I deal with these? > > > > Fix them as above or do as everybody elses do wait for me to fix it. > > :-) > > heh. Well, maybe I can set an example for those deadbeats :) :-)

2 1

Re: dlls/msvcrt/tests: printf
by Jaco Greeff 31 Oct '02

31 Oct '02

On Thu, 31 Oct 2002 17:57:12 +0100, Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> wrote : > Jaco> ... Tests that will fail > Jaco> with current implementation are temporarily commented out > > Don't comment them out, matrk them "todo". Look at the syntax in > documentation/testing. I've marked the code with a "FIXME". I don't want the test sequence to fail for this issue which is solved by my msvcrt patch. The way I've done it allows others to verify the new vfprintf patch with minimal work. > And plain inlined patches are preferred against attachments. I'm doing this via a mail web interface, it has the ugly habit of doing line-wraps. I also prefer inline patches (like to see what is going on without have to save etc.), it is just not entirely possible for me at this point. *sigh* Greetings, Jaco

3 2

Some other problems ...
by Paul Millar 31 Oct '02

31 Oct '02

Hi everyone, Just a couple of problems I've noticed. They look like they're due to some broken build dependencies. 1. I have a copy of wine on my laptop which I do "cvs update" every few days. After updating today, I did the usual "./configure --enable-opengl && make depend && make" and left it to compile. But, when I tried the result, I got a client/server mismatch for SERVER_PROTOCOL_VERSION. One was claimed to be v88 whilst the other was v89. Doing a "make distclean" then repeating the build "fixed" the problem. Patch http://cvs.winehq.com/patch.py?id=6064 (committed last Tuesday) bumped the SERVER_PROTOCOL_VERSION up to 89. So it looks like some of the binaries weren't updated during the build. I tried altering the version (manually) and rebuilding, but wine rebuilt correctly. 2. WRT hit a problem last night where "make test" failed. The log included messages like: gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -DSTRICT -DNONAMELESSUNION -DNONAMELESSSTRUCT -D_REENTRANT -o registry.o registry.c LD_LIBRARY_PATH="../../../library:../../../unicode:$LD_LIBRARY_PATH" ../../../tools/winebuild/winebuild -fPIC -DSTRICT -DNONAMELESSUNION -DNONAMELESSSTRUCT -o advapi32_test.exe.spec.c -exe advapi32_test.exe -mcui registry.o testlist.o -L../../../dlls -ladvapi32 -lkernel32 -lntdll gcc -shared -Wl,-Bsymbolic advapi32_test.exe.spec.o registry.o testlist.o -o advapi32_test.exe.so -L../../../library -lwine -lm advapi32_test.exe.spec.o: In function `__wine_exe_main': /home/paulm/WINE-cvs/wine/dlls/advapi32/tests/advapi32_test.exe.spec.c:116: undefined reference to `main' registry.o: In function `test_enum_value': /home/paulm/WINE-cvs/wine/dlls/advapi32/tests/registry.c:69: undefined reference to `winetest_set_ok_location' /home/paulm/WINE-cvs/wine/dlls/advapi32/tests/registry.c:69: undefined reference to `winetest_ok' /home/paulm/WINE-cvs/wine/dlls/advapi32/tests/registry.c:78: undefined reference to `winetest_set_ok_location' [... etc ...] The later build had six tests that succeded. These were the new scanf tests introduced into that build by patch http://cvs.winehq.com/patch.py?id=6107 I've just done a "make distclean" followed by a normal rebuild and test. Its currently running through the regression tests, but so far it seems to be working. These are vague reports of unrepeatable problems ... never a good thing! I'm quite busy right now (real work and everything), so I don't have time to investigate this myself. Just posting this hoping the cause its obvious to someone else :^) ---- Paul Millar

1 0

Re: dlls/msvcrt/tests: printf
by Jaco Greeff 31 Oct '02

31 Oct '02

On Thu Oct 31 20:04:30 2002, "Jaco Greeff" <jaco(a)puxedo.org> wrote : > On Thu, 31 Oct 2002 17:57:12 +0100, Uwe Bonnes > <bon(a)elektron.ikp.physik.tu-darmstadt.de> wrote : > > Jaco> ... Tests that will fail > > Jaco> with current implementation are temporarily commented out > > > > Don't comment them out, matrk them "todo". Look at the syntax in > > documentation/testing. > > I've marked the code with a "FIXME". Sorry, I misunderstood the first time around, will something like todo("linux") { do(something() == 1, "whatever"); } do the trick? But unsure about the definition I should use, I can see "cygwin", "freebsd", etc. This one will fail on all non-Windows platforms. Greetings, Jaco

1 0

Re: dlls/msvcrt/tests: printf
by Jaco Greeff 31 Oct '02

31 Oct '02

On Thu, 31 Oct 2002 11:04:48 -0600, Greg Turner <gmturner007(a)ameritech.net> wrote : > On Thursday 31 October 2002 10:34 am, Jaco Greeff wrote: > > - Tests that will fail with current implementation are temporarily > > commented out > > Is there a middle ground for tests that are expected to fail? If not, > IMO maybe there should be: It kinda defeats the purpose of a test > framework if we just comment out tests that don't work... Agreed. It will pass shortly though :) At this point the test will help anybody wishing to verify my latest msvcrt patch. Plus, it really should pass. The part that does fail is on Unicode printing, which give me one of a few choices: 1. Don't send in a test; 2. Be stubborn and let the test fail for everybody doing a make test; 3. Send in a really crippled test case; 4. Combination of 3 + 4 so people can easily have the framework to test if progress have been made. That is the reason why I've commented it out, hopefully shortly it will be fully featured. Greetings, Jaco

1 0

Re: dlls/msvcrt/tests: printf
by Greg Turner 31 Oct '02

31 Oct '02

On Thursday 31 October 2002 10:34 am, Jaco Greeff wrote: > - Tests that will fail with current implementation are temporarily > commented out Is there a middle ground for tests that are expected to fail? If not, IMO maybe there should be: It kinda defeats the purpose of a test framework if we just comment out tests that don't work... but OTOH, its pretty unfair to the other tests to have the whole "make test" fail because of some known issue. -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

1 0

Re: rpc_H_PL9
by Michael Stefaniuc 31 Oct '02

31 Oct '02

On Thu, Oct 31, 2002 at 08:49:18AM -0600, Greg Turner wrote: > LICENSE: X11 > > CHANGELOG: > * dlls/rpcrt4: rpc_server.c; > include: rpcdcep.h: > Greg Turner <gmturner007(a)ameritech.net> > - One more fixup for winapi_check > -UINT WINAPI I_RpcWindowProc( HANDLE hWnd, UINT Message, UINT wParam, ULONG lParam) +UINT WINAPI I_RpcWindowProc( void *hWnd, UINT Message, UINT wParam, ULONG lParam ) That's totaly broken. It's a problem in winapi_check and not in your code. Well, their is a problem in your code too, i would change HANDLE to HWND. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

2 2

RE: winapi_check question...
by Patrik Stridvall 31 Oct '02

31 Oct '02

> winapi_check tells me: > > ndr_stubless.c:86: rpcrt4: LONG_PTR WINAPIV > NdrClientCall2(PMIDL_STUB_DESC,PFORMAT_STRING,...): argument 1 > documentation: \ > /* CLIENT_CALL_RETURN */ This is because winapi_check misparser the line: LONG_PTR /* CLIENT_CALL_RETURN */ RPCRT4_NdrClientCall2(PMIDL_STUB_DESC pStubDesc, PFORMAT_STRING pFormat, va_list args) Ignore it. > rpc_epmap.c:56: rpcrt4: RPC_STATUS WINAPI > RpcEpRegisterA(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR,LPSTR): > no translation defined: PRPC_BINDING_VECTOR This is because winapi_check doesn't know the type of PRPC_BINDING_VECTOR. One day I will teach it to parse the header files properly. Until then tell it what type it is in the the file tools/winapi/win32.api: %%rpcrt4 ... %ptr ... PRPC_BINDING_VECTOR ... Since PRPC_BINDING_VECTOR is presumable a pointer it goes under the ptr section. > rpc_epmap.c:56: rpcrt4: RPC_STATUS WINAPI > RpcEpRegisterA(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR,LPSTR): > no translation defined: PUUID_VECTOR Same as above. > rpc_epmap.c:102: rpcrt4: RPC_STATUS WINAPI > RpcEpUnregister(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR): > argument 2 type is forbidden: PRPC_BINDING_VECTOR (unknown) Same as above. > how shall I deal with these? Fix them as above or do as everybody elses do wait for me to fix it. :-)

2 1

Re: dlls/msvcrt/tests: printf
by Uwe Bonnes 31 Oct '02

31 Oct '02

>>>>> "Jaco" == Jaco Greeff <jaco(a)puxedo.org> writes: Jaco> ... Tests that will fail Jaco> with current implementation are temporarily commented out Don't comment them out, matrk them "todo". Look at the syntax in documentation/testing. And plain inlined patches are preferred against attachments. 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

Re: Re: So lets say we do it
by chrismorgan＠rcn.com 31 Oct '02

31 Oct '02

> > From: Alexandre Julliard <julliard(a)winehq.com> > Date: 2002/10/31 Thu AM 11:24:28 EST > To: dpaun(a)rogers.com > CC: Wine Devel <wine-devel(a)winehq.com> > Subject: Re: So lets say we do it > > "Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > > > So the 5% left, install wine, install a Win-app, and play around. > > Great, it works! > > You forgot a few things here: > > First it doesn't even start because they don't have a config file. OK, > they copy one from somewhere, it doesn't work because the drives are > wrong. Then they don't have the proper registry (winedefault.reg? > what's that?) I was going to reply yesterday on this issue. I help a fair amount of people on irc that have config problems and there are a few things we should probably do to fix this. 1. Check the wine config on startup. If the config is missing or incorrect then launch a gui config app to fix things. It would be best if this tool had two user options, one for an Automatic setup and another for an Expert setup. We do a good job with wineinstall so I don't have much doubt that we could automate the config and satisfy 80%+ of users. 2. Make it easier for users to modify their configs via a gui tool. 3. Straighten out how packages(RPM, deb, etc) setup wine's config. I'm not even sure how this is done right now and LOTS of people come asking for help saying they have installed an RPM version of wine but don't know how to configure it. This might be completely solved by #1. Chris

1 0

Re: Re: So lets say we do it
by chrismorgan＠rcn.com 31 Oct '02

31 Oct '02

> > 2. People will look for the typical left-side menu: > > Home > > About > > Status > > Development > > Download > > Screenshots > > > > *BZZT* We don't have any. 5% will drop off here. > > Sorry to say that, but in this mail, *you* were talking *some* crap IMHO > ;-) > > We *do* have screenshots. The About page has some pretty nice screenshot. > OK, it's a minimalist approach, granted, but it does show IE etc. > I'd also like to second the opinion that we should have a dedicated "Screenshot" entry right off of the main page. I do the same stuff that Dimitrie does, go to a project, look at some text briefly and then immediately want to see what the app looks like when it is working. So maybe leave the screenshot link off of the "About" page but also put a link on the main page. Chris

1 0

RPC test code?
by Greg Turner 31 Oct '02

31 Oct '02

OK, wine made it's first successful RPC's on my box today (yay!) Now, it's time to do a smidgen of housekeeping, and whip up a test. This is a bit tricky, I have a few open questions, which I will enumerate: 1) It feels like cheating to use the same process as client /and/ server. OTOH, it will be a bit cleaner to do it as such... any thoughts on this? specifically, 1a) Will wedging what is basically a winelib app into my test directory create a problem in the configure/make system? Is there a clean way to make sure I invoke the right winelib .exe.so file (the one in my test directory)? 1b) Are all the process-control API's I will need for this in place? (in particular I should kill off the server in case of a failure... will this be a problem? I guess probably not, or else I'd see a lot more wine's hanging around in my process table.) 1c) If the test fails in the winelib thingy, I have to propagate this back to the test; but relying on RPC for this (aside from being unimplemented ATM) is a catch-22, since error propagation might be broken (hence the need for a test)... I guess I can think of creative solutions to this like putting stupid temp files somewhere. Any better ideas? 1d) Anyone know of a problem with this I haven't thought of yet? 2) Whether I use threads or processes, I need some coordination to happen; I am very concerned about race conditions. I want my tests to run under the most absurd and grueling conditions, with NO race conditions. But I can't wrap my mind around how to avoid them ATM. For example: 2a) Should the rpc.c "real" test be the client or the server? I can imagine races either way. Let's say rpc.c is the client. This isn't so bad at a glance; I invoke the server thread/process, and poll RPC from time to time until it goes active (how I do this is another issue, but I'll think of something). Now I do my magic, and request a shutdown via RPC to the server... but, in two cases there is technically a race: first, while I'm invoking the server, I have to wait for it to start as discussed; second, after I send the Shutdown RPC to the server, I have to actually wait for the process/thread to terminate. In both cases, how long is long enough? What if the tests are running on some absurdly bogged down machine that's simultaneously compiling a matrix of 10,000 different wine's, for example? On the other hand, if I use some really liberal timeout like 30 minutes, then in a failure condition, my test would appear to hang, this isn't so great either. If rpc.c is the server, similar problems exist. 2b-?) uh, I guess I squeezed all of these questions into 2a. 3) MIDL? I still haven't figured out the legal ramifications of using midl-generated code. I'd rather not spend a month working on widl before generating a test... so do I need to code my stubs by hand? Even if I do, they're gonna come out looking more-or-less just like MIDL code... maybe I need to figure out the licensing restrictions on MIDL-generated code myself, but does anyone know offhand, I didn't see any obvious discussion of this on microsoft.com or in the platform sdk. ugh. thanks for taking the time to read this long-winded post. Any responses, assistance, flames, etc. are appreciated. -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

4 6

Re: SetWindowHookEx
by steve.lustbader＠philips.com 31 Oct '02

31 Oct '02

This patch fixed it. Could you change the fixme message in user/hook.c to something more explicit than "won't work right," or at least include a comment in the code explaining why it won't work right? -Steve steve.lustbader(a)philips.com writes: > It's returning NULL for me, which implies it isn't working. Is there some > sort of trace that I can send you to help you out? Oops you are right, this should fix it: Index: server/hook.c =================================================================== RCS file: /opt/cvs-commit/wine/server/hook.c,v retrieving revision 1.1 diff -u -r1.1 hook.c --- server/hook.c 29 Oct 2002 00:41:42 -0000 1.1 +++ server/hook.c 30 Oct 2002 19:51:20 -0000 @@ -227,7 +227,8 @@ set_error( STATUS_INVALID_PARAMETER ); return; } - if (!(thread = get_thread_from_id( req->tid ))) return; + if (!req->tid) thread = (struct thread *)grab_object( current ); + else if (!(thread = get_thread_from_id( req->tid ))) return; if ((hook = add_hook( thread, req->id - WH_MINHOOK ))) { -- Alexandre Julliard julliard(a)winehq.com

1 0

Adobe SVG viewer mouse tracing
by Mike Hearn 31 Oct '02

31 Oct '02

Hi, I have CrossOver beta 1.3 and have got IE6 installed and version 3 of the Adobe SVG viewer. The installer doesn't work, but I got around that problem, the issue I'm interested in solving now is that mouse interaction is messed up, namely that when the plugin receives a mousemove event, it appears to immediately receive another for 0,0 - this is just a theory I've got however. I'm wondering if there's a way to restrict debug logging to code in a particular file? I'm not interested in any mouse messages except those to the COM object in NPSVG3.dll thanks -mike

1 0

winapi_check question...
by Greg Turner 31 Oct '02

31 Oct '02

winapi_check tells me: ndr_stubless.c:86: rpcrt4: LONG_PTR WINAPIV NdrClientCall2(PMIDL_STUB_DESC,PFORMAT_STRING,...): argument 1 documentation: \ /* CLIENT_CALL_RETURN */ rpc_epmap.c:56: rpcrt4: RPC_STATUS WINAPI RpcEpRegisterA(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR,LPSTR): no translation defined: PRPC_BINDING_VECTOR rpc_epmap.c:56: rpcrt4: RPC_STATUS WINAPI RpcEpRegisterA(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR,LPSTR): no translation defined: PUUID_VECTOR rpc_epmap.c:102: rpcrt4: RPC_STATUS WINAPI RpcEpUnregister(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR): argument 2 type is forbidden: PRPC_BINDING_VECTOR (unknown) how shall I deal with these? -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

1 0

Re: miscemu/wine gets into the way in map_image
by Uwe Bonnes 31 Oct '02

31 Oct '02

>>>>> "Alexandre" == Alexandre Julliard <julliard(a)winehq.com> writes: Alexandre> Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: >> However when unzip has unpacked the 160 MByte file and the Setup >> should start, a crash happens, and the debugger startup stops with >> "Memory exhausted". The same happens when I run in winedbg: Loaded >> debug information from ELF >> '/home/bon/tmp/wine/compile/wine/miscemu/wine' (0x00000000) >> Breakpoint 2 at 0x4000c714 (_end+0xf7fec) Memory exhausted. Alexandre> You probably need reduce the base address a bit to leave more Alexandre> space for malloc(). Try changing the 0x3ff to 0x3f0. Now of Alexandre> course we shouldn't be using malloc, so that hack would be a Alexandre> good way to enforce that <g> Alexandre, could we get this into the wine tree? At least one person stumled across that with the same application I had. 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

EMF bug
by doome 31 Oct '02

31 Oct '02

Hi! I am not sure if this is a bug, or I did something wrong. My collegaues made a little program what shows the bug. It shows an EMF file, but the text boxes appears bad. Two screenshots and the source are included in the tar.gz. Please somebody examine it, and help me if you can. The source, binaries, and screenshots can be downloaded from ftp://ftp.uhulinux.hu/misc/testprg.tar.gz. It needs to be exctracted to the wine c:\ directory Thanks for your help in advance! If needed I can send you wine debug msgs. -- doome

4 3

richedit
by Michael Stefaniuc 31 Oct '02

31 Oct '02

Hello, is somebody working on the richedit dll? I encountered 3 unknown RTF control words and wanted to add them but I got scared by the overzealous use of #define's in rtf.h . My first impuls was exchange that with some enum's, but i thought i better ask here before i do the work in vain. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

3 3

Is it me or is "winedbg --debugmsg -all" not honored
by Uwe Bonnes 30 Oct '02

30 Oct '02

Hallo, did I miss something or is it me or is the registry entry ( as advertised in winedefaults.reg) [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug] "Debugger"="winedbg --debugmsg -all %ld %ld" not honored any more ( since some time). The relay log is cluttered with about 150k lines of debugger start relay output :-( Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

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