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

Re: wpp

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > There is already a dummy --preprocessor option in wrc (for compatibility > with windres). First step would be properly implement that one, to allow > for external override of the preprocessor. Then we can experiment with it, > see what we get (errors, speed penalties, etc.). Frankly, this ranks about as high on the priority list as the strcat optimizations in makedep. Are there really no more real problems to solve that we need to spend so much effort inventing new ones? -- Alexandre Julliard julliard(a)winehq.com

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by Francois Gouget

On Mon, 9 Dec 2002 vkxzjq6lg(a)cswebmail.com wrote: [...] > Being too free with "let the code crash" is a bad idea. Microsoft got a lot > of really bad heckling in the Windows 3.1 era for GPFs. Wine doesn't want to > crash if it's reasonably harmless to continue (like for a failed screen > update). Does want to report the problem, of course, rather than silently > ignore it, otherwise it'll never get fixed. There is a very significant difference between Wine and Windows: if Wine crashes only one process is impacted. And if that process did something wrong then I think it's ok to let it crash. However, if Windows (3.1 or other) crashes (i.e. gives you a GPF or a blue screen of death), then: - all other applications die - all unsaved data of _other_ applications is lost - anything since the last flush to disk is lost - the filesystem may become corrupted And it is these other effects that make GPFs and blue-screen of death unacceptable. Translated to Wine, this means that it is not acceptable for the wineserver to crash, but it's not so bad if a single wine process crashes. That being said, if a Windows program works fine on Windows, then it should work fine in Wine, even if it does something stupid such as passing a NULL pointer to an API when it shouldn't. But for internal programming errors, crashing can be a good debug method: - it sure gets one's attention - it's supposed to generate a nice stack trace which you can use to complement the relay trace Of course, that implies that we should promptly fix any such crash. Otherwise it just makes Wine unusable without any benefit. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ A black hole is just God dividing by zero.

Dec. 9, 2002

RE: Janitorial Projects -- conformance tests --recruiting volunteers

by Kye Lewis

> C:\Downloads\Linux>advapi32_test.exe registry > h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set to > 'xxxxxxxxxx' instead of 'Te' > h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set to > 'xxxxxxx' instead of 'foobar' > h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set to > 'xxxxxxx' instead of 'foobar' > registry: 56 tests executed, 0 marked as todo, 3 failures. It is here that I notice a large discrepancy between this test and my test on the same Operating System: h:\wine\wine\dlls\advapi32\tests\registry.c:80: Test failed: data_count set to 24 instead of 7 h:\wine\wine\dlls\advapi32\tests\registry.c:81: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:94: Test failed: data_count set to 24 instead of 7 h:\wine\wine\dlls\advapi32\tests\registry.c:95: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set to 'xxxxxxxxxx' instead of 'Te' h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set to 'xxxxxxxxxx' instead of 'foobar' h:\wine\wine\dlls\advapi32\tests\registry.c:108: Test failed: data_count set to24 instead of 7 h:\wine\wine\dlls\advapi32\tests\registry.c:109: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set to 'xxxxxxxxxx' instead of 'foobar' h:\wine\wine\dlls\advapi32\tests\registry.c:122: Test failed: data_count set to24 instead of 7 h:\wine\wine\dlls\advapi32\tests\registry.c:123: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:134: Test failed: expected ERROR_SUCCESS, got 234 h:\wine\wine\dlls\advapi32\tests\registry.c:135: Test failed: val_count set to 20 instead of 4 h:\wine\wine\dlls\advapi32\tests\registry.c:136: Test failed: data_count set to 24 instead of 7 h:\wine\wine\dlls\advapi32\tests\registry.c:137: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:138: Test failed: value is 'xxxxxxxxxx' instead of Test h:\wine\wine\dlls\advapi32\tests\registry.c:139: Test failed: data is 'xxxxxxxxxx' instead of foobar h:\wine\wine\dlls\advapi32\tests\registry.c:155: Test failed: data_count set to 48 instead of 7*sizeof(WCHAR) h:\wine\wine\dlls\advapi32\tests\registry.c:156: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:169: Test failed: data_count set to 48 instead of 7*sizeof(WCHAR) h:\wine\wine\dlls\advapi32\tests\registry.c:170: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:182: Test failed: val_count set to 5 instead of 4 h:\wine\wine\dlls\advapi32\tests\registry.c:183: Test failed: data_count set to 48 instead of 7*sizeof(WCHAR) h:\wine\wine\dlls\advapi32\tests\registry.c:184: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:185: Test failed: value is not 'Test' h:\wine\wine\dlls\advapi32\tests\registry.c:195: Test failed: expected ERROR_SUCCESS, got 234 h:\wine\wine\dlls\advapi32\tests\registry.c:196: Test failed: val_count set to 5 instead of 4 h:\wine\wine\dlls\advapi32\tests\registry.c:197: Test failed: data_count set to 48 instead of 7*sizeof(WCHAR) h:\wine\wine\dlls\advapi32\tests\registry.c:198: Test failed: type 2 is not REG_SZ h:\wine\wine\dlls\advapi32\tests\registry.c:199: Test failed: value is not 'Test' h:\wine\wine\dlls\advapi32\tests\registry.c:200: Test failed: data is not 'foobar' registry: 56 tests executed, 0 marked as todo, 31 failures. Thanks, Kye Lewis kyethespy(a)liquid2k.com

Dec. 9, 2002

Re: How to find out if file is loaded?

by Francois Gouget

On Tue, 3 Dec 2002, Klaus Niederkrueger wrote: [...] > So it seems to me that the file tiles\TS01.BMP is loaded, but when I use > "ltrace wine ..." I don't find any output regarding this file. Why is > that? Maybe open operation is done by wineserver? (then the filedesc is sent to wine via a Unix pipe) -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly.

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad

by Francois Gouget

On 2 Dec 2002, Morten Welinder wrote: [...] > > Unless we're talking an inner and very intensive loop, all this is a > bit silly. > > However, assuming that it does make sense, sprintf variants are not > part of the answer. They're interpreted and var-arg type Why would vararg be a problem performance-wise? > More like something along these lines: > > char *tmpdst = dst; > > strcpy (tmpdst, src1); tmpdst += strlen (src1); [...] > This works even better when the strlen calls have known results. Except usually src* are constant strings and it's a major pain from a maintainability and readability point of vue to have to duplicate them. And whenever src* is not a constant, the above is twice as slow as cpycat because each string is read twice (once by strcpy and another time by strlen). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ 1 + e ^ ( i * pi ) = 0

Dec. 9, 2002

Re: Non latin fonts and non local fonts

by Huw D M Davies

On Mon, Dec 09, 2002 at 11:50:06PM +0200, Shachar Shemesh wrote: > Hi list, > > http://bugs.winehq.com/show_bug.cgi?id=1157 > > It appears that when I'm copying the Windows fonts to C:\windows\Fonts, > setting LANG to he_IL is all it takes for Hebrew to be displayed in edit > controls and dialog boxes. > > When I try to copy the exact same fonts to /usr/lib/X11/fonts/windows, > and adding them to the XF86Config fonts dir, and running ttmkfdir, no > go. The fonts are available to Wine (and each is enumerated multiple > times in the fonts dialog), but Hebrew is not displayed by default. > > Sometimes, when I force the CHARSET to HEBREW_CHARSET, I get Hebrew > after all, but I'm not at all sure the same font is used then. > > In addition to this problem, I was wondering why we no longer enumerate > the X fonts the moment there is ONE font file in c:\windows\Fonts? Is > there a reason for them to magically disappear? The difference is between: 1. Wine rendering the glyph itself and transfering the bitmap to the XServer using either the RENDER extension or X11 pixmap core requests. (client side rendering) 2. Letting the XServer render and display the glpyh all through X11 font core requests (server side rendering). [Note whether the XServer actually renders the glyphs itself or calls out to a font server makes no difference - to the client it looks like the XServer is doing the work. Now the X11 font core requests just don't provide enough control to properly mimic the Windows font api. For example there's no way to do anti-aliasing; there's also no way for the client to learn about the outlines of scalable fonts which is needed for printing. This makes server side rendering much less preferable than client side rendering. However to use client side rendering Wine needs to have access to some font files; once it has these it'll switch to using client side rendering for all fonts and not even query the XServer about its own fonts. So as soon as you give it one font in c:\windows\fonts Wine will ignore any fonts installed solely on the XServer. Now if you want Wine to see these fonts either copy them into c:\windows\fonts or add a [Fontdirs] section to the config file and add lines like "dir1"="/unix/path/to/font/dir" "dir2"="/unix/path/to/another/font/dir" Huw.

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad

by Francois Gouget

On Tue, 3 Dec 2002, Michal Janusz Miroslaw wrote: [...] > Since we are talking about catenating strings only (no %d and family), > then I would suggest combining speed of cpycat (in glibc there's stpcpy) > and ease of use of sprintf and use something like that: [...] > Then we could write: > > strpcpymore(buffer, "path", "/", "file", ".", "ext", NULL); Yep, that looks good. I guess it would return a pointer to the terminating '\0' too :-) However I have to note that it is a bit less flexible than the basic cpycat as you cannot do things like: cpycat(buf,foo); if (condition1) cpycat(buffer,bar); if (condition2) cpycat(buffer,stuff); cpycat(buffer,more); But yes, any of these would have been better than the braindead strcpy and strcat implementations we have in C libraries. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ In a world without fences who needs Gates?

Dec. 9, 2002

Re: MSI (MS Installer)

by Shachar Shemesh

Shachar Shemesh wrote: > Zsolt Rizsanyi wrote: > >> It is not implemented. That's sure. (Tough installing MS Office 2k >> installs it for you) >> I have not heard anybody speaking about implementing it on this list >> (I'm listening here since about a year). >> >> Regards >> Zsolt >> >> >> > As MSI is an MS redistributable, isn't it perfectly legal for us to > put a copy of it on our web site? Does this project have a lawyer that > can give an authorative answer to that question? > > Shachar > To answer my own question - they require that the installer only be redistributed with an application, that the application add significant functionality to the redistibutables themselves, and that the application be only compatible with MS Windows. I guess we can't put it on our site, though I very much doubt they are allowed to request that last paragraph. Still, we can direct people to their site and tell them to D/L it from there, if there are any problems. Sh.

Dec. 9, 2002

Re: Wine startup problem

by Leonardo Giordani

The war3.exe was only an example (however using -opengl does the same). This happens with every (EVERY) application... -- ------------ Leonardo Giordani leo.giordani(a)libero.it

Dec. 9, 2002

Re: Wine startup problem

by Bobby Bingham

did you read the warcraft 3 howto? (it's on the application database). ie: - did you install the no-cd patch - did you remove/rename the "Movies" folder - are you running with "-opengl" to use opengl rendering instead of D3D Bobby Bingham On Mon, Dec 09, 2002 at 11:00:43PM +0100, Leonardo Giordani wrote: > I'm using CVS Wine 20021125, but I cannot start any application: what I gete > is always > > -bash-2.05b$ wine War3.exe > Loading required GL library /usr/X11R6/lib/libGL.so.1.2 > err:ntdll:RtlpWaitForCriticalSection section 0x4010ad10 > "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) > tid=09545090 > > It hangs and does nothing. What's the matter? > > Thank you > > ------------ > Leonardo Giordani > leo.giordani(a)libero.it

Dec. 9, 2002

Re: Janitorial Projects -- conformance tests --recruiting volunteers

by Alberto Massari

>Volunters welcome. I thought I could try running them on my Windows XP Home machine.... C:\Downloads\Linux>advapi32_test.exe registry h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set to 'xxxxxxxxxx' instead of 'Te' h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set to 'xxxxxxx' instead of 'foobar' h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set to 'xxxxxxx' instead of 'foobar' registry: 56 tests executed, 0 marked as todo, 3 failures. C:\Downloads\Linux>kernel32_test.exe alloc alloc: 58 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe atom atom: 229398 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe codepage codepage: 2 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe directory directory: 48 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe drive drive: 160 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe environ environ: 39 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe file h:\wine\wine\dlls\kernel\tests\file.c:578: Test failed: DeleteFile should fail with an empty path, and last error value should be ERROR_FILE_NOT_FOUND h:\wine\wine\dlls\kernel\tests\file.c:610:Current offset = 0015 h:\wine\wine\dlls\kernel\tests\file.c:635:Current offset = 0015 file: 487238 tests executed, 0 marked as todo, 1 failure. C:\Downloads\Linux>kernel32_test.exe format_msg format_msg: 58 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe locale locale: 54 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>kernel32_test.exe path h:\wine\wine\dlls\kernel\tests\path.c:517: Test failed: GetLongPathNameA: wrong return code, 102 instead of 42 h:\wine\wine\dlls\kernel\tests\path.c:927:TMP=C:\DOCUME~1\alby\IMPOST~1\Temp h:\wine\wine\dlls\kernel\tests\path.c:935:TMP=C:\WINDOWS h:\wine\wine\dlls\kernel\tests\path.c:944:TMP=C:\ h:\wine\wine\dlls\kernel\tests\path.c:954:TMP=C: h:\wine\wine\dlls\kernel\tests\path.c:879: Test failed: win2000 BUG: expected 12, got 13 h:\wine\wine\dlls\kernel\tests\path.c:892: Test failed: win2000 BUG: expected 12, got 13 h:\wine\wine\dlls\kernel\tests\path.c:898: Test failed: win2000 BUG: should return path without terminating back slash path: 2083 tests executed, 0 marked as todo, 4 failures. C:\Downloads\Linux>kernel32_test.exe process tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\kernel\tests\process.c:374: Test failed: StartupInfoA:lpDesktop expected (null), got WinSta0\Default h:\wine\wine\dlls\kernel\tests\process.c:375: Test failed: StartupInfoA:lpTitle expected (null), got C:\Downloads\Linux\kernel32_test.exe tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\kernel\tests\process.c:450: Test failed: StartupInfoA:lpDesktop expected (null), got WinSta0\Default tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\kernel\tests\process.c:527: Test failed: StartupInfoA:lpTitle expected (null), got C:\Downloads\Linux\kernel32_test.exe tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. process: 116 tests executed, 0 marked as todo, 4 failures. C:\Downloads\Linux>kernel32_test.exe thread thread: 112 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>msvcrt_test.exe msvcrt C:\Downloads\Linux>netapi32_test.exe access h:\wine\wine\dlls\netapi32\tests\access.c:95: Test failed: Bad Network Path access: 23 tests executed, 0 marked as todo, 1 failure. C:\Downloads\Linux>netapi32_test.exe apibuf apibuf: 15 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>netapi32_test.exe wksta wksta: 14 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>Rem These don't compile with the MSVC headers C:\Downloads\Linux>rpcrt4_test.exe rpc h:\wine\wine\dlls\rpcrt4\tests\rpc.c:124: ** Uuid Conversion and Comparison Tests ** rpc: 901 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>shell32_test.exe shlfileop h:\wine\wine\dlls\shell32\tests\shlfileop.c:286: Test failed: Files are copied to other directory h:\wine\wine\dlls\shell32\tests\shlfileop.c:287: Test failed: The file is copied shlfileop: 121 tests executed, 0 marked as todo, 2 failures. C:\Downloads\Linux>shlwapi_test.exe clist h:\wine\wine\dlls\shlwapi\tests\clist.c:367: Test failed: allowed bad element size h:\wine\wine\dlls\shlwapi\tests\clist.c:372: Test failed: allowed adding a container clist: 236 tests executed, 0 marked as todo, 2 failures. C:\Downloads\Linux>shlwapi_test.exe shreg h:\wine\wine\dlls\shlwapi\tests\shreg.c:172: Test failed: (44,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:196: Test failed: (44,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:206: Test failed: () h:\wine\wine\dlls\shlwapi\tests\shreg.c:207: Test failed: () h:\wine\wine\dlls\shlwapi\tests\shreg.c:208: Test failed: (44,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:219: Test failed: (44,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:241: Test failed: didn't open dest shreg: 39 tests executed, 0 marked as todo, 7 failures. C:\Downloads\Linux>user32_test.exe class class: 80 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>user32_test.exe win h:\wine\wine\dlls\user\tests\win.c:91:main window 001E05DA main2 002E05CE desktop 00010014 child 000E05EC h:\wine\wine\dlls\user\tests\win.c:107:created child 00110698 h:\wine\wine\dlls\user\tests\win.c:120:created child of desktop 00120698 h:\wine\wine\dlls\user\tests\win.c:130:created child of child 00130698 h:\wine\wine\dlls\user\tests\win.c:140:created top-level 00140698 h:\wine\wine\dlls\user\tests\win.c:150:created owned top-level 00150698 h:\wine\wine\dlls\user\tests\win.c:160:created popup 00160698 h:\wine\wine\dlls\user\tests\win.c:170:created owned popup 00170698 h:\wine\wine\dlls\user\tests\win.c:180:created top-level owned by child 00180698 h:\wine\wine\dlls\user\tests\win.c:186:created popup owned by desktop 00190698 h:\wine\wine\dlls\user\tests\win.c:192:created popup owned by child 001A0698 h:\wine\wine\dlls\user\tests\win.c:198:created WS_CHILD popup 001B0698 h:\wine\wine\dlls\user\tests\win.c:204:created owned WS_CHILD popup 001C0698 h:\wine\wine\dlls\user\tests\win.c:209:testing parent changes h:\wine\wine\dlls\user\tests\win.c:221:created child 001D0698 h:\wine\wine\dlls\user\tests\win.c:247:created top-level 001E0698 h:\wine\wine\dlls\user\tests\win.c:264:created popup 001F0698 h:\wine\wine\dlls\user\tests\win.c:281:created child 00200698 h:\wine\wine\dlls\user\tests\win.c:298:created top-level 00210698 h:\wine\wine\dlls\user\tests\win.c:307:created owned popup 00220698 h:\wine\wine\dlls\user\tests\win.c:323:created owner 00230698 and popup 00120696 h:\wine\wine\dlls\user\tests\win.c:337:created owner 00130696 and popup 00240698 h:\wine\wine\dlls\user\tests\win.c:345:created owner 00140696 and popup 00250698 win: 373 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>user32_test.exe wsprintf wsprintf: 4 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>wininet_test.exe http h:\wine\wine\dlls\wininet\tests\http.c:90:Starting with flags 0x10000000 h:\wine\wine\dlls\wininet\tests\http.c:92:InternetOpenA <-- h:\wine\wine\dlls\wininet\tests\http.c:95:InternetOpenA --> h:\wine\wine\dlls\wininet\tests\http.c:101:InternetConnectA <-- h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0004 0xdeadbeef INTERNET_STATUS_HANDLE_CREATED(60) 0012E990 4 h:\wine\wine\dlls\wininet\tests\http.c:104:InternetConnectA --> h:\wine\wine\dlls\wininet\tests\http.c:108:HttpOpenRequestA <-- h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbead INTERNET_STATUS_HANDLE_CREATED(60) 0012EC04 4 h:\wine\wine\dlls\wininet\tests\http.c:122:HttpOpenRequestA --> h:\wine\wine\dlls\wininet\tests\http.c:126:HttpSendRequestA --> h:\wine\wine\dlls\wininet\tests\http.c:133:HttpSendRequestA <-- h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦H²L?I{?v?(80) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_RESOLVING_NAME(10) 014CFB04 15 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_NAME_RESOLVED(11) 014CFAF4 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTING_TO_SERVER(20) 014CFB9C 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTED_TO_SERVER(21) 014CFD40 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_SENDING_REQUEST(30) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_SENT(31) 014CFCE0 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_RECEIVING_RESPONSE(40) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_RESPONSE_RECEIVED(41) 014CFD60 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_COMPLETE(100) 014CFDA8 8 h:\wine\wine\dlls\wininet\tests\http.c:140:Option 0x17 -> 1 8 h:\wine\wine\dlls\wininet\tests\http.c:144:Option 0x22 -> 1 http://www.winehq.com/about/ h:\wine\wine\dlls\wininet\tests\http.c:149:Option 0x16 -> 1 HTTP/1.1 200 OK Date: Mon, 09 Dec 2002 22:20:28 GMT Server: Apache/1.3.22 (Unix) (Red-Hat/Linux) mod_ssl/2.8.5 OpenSSL/0.9.6 PHP/4.1.2 X-Powered-By: PHP/4.1.2 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: text/html h:\wine\wine\dlls\wininet\tests\http.c:154:Option 0x22 -> 1 http://www.winehq.com/about/ h:\wine\wine\dlls\wininet\tests\http.c:158:Option 0x5 -> 0 http://www.winehq.com/about/ (12150) h:\wine\wine\dlls\wininet\tests\http.c:163:Option 0x1 -> 1 text/html h:\wine\wine\dlls\wininet\tests\http.c:166:Entery Query loop h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 743 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 3204 h:\wine\wine\dlls\wininet\tests\http.c:172: Test failed: InternetQueryDataAvailable failed h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_COMPLETE(100) 014CFDA8 8 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CLOSING_CONNECTION(50) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTION_CLOSED(51) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_HANDLE_CLOSING(70) 014CFD68 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 014CFD24 4 h:\wine\wine\dlls\wininet\tests\http.c:90:Starting with flags 0x0 h:\wine\wine\dlls\wininet\tests\http.c:92:InternetOpenA <-- h:\wine\wine\dlls\wininet\tests\http.c:95:InternetOpenA --> h:\wine\wine\dlls\wininet\tests\http.c:101:InternetConnectA <-- h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0004 0xdeadbeef INTERNET_STATUS_HANDLE_CREATED(60) 0012E990 4 h:\wine\wine\dlls\wininet\tests\http.c:104:InternetConnectA --> h:\wine\wine\dlls\wininet\tests\http.c:108:HttpOpenRequestA <-- h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbead INTERNET_STATUS_HANDLE_CREATED(60) 0012EC04 4 h:\wine\wine\dlls\wininet\tests\http.c:122:HttpOpenRequestA --> h:\wine\wine\dlls\wininet\tests\http.c:126:HttpSendRequestA --> h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ÞÙ?(80) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTING_TO_SERVER(20) 0012EA3C 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTED_TO_SERVER(21) 0012EA18 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_SENDING_REQUEST(30) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_SENT(31) 0012EB28 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_RECEIVING_RESPONSE(40) 00000000 0 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_RESPONSE_RECEIVED(41) 0012EB10 4 h:\wine\wine\dlls\wininet\tests\http.c:133:HttpSendRequestA <-- h:\wine\wine\dlls\wininet\tests\http.c:140:Option 0x17 -> 1 8 h:\wine\wine\dlls\wininet\tests\http.c:144:Option 0x22 -> 1 http://www.winehq.com/about/ h:\wine\wine\dlls\wininet\tests\http.c:149:Option 0x16 -> 1 HTTP/1.1 200 OK Date: Mon, 09 Dec 2002 22:20:29 GMT Server: Apache/1.3.22 (Unix) (Red-Hat/Linux) mod_ssl/2.8.5 OpenSSL/0.9.6 PHP/4.1.2 X-Powered-By: PHP/4.1.2 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: text/html h:\wine\wine\dlls\wininet\tests\http.c:154:Option 0x22 -> 1 http://www.winehq.com/about/ h:\wine\wine\dlls\wininet\tests\http.c:158:Option 0x5 -> 0 http://www.winehq.com/about/ (12150) h:\wine\wine\dlls\wininet\tests\http.c:163:Option 0x1 -> 1 text/html h:\wine\wine\dlls\wininet\tests\http.c:166:Entery Query loop h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 743 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 3204 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 4236 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 3722 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4 http: 22 tests executed, 0 marked as todo, 1 failure. C:\Downloads\Linux>winmm_test.exe wave h:\wine\wine\dlls\winmm\tests\wave.c:56:found 2 WaveOut devices h:\wine\wine\dlls\winmm\tests\wave.c:82: 0: "SoundMAX Digital Audio" 5.10 (1:100): channels=65535 formats=bffff support=002c h:\wine\wine\dlls\winmm\tests\wave.c:133:Testing invalid 2MHz format h:\wine\wine\dlls\winmm\tests\wave.c:82: 1: "Riproduzione linea #0 modem" 5.0 (1:81): channels=1 formats=0000 support=0000 h:\wine\wine\dlls\winmm\tests\wave.c:133:Testing invalid 2MHz format wave: 56 tests executed, 0 marked as todo, 0 failures. C:\Downloads\Linux>ws2_32_test.exe sock h:\wine\wine\dlls\winsock\tests\sock.c:694: **** STARTING TEST 0 **** h:\wine\wine\dlls\winsock\tests\sock.c:332:simple_server (1740) starting h:\wine\wine\dlls\winsock\tests\sock.c:391:simple_client (ef4): starting h:\wine\wine\dlls\winsock\tests\sock.c:341:simple_server (1740) ready h:\wine\wine\dlls\winsock\tests\sock.c:394:simple_client (ef4): server ready h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (1740): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:391:simple_client (17fc): starting h:\wine\wine\dlls\winsock\tests\sock.c:394:simple_client (17fc): server ready h:\wine\wine\dlls\winsock\tests\sock.c:406:simple_client (17fc) connected h:\wine\wine\dlls\winsock\tests\sock.c:406:simple_client (ef4) connected h:\wine\wine\dlls\winsock\tests\sock.c:427:simple_client (17fc) exiting h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (1740): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:427:simple_client (ef4) exiting h:\wine\wine\dlls\winsock\tests\sock.c:374:simple_server (1740) exiting h:\wine\wine\dlls\winsock\tests\sock.c:696: **** TEST 0 COMPLETE **** h:\wine\wine\dlls\winsock\tests\sock.c:694: **** STARTING TEST 1 **** h:\wine\wine\dlls\winsock\tests\sock.c:332:simple_server (1438) starting h:\wine\wine\dlls\winsock\tests\sock.c:341:simple_server (1438) ready h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (1438): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:445:event_client (80): starting h:\wine\wine\dlls\winsock\tests\sock.c:445:event_client (8b0): starting h:\wine\wine\dlls\winsock\tests\sock.c:447:event_client (80): server ready h:\wine\wine\dlls\winsock\tests\sock.c:467:event_client (80) connected h:\wine\wine\dlls\winsock\tests\sock.c:447:event_client (8b0): server ready h:\wine\wine\dlls\winsock\tests\sock.c:467:event_client (8b0) connected h:\wine\wine\dlls\winsock\tests\sock.c:505:event_client (80): all data sent - shutdown h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (1438): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:505:event_client (8b0): all data sent - shutdown h:\wine\wine\dlls\winsock\tests\sock.c:374:simple_server (1438) exiting h:\wine\wine\dlls\winsock\tests\sock.c:526:event_client (8b0): all data received h:\wine\wine\dlls\winsock\tests\sock.c:538:event_client (8b0): close event h:\wine\wine\dlls\winsock\tests\sock.c:556:event_client (8b0) exiting h:\wine\wine\dlls\winsock\tests\sock.c:526:event_client (80): all data received h:\wine\wine\dlls\winsock\tests\sock.c:538:event_client (80): close event h:\wine\wine\dlls\winsock\tests\sock.c:556:event_client (80) exiting h:\wine\wine\dlls\winsock\tests\sock.c:696: **** TEST 1 COMPLETE **** sock: 164 tests executed, 0 marked as todo, 0 failures. Alberto

Dec. 9, 2002

Re: Wine startup problem

by Uwe Bonnes

>>>>> "Leonardo" == Leonardo Giordani <leo.giordani(a)libero.it> writes: Leonardo> I'm using CVS Wine 20021125, but I cannot start any Leonardo> application: what I gete is always Leonardo> -bash-2.05b$ wine War3.exe Loading required GL library Leonardo> /usr/X11R6/lib/libGL.so.1.2 Leonardo> err:ntdll:RtlpWaitForCriticalSection section 0x4010ad10 Leonardo> "../../loader/module.c: loader_section" wait timed out, Leonardo> retrying (60 sec) tid=09545090 Leonardo> It hangs and does nothing. What's the matter? Try another time. Also switch from desktop mode to normal mode and back. -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by vkxzjq6lg＠cswebmail.com

"Dimitrie O. Paun" wrote: > > On December 5, 2002 11:16 am, Alexandre Julliard wrote: > > It's the kind of thinking that leads to having an exception > > handler inside strlen() like Windows does. It's just plain wrong. > > <nod/>. This is generally true for other things as well: > > 1. Many places in our code where we have invariant like > pointer p is never NULL, yet we always have: > > if (!p) return NULL; /* or whatever error condition */ > > Such a check is harmful (hides bugs), slow (useless > runtime check), bloat (more generated code), > ugly (clutters the code), at the very least. Just > Don't Do It (TM) -- let the code crash. Agreed that it's harmful because it hides what may be a real error. Lousy idea unless p really is allowed to have that value. If it's a call exposed to external callers it needs to warn somehow, even to the console if necessary (assuming that Wine wants to give end users some feedback they can give back to the Wine developers and to the developer of the faulty application). Those warnings can vanish should there ever be a production build with debugging removed. If it's internal only it should be an assert or fixme. Being too free with "let the code crash" is a bad idea. Microsoft got a lot of really bad heckling in the Windows 3.1 era for GPFs. Wine doesn't want to crash if it's reasonably harmless to continue (like for a failed screen update). Does want to report the problem, of course, rather than silently ignore it, otherwise it'll never get fixed. > > 2. ZeroMemory when we don't need to, when we pass struct > internally, yet same functions can be called externally > with no guarantee that the struct has unused field > zeroed out. > Agreed if it is a call to an internal only function. If it's to a function with an external API then it may need zeroing to get to the state required for that. > 3. In general, we have all sort of 'defensive programming' > checks for invariants. Problem is, we never going to > catch bugs in this area this way. Just use assert() > if you feel a check is needed. If it's a documented external interface it can't assert and die because the application making the call presumably works on real Windows. So it needs to be warned/fixme'd or whatever so end users can report the issue to Wine developers for fixing. If it's internal, assert is sort of OK, though as someone trying to get an application working I want a fixme rather than sudden death (except in file output interfaces!). I don't need perfect functionality. I do need to get the app to the point where it is safely functioning and an assert may kill it when it doesn't need to die. > In short, this defensive programming crap is just that: crap. Do you agree with the way I've explained how I see the difference between redundant defensive programming and detecting and reporting problems which need to be fixed? If not, where do you differ and why? James ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/

Dec. 9, 2002

Re: MSI (MS Installer)

by Duane Clark

Uwe Bonnes wrote: >>>>>>"Zsolt" == Zsolt Rizsanyi <rizsanyi(a)myrealbox.com> writes: > > > Zsolt> On Monday 09 December 2002 17:54, Scott Cote wrote: > >> I've found that many of the test applications I've tried installing > >> failed due to the lack of MSIEXEC. If it is implemented, could you > >> tell me where to find it? If not, I'd like to contribute, could you > >> tell me if any work has been done and who to coordinate with? > > Zsolt> It is not implemented. That's sure. (Tough installing MS Office > Zsolt> 2k installs it for you) I have not heard anybody speaking about > Zsolt> implementing it on this list (I'm listening here since about a > Zsolt> year). > > We don't need to implement every MS dll. We only need to implement: > - core dlls (kernel32, comclt32, ...) which applications expect to be > available > - dlls used for compiling/porting (msvcrt) > > I guess this msiexec is not loaded to the system after a clean > Windowsinstall. In this case the installer must cope with the situation that > msiexec is not there and must provide it itself. And just as a bit more info, MSI can be downloaded freely and directly from Microsoft. Just go to http://search.microsoft.com/default.asp Type "msi" into the search box, and a couple different versions are available. Seems to work fine.

Dec. 9, 2002

Re: MSI (MS Installer)

by Shachar Shemesh

Zsolt Rizsanyi wrote: >It is not implemented. That's sure. (Tough installing MS Office 2k installs it >for you) >I have not heard anybody speaking about implementing it on this list (I'm >listening here since about a year). > >Regards >Zsolt > > > As MSI is an MS redistributable, isn't it perfectly legal for us to put a copy of it on our web site? Does this project have a lawyer that can give an authorative answer to that question? Shachar

Dec. 9, 2002

Re: wpp

by Francois Gouget

On Sun, 8 Dec 2002, Dimitrie O. Paun wrote: [...] > Hmm, I don't know about that either -- windres certainly calls gcc -E, > and it's working just fine. Anyway, I don't see a compelling reason to > change the status quo, thanks for helping me clarify this issue. What we might do is change the way we compile rc files so that we use gcc -E rather than wpp and see if that causes problems. This would have to be done in Wine and in winemaker (especially in winemaker). That way if there are problems we would be more likely to discover them (though it might take a few months) and would still be able to easily switch back to using wpp if necessary. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

On December 9, 2002 05:09 pm, Francois Gouget wrote: > What we might do is change the way we compile rc files so that we use > gcc -E rather than wpp and see if that causes problems. There is already a dummy --preprocessor option in wrc (for compatibility with windres). First step would be properly implement that one, to allow for external override of the preprocessor. Then we can experiment with it, see what we get (errors, speed penalties, etc.). -- Dimi.

Dec. 9, 2002

Re: Intel 8x0 and ALSA sound driver

by Nikolay Stefanov

I've fixed the problem - turns out that ALSA driver doesn't like it when the buffer and period sizes are set directly. I modified the setup code to use buffer and period times instead, with some values that I copied from the OGLE alsa driver. Also it seems that the driver crashes if these are set before the sample rate, if you are wondering about the change of order. Everything seems to work normally now, I tested it with WinAmp and some games. What do you think, is this is a driver issue or a wine issue? None of the other projects that I checked (ogle, mplayer) set the sizes directly, they use time values instead. Lastly, is there any special reason why the dsound implementation is not using mmap_write, like the wave one does? Nikolay PS: Thanks to Michal Miroslaw for the patch, it's a lot simpler than what I did initially. ------ patch against 20021125 --------- diff -ur sources/wine-20021125-orig/dlls/winmm/winealsa/audio.c sources/wine-20021125/dlls/winmm/winealsa/audio.c --- sources/wine-20021125-orig/dlls/winmm/winealsa/audio.c 2002-10-25 20:09:02.000000000 +0100 +++ sources/wine-20021125/dlls/winmm/winealsa/audio.c 2002-12-09 21:36:45.000000000 +0000 @@ -217,13 +217,13 @@ } \ } while(0) - EXIT_ON_ERROR( snd_ctl_open(&ctl,"hw:0",0) , "ctl open failed" ); + EXIT_ON_ERROR( snd_ctl_open(&ctl,"hw",0) , "ctl open failed" ); EXIT_ON_ERROR( snd_ctl_card_info(ctl, cardinfo), "card info failed"); EXIT_ON_ERROR( snd_ctl_elem_list(ctl, elemlist), "elem list failed"); nCtrls = snd_ctl_elem_list_get_count(elemlist); - EXIT_ON_ERROR( snd_hctl_open(&hctl,"hw:0",0), "hctl open failed"); + EXIT_ON_ERROR( snd_hctl_open(&hctl,"hw",0), "hctl open failed"); EXIT_ON_ERROR( snd_hctl_load(hctl), "hctl load failed" ); elem=snd_hctl_first_elem(hctl); @@ -405,7 +405,7 @@ wwo = &WOutDev[0]; /* FIXME: use better values */ - wwo->device = "hw:0,0"; + wwo->device = "hw"; wwo->caps.wMid = 0x0002; wwo->caps.wPid = 0x0104; strcpy(wwo->caps.szPname, "SB16 Wave Out"); @@ -1033,8 +1033,9 @@ snd_pcm_access_t access; snd_pcm_format_t format; int rate; - int buffer_size = 0x4000; /* in frames (1 frame = sizeof(sample) * n.channels) */ - int num_periods = 32; + unsigned int buffer_time = 500000; + unsigned int period_time = 10000; + int buffer_size; snd_pcm_uframes_t period_size; int flags; snd_pcm_t * pcm; @@ -1128,12 +1129,6 @@ format = (wwo->format.wBitsPerSample == 16) ? SND_PCM_FORMAT_S16_LE : SND_PCM_FORMAT_U8; EXIT_ON_ERROR( snd_pcm_hw_params_set_format(pcm, hw_params, format), MMSYSERR_INVALPARAM, "unable to set required format"); - EXIT_ON_ERROR( snd_pcm_hw_params_set_buffer_size_near(pcm, hw_params, buffer_size), MMSYSERR_NOMEM, "unable to get required buffer"); - buffer_size = snd_pcm_hw_params_get_buffer_size(hw_params); - - EXIT_ON_ERROR( snd_pcm_hw_params_set_period_size_near(pcm, hw_params, buffer_size/num_periods, 0), MMSYSERR_ERROR, "unable to set required period size"); - period_size = snd_pcm_hw_params_get_period_size(hw_params, 0); - rate = snd_pcm_hw_params_set_rate_near(pcm, hw_params, wwo->format.wf.nSamplesPerSec, 0); if (rate < 0) { ERR("Rate %ld Hz not available for playback: %s\n", wwo->format.wf.nSamplesPerSec, snd_strerror(rate)); @@ -1145,8 +1140,14 @@ snd_pcm_close(pcm); return WAVERR_BADFORMAT; } + + EXIT_ON_ERROR( snd_pcm_hw_params_set_buffer_time_near(pcm, hw_params, buffer_time, 0), MMSYSERR_INVALPARAM, "unable to set buffer time"); + EXIT_ON_ERROR( snd_pcm_hw_params_set_period_time_near(pcm, hw_params, period_time, 0), MMSYSERR_INVALPARAM, "unable to set period time"); EXIT_ON_ERROR( snd_pcm_hw_params(pcm, hw_params), MMSYSERR_INVALPARAM, "unable to set hw params for playback"); + + period_size = snd_pcm_hw_params_get_period_size(hw_params, 0); + buffer_size = snd_pcm_hw_params_get_buffer_size(hw_params); snd_pcm_sw_params_current(pcm, sw_params); EXIT_ON_ERROR( snd_pcm_sw_params_set_start_threshold(pcm, sw_params, dwFlags & WAVE_DIRECTSOUND ? INT_MAX : 1 ), MMSYSERR_ERROR, "unable to set start threshold");

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

On December 9, 2002 04:45 pm, Francois Gouget wrote: > Let's not forget the goal of Winelib: making > it possible to recompile Windows applications to Unix, not making it > possible to compile native Unix applications using the Windows > API+MinGW. Not that I disagree with your points, but I think there is some confusion about MinGW. MinGW apps are NOT native Unix apps. They are native Windows app that just happen to use gcc instead of MSVC for the compiler. Now, give that most OSS Windows app support MinGW, I think it's a very important segment we need to address (not to mention most like a lot easier to capture). Yeah, most commercial apps do use MSVC, but those app need internal forces for a port anyway, all we can do is make it easy for them. Most important in that area is probably .dsp support in winemaker, but this is a different ball of wax... -- Dimi.

Dec. 9, 2002

Wine startup problem

by Leonardo Giordani

I'm using CVS Wine 20021125, but I cannot start any application: what I gete is always -bash-2.05b$ wine War3.exe Loading required GL library /usr/X11R6/lib/libGL.so.1.2 err:ntdll:RtlpWaitForCriticalSection section 0x4010ad10 "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) tid=09545090 It hangs and does nothing. What's the matter? Thank you ------------ Leonardo Giordani leo.giordani(a)libero.it

Dec. 9, 2002

Re: wrc options

by Francois Gouget

On Sun, 8 Dec 2002, Dimitrie O. Paun wrote: [...] > " -L Leave case of embedded filenames as is\n" > > Shouldn't this one be on by default? Why do we need this option? I agree with that one. As it is wrc just convert the filenames to lowercase before trying to include them which is just plain wrong. In particular it causes compilation errors if the file really has a mized-case which is not that uncommon. It should either match them in a case-insensitive way, or leave them as is, and not do ugly hacks that are about as likely to cause compilation errors as they are to avoid some. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ "Lotto: A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U

Dec. 9, 2002

Re: MSI (MS Installer)

by Uwe Bonnes

>>>>> "Zsolt" == Zsolt Rizsanyi <rizsanyi(a)myrealbox.com> writes: Zsolt> On Monday 09 December 2002 17:54, Scott Cote wrote: >> I've found that many of the test applications I've tried installing >> failed due to the lack of MSIEXEC. If it is implemented, could you >> tell me where to find it? If not, I'd like to contribute, could you >> tell me if any work has been done and who to coordinate with? Zsolt> It is not implemented. That's sure. (Tough installing MS Office Zsolt> 2k installs it for you) I have not heard anybody speaking about Zsolt> implementing it on this list (I'm listening here since about a Zsolt> year). We don't need to implement every MS dll. We only need to implement: - core dlls (kernel32, comclt32, ...) which applications expect to be available - dlls used for compiling/porting (msvcrt) I guess this msiexec is not loaded to the system after a clean Windowsinstall. In this case the installer must cope with the situation that msiexec is not there and must provide it itself. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 9, 2002

Non latin fonts and non local fonts

by Shachar Shemesh

Hi list, http://bugs.winehq.com/show_bug.cgi?id=1157 It appears that when I'm copying the Windows fonts to C:\windows\Fonts, setting LANG to he_IL is all it takes for Hebrew to be displayed in edit controls and dialog boxes. When I try to copy the exact same fonts to /usr/lib/X11/fonts/windows, and adding them to the XF86Config fonts dir, and running ttmkfdir, no go. The fonts are available to Wine (and each is enumerated multiple times in the fonts dialog), but Hebrew is not displayed by default. Sometimes, when I force the CHARSET to HEBREW_CHARSET, I get Hebrew after all, but I'm not at all sure the same font is used then. In addition to this problem, I was wondering why we no longer enumerate the X fonts the moment there is ONE font file in c:\windows\Fonts? Is there a reason for them to magically disappear? Shachar

Dec. 9, 2002

Re: Janitorial Projects -- conformance tests --recruiting volunteers

by Tony Lambregts

David Miller wrote: > I could probably run some tests under WinXP. I just need to compile > the tests on windows, execute them, and post output to wine-devel? Is > this correct? > > > Pretty much. -- Tony Lambregts

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Tony Lambregts

Mike Hearn wrote: >The UK. > >I'm not au fait with the reverse engineering laws here, and I'm not very >good at it anyway, so I'd rather avoid it if possible. But once you've >seemingly exhausted a trace what do you do next? I can't breakpoint on a >call, because the call that would let me get the right part is never >called... > > > You can put a software breakpoint in the code (inside a complex if statement if need be) DbgBreakPoint() is the function to call. -- Tony Lambregts

Dec. 9, 2002

Re: wpp

by Francois Gouget

On Sun, 8 Dec 2002, Dimitrie O. Paun wrote: > On December 8, 2002 05:56 pm, Alexandre Julliard wrote: > > I believe it was mostly issues with getting rid of C code in header > > files, though that is handled in the main parser now. Still, it's not > > guaranteed that the C preprocessor would handle non C code correctly. > > Hmm, I don't know about that either -- windres certainly calls gcc -E, > and it's working just fine. Projects compiled using MinGW and windres are not 'normal' Windows projects. In particular they don't prove that a project built using Visual C++ and rc is going to compile if you process the rc files using gcc -E. Given the dominant position of Visual C++ on the Windows platform, compatibility with Visual C++ projects is the main point of Winelib. it is orders of magnitude more important than compatibility with windres and MinGW-based projects. Let's not forget the goal of Winelib: making it possible to recompile Windows applications to Unix, not making it possible to compile native Unix applications using the Windows API+MinGW. Better compatibility with MinGW is a means to that end, no more. I don't know whether we still need the integrated preprocessor, but I think we should not be too hasty in removing it. It would be pretty bad to remove it just to discover a few months later that it was needed after all. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ $live{free} || die "";

Dec. 9, 2002

Re: Janitorial Projects -- conformance tests --recruiting volunteers

by Francois Gouget

On Mon, 9 Dec 2002, David Miller wrote: > I could probably run some tests under WinXP. I just need to compile the > tests on windows, execute them, and post output to wine-devel? Is this correct? Almost. Currently building the tests on Windows requires using Linux at some point :-/ So what I did is compile them here, whip up a quick batch file to invoke them all, and zip them up. You can download them from: http://fgouget.free.fr/wine/winetests.zip Just unzip them in some random directory and run them as follows: runtests.bat The above script skips the generated tests (for no particular reason) and skips the sysparams user32 test because it messes the environment badly (e.g. the width of window borders). Given the number of tests that fail you may want to run them one by one to better capture their output. To do so just have a quick look at the batch file, running the tests is very easy, e.g.: kernel32_test.exe path The zip file I made is very rough on the edges. What we need is: * automatic generation of that batch file (by msvcmaker?) * automatic zipping of the tests * better handling of Wine_Header vs. MSVC_Header tests * or maybe just base this on the MinGW cross-compiler rather than the Visual C++ 'port' Volunters welcome. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ f u kn rd ts, ur wy 2 gky 4 ur wn gd.

Dec. 9, 2002

Re: MSI (MS Installer)

by Zsolt Rizsanyi

On Monday 09 December 2002 17:54, Scott Cote wrote: > I've found that many of the test applications I've tried installing failed > due to the lack of MSIEXEC. If it is implemented, could you tell me where > to find it? If not, I'd like to contribute, could you tell me if any work > has been done and who to coordinate with? It is not implemented. That's sure. (Tough installing MS Office 2k installs it for you) I have not heard anybody speaking about implementing it on this list (I'm listening here since about a year). Regards Zsolt

Dec. 9, 2002

Re: Turkish keyboard Support

by Zsolt Rizsanyi

On Monday 09 December 2002 19:29, Armish wrote: > Hi all, > I tried the latest wine (Wine-20021125.tar.gz) and saw > that though it supports the Turkish Keyboard Layout, I > cannot write the specail chars of Turkish (Like ı > ş ğ ü ç ö ...) > Then I found a (Turkish) keyboard.c but still don't > know where or how to it? (The keyboard.c is working > well with my kernel) What can I do? I dont think that the problem is with the keyboard layout. I had poblems entering hungarian keys odoubleacute (ő) and udoubleacute (ű). I fixed that problem with a hack to convert non Latin-1 keysyms to Unicode. I have sent that patch for inclusion, but I was said that there is a more correct patch in CX Office (the codeweavers' wine version) that will be merged soon. BTW what's the state of that merge? Regards Zsolt

Dec. 9, 2002

Re: Turkish keyboard Support

by Jeff Smith

Was this working under Wine-20021031? I have been trying to figure out a similar problem with the Spanish keyboard layout. If this caused a regression for you as well, it means I have been looking at the wrong problem. If you could test with the 20021031 version and compare results, that could be very helpful. -- Jeff S >From: Armish <acemimsi(a)yahoo.com> > >Hi all, >I tried the latest wine (Wine-20021125.tar.gz) and saw >that though it supports the Turkish Keyboard Layout, I >cannot write the specail chars of Turkish (Like ý >þ ð ü ç ö ...) >Then I found a (Turkish) keyboard.c but still don't >know where or how to it? (The keyboard.c is working >well with my kernel) What can I do? >(The keyboard.c is in the attach. for someone who want >to check) >Thanks _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

Dec. 9, 2002

Re: Fix the winmm/wave tests

by Francois Gouget

On 6 Dec 2002, Alexandre Julliard wrote: > Francois Gouget <fgouget(a)free.fr> writes: > > > * dlls/winmm/tests/wave.c > > > > Error handling in waveOutOpen works now (patch has been in CVs for a > > couple of weeks) -> removing the todo_wine > > This doesn't work for me: > > ../../../tools/runtest -q -P wine -M winmm.dll -T ../../.. -p winmm_test.exe.so wave.c && touch wave.ok > err:wave:wodOpen Rate doesn't match (requested 2000000 Hz, got 48000 Hz) > err:wave:wodOpen Rate doesn't match (requested 2000000 Hz, got 48000 Hz) > wave.c:145: Test failed: opening the device at 2MHz should fail 0: rc=4 Strange. 4 means MMSYSERR_ALLOCATED and it appears that it may be returned if a Unix process already is using the device or if the device really is already allocated by Wine. I guess it's reproducible? Was another process using the sound device at the time? Are you using the wineoss driver or are you using one of the new ones? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The greatest programming project of all took six days; on the seventh day the programmer rested. We've been trying to debug the *&^%$#@ thing ever since. Moral: design before you implement.

Dec. 9, 2002

Re: Question about STRICT

by Francois Gouget

On Sat, 7 Dec 2002, Vincent Béron wrote: [...] > I await your comments on it. [...] > +#ifndef NO_STRICT > +#ifndef STRICT > +#define STRICT > +#endif /* STRICT */ > +#endif /* NO_STRICT */ I did not know this was in the Windows headers but it is. Thus I think it makes sense to add it to 'windef.h' (with a bit of indentation for the #ifdefs). I suppose Winelib applications would need it. The only question is whether the Wine code should rely on it too: it's not very clean in that if you don't #inlude <windef.h> (directly or indirectly) then -DSTRICT is not turned on. But I'm not sure Wine has files that don't include windef.h at some point since windef.h is relatively low level. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The greatest programming project of all took six days; on the seventh day the programmer rested. We've been trying to debug the *&^%$#@ thing ever since. Moral: design before you implement.

Dec. 9, 2002

Turkish keyboard Support

by Armish

Hi all, I tried the latest wine (Wine-20021125.tar.gz) and saw that though it supports the Turkish Keyboard Layout, I cannot write the specail chars of Turkish (Like ı ş ğ � � � ...) Then I found a (Turkish) keyboard.c but still don't know where or how to it? (The keyboard.c is working well with my kernel) What can I do? (The keyboard.c is in the attach. for someone who want to check) Thanks __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Dec. 9, 2002

Re: Fw: Loading Autorun.inf on CD's

by Dustin Navea

That is basically what I have been saying.. sorry for the html output but I am replying from work thru sbc's site and theres no option to turn it off. Basically, we need wineautorun.inf to parse the file autorun.inf or Autorun.inf on CD's If you try to run a non-autorun file it pops up a dialog saying hey this isnt an autorun inf and so I cant do anything with it! The parsing itself shouldnt be too hard, but AFAICT the windows autorun loader only looks for autorun.inf (Case Insensitive) and parses it for the icon and the file to actually run. If we implemented this, it would make things a lot easier for v1.0 because users wouldnt have to learn command line just yet.. Fabian Cenedese <Cenedese(a)indel.ch> wrote: > > If we tweak the registry of a .inf (winedefault.reg), we can ask it to > > launch a tiny program that will open the .inf and run the program > > specified. > >Sounds like it could work, but what about inf installer files (ie TweakUI's >inf, or driver inf files) how would they be handled? Generally, .inf files are all installer files, only the autorun.inf is something special. If the file on the CD is named differently it doesn't work anymore. So we would just have to check for this name. I don't know how it is done on Windows, what makes the auto-insert check. But whatever program gets the insert notification it should call 'wine wineautorun.exe autorun.inf'. Wineautorun.exe will parse the autorun.inf. And all other .inf go to the installer. bye Fabi

Dec. 9, 2002

Re: regression: msvc4.0 install dies sooner now

by Dan Kegel

Dan Kegel wrote: > Dan Kegel wrote: > >> I found an unopened copy of msvc++ 4.0 at a garage sale last year for $5, >> couldn't resist. Today I finally tried to install it under Wine. > > OK, more details. I switched to testing the simplest > function of msvc's setup program: the exit button. > All I do is click on the exit button. (Easy, right?) > It works fine in Wine-20020804, but fails in Wine-20020904 and later. Following http://www.winehq.org/Docs/wine-devel/cvs-regression.shtml I managed to narrow the problem down to between 2002-08-26 and 2002-08-28. I'll narrow it down more when I get a chance. I'm sorely tempted to install http://ccache.samba.org/ or http://distcc.samba.org/ or even http://gecc.sourceforge.net/ as the 25 minutes it takes to do a full rebuild of wine is a bit of an impediment. (Though a big, big improvement from how long it took the first time I tried to build it back in the days of 90 MHz pentiums...) - Dan

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Mike Hearn

The UK. I'm not au fait with the reverse engineering laws here, and I'm not very good at it anyway, so I'd rather avoid it if possible. But once you've seemingly exhausted a trace what do you do next? I can't breakpoint on a call, because the call that would let me get the right part is never called... On Mon, 2002-12-09 at 17:14, Shachar Shemesh wrote: > Mike Hearn wrote: > > >Well, I have about 2 hours now when I can work on trying to get the > >adobe svg plugin to work in Wine. I have a deadline to meet for Friday > >that requires the plugin, so if I can't get it working back to Windows > >it is (it's like a damn magnet). > > > >I've already located a mouse bug (problem with my last patch, oops) and > >fixed it (patch sent), but the lack of render on paint problem still > >eludes me. Having not got a response to the last email, I'll assume it's > >OK to try poking about inside the plugin itself to figure out what's > >going wrong. If anybody has some tips, now would be the time to tell me > >about them :) > > > >I hope this doesn't invalidate any patches I might produce..... > > > > > IIRC, there are some specific laws allowing rev-eng for interoperability > in the EU. Which country are you in? > > Shachar > > > > > -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Shachar Shemesh

Mike Hearn wrote: >Well, I have about 2 hours now when I can work on trying to get the >adobe svg plugin to work in Wine. I have a deadline to meet for Friday >that requires the plugin, so if I can't get it working back to Windows >it is (it's like a damn magnet). > >I've already located a mouse bug (problem with my last patch, oops) and >fixed it (patch sent), but the lack of render on paint problem still >eludes me. Having not got a response to the last email, I'll assume it's >OK to try poking about inside the plugin itself to figure out what's >going wrong. If anybody has some tips, now would be the time to tell me >about them :) > >I hope this doesn't invalidate any patches I might produce..... > > IIRC, there are some specific laws allowing rev-eng for interoperability in the EU. Which country are you in? Shachar > >

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Hetz Ben-Hamo

On 09 Dec 2002 16:58:36 +0000, Mike Hearn wrote > Unfortunately the Mozilla plugin does not work - the Mozilla team pulled > the XPCOM plugin interface it used, and Adobe never updated it. Yeah, I just remembered. The guy from Adobe complained about the XPCom crap in a private email to me back then. > Or what, did you think I ran IE on Linux for the joy of it? ;) I don't know. Wine graphics with explorer is slow and very annoying (just look at a flash plugin running inside Explorer ).. Thanks, Hetz

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Mike Hearn

Unfortunately the Mozilla plugin does not work - the Mozilla team pulled the XPCOM plugin interface it used, and Adobe never updated it. That's probably because only IE offers sufficiently advanced interfaces to perform host scripting merge, ie where the javascript environment of the web page is merged with the javascript in the SVG file: this is a feature we use a lot of. Or what, did you think I ran IE on Linux for the joy of it? ;) By the way, the link to IDA on the tools page is broken, IDA seems to have commercialised. On Mon, 2002-12-09 at 16:49, Hetz Ben-Hamo wrote: > On 09 Dec 2002 16:37:16 +0000, Mike Hearn wrote > > Well, I have about 2 hours now when I can work on trying to get the > > adobe svg plugin to work in Wine. > > Hmm? > > There's already a native plugin for Linux.. > > http://plugindoc.mozdev.org/linux.html#SVG > > Thanks, > Hetz -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Dec. 9, 2002

MSI (MS Installer)

by Scott Cote

I've found that many of the test applications I've tried installing failed due to the lack of MSIEXEC. If it is implemented, could you tell me where to find it? If not, I'd like to contribute, could you tell me if any work has been done and who to coordinate with? Thanks, -Scott

Dec. 9, 2002

Re: Fix my broken WM_MOUSEHOVER patch

by Vincent Béron

Mike Hearn a écrit: > It's not inlined? Evolution seems to insist on wrapping it if I inline > it. Or was there some other problem? The problem is the actual format of the patch. It's not in unified format (cvs diff -u, or add diff -u to .cvsrc). With that format, it'll add some context around the modified lines, so it's easier to understand what's changed. Vincent

Dec. 9, 2002

Re: Fix my broken WM_MOUSEHOVER patch

by Mike Hearn

It's not inlined? Evolution seems to insist on wrapping it if I inline it. Or was there some other problem? On Mon, 2002-12-09 at 16:22, Dimitrie O. Paun wrote: > On December 9, 2002 11:26 am, Mike Hearn wrote: > > Patch is relative to wine root, made with cvs diff, is this right? > > Yes, and no (it's not in the right format). Please read: > > http://www.winehq.org/development/#patches > http://www.winehq.com/hypermail/wine-devel/2002/09/0127.html -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Hetz Ben-Hamo

On 09 Dec 2002 16:37:16 +0000, Mike Hearn wrote > Well, I have about 2 hours now when I can work on trying to get the > adobe svg plugin to work in Wine. Hmm? There's already a native plugin for Linux.. http://plugindoc.mozdev.org/linux.html#SVG Thanks, Hetz

Dec. 9, 2002

[Fwd: A registry editor taking shape ...]

by Dan Kegel

Hey, looks like the Samba guys are doing a registry editor... - Dan -------- Original Message -------- Subject: A registry editor taking shape ... Date: Mon, 9 Dec 2002 01:56:50 -0800 (PST) From: Richard Sharpe <rsharpe(a)richardsharpe.com> To: <samba-technical(a)samba.org> Hi, A registry editor, editreg, is slowly taking shape in Samba-head. The goal is to be able to do things like: - delete keys and values - add keys and values - change keys and values - Change the SIDS/SecDescs applied to keys. - write out the changes tree - create a tree from scratch What would be useful is some thoughts on how the interface should be constructed, as in command-line, or a .reg file of commands, etc. Regards ----- Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com

Dec. 9, 2002

Disassembly of the adobe svg plugin

by Mike Hearn

Well, I have about 2 hours now when I can work on trying to get the adobe svg plugin to work in Wine. I have a deadline to meet for Friday that requires the plugin, so if I can't get it working back to Windows it is (it's like a damn magnet). I've already located a mouse bug (problem with my last patch, oops) and fixed it (patch sent), but the lack of render on paint problem still eludes me. Having not got a response to the last email, I'll assume it's OK to try poking about inside the plugin itself to figure out what's going wrong. If anybody has some tips, now would be the time to tell me about them :) I hope this doesn't invalidate any patches I might produce..... -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Dec. 9, 2002

Re: Fix my broken WM_MOUSEHOVER patch

by Dimitrie O. Paun

On December 9, 2002 11:26 am, Mike Hearn wrote: > Patch is relative to wine root, made with cvs diff, is this right? Yes, and no (it's not in the right format). Please read: http://www.winehq.org/development/#patches http://www.winehq.com/hypermail/wine-devel/2002/09/0127.html -- Dimi.

Dec. 9, 2002

Re: Problem with DOSFS_OpenDevice

by Uwe Bonnes

>>>>> "Gustavo" == Gustavo Junior Alves <alves(a)coslinux.com.br> writes: Gustavo> Hi All, I having problems with raw printing. I receive this Gustavo> message from trace: device open lpt1 not supported (yet) Gustavo> Looking the code, I do not found any support for parallel ports Gustavo> neither on server or dos_fs. I missed something or Gustavo> DOSFS_OpenDevice does not support parallel printers? I seems that DOSFS_OpenDevice does not support parallel printers. Adding such support shouldn't be to hard, look e.g. at wine/msdos/ppdev.c. if you have a program to test. I didn't have such a program. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 9, 2002

Re: wine/dlls/winsock/socket.c: Force SO_REUSEADDR on before bind()/Ignore SO_DONTROUTE

by Martin Wilck

Am Mon, 2002-12-09 um 14.57 schrieb Christoph Frick: > > I'd like to know what remote addresses exactly the apps call bind() for, > > and in what order. Perhaps there are subtle differences in the way > > EADDRINUSE and SO_REUSEADDR are handled. > > I can basically describe you what this games do network-wise and/or i can > provide you with traces (with and without patch) - what do you prefer? What i > can not do is testing in windows. Run with -debugmsg trace+winsock. You may also need to set DEBUG_SOCKADDR to 1 (look for it close to the top of socket.c), and recompile and reinstall the winsock DLL. Oh, and given the "NetTrans" thing below, run with "trace+reg", too. > > However the patch implements the first behavior (ignore) whereas > > the Windows TCP/IP transport behaves as the second (later calls to > > getsockopt() refelect the SO_DONTROUTE settings, which seems to have no > > further effect). > > So closer to windows would be store and ignore. In general i wonder, if > windows does this always or if this depends somehow on the "device" the socket > is finally bound to - or in other words: is always the same code on windows in > charge or could it be that this might be implemened e.g. by a NIC driver. It is the "Service provider" which in this case is Microsoft TCP/IP (think of it as one of the "protocols" Windows allows you to install in the Network settings). Other service providers are IPX, NetBEUI, or Appletalk. Since TCP/IP is pretty important nowadays, if Microsoft TCP/IP ignores SO_DONTROUTE (actually, it seems to ignore the MSG_DONTROUTE flag to send(), too!) it is probably ignored almost everywhere in the MS world. Wine's Winsock implementation is not (yet) modular - it doesn't use service providers. > Why i ask: please see my mail to wine-devel from 2002-10-25; the game also > checks the .../NetTrans/... settings. I am not sure what these are for. They seem to be Win95/98 specific - my Win2k box doesn't have them. It appears that for Win9x there should be one System/Services/Class/NetTrans/000x entry for each installed transport service provider. > Maybe here is something missing that > tell the game to set SO_DONTROUTE. Wine does not set them automatically like > other hardware/driver related stuff. I really can not imagine, why a game > should set this option explicit when it connects to an server (the ip/name is > entered manually in this case, so the game should expect the host not in the > same network). Well, browsing through MSDN, the reason may be past trouble with PCs with several network interfaces, where the game wanted to connect through a dial-up connection rather than through a LAN (or vice-versa). In any case it can't be much more than a hack some games were using to work around some obscure Win9x networking limitation. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

Dec. 9, 2002

Problem with DOSFS_OpenDevice

by Gustavo Junior Alves

Hi All, I having problems with raw printing. I receive this message from trace: device open lpt1 not supported (yet) Looking the code, I do not found any support for parallel ports neither on server or dos_fs. I missed something or DOSFS_OpenDevice does not support parallel printers? Thanks for the help. Gustavo Junior Alves alves(a)coslinux.com.br

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

On December 9, 2002 07:19 am, Patrik Stridvall wrote: > Note that I said LIBRARY. Still running cpp is presumably > more lightweight that running "gcc -E". Based on what?!? Let's see numbers (one dummy, empty file): [dimi(a)dimi dev]$ cat dummy.c [dimi(a)dimi dev]$ time gcc -E dummy.c # 1 "dummy.c" # 1 "<built-in>" # 1 "<command line>" # 1 "dummy.c" real 0m0.010s user 0m0.002s sys 0m0.006s [dimi(a)dimi dev]$ time cpp dummy.c # 1 "dummy.c" # 1 "<built-in>" # 1 "<command line>" # 1 "dummy.c" real 0m0.017s user 0m0.002s sys 0m0.004s That's pretty fast. > I just remember abandoning the idea of using "gcc -E" for preprocessing > in winapi_check because of horrible a speed slowdown. This obviously is just plain wrong. Numbers clearly show this can't be the case. Initializing gcc (and it's gcc 3.2 which is supposedly slower than other gccs) takes 100ms, not that bad, it's certainly not "horrible". -- Dimi.

Dec. 9, 2002