- wine-devel - winehq.org

Conformance tests --MSVC Headers 2 of 2
by Tom 10 Dec '02

10 Dec '02

Build Log --------------------Configuration: ntdll_test - Win32 MSVC Headers-------------------- Command Lines Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2C.tmp" with contents [ /nologo /MTd /W3 /Gm /GX /ZI /Od /I "..\..\..\Output\\Win32_MSVC_Headers" /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_NTDLL_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_MSVC_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR"Output\Win32_MSVC_Headers/" /Fo"Output\Win32_MSVC_Headers/" /Fd"Output\Win32_MSVC_Headers/" /FD /GZ /c "C:\include\wine\dlls\ntdll\tests\error.c" "C:\include\wine\dlls\ntdll\tests\rtlbitmap.c" "C:\include\wine\dlls\ntdll\tests\rtlstr.c" ] Creating command line "cl.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2C.tmp" Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2D.tmp" with contents [ /nologo /subsystem:console /incremental:yes /pdb:"Output\Win32_MSVC_Headers/ntdll_test.pdb" /debug /machine:I386 /out:"Output\Win32_MSVC_Headers/ntdll_test.exe" /pdbtype:sept .\Output\Win32_MSVC_Headers\error.obj .\Output\Win32_MSVC_Headers\generated.obj .\Output\Win32_MSVC_Headers\rtlbitmap.obj .\Output\Win32_MSVC_Headers\rtlstr.obj .\Output\Win32_MSVC_Headers\testlist.obj ] Creating command line "link.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2D.tmp" Output Window Build Log --------------------Configuration: oleaut32_test - Win32 MSVC Headers-------------------- Command Lines Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2E.tmp" with contents [ /nologo /MTd /W3 /Gm /GX /ZI /Od /I "..\..\..\Output\\Win32_MSVC_Headers" /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_OLEAUT32_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_MSVC_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR"Output\Win32_MSVC_Headers/" /Fo"Output\Win32_MSVC_Headers/" /Fd"Output\Win32_MSVC_Headers/" /FD /GZ /c "C:\include\wine\dlls\oleaut32\tests\vartest.c" ] Creating command line "cl.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2E.tmp" Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2F.tmp" with contents [ oleaut32.lib /nologo /subsystem:console /incremental:yes /pdb:"Output\Win32_MSVC_Headers/oleaut32_test.pdb" /debug /machine:I386 /out:"Output\Win32_MSVC_Headers/oleaut32_test.exe" /pdbtype:sept .\Output\Win32_MSVC_Headers\vartest.obj .\Output\Win32_MSVC_Headers\testlist.obj ] Creating command line "link.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2F.tmp" Output Window Build Log --------------------Configuration: ntdll_test - Win32 MSVC Headers-------------------- Command Lines Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2C.tmp" with contents [ /nologo /MTd /W3 /Gm /GX /ZI /Od /I "..\..\..\Output\\Win32_MSVC_Headers" /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_NTDLL_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_MSVC_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR"Output\Win32_MSVC_Headers/" /Fo"Output\Win32_MSVC_Headers/" /Fd"Output\Win32_MSVC_Headers/" /FD /GZ /c "C:\include\wine\dlls\ntdll\tests\error.c" "C:\include\wine\dlls\ntdll\tests\rtlbitmap.c" "C:\include\wine\dlls\ntdll\tests\rtlstr.c" ] Creating command line "cl.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2C.tmp" Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2D.tmp" with contents [ /nologo /subsystem:console /incremental:yes /pdb:"Output\Win32_MSVC_Headers/ntdll_test.pdb" /debug /machine:I386 /out:"Output\Win32_MSVC_Headers/ntdll_test.exe" /pdbtype:sept .\Output\Win32_MSVC_Headers\error.obj .\Output\Win32_MSVC_Headers\generated.obj .\Output\Win32_MSVC_Headers\rtlbitmap.obj .\Output\Win32_MSVC_Headers\rtlstr.obj .\Output\Win32_MSVC_Headers\testlist.obj ] Creating command line "link.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP2D.tmp" Output Window

1 0

what to do with include/wine/obj_base.h?
by Ove Kaaven 10 Dec '02

10 Dec '02

I've submitted a patch to move the API prototypes out of obj_base.h, and I'd now be ready to submit unknwn.idl and unknwn.h, which would also supersede the interfaces defined in there, but I'm unsure about what to do with the remainder of it, namely the ICOM_* macros in there. Note that there's a shortcoming of those macros, they don't handle array arguments. Such arguments are binary-compatible with pointer arguments though, so it's not a serious shortcoming for Wine and widl (which could easily convert array args in IDL to pointer args in C), but it's a little ugly and may have source-compatibility issues if widl is used by Winelib code that implements interfaces with such method args. There are standard COM interfaces with this problem too, e.g. IPropertyStorage, but since such interfaces are implemented by Wine and not by app code, there's unlikely to be source-compatibility issues there. So the options include 1) keep using obj_base.h as it is, let widl use those macros as is (and convert array args to pointer args), include it into unknwn.h 2) move ICOM macros to include/objbase.h, and dispose of obj_base.h 3) make widl use the MS-style macros in objbase.h (but I'm not sure what to do about ICOM_MSVTABLE_COMPAT and ICOM_USE_COM_INTERFACE_ATTRIBUTE in this case) 4) make widl not use macros at all, but emit full C and C++ definitions directly (this is what midl.exe does, it seems) 5) make widl support any of the above with a command-line option, so that Wine headers uses 1 or 2, while Winelib apps get to use 3 or 4. 6) redesign the ICOM macros (but I doubt anyone's going to volunteer for that unless tied to a chair supervised by an ancient master of torture with a cat-o'-nine-tails in his toolbox, there's too much code to change)

4 5

Re: wine/dlls/winsock/socket.c: Force SO_REUSEADDR ...
by Martin Wilck 10 Dec '02

10 Dec '02

Hi, judging from the Traces these programs are rare examples of lame network programming. You find series of things that shouldn't be done, such as bind()ing in a client application, not closing down a socket cleanly but expecting the next bind() to the same address to succeed, polling the socket with ioctl (FIONREAD), etc. I am really asking myself if it's right to hack wine to violate the specs just for the sake of so poorly programmed applications. I'd be grateful for advice by experienced Wine hackers here. Perhaps we need to introduce Windows version-dependent behavior. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 1

Re: Janitorial Projects -- conformance tests --recruiting volunteers
by David Miller 10 Dec '02

10 Dec '02

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?

7 12

Re: strcat+strcat+strcat == baaad"
by Jeff Smith 10 Dec '02

10 Dec '02

You caught me... I thought something like this existed. I would say that by default, Auto should be 0. I think this would be best for the average user. They are probably even less likely than me to read the debugging documentation (and want to change a registry setting like this). -- Jeff S >From: Eric Pouech <eric.pouech(a)wanadoo.fr> > >>Can we do something like throw up a message box before loading the >>debugger, >>asking if we want to debug? Or perhaps there should be a command-line >>option to >>the debugger that presents said dialog, then use that option when starting >>the >>debugger in the event of an crash. >RTFM >hints: AeDebug, Auto >A+ _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

1 0

Re: strcat+strcat+strcat == baaad"
by Jeff Smith 10 Dec '02

10 Dec '02

>From: vkxzjq6lg(a)cswebmail.com > >Francois Gouget wrote: > > > Of course, that implies that we should promptly fix any such crash. > > Otherwise it just makes Wine unusable without any benefit. > >That's the catch. I'm not approaching Wine as a Wine developer. Wine is >almost ready for >prime time now and as a non-Wine developer (who's roped in so far only as >far as necessary >to get the app I want to run running) I'm approaching it as a near >production system. > >When only hard core Wine developers were seeing it, opening the debugger >made sense. > >Wine is leaving the core development stage and now it's time to be >arranging for bug >reporting mechanisms which don't require that you be a programmer willing >to start >debugging Wine to get your applications running. > >That means avoiding a raw debugger window and providing something more end >user friendly. >To me that means something like logging every non-dangerous failure >possible rather than >killing the application. Then, when the application finishes, winseerver >can pop up a >polite window telling the user that there was a problem and asking them to >report it to >the developers, making it easy to do that. > >It definitely doesn't involve opening debugger windows. Those will scare >away the end >users who need to be submitting those logs so the developers can see which >app or internal >routine was breaking the rules and what needs to be fixed. > >So: Wine's almost there (and congratulations on getting to the point where >I can seriously >write that!). Time to be thinking about what end users can handle and >changing how garbage >data reporting is handled to make it more friendly to them. Can we do something like throw up a message box before loading the debugger, asking if we want to debug? Or perhaps there should be a command-line option to the debugger that presents said dialog, then use that option when starting the debugger in the event of an crash. Perhaps this can be combined with some of the other ideas to create a reasonable user experience during a failure. -- Jeff S _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

3 2

WinXP Professional conformance test results
by David Miller 10 Dec '02

10 Dec '02

These tests were completed individually on WinXP Pro using the binaries from here: http://fgouget.free.fr/wine/winetests.zip C:\winetests>advapi32_test.exe registry 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 to 24 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. C:\winetests>kernel32_test.exe alloc alloc: 58 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe atom atom: 229398 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe codepage codepage: 2 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe directory directory: 48 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe drive drive: 158 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe environ environ: 39 tests executed, 0 marked as todo, 0 failures. C:\winetests>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:\winetests>kernel32_test.exe format_msg format_msg: 58 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe locale locale: 54 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe path h:\wine\wine\dlls\kernel\tests\path.c:517: Test failed: GetLongPathNameA: wrong return code, 104 instead of 44 h:\wine\wine\dlls\kernel\tests\path.c:927:TMP=C:\DOCUME~1\ADMINI~1\LOCALS~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:\winetests>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:lpDesktp expected (null), got WinSta0\Default h:\wine\wine\dlls\kernel\tests\process.c:375: Test failed: StartupInfoA:lpTitle expected (null), got C:\winetests\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:lpDesktp 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:\winetests\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:\winetests>kernel32_test.exe thread thread: 112 tests executed, 0 marked as todo, 0 failures. msvcrt_test.exe msvcrt <-- crashes C:\winetests> C:\winetests>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:\winetests>netapi32_test.exe apibuf apibuf: 15 tests executed, 0 marked as todo, 0 failures. C:\winetests>netapi32_test.exe wksta wksta: 14 tests executed, 0 marked as todo, 0 failures. C:\winetests>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:\winetests>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:\winetests>shell32_test.exe shlfileop h:\wine\wine\dlls\shell32\tests\shlfileop.c:286: Test failed: Files are copied t o 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:\winetests>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:\winetests>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:263: Test failed: didn't open copy (test didn't complete in 10 min, I ctrl-C out at this point) C:\winetests>user32_test.exe class class: 80 tests executed, 0 marked as todo, 0 failures. C:\winetests>user32_test.exe win h:\wine\wine\dlls\user\tests\win.c:91:main window 001F0080 main2 00220110 desktop 00010014 child 000B00F4 h:\wine\wine\dlls\user\tests\win.c:107:created child 001E00F6 h:\wine\wine\dlls\user\tests\win.c:120:created child of desktop 001F00F6 h:\wine\wine\dlls\user\tests\win.c:130:created child of child 002000F6 h:\wine\wine\dlls\user\tests\win.c:140:created top-level 002100F6 h:\wine\wine\dlls\user\tests\win.c:150:created owned top-level 002200F6 h:\wine\wine\dlls\user\tests\win.c:160:created popup 002300F6 h:\wine\wine\dlls\user\tests\win.c:170:created owned popup 002400F6 h:\wine\wine\dlls\user\tests\win.c:180:created top-level owned by child 002500F6 h:\wine\wine\dlls\user\tests\win.c:186:created popup owned by desktop 002600F6 h:\wine\wine\dlls\user\tests\win.c:192:created popup owned by child 002700F6 h:\wine\wine\dlls\user\tests\win.c:198:created WS_CHILD popup 002800F6 h:\wine\wine\dlls\user\tests\win.c:204:created owned WS_CHILD popup 002900F6 h:\wine\wine\dlls\user\tests\win.c:209:testing parent changes h:\wine\wine\dlls\user\tests\win.c:221:created child 002A00F6 h:\wine\wine\dlls\user\tests\win.c:247:created top-level 002B00F6 h:\wine\wine\dlls\user\tests\win.c:264:created popup 002C00F6 h:\wine\wine\dlls\user\tests\win.c:281:created child 002D00F6 h:\wine\wine\dlls\user\tests\win.c:298:created top-level 002E00F6 h:\wine\wine\dlls\user\tests\win.c:307:created owned popup 002F00F6 h:\wine\wine\dlls\user\tests\win.c:323:created owner 003000F6 and popup 001600CE h:\wine\wine\dlls\user\tests\win.c:337:created owner 001700CE and popup 003100F6 h:\wine\wine\dlls\user\tests\win.c:345:created owner 001800CE and popup 003200F6 win: 373 tests executed, 0 marked as todo, 0 failures. C:\winetests>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 INTERNET_STATUS_RESOLVING_NAME(10) 0102FB04 15 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_NAME_RESOLVED(11) 0102FAF4 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTING_TO_SERVER(20) 0102FB9C 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTED_TO_SERVER(21) 0102FD40 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) 0102FCE0 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) 0102FD64 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_COMPLETE(100) 0102FDA8 8 h:\wine\wine\dlls\wininet\tests\http.c:140:Option 0x17 -> 1 0 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: Tue, 10 Dec 2002 05:27:22 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 3348 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) 0102FDA8 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) 0012EC30 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 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 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) 0012EB14 4 h:\wine\wine\dlls\wininet\tests\http.c:133:HttpSendRequestA <-- h:\wine\wine\dlls\wininet\tests\http.c:140:Option 0x17 -> 1 0 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: Tue, 10 Dec 2002 05:27:23 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 3348 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 3760 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 620 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1974 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: 24 tests executed, 0 marked as todo, 1 failure. C:\winetests>winmm_test.exe wave h:\wine\wine\dlls\winmm\tests\wave.c:56:found 1 WaveOut devices h:\wine\wine\dlls\winmm\tests\wave.c:82: 0: "Sound Blaster AWE64" 5.10 (1:100): channels=65535 formats=bffff support=002c h:\wine\wine\dlls\winmm\tests\wave.c:133:Testing invalid 2MHz format wave: 53 tests executed, 0 marked as todo, 0 failures C:\winetests>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 (6e0) starting h:\wine\wine\dlls\winsock\tests\sock.c:341:simple_server (6e0) ready h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (6e0): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:391:simple_client (728): starting h:\wine\wine\dlls\winsock\tests\sock.c:394:simple_client (728): server ready h:\wine\wine\dlls\winsock\tests\sock.c:391:simple_client (724): starting h:\wine\wine\dlls\winsock\tests\sock.c:394:simple_client (724): server ready h:\wine\wine\dlls\winsock\tests\sock.c:406:simple_client (728) connected h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (6e0): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:406:simple_client (724) connected h:\wine\wine\dlls\winsock\tests\sock.c:374:simple_server (6e0) exiting h:\wine\wine\dlls\winsock\tests\sock.c:427:simple_client (728) exiting h:\wine\wine\dlls\winsock\tests\sock.c:427:simple_client (724) 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 (748) starting h:\wine\wine\dlls\winsock\tests\sock.c:341:simple_server (748) ready h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (748): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:445:event_client (604): starting h:\wine\wine\dlls\winsock\tests\sock.c:445:event_client (750): starting h:\wine\wine\dlls\winsock\tests\sock.c:447:event_client (604): server ready h:\wine\wine\dlls\winsock\tests\sock.c:467:event_client (604) connected h:\wine\wine\dlls\winsock\tests\sock.c:505:event_client (604): all data sent - shutdown h:\wine\wine\dlls\winsock\tests\sock.c:346:simple_server (748): waiting for client h:\wine\wine\dlls\winsock\tests\sock.c:526:event_client (604): all data received h:\wine\wine\dlls\winsock\tests\sock.c:538:event_client (604): close event h:\wine\wine\dlls\winsock\tests\sock.c:556:event_client (604) exiting h:\wine\wine\dlls\winsock\tests\sock.c:447:event_client (750): server ready h:\wine\wine\dlls\winsock\tests\sock.c:467:event_client (750) connected h:\wine\wine\dlls\winsock\tests\sock.c:505:event_client (750): all data sent - shutdown h:\wine\wine\dlls\winsock\tests\sock.c:374:simple_server (748) exiting h:\wine\wine\dlls\winsock\tests\sock.c:526:event_client (750): all data received h:\wine\wine\dlls\winsock\tests\sock.c:538:event_client (750): close event h:\wine\wine\dlls\winsock\tests\sock.c:556:event_client (750) exiting h:\wine\wine\dlls\winsock\tests\sock.c:696: **** TEST 1 COMPLETE **** sock: 128 tests executed, 0 marked as todo, 0 failures. C:\winetests>user32_test.exe sysparams h:\wine\wine\dlls\user\tests\sysparams.c:184:testing SPI_{GET,SET}BEEP h:\wine\wine\dlls\user\tests\sysparams.c:306:testing SPI_{GET,SET}MOUSE h:\wine\wine\dlls\user\tests\sysparams.c:374:testing SPI_{GET,SET}BORDER h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=1, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=0, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=7, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=20, value= h:\wine\wine\dlls\user\tests\sysparams.c:406:testing SPI_{GET,SET}KEYBOARDSPEED h:\wine\wine\dlls\user\tests\sysparams.c:440:testing SPI_ICONHORIZONTALSPACING h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconSpacing, testValue=101, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconSpacing, testValue=32, value= h:\wine\wine\dlls\user\tests\sysparams.c:480:testing SPI_{GET,SET}SCREENSAVETIMEOUT h:\wine\wine\dlls\user\tests\sysparams.c:515:testing SPI_{GET,SET}SCREENSAVEACTIVE h:\wine\wine\dlls\user\tests\sysparams.c:555:testing SPI_{GET,SET}KEYBOARDDELAY h:\wine\wine\dlls\user\tests\sysparams.c:590:testing SPI_ICONVERTICALSPACING h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconVerticalSpacing, testValue=101, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconVerticalSpacing, testValue=32, value= h:\wine\wine\dlls\user\tests\sysparams.c:635:testing SPI_{GET,SET}ICONTITLEWRAP h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconTitleWrap, testValue=1, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconTitleWrap, testValue=0, value= h:\wine\wine\dlls\user\tests\sysparams.c:670:testing SPI_{GET,SET}MENUDROPALIGNMENT h:\wine\wine\dlls\user\tests\sysparams.c:707:testing SPI_SETDOUBLECLKWIDTH h:\wine\wine\dlls\user\tests\sysparams.c:738:testing SPI_SETDOUBLECLKHEIGHT h:\wine\wine\dlls\user\tests\sysparams.c:770:testing SPI_SETDOUBLECLICKTIME h:\wine\wine\dlls\user\tests\sysparams.c:817:testing SPI_SETMOUSEBUTTONSWAP h:\wine\wine\dlls\user\tests\sysparams.c:880:testing SPI_{GET,SET}DRAGFULLWINDOWS h:\wine\wine\dlls\user\tests\sysparams.c:915:testing SPI_{GET,SET}WORKAREA h:\wine\wine\dlls\user\tests\sysparams.c:953:testing SPI_{GET,SET}SHOWSOUNDS h:\wine\wine\dlls\user\tests\sysparams.c:997:testing SPI_{GET,SET}DESKWALLPAPER sysparams: 318 tests executed, 0 marked as todo, 10 failures.

1 0

Re: strcat+strcat+strcat == baaad"
by vkxzjq6lg＠cswebmail.com 10 Dec '02

10 Dec '02

"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/

3 2

[Fwd: A registry editor taking shape ...]
by Dan Kegel 10 Dec '02

10 Dec '02

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

2 1

Import Lib patche
by Steven Edwards 10 Dec '02

10 Dec '02

Hola, Just wondering if you were still doing the import lib stuff. I saw in a past message that you had some patches outstanding and assumed import lib patch is one of them. I think this is the only thing holding up being able to compile all of the regression tests under windows via Mingw. Thanks Steven __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

1 0

wpp
by Dimitrie O. Paun 10 Dec '02

10 Dec '02

Folks, Anyone remembers why we need our own cpp implementation, instead of simply using cpp/gcc -E? -- Dimi.

5 11

Windows XP Conformance Test results...
by Kye Lewis 10 Dec '02

10 Dec '02

Hi, My Results using the batch file and Windows XP. If you need any more information about msvcrt_test crash, just ask. My desktop also becomes smaller after running user32_test sysparams, the approximate time of this is marked below in the appropriate section. These results are obtained with Windows XP Home ==== advapi32_test ==== 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. ==== kernel32_test ==== alloc: 58 tests executed, 0 marked as todo, 0 failures. atom: 229398 tests executed, 0 marked as todo, 0 failures. codepage: 2 tests executed, 0 marked as todo, 0 failures. directory: 48 tests executed, 0 marked as todo, 0 failures. drive: 156 tests executed, 0 marked as todo, 0 failures. environ: 39 tests executed, 0 marked as todo, 0 failures. 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. format_msg: 58 tests executed, 0 marked as todo, 0 failures. generated: 609 tests executed, 0 marked as todo, 0 failures. locale: 54 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\kernel\tests\path.c:927:TMP=C:\WINDOWS\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, 3 failures. 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:\DOCUME~1\Owner\DESKTOP\WINETE~1\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:\DOCUME~1\Owner\DESKTOP\WINETE~1\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. thread: 112 tests executed, 0 marked as todo, 0 failures. ==== msvcrt_test ==== Fails to run (msvcrt_test.exe has encountered a problem and needs to close. We are sorry for the inconvenience) Debug Shows Unhandled exception in msvcrt_test.exe (NTDLL.DLL): 0xC0000005: Access Violation More information available if required ==== netapi32_test ==== h:\wine\wine\dlls\netapi32\tests\access.c:95: Test failed: Bad Network Path access: 23 tests executed, 0 marked as todo, 1 failure. apibuf: 15 tests executed, 0 marked as todo, 0 failures. wksta: 14 tests executed, 0 marked as todo, 0 failures. ==== rpcrt4_test ==== h:\wine\wine\dlls\rpcrt4\tests\rpc.c:124: ** Uuid Conversion and Comparison Tests ** rpc: 901 tests executed, 0 marked as todo, 0 failures. ==== shell32_test ==== generated: 272 tests executed, 0 marked as todo, 0 failures. 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. ==== shlwapi_test ==== 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. generated: 19 tests executed, 0 marked as todo, 0 failures. 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. ==== user32_test ==== class: 80 tests executed, 0 marked as todo, 0 failures. generated: 1524 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\user\tests\sysparams.c:184:testing SPI_{GET,SET}BEEP h:\wine\wine\dlls\user\tests\sysparams.c:306:testing SPI_{GET,SET}MOUSE h:\wine\wine\dlls\user\tests\sysparams.c:374:testing SPI_{GET,SET}BORDER h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=1, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=0, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=7, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=BorderWidth, testValue=20, value= h:\wine\wine\dlls\user\tests\sysparams.c:406:testing SPI_{GET,SET}KEYBOARDSPEED h:\wine\wine\dlls\user\tests\sysparams.c:440:testing SPI_ICONHORIZONTALSPACING h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconSpacing, testValue=101, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconSpacing, testValue=32, value= h:\wine\wine\dlls\user\tests\sysparams.c:480:testing SPI_{GET,SET}SCREENSAVETIMEOUT h:\wine\wine\dlls\user\tests\sysparams.c:515:testing SPI_{GET,SET}SCREENSAVEACTIVE h:\wine\wine\dlls\user\tests\sysparams.c:555:testing SPI_{GET,SET}KEYBOARDDELAY h:\wine\wine\dlls\user\tests\sysparams.c:590:testing SPI_ICONVERTICALSPACING h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconVerticalSpacing, testValue=101, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconVerticalSpacing, testValue=32, value= h:\wine\wine\dlls\user\tests\sysparams.c:635:testing SPI_{GET,SET}ICONTITLEWRAP h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconTitleWrap, testValue=1, value= h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value in registry: subKey=Control Panel\Desktop, valName=IconTitleWrap, testValue=0, value= h:\wine\wine\dlls\user\tests\sysparams.c:670:testing SPI_{GET,SET}MENUDROPALIGNMENT h:\wine\wine\dlls\user\tests\sysparams.c:707:testing SPI_SETDOUBLECLKWIDTH h:\wine\wine\dlls\user\tests\sysparams.c:738:testing SPI_SETDOUBLECLKHEIGHT h:\wine\wine\dlls\user\tests\sysparams.c:770:testing SPI_SETDOUBLECLICKTIME h:\wine\wine\dlls\user\tests\sysparams.c:817:testing SPI_SETMOUSEBUTTONSWAP // Desktop Resizes somewhere between here: h:\wine\wine\dlls\user\tests\sysparams.c:880:testing SPI_{GET,SET}DRAGFULLWINDOWS h:\wine\wine\dlls\user\tests\sysparams.c:915:testing SPI_{GET,SET}WORKAREA And Here // h:\wine\wine\dlls\user\tests\sysparams.c:953:testing SPI_{GET,SET}SHOWSOUNDS h:\wine\wine\dlls\user\tests\sysparams.c:997:testing SPI_{GET,SET}DESKWALLPAPER sysparams: 318 tests executed, 0 marked as todo, 10 failures. win: 373 tests executed, 0 marked as todo, 0 failures. wsprintf: 4 tests executed, 0 marked as todo, 0 failures. ==== wininet_test ==== generated: 252 tests executed, 0 marked as todo, 0 failures. 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 INTERNET_STATUS_RESOLVING_NAME(10) 00D6FB04 15 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_NAME_RESOLVED(11) 00D6FAF4 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTING_TO_SERVER(20) 00D6FB9C 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTED_TO_SERVER(21) 00D6FD40 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) 00D6FCE0 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) 00D6FD60 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_COMPLETE(100) 00D6FDA8 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.0 200 OK Date: Mon, 09 Dec 2002 22:47:48 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 Content-Type: text/html X-Cache: MISS from cache.net2000.com.au Connection: close 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 773 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 465 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) 00D6FDA8 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) 0012EC30 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 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 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.0 200 OK Date: Mon, 09 Dec 2002 22:47:49 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 Content-Type: text/html X-Cache: MISS from cache.net2000.com.au Connection: close 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 773 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 465 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 447 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) 0012EC30 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4 http: 28 tests executed, 0 marked as todo, 1 failure. ==== winmm_test ==== h:\wine\wine\dlls\winmm\tests\wave.c:56:found 1 WaveOut devices h:\wine\wine\dlls\winmm\tests\wave.c:82: 0: "SB Live! Wave Device" 5.10 (1:100): channels=65535 formats=bffff support=002c h:\wine\wine\dlls\winmm\tests\wave.c:133:Testing invalid 2MHz format wave: 53 tests executed, 0 marked as todo, 0 failures. ==== ws2_32_test ==== sock: 128 tests executed, 0 marked as todo, 0 failures.

1 0

Re: strcat+strcat+strcat == baaad"
by vkxzjq6lg＠cswebmail.com 10 Dec '02

10 Dec '02

Francois Gouget wrote: > Of course, that implies that we should promptly fix any such crash. > Otherwise it just makes Wine unusable without any benefit. That's the catch. I'm not approaching Wine as a Wine developer. Wine is almost ready for prime time now and as a non-Wine developer (who's roped in so far only as far as necessary to get the app I want to run running) I'm approaching it as a near production system. When only hard core Wine developers were seeing it, opening the debugger made sense. Wine is leaving the core development stage and now it's time to be arranging for bug reporting mechanisms which don't require that you be a programmer willing to start debugging Wine to get your applications running. That means avoiding a raw debugger window and providing something more end user friendly. To me that means something like logging every non-dangerous failure possible rather than killing the application. Then, when the application finishes, winseerver can pop up a polite window telling the user that there was a problem and asking them to report it to the developers, making it easy to do that. It definitely doesn't involve opening debugger windows. Those will scare away the end users who need to be submitting those logs so the developers can see which app or internal routine was breaking the rules and what needs to be fixed. So: Wine's almost there (and congratulations on getting to the point where I can seriously write that!). Time to be thinking about what end users can handle and changing how garbage data reporting is handled to make it more friendly to them. ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/

2 1

DOSMEM_Init VirtualProtect fails
by vkxzjq6lg＠cswebmail.com 10 Dec '02

10 Dec '02

To further my porting work, I've patched my copy of DOSMEM.C like this: else if (dos_init && !already_mapped) { if (DOSMEM_dosmem) { ERR( "Needs access to the first megabyte for DOS mode\n" ); ExitProcess(1); } MESSAGE( "Warning: unprotecting the first 64KB of memory to allow real-mode calls.\n" " NULL pointer accesses will no longer be caught.\n" ); /* James Day added the if/FIXME/return false around this VirtualProtect because OzWin on my AMD K6-3 gave this result: wine --debugmsg +dosmem ozwin2 fixme:toolhelp:InterruptRegister16 (0000, 0x26f00ba), stub. Warning: unprotecting the first 64KB of memory to allow real-mode calls. NULL pointer accesses will no longer be caught. fixme:dosmem:DOSMEM_Init Failed to unprotect first 64KB of memory. init=1, done=1, mapped=0 fixme:toolhelp:InterruptUnRegister16 (0000), stub. */ if ( ! VirtualProtect( NULL, 0x10000, PAGE_EXECUTE_READWRITE, NULL ) ) { FIXME("Failed to unprotect first 64KB of memory. init=%d, done=%d, mapped=%d\n", (int)dos_init, already_done, already_mapped); return FALSE; } /* copy the BIOS and ISR area down */ memcpy( DOSMEM_dosmem, DOSMEM_sysmem, 0x400 + 0x100 ); NtProtectVirtualMemory is returning STATUS_INVALID_PARAMETER to VirtualProtectEx and DOSMEM_Init wasn't handling this failure gracefully - the memcpy was tripping the debugger and falling flat, taking the application with it. Anyone got any better ideas? Want more information on what's happening, like which of the STATUS_INVALID_PARAMETER cases is happening? Lindows 3.0 OS (Debian plus bits), Wine 20021125 compiled here with only this change. Not running as root. 128MB of RAM. ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/

1 0

How to find out if file is loaded?
by Klaus Niederkrueger 09 Dec '02

09 Dec '02

Hello, I would like to know the following: I start some program with "wine -debugmsg +file" and I get quite a lot of times trace:file:CreateFileW L"tiles\\TS01.bmp" GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE OPEN_EXISTING attributes 0x80 trace:file:CreateFileW returning 0x58 trace:file:_lopen ('tiles\TS01.BMP',0000) trace:file:CreateFileW L"tiles\\TS01.BMP" GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE OPEN_EXISTING attributes 0x0 trace:file:CreateFileW returning 0x58 trace:file:ReadFile 0x58 0x406d2690 14 0x406d264c (nil) trace:file:ReadFile 0x58 0x406d2668 40 0x406d264c (nil) trace:file:ReadFile 0x58 0x406d26a4 1024 0x406d264c (nil) trace:file:_lclose handle 88 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? Thanks for any answer Klaus

2 2

Re: strcat+strcat+strcat == baaad
by Morten Welinder 09 Dec '02

09 Dec '02

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, both of which are little good for efficiency. More like something along these lines: char *tmpdst = dst; strcpy (tmpdst, src1); tmpdst += strlen (src1); strcpy (tmpdst, src2); tmpdst += strlen (src2); strcpy (tmpdst, src3); tmpdst += strlen (src3); ... strcpy (tmpdst, srcN); tmpdst += strlen (srcN); ... This works even better when the strlen calls have known results. Of course, nothing keeps the compiler from noticing a certain pattern of sprintf calls can producing an equaivalent of the above, but right now gcc will not do that if I recall correctly. Morten

2 1

Non latin fonts and non local fonts
by Shachar Shemesh 09 Dec '02

09 Dec '02

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

2 1

Re: strcat+strcat+strcat == baaad
by Alexandre Julliard 09 Dec '02

09 Dec '02

Francois Gouget <fgouget(a)free.fr> writes: > I don't like pieces of code that go: > > strcpy(foo, bar1); > strcat(foo, bar2); > strcat(foo, bar3); > strcat(foo, bar4); > strcat(foo, bar5); > strcat(foo, bar6); > > It's really inefficient: the cost increases quadratically with the size > of the resulting string. Well, no, the cost is linear. It would only be quadratic if the number of strcat calls depended on the length of the string. > It's more efficient to do: > > sprintf(foo, "%s%s%s%s%s%s", bar1,bar2,bar3,bar4,bar5,bar6); I seriously doubt that sprintf would be faster that a couple of strcats. And I don't think we need to worry about this kind of micro-optimizations right now... -- Alexandre Julliard julliard(a)winehq.com

10 26

Wine startup problem
by Leonardo Giordani 09 Dec '02

09 Dec '02

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

3 3

Disassembly of the adobe svg plugin
by Mike Hearn 09 Dec '02

09 Dec '02

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

4 6

Turkish keyboard Support
by Armish 09 Dec '02

09 Dec '02

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

2 1

Re: Turkish keyboard Support
by Jeff Smith 09 Dec '02

09 Dec '02

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

1 0

POSE (Palm OS Emulator) on WINE?
by Bodo Wenzel 09 Dec '02

09 Dec '02

Hi list. Because Sony doesn't provide a Unix source code branch, I tried to run their Windows based POSE on WINE. At first glance it runs, but only until a command of the context menu is chosen. WINE reports an "unhandled exception" and launches the debugger. My question: does anyone heard about how to make POSE run on WINE? Is anyone interested in making them work together? Both are Open Source... Unfortunately I can't because of my lack of time :-( TIA, Bodo

2 2

Re: Fix the winmm/wave tests
by Alexandre Julliard 09 Dec '02

09 Dec '02

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 -- Alexandre Julliard julliard(a)winehq.com

2 1

Question about STRICT
by Vincent Béron 09 Dec '02

09 Dec '02

I was compiling the tests on MSVC (hence my patch), and the gdi32test wouldn't compile with the Wine headers (but would with MSVC's). The problem can be traced back to the absence of STRICT in windef.h. With the closure of bug #90 (compilation with -DSTRICT), I think it would make sense to define it in a header (windef.h seems logical), with an ifdef NO_STRICT provision (see the attached proposed patch). This would allow to remove all -DSTRICT on compilation command lines. I await your comments on it. Vincent --- wine-20021206-1700/include/windef.h 2002-10-23 20:47:38.000000000 -0400 +++ wine-20021206-1700/include/windef.h 2002-12-07 16:34:02.000000000 -0500 @@ -28,6 +28,12 @@ #ifndef WINVER #define WINVER 0x0500 #endif + +#ifndef NO_STRICT +#ifndef STRICT +#define STRICT +#endif /* STRICT */ +#endif /* NO_STRICT */ #include "winnt.h"

2 1

Fw: Loading Autorun.inf on CD's
by Dustin Navea 09 Dec '02

09 Dec '02

----- Original Message ----- From: "Sylvain Petreolle" <spetreolle(a)yahoo.fr> To: "Tony Lambregts" <tony_lambregts(a)telusplanet.net>; "Dustin Navea" <speeddymon(a)sbcglobal.net> Cc: "Sylvain Petreolle" <spetreolle(a)yahoo.fr>; "Wine Developers" <wine-devel(a)winehq.com> Sent: Sunday, December 08, 2002 5:11 AM Subject: Re: Loading Autorun.inf on CD's > If you want act in this way, I have something for you. > This could help Paul Jones, who is searching how to "launch" *.msi > installers. interesting > The better way we can handle this is a program who tries to open every > document we give to it. A freeware utility exists in cygwin world and > is called cygstart, using the existing registry. If we give it a .doc, > it looks in HKCR and starts Worpad/Winword. > That is a definite must.. > 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? > > I have not seen this work either and definitely not with an .inf. Yes > > it > > would be cool and if you want to start a bug concerning it feel free. > > I > > am not that worried about it though. The way I see it is that most of > > > > this is not realy a wine problem but rather with setting up autorun > > so > > that it is able to understand what to do with an .inf file. I suppose > > > > another way to look at it might be that wcmd could/should be able to > > handle something like "wcmd autorun.inf". > > -Dustin

2 2

regression: msvc4.0 install dies sooner now
by Dan Kegel 09 Dec '02

09 Dec '02

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. wine-20020605-2 (rh8): installer started; when I clicked on 'Install Visual C++', it put up a 'Installing... please wait' dialog, then failed with a 'Can't read version info from C:\windows\kernel386.drv' message (more or less), then hung. wine-20021125 (from source): installer started; when I clicked on 'Install Visual C++', it hung. Looks like a regression to me. Logs of --debugmsg +relay are up at http://www.kegel.com/msvc4setup-wine20020605.log.bz2 http://www.kegel.com/msvc4setup-wine20021125.log.bz2 The latter file is 28MB uncompressed, 512KB compressed. I'm now building the intermediate releases of wine to see if I can narrow down when the regression occurred. - Dan

4 6

Re: Fix my broken WM_MOUSEHOVER patch
by Dimitrie O. Paun 09 Dec '02

09 Dec '02

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.

3 2

Problem with DOSFS_OpenDevice
by Gustavo Junior Alves 09 Dec '02

09 Dec '02

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

2 1

Re: wine/dlls/winsock socket.c
by Martin Wilck 09 Dec '02

09 Dec '02

Am Sam, 2002-12-07 um 00.19 schrieb Alexandre Julliard: > Christoph Frick <frick(a)SC-Networks.de> > Force (WS_)SO_REUSEADDR before binding to a socket; Sorry, this is definitely wrong. Windows, just as Unix, returns WSAEADDRINUSE if SO_REUSEADDR isn't set (just tried it on W2k). There must be some special circumstances involved in those games the patch is supposed to fix. Perhaps they assume a certain Winsock implementation or Windows version. 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. > ignore (WS_)SO_DONTROUTE; Network games in Grand Prix Legends and Nascar 2002 > are possible now. Footnote (i) in http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/wi… says that this is - in principle - legal: "A service provider may silently ignore this option on WSPSetSockOpt and return a constant value for WSPGetSockOpt, or it may accept a value for WSPSetSockOpt and return the corresponding value in WSPGetSockOpt without using the value in any way." 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). > Patch: http://cvs.winehq.com/patch.py?id=6523 Alexandre, please back this patch out for now, at least the SO_REUSEADDR part which is plain wrong. Please don't get me wrong: These issues need to be fixed, but please, not by applying hackish patches for special applications such as this one. Christoph: sorry I missed out on your previous mails to wine-devel. Next time, say something about sockets in the subject line and chances are I won't miss them again. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 2

RE: wpp
by Patrik Stridvall 09 Dec '02

09 Dec '02

> On December 8, 2002 06:01 pm, Patrik Stridvall wrote: > > It would be very nice it something made a GNU C compiler > > library to support among other things only running > > the preprocessor. > > Um, you mean like "cpp"? The debian packagers have even split > it out from > the gcc package for convenience, the package description explains; > > --------- > [snip] > The GNU C preprocessor is a macro processor that is used > automatically by > the GNU C compiler to transform programs before actual compilation. > > This package has been separated from gcc for the benefit of those who > require the preprocessor but not the compiler. > [snip] > --------- > > so clearly it can be done, and this is presumably for the > reasons Dimitrie > mentioned - preprocessing can be a useful (and much faster) subset to > separate out from the compilation process. Note that I said LIBRARY. Still running cpp is presumably more lightweight that running "gcc -E". > But as for the GPL argument against using the GNU C > (pre)compiler from a > run-time (ie. "forking/exec of 'gcc -E' is like linking to a > GPL lib"), I > find that rather hard to believe - especially as invoking > "gcc -E" can be > framed in very user-supplied terms. Eg. if the user is able to (in > theory) configure the program to exec() any precompilation > programs (and > command-line options) they want, then who is going to sue > *who* when the > default value for that setting just happens to be "gcc -E" when the > program installs? Exactly, as I said, it would never fly in court. However that doesn't mean that the FSF doesn't claim it never the less: http://www.fsf.org/licenses/gpl-faq.html#GPLInProprietarySystem > Richard Stallman will sue Redhat? Or will > the FSF begin > a crackdown against adolescent nerds who illegally point > GPL-incompatible > configuration files to GPL-licensed precompilers ...? I really don't > think this should be a cause for concern. No, I don't think it would be a cause for concern either. Still, as I said, that is what they claim. Obviously they are not stupid so it would be very unlikely that they would press the issue. They seem to prefer to use FUD to accieve their goals instead.

2 1

Winedbg and gcc 3.2
by Alberto Massari 09 Dec '02

09 Dec '02

Hi everybody, a few weeks ago I changed my build machine from a RedHat 7.2 + gcc 2.9x to a Mandrake 9.0 + gcc 3.2, and I noticed that I was unable to debug the Wine libraries (I got messages like "No debug information in ELF '/usr/local/lib/wine/xxxx.dll.so'), while gdb worked just fine. So today I digged a little bit and I found that winedbg supports the "stabs" debug format, and looks for the ".stabs" segment in the binary. The copy of gcc 3.2 I have (gcc-3.2-1mdk) doesn't produce this segment unless I replace the -g option with -gstabs. My questions at this point are: - is this behavior typical of every gcc 3.2? or it's only Mandrake that does it? - is somebody going to change the "configure" script to detect such a situation and specify "-gstabs" instead of "-g"? (I would volunteer myself, but I am not expert in this field... I just hacked my copy to make it work in my tree) - or should winedbg be improved to understand more debug formats, so that it can handle whatever informations the "-g" option spits out? Thanks, Alberto P.S. Please don't flame me if I said something naive....

2 2

GDI RestoreDC()
by Mike Hearn 09 Dec '02

09 Dec '02

Hi all, I think I've traced the problem with the Adobe SVG plugin not reliably rendering: This is from a good run (when I use an svg file I know will render OK): 080746b8:Call kernel32.LOCAL_Free(0000019f,00001aca) ret=40948f6b 080746b8:Ret kernel32.LOCAL_Free() retval=00000000 ret=40948f6b trace:gdi:GDI_FreeObject (0x1aca): leave 1 080746b8:Ret gdi32.DeleteObject() retval=00000001 ret=5300a17c 080746b8:Call gdi32.BitBlt(000008a8,00000000,00000000,0000008c,0000008c,00000ba0,00000000,00000000,00cc0020) ret=5300a1ae As you can see, it appears to perform the BitBlt call correctly, those parameters look correct. Here is the same section from a bad run: 080746b8:Call kernel32.LOCAL_Free(0000019f,00001ac2) ret=40948f6b 080746b8:Ret kernel32.LOCAL_Free() retval=00000000 ret=40948f6b trace:gdi:GDI_FreeObject (0x1ac2): leave 1 080746b8:Ret gdi32.DeleteObject() retval=00000001 ret=5301b3df 080746b8:Call gdi32.RestoreDC(000008a8,ffffffff) ret=53018c68 It doesn't call BitBlt at all, not now, not later, not at all. Instead, it calls RestoreDC for no apparently good reason. That last argument looks highly suspicious, in that MSDN says it's an int which when positive identifies a state and when negative identifies a "step", ie -1 would restore the last state from the stack. I can't figure out what ffffffff would be as an int though :( Would it be negative or positive? Either way, is this an intelligent sort of value for the parameter to have? The MSDN docs are here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/devcon… I can't figure out why it would suddenly call RestoreDC and then seemingly go off on a tangent (the traces match up until that point), rather than do a BitBlt like it's supposed to. The SVG files vary only in that the "good" one has some interactivity (but it's not triggered at startup). Does anybody have any ideas? I'm fresh out for today. thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

2 2

RE: wpp
by Patrik Stridvall 09 Dec '02

09 Dec '02

> In other words, preprocessing is like 10% of compilation, so > it can't be unbearably slow. Something else is wrong. Perhaps. It was quite a few years ago I did it. I just remember abandoning the idea of using "gcc -E" for preprocessing in winapi_check because of horrible a speed slowdown. > > The FSF claims that you forking and calling a GPL:ed executable > > is the same as linking with a GPL:ed library and calling > > functions in that library. > > Do you have a reference to this? Never heard of something like > this before. It was dicussed extensively during the great licensing war. http://www.fsf.org/licenses/gpl-faq.html#GPLInProprietarySystem The main part is this I think: < The difference between this and "incorporating" the GPL-covered software < is partly a matter of substance and partly form. The substantive part is < this: if the two programs are combined so that they become effectively < two parts of one program, then you can't treat them as two separate programs. < So the GPL has to cover the whole thing. In the case of wrc it is pretty clear that "gcc -E" will one of the parts of the whole program and thus wrc must be under the GPL (or compatible with it). While, as I said earlier, this is a not a direct problem for a LGPL application, we have as I said I policy not to "link" with GPL:ed applications.

1 0

Re: Janitorial Projects -- conformance tests --recruiting volunteers
by David Miller 09 Dec '02

09 Dec '02

As someone only attempting to learn C I am looking for some other way to contribute something to wine. I have WinXP home on my laptop, so I could do WinXP tests if you can give me more information on what needs to be done. Dave

1 0

RE: wpp
by Patrik Stridvall 09 Dec '02

09 Dec '02

> On December 8, 2002 03:27 pm, Patrik Stridvall wrote: > > It is faster. Mucher faster. Using cpp/gcc -E needs to > > fork a new process for example. > > What?!? You got to be kiddin', right? If you can measure > any difference in build time between the forking gcc -E > and using wpp I'll give you a dollar in small change. I personally have only tried piping every file parsed by winapi_check through "gcc -E" and it is was unbearably slow, so I removed the code. The parsing it itself can't possibly taken that extra time. So I'm pretty sure that I can measure it, yes. However, the big question is not if it is measuarable but rather if it is worth the cost or not. So, yes, I agree that we need to discuss the question. > On Linux process creating is extremely fast, and we do > fork 1000s of processes while building wine, this sort > of argument is just silly. Well, it is not really the "fork" in it self that is the problem it is the overhead of loading and initializing gcc and that sort of things. > By the same rationale I suggest having a complete copy > of gcc, ld, nm, and whatever tools we use while building > wine. It is not primarily a question of having a complete copy of whatever. It is a question of having whatever accessable as functions in a library to avoid a lot of unnessary overhead. It would be very nice it something made a GNU C compiler library to support among other things only running the preprocessor. > So no, if speed is the only argument, I say we get rid > of it: it's not worth maintaining a fraction of all that > additional code. 1. Depending on "gcc -E" will make it harder to port wrc to Windows. 2. It might be less flexible (not sure though). > > And then of course using "gcc -E" would possibly cause > > a GPL violatation. Not that it would matter very much > > if wrc and friend were GPL:ed. > > WTF are you talking about?!? How did you figure this one > out? Really, this is simply false, you can fork GPL > programs all you want, and cause no GPL violation. The FSF claims that you forking and calling a GPL:ed executable is the same as linking with a GPL:ed library and calling functions in that library. This is of course absurd and would IMHO opinion nether fly in a court of law but still.... Sure wrc and friend are under a GPL compatible license (LGPL), so it wouldn't be a direct violation. However Wine has a policy that we do not link with GPL:ed libraries regardless in order to avoid possible problems for companies working with Wine so no we really can't make wrc depend of "gcc -E".

3 2

Re: Wine/FF7 midi help request
by Jeff Smith 08 Dec '02

08 Dec '02

>From: Robotech_Master <robotech(a)eyrie.org> > >On Tue Jun 11 2002 - 13:50:43 CDT Johan Gill wrote (as part of a >discussion about midi in WINE in which FF7 was mentioned): > > > Done. TiMidity++-2.12.0beta as alsa sequencer client requires no > > modification to wine at all, and the OSS emulation of ALSA makes the > > thing transparent to WINE. > >Can you, or someone, please let me know how to set up wine to use >this? I'm running Debian Linux; these are the versions of timidity >and wine that I have: > >ii timidity 2.11.2-1.3 Software-only MIDI sequencer. >ii wine 0.0.20021125-1 Windows Emulator (Binary Emulator) This is something I would not mind knowing myself. It's not too high a priority for me though as I have SoundFonts working on my SBLive now. >For sound, I'm using artsdsp 0.6.1 to emulate esd. I have a >Soundblaster live card. > >On the FF7 config program, it gives me the choices > > Wine OSS midi out (#0) - disabled > EMU10K1 midi This looks like what I would get from the OSS driver - emu10k1. The module name for the ALSA driver is snd-emu10k1. The choices I would expect from ALSA's OSS emulation would be something like: Emu10k1 MIDI 0-0 Emu10k1 Port 0 Emu10k1 Port 1 Emu10k1 Port 2 Emu10k1 Port 3 >Under "midi data" it gives me the choises > > General midi > Soundfont midi (Creative AWE32/AWE64) > Yamaha XG midi I would imagine this should stay on General midi unless you are *sure* it needs to be on another selection. >No matter what I try, in whatever combination, I get "Error opening >device" and the wine console says > >fixme:winmm:MIDI_StreamOpen *lpuDeviceID=1 >fixme:dsound:IDirectSoundImpl_SetCooperativeLevel >(0x403ab930,0001003c,3):stub > >Can someone help me out--or point me at somewhere else I can find >help? Try running it like this ... wine -debugmsg +winmm,+midi,+msacm program_name.exe ... and send the output. -- Jeff S _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

3 3

RE: wpp
by Patrik Stridvall 08 Dec '02

08 Dec '02

> Anyone remembers why we need our own cpp implementation, > instead of simply using cpp/gcc -E? It is faster. Mucher faster. Using cpp/gcc -E needs to fork a new process for example. And then of course using "gcc -E" would possibly cause a GPL violatation. Not that it would matter very much if wrc and friend were GPL:ed. Obviously any GPL claim would be absurd as we discussed to death in the great licensing flamewar but still.

2 1

Re: Intel 8x0 and ALSA sound driver
by Nikolay Stefanov 08 Dec '02

08 Dec '02

On Sunday 08 December 2002 5:39 pm, Eric Pouech wrote: > which I'm say is a bad idea. the Alsa driver should report all available > drivers, and you should not be forced to define the one you want. > To be more correct, the notion of "default device" exists under windows, > but has to be handled at the wave mapper level, not at the driver level. Aha, got it. I doubt that I will be able to implement this, so I might just file it as a bug report. > that's why I say we have to remove those assertions and do proper error > handling instead > btw, if ALSA fails with an assert it's either: > - a bug in the ALSA driver > - a bug in the ALSA library > => those should be fixed (as ALSA isn't 1.0 yet, there's no need to work > around it in wine code) I had a look at mplayer code and it is structured in a completely different way than winealsa for the mmap case. I'm looking at wodPlayer_WriteMaxFrags, btw. This leads me to believe that the way wine does it is off, and it's not a driver issue... I'll try to tinker a bit with it and see whether I have any success. Nikolay

1 0

Loading Autorun.inf on CD's
by Dustin Navea 08 Dec '02

08 Dec '02

Hey guys, I was browsing through the forums on franksworld.net and noticed this post: http://www.frankscorner.org/wineforum/viewthread.php?tid=158 Now that got me thinking, wine doesnt have any method to check .inf files right now and load an installer if it finds one on a CD. I was wondering, what do you guys think it would take to get that supported? I know that we would probably have to associate .inf files with wine and/or have some sort of a wine cd detector that actively monitors cd's for autorun files, but what would need to be added to wine itself to parse an autorun file, so that we could create the loader later? -Dustin

3 5

Re: what to do with include/wine/obj_base.h?
by Jeff Smith 08 Dec '02

08 Dec '02

>From: Ove Kaaven <ovehk(a)ping.uio.no> >On 6 Dec 2002, Alexandre Julliard wrote: > > > Ove Kaaven <ovehk(a)ping.uio.no> writes: > > > > > 4) make widl not use macros at all, but emit full C and C++ >definitions > > > directly (this is what midl.exe does, it seems) > > > > I'd say this is the way to go if it's not too painful, it seems to be > > the most flexible. In any case obj_base.h has to go, so if we keep the > > macros they have to be put inside one of the standard headers, which > > wouldn't be very clean. > >We may have to keep the macros anyway, there are headers that use them >that can't be generated from IDL, like the DirectX headers. I suppose they >could be converted to using the MS-style objbase.h macros by perl scripts >or by rewriting them from api headers or something, but someone else would >have to take on that task, I think. > >But I'll try to add a widl header generation mode that don't use macros, >then. I don't really care whether the ICOM_ macros go or stay in the current form, but if they stay, they should at least be corrected in the following sense. Presently, a typical macro in obj_base.h is #define ICOM_METHOD4(ret,xfn,ta,na,tb,nb,tc,nc,td,nd) \ public: virtual ret CALLBACK (xfn)(ta a,tb b,tc c,td d) = 0; Note that we have na, nb, ... on the 'left' matching with a, b, ... on the 'right'. Not that this causes problems, it's just that it isn't right. And if the stuff gets stripped, it is a moot point anyway. If anyone thinks it is worth any effort, I can easily create a patch. -- Jeff S _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus

2 1

Re: wine/dlls Maketest.rules.in Makedll.rules.in
by Eric Pouech 07 Dec '02

07 Dec '02

Alexandre Julliard a écrit : > > ChangeSet ID: 6522 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2002/12/06 13:51:20 > > Modified files: > dlls : Maketest.rules.in Makedll.rules.in > > Log message: > Build test programs as part of the normal build. > > Patch: http://cvs.winehq.com/patch.py?id=6522 Alexandre, this patch is broken when building from a clean tree: - when building the tests for ntdll we need to link to kernel32 (for a cui program) which isn't built at this time - IMO, building the tests programs at the same time as the modules is a bad idea. we don't impose that tests for DLL x only depends on DLL x and DLLs built (in the wine dependency order) before x. - so, either we back up to the previous mode, or we add dependencies on test building as well A+

2 1

tools/wrc/wrc.c portability breakage
by Gerald Pfeifer 07 Dec '02

07 Dec '02

The following patch broke portability of tools/wrc/wrc.c: revision 1.18 date: 2002/12/06 19:49:36; author: julliard; state: Exp; lines: +78 -10 Dimitrie O. Paun <dpaun(a)rogers.com> Make wrc command line compatible with windres. 1) getopt() is supposed to to come from <unistd.h>, and <getopt.h> is a non-standard header. 2) getopt_long() is non-portable (and does not exist on FreeBSD, for example). The man page for getopt() clearly shows that, BTW: #define _GNU_SOURCE #include <getopt.h> Would you mind fixing this problem? Thanks, Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.pfeifer.com/gerald/

2 4

Failure running 1998-era online manual
by Dan Kegel 07 Dec '02

07 Dec '02

I grabbed Wine-20021125 and built it on my Red Hat 7.3 box. Its behavior installing http://enduser:enduser@bbs.toshiba.co.uk/file/area128/S22D95UM.ZIP (the Windows 95 version of the user manual for my 1998-era Toshiba laptop) seems much improved over May/June 2002 wine, cool! However, running the app does no better. To run the app, you do cd 'c/Program Files/DOC' wine edoc32.exe TOSHIBA.M14 On Windows, it works fine. On Wine, it displays a splash screen, then exits. Here's a partial log: 08074e50:Ret kernel32.lstrcpyA() retval=406d2dc0 ret=01643c25 08074e50:Call winmm.mmioInstallIOProcA(2034314d,01643b30,10010000) ret=01643c54 trace:mmio:MMIO_InstallIOProc (540291405, 0x1643b30, 10010000, 1) fixme:mmio:MMIO_InstallIOProc Global procedures not implemented ... 08074e50:Ret winmm.mmioInstallIOProcA() retval=01643b30 ret=01643c54 08074e50:Ret PE DLL (proc=0x1641030,module=0x1640000,type=1,res=0x1) retval=1 ... 08074e50:Starting process C:\Program Files\DOC\edoc32.exe (entryproc=0x41c9b0) ... 08074e50:Call winmm.mmioOpenA(406d2cfc "+init",00000000,00000000) ret=00405fd6 trace:mmio:MMIO_Open ('+init', (nil), 00000000, 1); 08074e50:Call ntdll.RtlAllocateHeap(40380000,00000008,0000005c) ret=40c3e59b 08074e50:Ret ntdll.RtlAllocateHeap() retval=403c42b8 ret=40c3e59b trace:mmio:MMIO_ParseExtA ("+init") err:mmio:MMIO_ParseExtA + but no . in szFileName: "+init" It sounds like mmioOpen's documentation at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/multimed/m… is incomplete; it doesn't describe what the function does when there's no filename, just a +init, in the string passed to mmioOpen. I tried patching the source for MMIO_ParseExtA to assume an extension of "" in this case, but it didn't help, the program still exits. Any suggestions? - Dan

2 2

Language search order
by Shachar Shemesh 07 Dec '02

07 Dec '02

From dlls/kernel/locale.c if (GetEnvironmentVariableA( "LC_ALL", buf, sizeof(buf) ) || GetEnvironmentVariableA( "*LC_CTYPE*", buf, sizeof(buf) ) || GetEnvironmentVariableA( "LANGUAGE", buf, sizeof(buf) ) || GetEnvironmentVariableA( "LC_MESSAGES", buf, sizeof(buf) ) || GetEnvironmentVariableA( "LANG", buf, sizeof(buf) )) Hi list, I'm trying to understand the above line of code. It would appear to me that default_lcid is used for "find resource". The manual for locale says: LC_CTYPE This changes the behaviour of the character handling and classi- fication functions, such as isupper() and toupper(), and the multi-byte character functions such as mblen() or wctomb(). Specifically, I'm looking into setting LC_CTYPE to "he_IL" so I can type Hebrew characters, while setting "LC_MESSAGE" to "C" so the messages programs issue are in English (or whatever their local setting says). It seems to me we may want to support independant settings of the two. I realize that there are places where we may want to use the information from LC_CTYPE (WideCharToMultiByte comes to mine), but I believe that we should use a different setting for that so we can allow Unix users independant control over both settings. Thoughts? Shachar

1 0

Unicode question
by Rolf Kalbermatter 07 Dec '02

07 Dec '02

Hello, In trying to get shell32 a little bit more Unicodified I came across this function ParseFieldA which is taken from shellord.c. I'm quite unfamiliar with Unicode so I still have to learn a lot. I have finally found most of the string manipulation functions which work for Unicode but when it comes down to simple character comparison I'm a little bit in the dark here. Some code snippets elsewhere in wine make me believe that for the english charset WCHAR == char is actually mostly true. However I wonder if this can be relied on in code. For instance the Unicode version of ParseField would in that case look like this but I really want the opinion of someone else on, if the code if (*src++ == ',') nField--; is actually working as expected on all systems independent of the actually used charsets for the local languages. And has anyone a good idea what the semi-stub would mean for this function? Maybe that it should ignore commas in quoted strings? /************************************************************************* * ParseFieldW [internal] * * copies a field from a ',' delimited string * * first field is nField = 1 */ DWORD WINAPI ParseFieldW(LPCWSTR src, DWORD nField, LPWSTR dst, DWORD len) { WARN("(%s,0x%08lx,%p,%ld) semi-stub.\n", debugstr_w(src), nField, dst, len); if (!src || !src[0] || !dst || !len) return 0; /* skip n fields delimited by ',' */ while (nField > 1) { if (*src == 0x0) return FALSE; if (*src++ == ',') nField--; } /* copy part till the next ',' to dst */ while ( *src != 0x0 && *src != ',' && (len--)>0 ) *(dst++) = *(src++); /* finalize the string */ *dst = 0x0; return TRUE; } Rolf Kalbermatter

4 3

RE: Let --disable-debug actually do something
by Medland, Bill 07 Dec '02

07 Dec '02

> -----Original Message----- > From: Alexandre Julliard [mailto:julliard@winehq.com] > Sent: Friday, December 06, 2002 12:53 PM > To: Medland, Bill > Cc: wine-devel(a)winehq.com > Subject: Re: Let --disable-debug actually do something > > > "Medland, Bill" <Bill.Medland(a)accpac.com> writes: > > > --- wine/include/wine/debug.h 5 Jul 2002 21:22:09 > -0000 1.5 > > +++ wine/include/wine/debug.h 4 Dec 2002 04:52:22 -0000 > > @@ -23,6 +23,7 @@ > > > > #include <stdarg.h> > > #include "windef.h" > > +#include "config.h" > > You can't do that, installed includes shouldn't depend on config.h. Oh. So how is setting --disable-debug supposed to result in the FIXMES being compiled out? I just don't understand what is supposed to be happening here; all I know is that it isn't working. (Or is that not what it is supposed to do?) a) --disable-debug results in the settings in config.h changing. b) wine/debug.h tests that setting that becomes defined in config.h, in order to reduce FIXME to a basically null statement. c) dlls/user/hook.c, for example, includes a FIXME statement. neither hook.c nor debug.h include config.h so if I insert #ifndef NO_DEBUG_MSGS #error I was right #endif just before the fixme of NotifyWinEvent then it tells me I am right. I can only think of two ways that setting --disable-debug could be expected to result in the FIXMES being compiled out (which I presume is what is supposed to happen). Either it is supposed to result in a change to the makefiles so the -D NO_DEBUG_MSGS gets specified (and I see no indication of that) or else it results in a #define NO_DEBUG_MSGS at a suitable point that comes before it is actually needed (which appears to be the intention). So I presume that the problem is that config.h is not being included before its contents are needed. So the question is where should it be included. One solution would be to include it explicitly in every file that includes a WARN, FIXME or TRACE. Do you really want that? The other is to include it in the file that uses it (viz. debug.h). So tell me why I am an idiot and what solution you want me implement. I guess the simplest would be to drop --disable-debug from the configure. > > -- > Alexandre Julliard > julliard(a)winehq.com > Bill Medland

4 3

Where to use dosdev
by György 'Nog' Jeney 07 Dec '02

07 Dec '02

In some of the int21 routines it says that we should use DOSDEV_Peek/Read/Write. Should we also use the functions in the devices.c to implement all functions on devices like ioctls etc.? nog.

2 3

small updates to debugger.sgml
by Tony Lambregts 07 Dec '02

07 Dec '02

Before I could feel right about adding "Advanced Debugging Techniques" to the documnetation I needed to update the documentation on the debugger. There is still one section that is out of date (that I am aware of). The section that I am refering to is as follows > Program hangs, nothing happens > > Switch to UNIX shell, get the process-ID using ps -a | grep wine, and > do a kill -HUP <pid> (without the < and >). Wine will then enter its > internal debugger and you can proceed as explained above. Also, you > can use --debug switch and then you can get into internal debugger by > pressing Ctrl-C in the terminal where you run Wine. > This is _wrong_ since neither work. I have added a fix me message in front of this since I am unable to come up with anything usefull to replace it. If anyone has a usefull suggestion I would appreciate it. Change log: Update the debugger documentation for current usage. Files: /documnetation/debugger.sgml -- Tony Lambregts Index: debugger.sgml =================================================================== RCS file: /home/wine/wine/documentation/debugger.sgml,v retrieving revision 1.13 diff -u -r1.13 debugger.sgml --- debugger.sgml 1 Oct 2002 18:13:09 -0000 1.13 +++ debugger.sgml 29 Nov 2002 06:08:53 -0000 @@ -271,8 +271,9 @@ <para> This file describes where to start debugging Wine. If at any point you get stuck and want to ask for help, please read the - file <filename>documentation/bugreports</filename> for - information on how to write useful bug reports. + <emphasis>How to Report A Bug</emphasis> section of the + <emphasis>Wine Users Guide</emphasis> for information on how to write + useful bug reports. </para> <sect2> @@ -311,8 +312,7 @@ <para> Steps to debug a crash. You may stop at any step, but please report the bug and provide as much of the information - gathered to the newsgroup or the relevant developer as - feasible. + gathered to the bug report as feasible. </para> <orderedlist> @@ -362,17 +362,26 @@ If you have found a misbehaving function, try to find out why it misbehaves. Find the function in the source code. Try to make sense of the arguments passed. Usually there is - a <function>TRACE(<channel>,"(...)\n");</function> at - the beginning of the function. Rerun wine with + a <function>WINE_DEFAULT_DEBUG_CHANNEL(<channel>);</function> + at the beginning of the file. Rerun wine with <parameter>-debugmsg +xyz,+relay</parameter> added to the commandline. </para> + <para> + Occasionally there are additional debug channels defined at the + begining of the file in the form. + <function>WINE_DECLARE_DEBUG_CHANNEL(<channel>);</function> + If so the offending fuction may also uses one of these alternate + channels. Look through the the function for + <function>TRACE_(<channel>)(" ... /n");</function> and add any + additional channels to the commandline. + </para> </listitem> <listitem> <para> Additional information on how to debug using the internal debugger can be found in - <filename>debugger/README</filename>. + <filename>programs/winedbg/README</filename>. </para> </listitem> <listitem> @@ -386,29 +395,25 @@ </listitem> <listitem> <para> - If even that isn't enough, add more debug output for - yourself into the functions you find relevant. See - <filename>documentation/debug-msgs</filename>. You might + If even that isn't enough, add more debug output for yourself + into the functions you find relevant. See The section on Debug + Logging in this guide for more information. You might also try to run the program in <command>gdb</command> instead of using the WINE-debugger. If you do that, use <parameter>handle SIGSEGV nostop noprint</parameter> to disable the handling of seg faults inside - <command>gdb</command> (needed for Win16). If you don't use - the <parameter>--desktop</parameter> or - <parameter>--managed</parameter> option, start the WINE - process with <parameter>--sync</parameter>, or chances are - good to get X into an unusable state. + <command>gdb</command> (needed for Win16). </para> </listitem> <listitem> <para> - You can also set a breakpoint for that function. Start wine - with the <parameter>--debug</parameter> option added to the - commandline. After loading the executable wine will enter - the internal debugger. Use <parameter>break - KERNEL_LSTRLEN</parameter> (replace by function you want - to debug, CASE IS RELEVANT) to set a breakpoint. Then use - <command>continue</command> to start normal + You can also set a breakpoint for that function. Start wine + useing <command>winedbg</command> instead of + <command>wine</command>. Once the debugger is is running enter + <command>break</command> <parameter>KERNEL_LSTRLEN</parameter> + (replace by function you want to debug, CASE IS RELEVANT) + to set a breakpoint. Then + use <command>continue</command> to start normal program-execution. Wine will stop if it reaches the breakpoint. If the program isn't yet at the crashing call of that function, use <command>continue</command> again @@ -425,6 +430,7 @@ <title>Program hangs, nothing happens</title> <para> + <emphasis>Fix me - this is out of date </emphasis> Switch to UNIX shell, get the process-ID using <command>ps -a | grep wine</command>, and do a <command>kill -HUP <pid></command> (without the < and >). Wine will @@ -449,8 +455,7 @@ </para> <para> Since the failure happens usually directly before setting up - the Messagebox you can start wine with - <parameter>--debug</parameter> added to the commandline, set a + the Messagebox you can start winedbg and set a breakpoint at <function>MessageBoxA</function> (called by win16 and win32 programs) and proceed with <command>continue</command>. With <parameter>--debugmsg

2 3

Re: Some fixes in capabilities
by Andreas Mohr 07 Dec '02

07 Dec '02

On Tue, Nov 26, 2002 at 10:23:55PM +0100, Lionel Ulmer wrote: > Hi all, > > As long as we do not support multi-texturing in our D3D driver, fill the > caps properly. Now SS2 does not try to do multitexturing anymore (not that > it actually works now, it's just that it would break less :-) ). > > Note: is there a way from DLL X to activate relay debugging ? What happens > is that SS2 somehow freezes at one point and doing a relay trace from > the start is about a 3 GB file... So what I would like to do is at a > specific function in the D3D code that I know to be just before the > freeze, call 'activate relay' and voila, I have relaying on :-) (to be > able to do that for all DLLs would be even better). > > But well, considering DLL separation and all that, I doubt that this > would be possible :-/ Oh pleeeeze... I thought that at least the Wine developers are reading the wine docu properly... ;-) Let's see... first you use completely inacceptable words, and then you admit to never reading the docu... bad, bad, very bad guy. :) Read wine.man. It explains how to do relay logging for a single DLL. Although I'm afraid that this might actually be broken at the moment maybe :-\ -- "My attitude is, everybody should try competing with Microsoft once in their life. Once." - Marc Andreessen, former Netscape lead employee, in a "browser wars" interview

7 8

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