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

Aug 26 change in winmm/wineoss/audio.c broke msvc++4.0 installer?

by Dan Kegel

I finally tracked down the regression in the MSVC 4.0 installer to one patch: http://www.winehq.com/hypermail/wine-cvs/2002/08/0166.html ------ Modified files: dlls/winmm/wineoss: audio.c Log message: Ove Kaaven <ovek(a)transgaming.com> Tweaks to improve playback performance and reduce sound glitches: - wodGetPosition does not send an update message to the player thread; this reduces the accuracy of the readout from byte-accuracy to near fragment-accuracy, but we save 2-4 context switches and kernel scheduling penalties. - if FeedDSP runs out of data, do not flush output buffers before notifications are sent and given the chance to provide more sound data. Do not flush before we're down to the last fragment. - messages to the player thread are signaled using Unix pipes instead of Win32 synchronization primitives, to avoid having the player thread wait for the wineserver (and context switches from/to it) before the it can feed more data to the sound card. - ring buffer size is increased from 30 to 192 to support some games that fires 128 messages at once to determine DMA buffer size. ------ Before this patch, clicking on "Exit" in MSVC 4.0 installer worked. After this patch, it hangs. Baseline: inserting disc 1 of MSVC4.0 into drive and mounting it cvs update -D "2002-08-26 17:49 EDT" ./configure make depend && make ./wine d:setup.exe click on exit it terminates normally Error case: cvs update -D "2002-08-26 17:50 EDT" ./configure comment out #ifdef HAVE_SYS_POLL in dlls/winmm/wineoss/audio.c so it compiles comment out #define USE_PIPE_SYNC in dlls/winmm/wineoss/audio.c to get closer to old behavior make depend && make ./wine --debugmsg +event,+relay,+wave d:setup.exe > /tmp/bad.log 2>&1 click on exit it hangs, must kill with SIGINT Log in http://www.kegel.com/msvc4-setup-wine-20020826-17:50.bad.log.bz2 Problem occurred whether or not I commented out #define USE_PIPE_SYNC I'd be happy to provide more info. FWIW I'm running Red Hat 8.0. - Dan

Dec. 10, 2002

Re: lz32 & kernel32

by Marcus Meissner

On Tue, Dec 10, 2002 at 01:06:54AM -0800, Francois Gouget wrote: > > I have checked the Wine spec files against the list of APIs exported by > the various Windows libraries and started on resolving the > discrepancies. > > One of the (smaller) things I found is that in Win2000 and WinXP the LZ > API is implemented in kernel32 and lz32 only contains forwards that > point to kernel32. In all other Windows version however, the LZ API is > not available from kernel32 and is implemented in lz32. > > What should we do? Should we have kernel32 import lz32 and forward the > LZ functions it? Or should we do like Windows, which means moving the LZ > APIs to kernel32, and turn all the entry points in lz32 into forwards > pointing to kernel32 like on Windows? If the LZ APIs are exposed from kernel32 ... Then I would say yes. Will the forwarding work for the 16bit version too? Ciao, Marcus

Dec. 10, 2002

Fix for comparisons in netapi32/tests

by Vincent Béron

Two comparisons were always true due to the types. Not sure about the proper fix though. Changelog: Changed comparisons so they're not always true. Vincent Index: wine/dlls/netapi32/tests/apibuf.c =================================================================== RCS file: /home/wine/wine/dlls/netapi32/tests/apibuf.c,v retrieving revision 1.1 diff -u -r1.1 apibuf.c --- wine/dlls/netapi32/tests/apibuf.c 11 Sep 2002 02:35:18 -0000 1.1 +++ wine/dlls/netapi32/tests/apibuf.c 10 Dec 2002 17:25:20 -0000 @@ -48,14 +48,14 @@ ok(NetApiBufferFree(p) == NERR_Success, "Freed"); ok(NetApiBufferSize(p, &dwSize) == NERR_Success, "Got size"); - ok(dwSize >= 0, "The size"); + ok(dwSize < 0x80000000, "The size"); ok(NetApiBufferSize(NULL, &dwSize) == ERROR_INVALID_PARAMETER, "Error for NULL pointer"); /* 0-length buffer */ ok(NetApiBufferAllocate(0, (LPVOID *)&p) == NERR_Success, "Reserved memory"); ok(NetApiBufferSize(p, &dwSize) == NERR_Success, "Got size"); - ok((dwSize >= 0) && (dwSize < 0xFFFFFFFF),"The size of the 0-length buffer"); + ok(dwSize < 0xFFFFFFFF, "The size of the 0-length buffer"); ok(NetApiBufferFree(p) == NERR_Success, "Freed"); }

Dec. 10, 2002

Re: MSI (MS Installer)

by Shachar Shemesh

Uwe Bonnes wrote: >Okay, now even I understand that msiexec is getting a problem. > >Argh! > > Well I think Windows 2000 shiped with MSI 1.0, which was, to put it mildly, inadequate. Which is not to say we are going to have a nice time of it. Not at all. I have played around with MSI a bit back in the times (about two years ago), and it is going to be a bitch. It is a semi-relational database, and it has SQL language to make it tick. It has a bunch of mandatory tables, and a few less-mandatory. It carries it's own CAB files inside a streams table. The format for the binary file will need to be understood. Also, I know of at least one table that is there if queried by name, but does not appear if table listing is being requested. That particular table appeared in the MSDN docs. What about the others? If we are going to be rev-enging the MSI file format, that is not going to be much of a problem (Probably!), and I don't really think that the MSI itself is going to have too many undocumented APIs (let's not forget that most installations are produced using InstallShield and Wise, not by MS). Also, MSI installed apps have a special kind of shortcut that tracks uses and allows for delayed installations (i.e. - install just the icon now, we'll install the actual file when needed). I'm pretty sure there is a heavy dependancy of MSI on file and directory tracking (it's ability to recover slightly missing installs). So, it's not going to be easy, and there is a lot of infrastructure still missing. Shachar

Dec. 10, 2002

Re: MSI (MS Installer)

by Sylvain Petreolle

Do you really think that rpm/deb are nasty ? ;) The Windows Installer Service is just a rpm-like (guess what distribution I run ;) > Those MSI's are really nasty. IIRC, theyre like one big > relational-database-style table in there, and, since they are > cramming > all the features of this particular "app" (the "Windows Installer > Service," I guess) into a single table, you can guess how elegant and > > beautifully orthogonal the results are. I haven't really messed with > > them but I get the impression it might be kinda hairy/undocumented > territory. > ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 10, 2002

test

by Tom

I sent two emails about 15 min ago and they have not shown up.. So this is just a test.. Sorry Tom

Dec. 10, 2002

Conformance test --MSVC Headers 1 of 2 OverLook last 1 of 2 ...

by Tom

Crap.. Sorry here is the Real 1 of 2 Tom --- Here is the Build with MSVC Headers ---- --------------------Configuration: advapi32_test - Win32 MSVC Headers-------------------- advapi32_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: dsound_test - Win32 MSVC Headers-------------------- dsound_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: gdi32_test - Win32 MSVC Headers-------------------- gdi32_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: kernel32_test - Win32 MSVC Headers-------------------- kernel32_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: msvcrt_test - Win32 MSVC Headers-------------------- msvcrt_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: netapi32_test - Win32 MSVC Headers-------------------- netapi32_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: ntdll_test - Win32 MSVC Headers-------------------- Compiling... error.c c:\include\wine\dlls\ntdll\tests\error.c(23) : fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory rtlbitmap.c c:\include\wine\dlls\ntdll\tests\rtlbitmap.c(26) : fatal error C1083: Cannot open include file: 'winternl.h': No such file or directory rtlstr.c c:\program files\microsoft visual studio\vc98\include\winbase.h(216) : error C2061: syntax error : identifier 'DWORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(217) : error C2061: syntax error : identifier 'InternalHigh' c:\program files\microsoft visual studio\vc98\include\winbase.h(217) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(218) : error C2061: syntax error : identifier 'Offset' c:\program files\microsoft visual studio\vc98\include\winbase.h(218) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(219) : error C2061: syntax error : identifier 'OffsetHigh' c:\program files\microsoft visual studio\vc98\include\winbase.h(219) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(220) : error C2061: syntax error : identifier 'hEvent' c:\program files\microsoft visual studio\vc98\include\winbase.h(220) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(221) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(224) : error C2061: syntax error : identifier 'DWORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(225) : error C2061: syntax error : identifier 'lpSecurityDescriptor' c:\program files\microsoft visual studio\vc98\include\winbase.h(225) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(226) : error C2061: syntax error : identifier 'bInheritHandle' c:\program files\microsoft visual studio\vc98\include\winbase.h(226) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(227) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(230) : error C2061: syntax error : identifier 'HANDLE' c:\program files\microsoft visual studio\vc98\include\winbase.h(231) : error C2061: syntax error : identifier 'hThread' c:\program files\microsoft visual studio\vc98\include\winbase.h(231) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(232) : error C2061: syntax error : identifier 'dwProcessId' c:\program files\microsoft visual studio\vc98\include\winbase.h(232) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(233) : error C2061: syntax error : identifier 'dwThreadId' c:\program files\microsoft visual studio\vc98\include\winbase.h(233) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(234) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(241) : error C2061: syntax error : identifier 'DWORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(242) : error C2061: syntax error : identifier 'dwHighDateTime' c:\program files\microsoft visual studio\vc98\include\winbase.h(242) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(243) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(250) : error C2061: syntax error : identifier 'WORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(251) : error C2061: syntax error : identifier 'wMonth' c:\program files\microsoft visual studio\vc98\include\winbase.h(251) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(252) : error C2061: syntax error : identifier 'wDayOfWeek' c:\program files\microsoft visual studio\vc98\include\winbase.h(252) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(253) : error C2061: syntax error : identifier 'wDay' c:\program files\microsoft visual studio\vc98\include\winbase.h(253) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(254) : error C2061: syntax error : identifier 'wHour' c:\program files\microsoft visual studio\vc98\include\winbase.h(254) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(255) : error C2061: syntax error : identifier 'wMinute' c:\program files\microsoft visual studio\vc98\include\winbase.h(255) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(256) : error C2061: syntax error : identifier 'wSecond' c:\program files\microsoft visual studio\vc98\include\winbase.h(256) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(257) : error C2061: syntax error : identifier 'wMilliseconds' c:\program files\microsoft visual studio\vc98\include\winbase.h(257) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(258) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(260) : error C2143: syntax error : missing ')' before '*' c:\program files\microsoft visual studio\vc98\include\winbase.h(260) : error C2143: syntax error : missing '{' before '*' c:\program files\microsoft visual studio\vc98\include\winbase.h(260) : error C2059: syntax error : ')' c:\program files\microsoft visual studio\vc98\include\winbase.h(261) : error C2146: syntax error : missing ')' before identifier 'lpThreadParameter' c:\program files\microsoft visual studio\vc98\include\winbase.h(261) : error C2061: syntax error : identifier 'lpThreadParameter' c:\program files\microsoft visual studio\vc98\include\winbase.h(261) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(262) : error C2059: syntax error : ')' c:\program files\microsoft visual studio\vc98\include\winbase.h(263) : error C2061: syntax error : identifier 'LPTHREAD_START_ROUTINE' c:\program files\microsoft visual studio\vc98\include\winbase.h(263) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(272) : error C2061: syntax error : identifier 'CRITICAL_SECTION' c:\program files\microsoft visual studio\vc98\include\winbase.h(272) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(273) : error C2061: syntax error : identifier 'PCRITICAL_SECTION' c:\program files\microsoft visual studio\vc98\include\winbase.h(273) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(274) : error C2061: syntax error : identifier 'LPCRITICAL_SECTION' c:\program files\microsoft visual studio\vc98\include\winbase.h(274) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(276) : error C2061: syntax error : identifier 'CRITICAL_SECTION_DEBUG' c:\program files\microsoft visual studio\vc98\include\winbase.h(276) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(277) : error C2061: syntax error : identifier 'PCRITICAL_SECTION_DEBUG' c:\program files\microsoft visual studio\vc98\include\winbase.h(277) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(278) : error C2061: syntax error : identifier 'LPCRITICAL_SECTION_DEBUG' c:\program files\microsoft visual studio\vc98\include\winbase.h(278) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(281) : error C2061: syntax error : identifier 'LPLDT_ENTRY' c:\program files\microsoft visual studio\vc98\include\winbase.h(281) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(391) : error C2061: syntax error : identifier 'WORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(392) : error C2061: syntax error : identifier 'wPacketVersion' c:\program files\microsoft visual studio\vc98\include\winbase.h(392) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(393) : error C2061: syntax error : identifier 'dwServiceMask' c:\program files\microsoft visual studio\vc98\include\winbase.h(393) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(394) : error C2061: syntax error : identifier 'dwReserved1' c:\program files\microsoft visual studio\vc98\include\winbase.h(394) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(395) : error C2061: syntax error : identifier 'dwMaxTxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(395) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(396) : error C2061: syntax error : identifier 'dwMaxRxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(396) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(397) : error C2061: syntax error : identifier 'dwMaxBaud' c:\program files\microsoft visual studio\vc98\include\winbase.h(397) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(398) : error C2061: syntax error : identifier 'dwProvSubType' c:\program files\microsoft visual studio\vc98\include\winbase.h(398) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(399) : error C2061: syntax error : identifier 'dwProvCapabilities' c:\program files\microsoft visual studio\vc98\include\winbase.h(399) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(400) : error C2061: syntax error : identifier 'dwSettableParams' c:\program files\microsoft visual studio\vc98\include\winbase.h(400) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(401) : error C2061: syntax error : identifier 'dwSettableBaud' c:\program files\microsoft visual studio\vc98\include\winbase.h(401) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(402) : error C2061: syntax error : identifier 'wSettableData' c:\program files\microsoft visual studio\vc98\include\winbase.h(402) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(403) : error C2061: syntax error : identifier 'wSettableStopParity' c:\program files\microsoft visual studio\vc98\include\winbase.h(403) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(404) : error C2061: syntax error : identifier 'dwCurrentTxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(404) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(405) : error C2061: syntax error : identifier 'dwCurrentRxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(405) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(406) : error C2061: syntax error : identifier 'dwProvSpec1' c:\program files\microsoft visual studio\vc98\include\winbase.h(406) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(407) : error C2061: syntax error : identifier 'dwProvSpec2' c:\program files\microsoft visual studio\vc98\include\winbase.h(407) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(408) : error C2061: syntax error : identifier 'wcProvChar' c:\program files\microsoft visual studio\vc98\include\winbase.h(408) : fatal error C1003: error count exceeds 100; stopping compilation Generating Code... Error executing cl.exe. ntdll_test.exe - 104 error(s), 0 warning(s) --------------------Configuration: oleaut32_test - Win32 MSVC Headers-------------------- Compiling... vartest.c NOTE: WINVER has been defined as 0x0500 or greater which enables Windows NT 5.0 and Windows 98 features. When these headers were released, Windows NT 5.0 beta 1 and Windows 98 beta 2.1 were the current versions. For this release when WINVER is defined as 0x0500 or greater, you can only build beta or test applications. To build a retail application, set WINVER to 0x0400 or visit http://www.microsoft.com/msdn/sdk to see if retail Windows NT 5.0 or Windows 98 headers are available. See the SDK release notes for more information. c:\include\wine\dlls\oleaut32\tests\vartest.c(656) : fatal error C1064: compiler limit : token overflowed internal buffer Error executing cl.exe. oleaut32_test.exe - 1 error(s), 0 warning(s) --------------------Configuration: rpcrt4_test - Win32 MSVC Headers-------------------- rpcrt4_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: shell32_test - Win32 MSVC Headers-------------------- shell32_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: shlwapi_test - Win32 MSVC Headers-------------------- shlwapi_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: urlmon_test - Win32 MSVC Headers-------------------- urlmon_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: user32_test - Win32 MSVC Headers-------------------- user32_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: ntdll_test - Win32 MSVC Headers-------------------- Compiling... error.c c:\include\wine\dlls\ntdll\tests\error.c(23) : fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory rtlbitmap.c c:\include\wine\dlls\ntdll\tests\rtlbitmap.c(26) : fatal error C1083: Cannot open include file: 'winternl.h': No such file or directory rtlstr.c c:\program files\microsoft visual studio\vc98\include\winbase.h(216) : error C2061: syntax error : identifier 'DWORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(217) : error C2061: syntax error : identifier 'InternalHigh' c:\program files\microsoft visual studio\vc98\include\winbase.h(217) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(218) : error C2061: syntax error : identifier 'Offset' c:\program files\microsoft visual studio\vc98\include\winbase.h(218) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(219) : error C2061: syntax error : identifier 'OffsetHigh' c:\program files\microsoft visual studio\vc98\include\winbase.h(219) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(220) : error C2061: syntax error : identifier 'hEvent' c:\program files\microsoft visual studio\vc98\include\winbase.h(220) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(221) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(224) : error C2061: syntax error : identifier 'DWORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(225) : error C2061: syntax error : identifier 'lpSecurityDescriptor' c:\program files\microsoft visual studio\vc98\include\winbase.h(225) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(226) : error C2061: syntax error : identifier 'bInheritHandle' c:\program files\microsoft visual studio\vc98\include\winbase.h(226) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(227) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(230) : error C2061: syntax error : identifier 'HANDLE' c:\program files\microsoft visual studio\vc98\include\winbase.h(231) : error C2061: syntax error : identifier 'hThread' c:\program files\microsoft visual studio\vc98\include\winbase.h(231) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(232) : error C2061: syntax error : identifier 'dwProcessId' c:\program files\microsoft visual studio\vc98\include\winbase.h(232) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(233) : error C2061: syntax error : identifier 'dwThreadId' c:\program files\microsoft visual studio\vc98\include\winbase.h(233) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(234) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(241) : error C2061: syntax error : identifier 'DWORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(242) : error C2061: syntax error : identifier 'dwHighDateTime' c:\program files\microsoft visual studio\vc98\include\winbase.h(242) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(243) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(250) : error C2061: syntax error : identifier 'WORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(251) : error C2061: syntax error : identifier 'wMonth' c:\program files\microsoft visual studio\vc98\include\winbase.h(251) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(252) : error C2061: syntax error : identifier 'wDayOfWeek' c:\program files\microsoft visual studio\vc98\include\winbase.h(252) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(253) : error C2061: syntax error : identifier 'wDay' c:\program files\microsoft visual studio\vc98\include\winbase.h(253) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(254) : error C2061: syntax error : identifier 'wHour' c:\program files\microsoft visual studio\vc98\include\winbase.h(254) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(255) : error C2061: syntax error : identifier 'wMinute' c:\program files\microsoft visual studio\vc98\include\winbase.h(255) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(256) : error C2061: syntax error : identifier 'wSecond' c:\program files\microsoft visual studio\vc98\include\winbase.h(256) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(257) : error C2061: syntax error : identifier 'wMilliseconds' c:\program files\microsoft visual studio\vc98\include\winbase.h(257) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(258) : error C2059: syntax error : '}' c:\program files\microsoft visual studio\vc98\include\winbase.h(260) : error C2143: syntax error : missing ')' before '*' c:\program files\microsoft visual studio\vc98\include\winbase.h(260) : error C2143: syntax error : missing '{' before '*' c:\program files\microsoft visual studio\vc98\include\winbase.h(260) : error C2059: syntax error : ')' c:\program files\microsoft visual studio\vc98\include\winbase.h(261) : error C2146: syntax error : missing ')' before identifier 'lpThreadParameter' c:\program files\microsoft visual studio\vc98\include\winbase.h(261) : error C2061: syntax error : identifier 'lpThreadParameter' c:\program files\microsoft visual studio\vc98\include\winbase.h(261) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(262) : error C2059: syntax error : ')' c:\program files\microsoft visual studio\vc98\include\winbase.h(263) : error C2061: syntax error : identifier 'LPTHREAD_START_ROUTINE' c:\program files\microsoft visual studio\vc98\include\winbase.h(263) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(272) : error C2061: syntax error : identifier 'CRITICAL_SECTION' c:\program files\microsoft visual studio\vc98\include\winbase.h(272) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(273) : error C2061: syntax error : identifier 'PCRITICAL_SECTION' c:\program files\microsoft visual studio\vc98\include\winbase.h(273) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(274) : error C2061: syntax error : identifier 'LPCRITICAL_SECTION' c:\program files\microsoft visual studio\vc98\include\winbase.h(274) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(276) : error C2061: syntax error : identifier 'CRITICAL_SECTION_DEBUG' c:\program files\microsoft visual studio\vc98\include\winbase.h(276) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(277) : error C2061: syntax error : identifier 'PCRITICAL_SECTION_DEBUG' c:\program files\microsoft visual studio\vc98\include\winbase.h(277) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(278) : error C2061: syntax error : identifier 'LPCRITICAL_SECTION_DEBUG' c:\program files\microsoft visual studio\vc98\include\winbase.h(278) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(281) : error C2061: syntax error : identifier 'LPLDT_ENTRY' c:\program files\microsoft visual studio\vc98\include\winbase.h(281) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(391) : error C2061: syntax error : identifier 'WORD' c:\program files\microsoft visual studio\vc98\include\winbase.h(392) : error C2061: syntax error : identifier 'wPacketVersion' c:\program files\microsoft visual studio\vc98\include\winbase.h(392) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(393) : error C2061: syntax error : identifier 'dwServiceMask' c:\program files\microsoft visual studio\vc98\include\winbase.h(393) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(394) : error C2061: syntax error : identifier 'dwReserved1' c:\program files\microsoft visual studio\vc98\include\winbase.h(394) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(395) : error C2061: syntax error : identifier 'dwMaxTxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(395) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(396) : error C2061: syntax error : identifier 'dwMaxRxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(396) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(397) : error C2061: syntax error : identifier 'dwMaxBaud' c:\program files\microsoft visual studio\vc98\include\winbase.h(397) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(398) : error C2061: syntax error : identifier 'dwProvSubType' c:\program files\microsoft visual studio\vc98\include\winbase.h(398) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(399) : error C2061: syntax error : identifier 'dwProvCapabilities' c:\program files\microsoft visual studio\vc98\include\winbase.h(399) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(400) : error C2061: syntax error : identifier 'dwSettableParams' c:\program files\microsoft visual studio\vc98\include\winbase.h(400) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(401) : error C2061: syntax error : identifier 'dwSettableBaud' c:\program files\microsoft visual studio\vc98\include\winbase.h(401) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(402) : error C2061: syntax error : identifier 'wSettableData' c:\program files\microsoft visual studio\vc98\include\winbase.h(402) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(403) : error C2061: syntax error : identifier 'wSettableStopParity' c:\program files\microsoft visual studio\vc98\include\winbase.h(403) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(404) : error C2061: syntax error : identifier 'dwCurrentTxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(404) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(405) : error C2061: syntax error : identifier 'dwCurrentRxQueue' c:\program files\microsoft visual studio\vc98\include\winbase.h(405) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(406) : error C2061: syntax error : identifier 'dwProvSpec1' c:\program files\microsoft visual studio\vc98\include\winbase.h(406) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(407) : error C2061: syntax error : identifier 'dwProvSpec2' c:\program files\microsoft visual studio\vc98\include\winbase.h(407) : error C2059: syntax error : ';' c:\program files\microsoft visual studio\vc98\include\winbase.h(408) : error C2061: syntax error : identifier 'wcProvChar' c:\program files\microsoft visual studio\vc98\include\winbase.h(408) : fatal error C1003: error count exceeds 100; stopping compilation Generating Code... Error executing cl.exe. wineruntests.exe - 104 error(s), 0 warning(s) --------------------Configuration: winetest - Win32 MSVC Headers-------------------- winetest.lib - 0 error(s), 0 warning(s) --------------------Configuration: wininet_test - Win32 MSVC Headers-------------------- wininet_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: winmm_test - Win32 MSVC Headers-------------------- winmm_test.exe - 0 error(s), 0 warning(s) --------------------Configuration: ws2_32_test - Win32 MSVC Headers-------------------- ws2_32_test.exe - 0 error(s), 0 warning(s)

Dec. 10, 2002

Warning fix in msvcrt_test

by Vincent Béron

Another thing noticed while compiling the tests on MSVC... In the msvcrt_test project, the link finishes with this warning: LINK : warning LNK4098: defaultlib "LIBCMTD" conflicts with use of other libs; use /NODEFAULTLIB:library It's pretty easy to fix it manually (and the warning doesn't seem to cause harm), but it would be nice of Patrik to incorporate what this patch does (the project's file is a generated file, so the patch cannot be directly applied to CVS). Vincent --- wine/dlls/msvcrt/tests/msvcrt_test.dsp 2002-12-10 09:33:46.000000000 -0500 +++ wine/dlls/msvcrt/tests/msvcrt_test.dsp 2002-12-10 11:06:21.000000000 -0500 @@ -38,6 +38,7 @@ # PROP Use_Debug_Libraries 1 # PROP Output_Dir "Output\Win32_MSVC_Headers" # PROP Intermediate_Dir "Output\Win32_MSVC_Headers" +# PROP Ignore_Export_Lib 0 # PROP Target_Dir "" # ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_MBCS" /D "_LIB" /YX /FD /GZ /c # ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I ..\..\..\Output\\Win32_MSVC_Headers /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_MSVCRT_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_MSVC_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR /FD /GZ /c @@ -48,7 +48,7 @@ # ADD BSC32 /nologo LINK32=link.exe # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /pdbtype:sept -# ADD LINK32 /nologo msvcrt.lib /subsystem:console /debug /machine:I386 /pdbtype:sept +# ADD LINK32 msvcrt.lib /nologo /subsystem:console /debug /machine:I386 /nodefaultlib:"libcmtd.lib" /pdbtype:sept !ELSEIF "$(CFG)" == "msvcrt_test - Win32 Wine Headers" @@ -61,6 +62,7 @@ # PROP Use_Debug_Libraries 1 # PROP Output_Dir "Output\Win32_Wine_Headers" # PROP Intermediate_Dir "Output\Win32_Wine_Headers" +# PROP Ignore_Export_Lib 0 # PROP Target_Dir "" # ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_MBCS" /D "_LIB" /YX /FD /GZ /c # ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I ..\..\..\Output\\Win32_Wine_Headers /I ..\..\..\include /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_MSVCRT_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_Wine_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR /FD /GZ /c @@ -71,7 +71,7 @@ # ADD BSC32 /nologo LINK32=link.exe # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /pdbtype:sept -# ADD LINK32 /nologo msvcrt.lib /subsystem:console /debug /machine:I386 /pdbtype:sept +# ADD LINK32 msvcrt.lib /nologo /subsystem:console /debug /machine:I386 /nodefaultlib:"libcmtd.lib" /pdbtype:sept !ENDIF

Dec. 10, 2002

Re: Recent wrc changes break mingw

by Steven Edwards

> I've already sent a patch to Alexandre a few days ago, but he has not > applied it yet. Maybe he wants it done differently, and I do not blame > him, I submitted the simplest thing possible. ok cool, I just saw your patch and it looks like its going to work. lets hope he takes it. Thanks Steven __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Dec. 10, 2002

Re: Accented Characters

by Zsolt Rizsanyi

On Tuesday 10 December 2002 13:05, Richard Allen wrote: > Hello all. I've been trying to get accented characters to work propperly > in wine. > For those who dont know, accented characters are beasts like "áéýúíó" > We obtain them by pressing the dead key (mute_acute in my case) and then > the key we want accented. > > I'm using CVS as of yesterday. > [ra(a)xo winecvs]$ cat wine/VERSION > Wine version 20021125 > > As far as I can tell, dlls/x11drv/keyboard.c seems to be where my > problem is. > > [ra(a)xo ra]$ wine /home/ra/.wine/c_drive/Program\ Files/mIRC/mirc.exe > fixme:keyboard:X11DRV_KEYBOARD_DetectLayout Your keyboard layout was not > found! Using closest match instead (Icelandic keyboard layout) for scancode > mapping. Please define your layout in windows/x11drv/keyboard.c and submit > them to us for inclusion into future Wine releases. > See the Wine User Guide, chapter "Keyboard" for more information. > > Now, keyboard.c does have a definition for the Icelandic keyboard, but as > far as I can tell it's only used to recognize what keymap is in action, and > not to define it ?. I've experimented with it, things like changing the > "2" key to a "b" but it did not change the keyboard layout. > > The warning above is just because the definition in wine for the IS keymap > doesnt match the one thats shipping with XFRee86 completely ? > > Anyway. my battle for the accented characters continues. The keyboard > handling in wine is unlike anything I've ever seen before. > Can anyone give me a quick runthru on how keyboard handling really works > in wine, and prehaps help fix this ? > > Also, how are accented characters (dead keys) working in other languages ? > Is this a problem limited to Icelandic or to accented characters in > general ? AFAIK this is a general problem. The attached patch should solve it. Tough it is not the proper fix (at least there is a better fix that will be merged in wine in the future). For more info see my reply to email 'Turkish keyboard Support' from yesterday. Regards Zsolt

Dec. 10, 2002

Re: Recent wrc changes break mingw

by Dimitrie O. Paun

On December 10, 2002 10:18 am, Steven Edwards wrote: > Mingw lacks getopt.h so we are now broken on mingw. Should I rip the needed > support and add it to libwine or is there a better way? I've already sent a patch to Alexandre a few days ago, but he has not applied it yet. Maybe he wants it done differently, and I do not blame him, I submitted the simplest thing possible. -- Dimi.

Dec. 10, 2002

Recent wrc changes break mingw

by Steven Edwards

Mingw lacks getopt.h so we are now broken on mingw. Should I rip the needed support and add it to libwine or is there a better way? gcc -c -I. -I. -I../../include -I../../include -D__MINGW__ -D_WINDOWS -DWINE_NO WINSOCK -Wall -mpreferred-stack-boundary=2 -D__WINE__ -D_REENTRANT -o wrc.o wrc .c wrc.c:62:20: getopt.h: No such file or directory wrc.c:287: elements of array `long_options' have incomplete type wrc.c:288: warning: excess elements in struct initializer wrc.c:288: warning: (near initialization for `long_options[0]') wrc.c:288: warning: excess elements in struct initializer wrc.c:288: warning: (near initialization for `long_options[0]') wrc.c:288: warning: excess elements in struct initializer wrc.c:288: warning: (near initialization for `long_options[0]') wrc.c:288: warning: excess elements in struct initializer wrc.c:288: warning: (near initialization for `long_options[0]') wrc.c:289: warning: excess elements in struct initializer wrc.c:289: warning: (near initialization for `long_options[1]') wrc.c:289: warning: excess elements in struct initializer wrc.c:289: warning: (near initialization for `long_options[1]') wrc.c:289: warning: excess elements in struct initializer wrc.c:289: warning: (near initialization for `long_options[1]') wrc.c:289: warning: excess elements in struct initializer wrc.c:289: warning: (near initialization for `long_options[1]') wrc.c:290: warning: excess elements in struct initializer wrc.c:290: warning: (near initialization for `long_options[2]') wrc.c:290: warning: excess elements in struct initializer wrc.c:290: warning: (near initialization for `long_options[2]') wrc.c:290: warning: excess elements in struct initializer wrc.c:290: warning: (near initialization for `long_options[2]') wrc.c:290: warning: excess elements in struct initializer wrc.c:290: warning: (near initialization for `long_options[2]') wrc.c:291: warning: excess elements in struct initializer wrc.c:291: warning: (near initialization for `long_options[3]') wrc.c:291: warning: excess elements in struct initializer wrc.c:291: warning: (near initialization for `long_options[3]') wrc.c:291: warning: excess elements in struct initializer wrc.c:291: warning: (near initialization for `long_options[3]') wrc.c:291: warning: excess elements in struct initializer wrc.c:291: warning: (near initialization for `long_options[3]') wrc.c:292: warning: excess elements in struct initializer wrc.c:292: warning: (near initialization for `long_options[4]') wrc.c:292: warning: excess elements in struct initializer wrc.c:292: warning: (near initialization for `long_options[4]') wrc.c:292: warning: excess elements in struct initializer wrc.c:292: warning: (near initialization for `long_options[4]') wrc.c:292: warning: excess elements in struct initializer wrc.c:292: warning: (near initialization for `long_options[4]') wrc.c:293: warning: excess elements in struct initializer wrc.c:293: warning: (near initialization for `long_options[5]') wrc.c:293: warning: excess elements in struct initializer wrc.c:293: warning: (near initialization for `long_options[5]') wrc.c:293: warning: excess elements in struct initializer wrc.c:293: warning: (near initialization for `long_options[5]') wrc.c:293: warning: excess elements in struct initializer wrc.c:293: warning: (near initialization for `long_options[5]') wrc.c:294: warning: excess elements in struct initializer wrc.c:294: warning: (near initialization for `long_options[6]') wrc.c:294: warning: excess elements in struct initializer wrc.c:294: warning: (near initialization for `long_options[6]') wrc.c:294: warning: excess elements in struct initializer wrc.c:294: warning: (near initialization for `long_options[6]') wrc.c:294: warning: excess elements in struct initializer wrc.c:294: warning: (near initialization for `long_options[6]') wrc.c:295: warning: excess elements in struct initializer wrc.c:295: warning: (near initialization for `long_options[7]') wrc.c:295: warning: excess elements in struct initializer wrc.c:295: warning: (near initialization for `long_options[7]') wrc.c:295: warning: excess elements in struct initializer wrc.c:295: warning: (near initialization for `long_options[7]') wrc.c:295: warning: excess elements in struct initializer wrc.c:295: warning: (near initialization for `long_options[7]') wrc.c:296: warning: excess elements in struct initializer wrc.c:296: warning: (near initialization for `long_options[8]') wrc.c:296: warning: excess elements in struct initializer wrc.c:296: warning: (near initialization for `long_options[8]') wrc.c:296: warning: excess elements in struct initializer wrc.c:296: warning: (near initialization for `long_options[8]') wrc.c:296: warning: excess elements in struct initializer wrc.c:296: warning: (near initialization for `long_options[8]') wrc.c:297: warning: excess elements in struct initializer wrc.c:297: warning: (near initialization for `long_options[9]') wrc.c:297: warning: excess elements in struct initializer wrc.c:297: warning: (near initialization for `long_options[9]') wrc.c:297: warning: excess elements in struct initializer wrc.c:297: warning: (near initialization for `long_options[9]') wrc.c:297: warning: excess elements in struct initializer wrc.c:297: warning: (near initialization for `long_options[9]') wrc.c:298: warning: excess elements in struct initializer wrc.c:298: warning: (near initialization for `long_options[10]') wrc.c:298: warning: excess elements in struct initializer wrc.c:298: warning: (near initialization for `long_options[10]') wrc.c:298: warning: excess elements in struct initializer wrc.c:298: warning: (near initialization for `long_options[10]') wrc.c:298: warning: excess elements in struct initializer wrc.c:298: warning: (near initialization for `long_options[10]') wrc.c: In function `main': wrc.c:330: warning: implicit declaration of function `getopt_long' make[2]: *** [wrc.o] Error 1 make[2]: Leaving directory `/g/src/wine-dev/wine/tools/wrc' make[1]: *** [wrc] Error 2 make[1]: Leaving directory `/g/src/wine-dev/wine/tools' make: *** [tools] Error 2 isolation(a)PH33R /g/src/wine-dev/wine $ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Dec. 10, 2002

Re: Win2000 Conformance Test Results...

by David Fraser

Hi Just ran the same tests, reported results where different. Maybe this will help debugging... David Kye Lewis wrote: >==== advapi32_test ==== > >registry: 56 tests executed, 0 marked as todo, 0 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: 160 tests executed, 0 marked as todo, 0 failures. > I get drive: 158 tests executed, 0 marked as todo, 0 failures. Hmmm... are we using different versions of the tests? I'm using http://fgouget.free.fr/wine/winetests.zip, ls -l and m5sum -rw-rw-r-- 1 share share 672352 Dec 9 23:25 winetests.zip b69f703ee7f71ef8a9bd4114828394ab winetests.zip which doesn't seem to have changed (downloaded it again) >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. >locale: 54 tests executed, 0 marked as todo, 0 failures. > >h:\wine\wine\dlls\kernel\tests\path.c:927:TMP=C:\WINNT\TEMP >h:\wine\wine\dlls\kernel\tests\path.c:935:TMP=C:\WINNT >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:822: Test failed: win2000 BUG:expected 10, got 11 >h:\wine\wine\dlls\kernel\tests\path.c:834: Test failed: win2000 BUG:expected 10, got 11 >h:\wine\wine\dlls\kernel\tests\path.c:848: Test failed: win2000 BUG:expected 10, got 11 >h:\wine\wine\dlls\kernel\tests\path.c:879: Test failed: win2000 BUG:expected 10, got 11 >h:\wine\wine\dlls\kernel\tests\path.c:892: Test failed: win2000 BUG:expected 10, got 11 >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, 6 failures. > for kernel32_test path, I got this additional error (before all the others) h:\wine\wine\dlls\kernel\tests\path.c:517: Test failed: GetLongPathNameA: wrong returncode, 105 instead of 105 > >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\KYELEW~1\DESKTOP\WINETE~1\KERNEL32_TEST.exe >h:\wine\wine\dlls\kernel\tests\process.c:450: Test failed:StartupInfoA:lpDesktop expected (null), got WinSta0\Default >h:\wine\wine\dlls\kernel\tests\process.c:527: Test failed:StartupInfoA:lpTitle expected (null), got >C:\DOCUME~1\KYELEW~1\DESKTOP\WINETE~1\KERNEL32_TEST.exe > >process: 116 tests executed, 0 marked as todo, 4 failures. > Exactly the same except I have 10 messages interspersed with these, saying: tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. Why these extra messages? >thread: 112 tests executed, 0 marked as todo, 0 failures. > >==== msvcrt_test ==== > >Test will not run > Yup, gives a GPF. >==== 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 ==== > >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 ==== > >clist: 236 tests executed, 0 marked as todo, 0 failures. > Here I get two failures: 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 >generated: 19 tests executed, 0 marked as todo, 0 failures. > >h:\wine\wine\dlls\shlwapi\tests\shreg.c:79: Test failed: RegCreateKeyA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:105: Test failed: SHGetValueA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:106: Test failed: (0123456789,bar\subdir1) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:107: Test failed: (ffffffff) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:112: Test failed: SHGetValueA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:113: Test failed: (0123456789) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:114: Test failed: (ffffffff) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:140: Test failed: test4 RegOpenKey >h:\wine\wine\dlls\shlwapi\tests\shreg.c:150: Test failed: SHQueryValueExA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:156: Test failed: SHQueryValueExA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:157: Test failed: (3435973836) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:164: Test failed: SHQueryValueExA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:165: Test failed: (6,24) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:171: Test failed: SHQueryValueExA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:172: Test failed: (6,43) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:182: Test failed: (6) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:184: Test failed: (3435973836) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:185: Test failed: (6,24) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:194: Test failed: ERROR_MORE_DATA >h:\wine\wine\dlls\shlwapi\tests\shreg.c:196: Test failed: (6,43) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:197: Test failed: (3435973836) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:205: Test failed: Expected ERROR_MORE_DATA >h:\wine\wine\dlls\shlwapi\tests\shreg.c:206: Test failed: (0123456789) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:207: Test failed: (0123456789) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:208: Test failed: (39,43) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:209: Test failed: (3435973836) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:218: Test failed: (6) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:219: Test failed: (6,43) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:220: Test failed: (3435973836) >h:\wine\wine\dlls\shlwapi\tests\shreg.c:125: Test failed: SHRegGetPathA failed >h:\wine\wine\dlls\shlwapi\tests\shreg.c:126: Test failed: () >h:\wine\wine\dlls\shlwapi\tests\shreg.c:241: Test failed: didn't open dest > >shreg: 36 tests executed, 0 marked as todo, 32 failures. > Same but I get 0 for all your 3435973836 which is 0xcccccccc. Must be a debug/release build thing - variable not being initialized. Should we print out some of these results in hex as well to make life easier? Also for shreg:126 (second last) I get Test failed: (0123456789) > >==== 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:139: Test failed: Missed a >message: change_counter=2 >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:139: Test failed: Missed a >message: change_counter=2 >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:139: Test failed: Missed a >message: change_counter=0 >h:\wine\wine\dlls\user\tests\sysparams.c:142: Test failed: Wrong action >47 != 0 >h:\wine\wine\dlls\user\tests\sysparams.c:926: Test failed: left: got 0 >instead of 1 >h:\wine\wine\dlls\user\tests\sysparams.c:927: Test failed: top: got 0 >instead of 1 >h:\wine\wine\dlls\user\tests\sysparams.c:928: Test failed: right: got >792 instead of 800 >h:\wine\wine\dlls\user\tests\sysparams.c:929: Test failed: bottom: got >595 instead of 600 >h:\wine\wine\dlls\user\tests\sysparams.c:139: Test failed: Missed a >message: change_counter=0 >h:\wine\wine\dlls\user\tests\sysparams.c:142: Test failed: Wrong action >47 != 0 >h:\wine\wine\dlls\user\tests\sysparams.c:939: Test failed: left: got 0 >instead of 2 >h:\wine\wine\dlls\user\tests\sysparams.c:940: Test failed: top: got 0 >instead of 2 >h:\wine\wine\dlls\user\tests\sysparams.c:941: Test failed: right: got >792 instead of 801 >h:\wine\wine\dlls\user\tests\sysparams.c:942: Test failed: bottom: got >595 instead of 601 >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 > >** Notes for this test; Does not clean up tests properly - widens the >taskbar in W2k! *** >also makes desktop area smaller (fixed by changing taskbar width again) > >sysparams: 318 tests executed, 0 marked as todo, 24 failures. >win: 373 tests executed, 0 marked as todo, 0 failures. >wsprintf: 4 tests executed, 0 marked as todo, 0 failures. > >wininet: > >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) 0012E994 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) 00B2FBDC 15 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead >INTERNET_STATUS_NAME_RESOLVED(11) 00B2FBCC 12 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead >INTERNET_STATUS_CONNECTING_TO_SERVER(20) 00B2FC48 12 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead >INTERNET_STATUS_CONNECTED_TO_SERVER(21) 00B2FDDC 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) 00B2FD84 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) 00B2FE04 4 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead >INTERNET_STATUS_REQUEST_COMPLETE(100) 00B2FE40 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.0 >200 OK >Date: Tue, 10 Dec 2002 05:01:53 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 cache3.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 772 >h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 466 >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) 00B2FE40 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) 00B2FDD0 4 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef >INTERNET_STATUS_HANDLE_CLOSING(70) 00B2FD6C 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) 0012E994 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) 0012EA4C 12 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead >INTERNET_STATUS_CONNECTED_TO_SERVER(21) 0012EA28 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) 0012EB30 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.0 >200 OK >Date: Tue, 10 Dec 2002 05:01:55 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 cache3.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 772 >h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 466 >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) 0012EBFC 4 >h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef >INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC0C 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: "Sound Blaster 16" 5.0 >(1:100): channels=65535 formats=0fff 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. > >==== w2_32_test ==== > >sock: 128 tests executed, 0 marked as todo, 0 failures. > > > > >I will now be concentrating on working out what is wrong with these >tests :) > > > > >Thanks, >Kye Lewis > >================ >You can reach me at: >kyethespy(a)liquid2k.com at most times >lew01(a)mcsc.vic.edu.au from 9am to 3pm Monday to Friday >lewislan(a)net2000.com.au is an alternative email > > > > >

Dec. 10, 2002

Conformance tests --MSVC Headers 2 of 2

by Tom

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

Dec. 10, 2002

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

by Vincent Béron

Le lun 09/12/2002 à 19:55, Tom a écrit : > My system is W2K Visual C++ 6.0 > Built test on RedHat 7.3 and moved over to Win box > > These are build Errors on W2K > > Tom > > ---- > > advapi32_test.exe - 0 error(s), 0 warning(s) > dsound_test.exe - 0 error(s), 0 warning(s) > gdi32_test.exe - 17 error(s), 1 warning(s) > kernel32_test.exe - 0 error(s), 0 warning(s) > msvcrt_test.exe - 0 error(s), 0 warning(s) > netapi32_test.exe - 0 error(s), 0 warning(s) > ntdll_test.exe - 0 error(s), 0 warning(s) > oleaut32_test.exe - 1 error(s), 0 warning(s) > rpcrt4_test.exe - 0 error(s), 0 warning(s) > shell32_test.exe - 0 error(s), 0 warning(s) > shlwapi_test.exe - 0 error(s), 0 warning(s) > urlmon_test.exe - 0 error(s), 0 warning(s) > user32_test.exe - 0 error(s), 0 warning(s) > wineruntests.exe - 17 error(s), 1 warning(s) I don't see the output of this one... > winetest.lib - 0 error(s), 0 warning(s) > wininet_test.exe - 0 error(s), 0 warning(s) > winmm_test.exe - 0 error(s), 0 warning(s) > ws2_32_test.exe - 0 error(s), 0 warning(s) > > Build Log > > --------------------Configuration: gdi32_test - Win32 Wine > Headers-------------------- ... > generated.c > c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2061: syntax error > : identifier 'OLDFONTENUMPROCA' This error (the others follow directly) is because STRICT is undefined. I'll send a cleaned-up version of my first version. > Build Log > > --------------------Configuration: oleaut32_test - Win32 Wine > Headers-------------------- ... > vartest.c > c:\include\wine\dlls\oleaut32\tests\vartest.c(656) : fatal error C1064: > compiler limit : token overflowed internal buffer I'll take a look at this one also. Vincent

Dec. 10, 2002

Re: what to do with include/wine/obj_base.h?

by Vincent Béron

Le lun 09/12/2002 à 19:15, Francois Gouget a écrit : > Or is it just that MSVC does not like the ',,' in macro invocations? I'll do some more tests later today, but from my experience last week with using the WINE headers to compile the tests on MSVC, it doesn't. It caused an error, not only a warning, IIRC. Vincent

Dec. 10, 2002

Re: MSI (MS Installer)

by Uwe Bonnes

>>>>> "David" == David Fraser <davidf(a)sjsoft.com> writes: David> Actually it is included with Windows 2000, XP and Me etc: David> Windows® Installer is an installation and configuration service David> that reduces the total cost of ownership. The installer ships David> with Microsoft® Windows® .NET Server 2003 family, Windows® XP, David> Windows® 2000, and Windows® Millennium Edition (Windows® Me). The David> installer is also provided as a service pack to Microsoft® David> Windows NT® version 4.0., Windows® 98, and Windows® 95. (from David> http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_start_p…) David> Although it depends what you call the ms core distribution I Okay, now even I understand that msiexec is getting a problem. Argh! -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 10, 2002

Re: MSI (MS Installer)

by Mike Hearn

Indeed, and quite a few apps are starting to ship only with MSIs. As XP replaces 98, that is only going to become a bigger problem. For now, having a script which downloads and installs the MSI system from microsoft.com should suffice. It'd have to fake user agent strings, but that's no big deal. MS won't pull that download for quite some time, at least until the user base of 98 is negligable, so it's not an immediately pressing problem. David Fraser wrote: > Uwe Bonnes wrote: > >> It's not wine that needs msiexec, it's some application with it's >> installer. So this application has to care for msiexec. >> >> If things change and msiexec get's part of the ms core distribution, >> we can >> reconsider... >> >> Bye >> >> > Actually it is included with Windows 2000, XP and Me etc: > Windows® Installer is an installation and configuration service that > reduces the total cost of ownership. The installer ships with > Microsoft® Windows® .NET Server 2003 family, Windows® XP, Windows® > 2000, and Windows® Millennium Edition (Windows® Me). The installer is > also provided as a service pack to Microsoft® Windows NT® version > 4.0., Windows® 98, and Windows® 95. (from > http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_start_p…) > > Although it depends what you call the ms core distribution I guess... > > David > > > >

Dec. 10, 2002

Re: MSI (MS Installer)

by David Fraser

Uwe Bonnes wrote: >It's not wine that needs msiexec, it's some application with it's >installer. So this application has to care for msiexec. > >If things change and msiexec get's part of the ms core distribution, we can >reconsider... > >Bye > > Actually it is included with Windows 2000, XP and Me etc: Windows® Installer is an installation and configuration service that reduces the total cost of ownership. The installer ships with Microsoft® Windows® .NET Server 2003 family, Windows® XP, Windows® 2000, and Windows® Millennium Edition (Windows® Me). The installer is also provided as a service pack to Microsoft® Windows NT® version 4.0., Windows® 98, and Windows® 95. (from http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_start_p…) Although it depends what you call the ms core distribution I guess... David

Dec. 10, 2002

Accented Characters

by Richard Allen

Hello all. I've been trying to get accented characters to work propperly in wine. For those who dont know, accented characters are beasts like "áéýúíó" We obtain them by pressing the dead key (mute_acute in my case) and then the key we want accented. I'm using CVS as of yesterday. [ra(a)xo winecvs]$ cat wine/VERSION Wine version 20021125 As far as I can tell, dlls/x11drv/keyboard.c seems to be where my problem is. [ra(a)xo ra]$ wine /home/ra/.wine/c_drive/Program\ Files/mIRC/mirc.exe fixme:keyboard:X11DRV_KEYBOARD_DetectLayout Your keyboard layout was not found! Using closest match instead (Icelandic keyboard layout) for scancode mapping. Please define your layout in windows/x11drv/keyboard.c and submit them to us for inclusion into future Wine releases. See the Wine User Guide, chapter "Keyboard" for more information. Now, keyboard.c does have a definition for the Icelandic keyboard, but as far as I can tell it's only used to recognize what keymap is in action, and not to define it ?. I've experimented with it, things like changing the "2" key to a "b" but it did not change the keyboard layout. The warning above is just because the definition in wine for the IS keymap doesnt match the one thats shipping with XFRee86 completely ? Anyway. my battle for the accented characters continues. The keyboard handling in wine is unlike anything I've ever seen before. Can anyone give me a quick runthru on how keyboard handling really works in wine, and prehaps help fix this ? Also, how are accented characters (dead keys) working in other languages ? Is this a problem limited to Icelandic or to accented characters in general ? Thanks in advance for any help :) -- Rikki. -- RHCE, RHCX, HP-UX Certified Administrator. -- Solaris 7 Certified Systems and Network Administrator. Bell Labs Unix -- Reach out and grep someone. Those who do not understand Unix are condemned to reinvent it, poorly.

Dec. 10, 2002

Re: wine/dlls/winsock/socket.c: Force SO_REUSEADDR ...

by Christoph Frick

On 10 Dec 2002, Martin Wilck wrote: Hi Martin! > 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. And this is only the coding side - also the logic used for the network code is not that smart. But id like to say that both games use quite the same code and both applications run AFAIK without problems in win9X, win2k and winxp. I could also trace it with other -winver settings if you like. But the last time i tested the games both where not able to find their network devices in >win9X - which let me believe that there is something like HK../NetTrans/... also in the NT branch of windows. So whatever they do, the do it either because wine makes them believe they have to do it or the behaviour of windows differs here in handling this situation. Id be glad to help where i can - but i dont have much more clues about it here. > 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. My intention was not to cause much trouble with this hack. My intention was to make the games work and therefore ask for some help here. If this results in much work and trouble id say its not worth it. I will provide my hack further for the people asking me for it and i will make it clear to them, that this hack is in no way good, tested, ok with this group, ... CU!

Dec. 10, 2002

Re: wine/dlls/winsock/socket.c: Force SO_REUSEADDR ...

by Martin Wilck

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(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

Dec. 10, 2002

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

by Alberto Massari

At 17.01 09/12/2002 -0800, Francois Gouget wrote: >On Tue, 10 Dec 2002, Kye Lewis wrote: > > > > C:\Downloads\Linux>advapi32_test.exe registry > > > h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set > > to > > > 'xxxxxxxxxx' instead of 'Te' > > > h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set > > to > > > 'xxxxxxx' instead of 'foobar' > > > h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set > > to > > > 'xxxxxxx' instead of 'foobar' > > > registry: 56 tests executed, 0 marked as todo, 3 failures. > > > > It is here that I notice a large discrepancy between this test and my > > test on the same Operating System: > > > > h:\wine\wine\dlls\advapi32\tests\registry.c:80: Test failed: data_count > > set to 24 instead of 7 > > h:\wine\wine\dlls\advapi32\tests\registry.c:81: Test failed: type 2 is > > not REG_SZ >[...] > >I guess that means the test makes assumptions that are not valid. It >would be interesting to find out what the differences are between your >bo and Alberto's: Home Edition vs. Profesional, internationaliztion >issues, etc. My machine is an Italian version of XP Home SP1, maybe this could play a role...advapi32.dll is version 5.1.2600.1106 Anyhow, it seems to me that the results are in line with what the test is expecting, apart from the fact that the test expects that RegEnumValue will fill the return buffer with the amount of characters it can hold, even if the value is longer. But MSDN states that "if the buffer specified by lpData is not large enough to hold the data, the function returns ERROR_MORE_DATA and stores the required buffer size in the variable pointed to by lpcbData. In this case, the contents of lpData are undefined." Alberto

Dec. 10, 2002

Re: MSI (MS Installer)

by Uwe Bonnes

>>>>> "Greg" == Greg Turner <gmturner007(a)ameritech.net> writes: Greg> Ultimately, my guess is Microsoft simply wouldn't want Greg> wine-associated folks redistributing msiexec, whether their rules Greg> allow for this or not... so IMO nobody should do so unless they Greg> are willing to duke it out with an army of lawyers, go to the Greg> media, start a legal defense fund, endure nuisance lawsuits, etc., Greg> over the issue -- however remote that possibility may be, being Greg> prepared for the worst-case scenario is the only way to be ready Greg> for life's nasty surprises when they do come... And there is also Greg> that aphorism about picking one's battles... It's not wine that needs msiexec, it's some application with it's installer. So this application has to care for msiexec. If things change and msiexec get's part of the ms core distribution, we can reconsider... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 10, 2002

lz32 & kernel32

by Francois Gouget

I have checked the Wine spec files against the list of APIs exported by the various Windows libraries and started on resolving the discrepancies. One of the (smaller) things I found is that in Win2000 and WinXP the LZ API is implemented in kernel32 and lz32 only contains forwards that point to kernel32. In all other Windows version however, the LZ API is not available from kernel32 and is implemented in lz32. What should we do? Should we have kernel32 import lz32 and forward the LZ functions it? Or should we do like Windows, which means moving the LZ APIs to kernel32, and turn all the entry points in lz32 into forwards pointing to kernel32 like on Windows? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Avoid the Gates of Hell - use Linux.

Dec. 10, 2002

Re: MSI (MS Installer)

by Greg Turner

On Monday 09 December 2002 04:53 pm, Shachar Shemesh wrote: > To answer my own question - they require that the installer only be > redistributed with an application, that the application add > significant functionality to the redistibutables themselves, how nice of them ;) > and that > the application be only compatible with MS Windows. sheesh, typical. I take it back. > I guess we can't > put it on our site, though I very much doubt they are allowed to > request that last paragraph. Still, we can direct people to their > site and tell them to D/L it from there, if there are any problems. IMO, eventually wine should probably implement msiexec, but it might be pretty challenging, and, considering it's "just a free download" I guess it's a pretty low priority compared to things like uh, cabinet.dll (I heard somebody was supposed to be working on this but was screwing around with kde3.1rc5 instead :(. "Potato Guy" is a real breakthrough of modern OOP programming techniques, you should all check it out! Just think: only 18 hours of compiling, and you, too, can have a small worm crawl across on top of your foreground window. I think this means Linux has finally caught up with Microsoft!). Er... but I digress... Those MSI's are really nasty. IIRC, theyre like one big relational-database-style table in there, and, since they are cramming all the features of this particular "app" (the "Windows Installer Service," I guess) into a single table, you can guess how elegant and beautifully orthogonal the results are. I haven't really messed with them but I get the impression it might be kinda hairy/undocumented territory. Anyways, what was the point of my post? Oh yeah: despite all of the above reasons not to implement MSIEXEC for wine, I think, in an ideal world, you wouldn't need to go to Microsoft and download things just to run installers in wine. The more wine users depend on MS to make their wine work, the easier it is for MS to pull the plug, screw it up, etc. (which is not to say that MS has been taking such measures against wine... yet... but if past performance is any indicator of future returns, as soon as wine becomes a threat to the OS monopoly in their view of the world, this could instantly change). Oh, and while I'm on a rant... if we wanted to be smart-asses and play dangerous lawyer games, we could redistribute msiexec with a native compile of winemine or some other small frob. Ultimately, my guess is Microsoft simply wouldn't want wine-associated folks redistributing msiexec, whether their rules allow for this or not... so IMO nobody should do so unless they are willing to duke it out with an army of lawyers, go to the media, start a legal defense fund, endure nuisance lawsuits, etc., over the issue -- however remote that possibility may be, being prepared for the worst-case scenario is the only way to be ready for life's nasty surprises when they do come... And there is also that aphorism about picking one's battles... -- gmt Disclaimer: I'm no a lawyer. If you take legal advice from me seriously, you're an idiot, and you deserve whatever you get. Blah Blah Blah Boilerplate Boilerplate Boilerplate. Be safe out there!

Dec. 10, 2002

Re: what to do with include/wine/obj_base.h?

by Ove Kaaven

On Mon, 9 Dec 2002, Francois Gouget wrote: > Also I would not be surprised if the MS macros were less flexible than > the ICOM macros and required that you have a compiler that can generate > C++ classes with just the right binary layout. Yeah, as mentioned in my original mail, I didn't know where to hook in ICOM_USE_COM_INTERFACE_ATTRIBUTE and ICOM_MSVTABLE_COMPAT if we used them. The latter could probably be plugged into BEGIN_INTERFACE, but the former (which seems more useful) has no place. We'd have to add a Wine-specific macro for that at least... > Concerning the array issue, isn't 'int[] a' equivalent to 'int a[]'? I've never seen that syntax with named parameters (I do know int[] to be valid with unnamed parameters in C++, but unnamed parameters aren't allowed in C). Does it work everywhere? Certainly doesn't on my gcc 2.95... $ cat foo.c int func(int[] b) { return 0; } int main() { int[5] a; return 0; } $ cc -c foo.c foo.c:1: parse error before `b' foo.c: In function `main': foo.c:8: parse error before `[' $ c++ -c foo.c dill.c: In function `int main()': dill.c:8: parse error before `[' (hmm, seems to be valid as a function argument in C++, but not C?) > Or is it just that MSVC does not like the ',,' in macro invocations? That's a separate issue that I don't know anything about.

Dec. 10, 2002

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

by Francois Gouget

On Mon, 9 Dec 2002, Tony Lambregts wrote: [...] > I was unable to redirect the output of the tests to a file. For > example "ws2_32_test.exe sock > temp.txt" would give me a 0 lenght > file is it supposed to work that way? Redirections are handled by the shell. This is true on Unix, on Windows NT, on Windows 9x and on DOS. Of course on Windows 9x and DOS the shell is so bad that it doesn't even support redirections. > Some tests output more than 50 lines so that even with the terminal > set to 50 lines I would not be able to copy all of them. Yes, with vanilla Win9x there is not solution. The only solutions I see are: * run the test in a debugger and to suspend it at the appropriate time. This is what I usually do. Of course it sort of implies you are also committed to fixing the bug while you're at it. * write your own tool to start the tests and redirect their output to a file. * use a better shell out of cygwin or mks toolkit. > Also a lot (most) of the tests had the prefix of where the file > resided on when it was compiled for each line, which made for very > long lines. I cleaned up the lines wrap, but is it really nessesary to > print the whole path. Probably not. > The output from the tests is at > http://bugs.winehq.com/showattachment.cgi?attach_id=350 Thanks. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ I haven't lost my mind, it's backed up on tape around here somewhere...

Dec. 10, 2002

Re: strcat+strcat+strcat == baaad"

by Jeff Smith

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

Dec. 10, 2002

Re: strcat+strcat+strcat == baaad"

by Greg Turner

On Tuesday 10 December 2002 01:10 am, Jeff Smith wrote: > 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. As you surely all know, this is common practice amongst various development environments and IMO wouldn't be a bad idea, at least as an optional (registry-configurable?) thing. Since I set winedbg to pop up in my main terminal, I would be especially pleased by this, since it would allow me to choose which of the ten processes that simultanously crashed I actually want attached to a debugger... there are all kinds of fancy possibilities that immediately come to mind, of course, but talk is cheap.... oh, and another nice thing: this provides feedback for crashes that occur when no terminal is attached (instead of silently disappearing windows). BTW, who the hell is Dr. Watson, and where can I find him 'cause I would like to beat him to a bloody pulp! ;) -- gmt

Dec. 10, 2002

Re: strcat+strcat+strcat == baaad"

by Eric Pouech

> 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+

Dec. 10, 2002

Re: strcat+strcat+strcat == baaad"

by Jeff Smith

>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

Dec. 10, 2002

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

by Tony Lambregts

Francois Gouget wrote: >So what I did is compile them here, whip up a quick batch file to >invoke them all, and zip them up. You can download them from: > >http://fgouget.free.fr/wine/winetests.zip > > >Just unzip them in some random directory and run them as follows: > >runtests.bat > > >The above script skips the generated tests (for no particular reason) >and skips the sysparams user32 test because it messes the environment >badly (e.g. the width of window borders). > >Given the number of tests that fail you may want to run them one by one >to better capture their output. To do so just have a quick look at >the batch file, running the tests is very easy, e.g.: > >kernel32_test.exe path > > > > [snip} I started a bug report http://bugs.winehq.com/show_bug.cgi?id=1185 for the conformance test not running on windows 98 Runing the tests on Microsoft Windows 98 (4.10.1998) a lot of tests fail. tests downloaded from http://fgouget.free.fr/wine/winetests.zip I was unable to redirect the output of the tests to a file. For example "ws2_32_test.exe sock > temp.txt" would give me a 0 lenght file is it supposed to work that way? Some tests output more than 50 lines so that even with the terminal set to 50 lines I would not be able to copy all of them. Also a lot (most) of the tests had the prefix of where the file resided on when it was compiled for each line, which made for very long lines. I cleaned up the lines wrap, but is it really nessesary to print the whole path. The output from the tests is at http://bugs.winehq.com/showattachment.cgi?attach_id=350 -- Tony Lambregts

Dec. 10, 2002

WinXP Professional conformance test results

by David Miller

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.

Dec. 9, 2002

WinXP advapi32_test

by Kye Lewis

Hi, It would seem to be that all advapi32_test is trying to do is overflow, and see if wine (or in this case windows) responds correctly. As far as I can see, there is currently no way that that test could *ever* work properly. Maybe I have an old version of this file? (Or maybe I'm missing something completely obvious) In the version of dlls/advapi32/tests/registry.c that I have, it puts "xxxxxxxxxx" into both value and data, and in *most* cases, expects either Test or foobar (or a truncated version depending on the other values) to be returned. How can Test OR foobar ever be returned from xxxxxxxxxx? It always seems to fail because of this. It expects a truncated word (because it's been overflowed) which is fair enough, but it expects "Te" for example, and gets "xx" instead, and this is why it seems to be failing these tests. Thanks, Kye Lewis ================ You can reach me at: kyethespy(a)liquid2k.com at most times lew01(a)mcsc.vic.edu.au from 9am to 3pm Monday to Friday lewislan(a)net2000.com.au is an alternative email

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by Dimitrie O. Paun

On December 9, 2002 05:29 pm, vkxzjq6lg(a)cswebmail.com wrote: > 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? Let me try to explain a bit more what I mean. There are two kinds of error conditions: 1. Programming Bugs: this include having inconsistent state, a NULL pointer when it should never be NULL, etc. 2. External Errors: other component failing, disk full, etc. What I'm saying is that for (1) we should die (most of the time), and for (2) we should fail gracefully, and seldom signal the problem. You see, this classification depends on categorizing the code into internal and external. Internal code is what we control (such as the implementation of the a control, or a component, etc); in such internal code we get to decide the invariants, and it's OK (and preferable) that we crash if such an invariant doesn't hold true. I don't think it's acceptable to add tests all over the place that print error messages: it bloats the code, makes it slower, and uglifies it to the point where you can't figure out what you're actually trying to do. In such cases I consider such checks to be detrimental. For external code, we no longer have the luxury to do what we want. Most (all?) Win32 APIs don't crash on NULL pointers, and so we should not crash either. Also, outputting a message in such a case is not needed -- this is normal behavior, and outputting messages just clutters the code, as well as the output. Again, such messages are detrimental. A few of the Win32 functions go a step further (oh, the horror!), and accept bad pointers without crashing. We should replicate such brain-dead behavior only if we know that (a) Windows does it this way in all versions, and (b) there are significant apps that depend on such behavior. As you can see, there are few cases where outputting messages is waranted. It is mostly in places where we know we don't implement the entire specification. Too many messages are as bad as too few. We already output quite a few, adding tests and ERRs/WARNs all over the place is not a good idea. -- Dimi.

Dec. 9, 2002

Win2000 Conformance Test Results...

by Kye Lewis

==== advapi32_test ==== registry: 56 tests executed, 0 marked as todo, 0 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: 160 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. locale: 54 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\kernel\tests\path.c:927:TMP=C:\WINNT\TEMP h:\wine\wine\dlls\kernel\tests\path.c:935:TMP=C:\WINNT 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:822: Test failed: win2000 BUG: expected 10, got 11 h:\wine\wine\dlls\kernel\tests\path.c:834: Test failed: win2000 BUG: expected 10, got 11 h:\wine\wine\dlls\kernel\tests\path.c:848: Test failed: win2000 BUG: expected 10, got 11 h:\wine\wine\dlls\kernel\tests\path.c:879: Test failed: win2000 BUG: expected 10, got 11 h:\wine\wine\dlls\kernel\tests\path.c:892: Test failed: win2000 BUG: expected 10, got 11 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, 6 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\KYELEW~1\DESKTOP\WINETE~1\KERNEL32_TEST.exe h:\wine\wine\dlls\kernel\tests\process.c:450: Test failed: StartupInfoA:lpDesktop expected (null), got WinSta0\Default h:\wine\wine\dlls\kernel\tests\process.c:527: Test failed: StartupInfoA:lpTitle expected (null), got C:\DOCUME~1\KYELEW~1\DESKTOP\WINETE~1\KERNEL32_TEST.exe process: 116 tests executed, 0 marked as todo, 4 failures. thread: 112 tests executed, 0 marked as todo, 0 failures. ==== msvcrt_test ==== Test will not run ==== 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 ==== 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 ==== clist: 236 tests executed, 0 marked as todo, 0 failures. generated: 19 tests executed, 0 marked as todo, 0 failures. h:\wine\wine\dlls\shlwapi\tests\shreg.c:79: Test failed: RegCreateKeyA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:105: Test failed: SHGetValueA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:106: Test failed: (0123456789,bar\subdir1) h:\wine\wine\dlls\shlwapi\tests\shreg.c:107: Test failed: (ffffffff) h:\wine\wine\dlls\shlwapi\tests\shreg.c:112: Test failed: SHGetValueA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:113: Test failed: (0123456789) h:\wine\wine\dlls\shlwapi\tests\shreg.c:114: Test failed: (ffffffff) h:\wine\wine\dlls\shlwapi\tests\shreg.c:140: Test failed: test4 RegOpenKey h:\wine\wine\dlls\shlwapi\tests\shreg.c:150: Test failed: SHQueryValueExA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:156: Test failed: SHQueryValueExA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:157: Test failed: (3435973836) h:\wine\wine\dlls\shlwapi\tests\shreg.c:164: Test failed: SHQueryValueExA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:165: Test failed: (6,24) h:\wine\wine\dlls\shlwapi\tests\shreg.c:171: Test failed: SHQueryValueExA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:172: Test failed: (6,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:182: Test failed: (6) h:\wine\wine\dlls\shlwapi\tests\shreg.c:184: Test failed: (3435973836) h:\wine\wine\dlls\shlwapi\tests\shreg.c:185: Test failed: (6,24) h:\wine\wine\dlls\shlwapi\tests\shreg.c:194: Test failed: ERROR_MORE_DATA h:\wine\wine\dlls\shlwapi\tests\shreg.c:196: Test failed: (6,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:197: Test failed: (3435973836) h:\wine\wine\dlls\shlwapi\tests\shreg.c:205: Test failed: Expected ERROR_MORE_DATA h:\wine\wine\dlls\shlwapi\tests\shreg.c:206: Test failed: (0123456789) h:\wine\wine\dlls\shlwapi\tests\shreg.c:207: Test failed: (0123456789) h:\wine\wine\dlls\shlwapi\tests\shreg.c:208: Test failed: (39,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:209: Test failed: (3435973836) h:\wine\wine\dlls\shlwapi\tests\shreg.c:218: Test failed: (6) h:\wine\wine\dlls\shlwapi\tests\shreg.c:219: Test failed: (6,43) h:\wine\wine\dlls\shlwapi\tests\shreg.c:220: Test failed: (3435973836) h:\wine\wine\dlls\shlwapi\tests\shreg.c:125: Test failed: SHRegGetPathA failed h:\wine\wine\dlls\shlwapi\tests\shreg.c:126: Test failed: () h:\wine\wine\dlls\shlwapi\tests\shreg.c:241: Test failed: didn't open dest shreg: 36 tests executed, 0 marked as todo, 32 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:139: Test failed: Missed a message: change_counter=2 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:139: Test failed: Missed a message: change_counter=2 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:139: Test failed: Missed a message: change_counter=0 h:\wine\wine\dlls\user\tests\sysparams.c:142: Test failed: Wrong action 47 != 0 h:\wine\wine\dlls\user\tests\sysparams.c:926: Test failed: left: got 0 instead of 1 h:\wine\wine\dlls\user\tests\sysparams.c:927: Test failed: top: got 0 instead of 1 h:\wine\wine\dlls\user\tests\sysparams.c:928: Test failed: right: got 792 instead of 800 h:\wine\wine\dlls\user\tests\sysparams.c:929: Test failed: bottom: got 595 instead of 600 h:\wine\wine\dlls\user\tests\sysparams.c:139: Test failed: Missed a message: change_counter=0 h:\wine\wine\dlls\user\tests\sysparams.c:142: Test failed: Wrong action 47 != 0 h:\wine\wine\dlls\user\tests\sysparams.c:939: Test failed: left: got 0 instead of 2 h:\wine\wine\dlls\user\tests\sysparams.c:940: Test failed: top: got 0 instead of 2 h:\wine\wine\dlls\user\tests\sysparams.c:941: Test failed: right: got 792 instead of 801 h:\wine\wine\dlls\user\tests\sysparams.c:942: Test failed: bottom: got 595 instead of 601 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 ** Notes for this test; Does not clean up tests properly - widens the taskbar in W2k! *** also makes desktop area smaller (fixed by changing taskbar width again) sysparams: 318 tests executed, 0 marked as todo, 24 failures. win: 373 tests executed, 0 marked as todo, 0 failures. wsprintf: 4 tests executed, 0 marked as todo, 0 failures. wininet: 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) 0012E994 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) 00B2FBDC 15 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_NAME_RESOLVED(11) 00B2FBCC 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTING_TO_SERVER(20) 00B2FC48 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTED_TO_SERVER(21) 00B2FDDC 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) 00B2FD84 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) 00B2FE04 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_REQUEST_COMPLETE(100) 00B2FE40 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.0 200 OK Date: Tue, 10 Dec 2002 05:01:53 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 cache3.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 772 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 466 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) 00B2FE40 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) 00B2FDD0 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 00B2FD6C 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) 0012E994 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) 0012EA4C 12 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead INTERNET_STATUS_CONNECTED_TO_SERVER(21) 0012EA28 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) 0012EB30 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.0 200 OK Date: Tue, 10 Dec 2002 05:01:55 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 cache3.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 772 h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 466 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) 0012EBFC 4 h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC0C 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: "Sound Blaster 16" 5.0 (1:100): channels=65535 formats=0fff 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. ==== w2_32_test ==== sock: 128 tests executed, 0 marked as todo, 0 failures. I will now be concentrating on working out what is wrong with these tests :) Thanks, Kye Lewis ================ You can reach me at: kyethespy(a)liquid2k.com at most times lew01(a)mcsc.vic.edu.au from 9am to 3pm Monday to Friday lewislan(a)net2000.com.au is an alternative email

Dec. 9, 2002

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

by Steven Edwards

The ReactOS project has a fully working console registry editor called regexplorer but it is GPL and done in C++. If anyone is interested in it or needs it under another license let me know. Thanks Steven --- Dan Kegel <dank(a)kegel.com> wrote: > 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 > > > > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Dec. 9, 2002

Import Lib patche

by Steven Edwards

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

Dec. 9, 2002

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

by Francois Gouget

On Mon, 9 Dec 2002, Alberto Massari wrote: > > >Volunters welcome. > > I thought I could try running them on my Windows XP Home machine.... Thanks, I integrated your results and Kye's on the status page: http://fgouget.free.fr/wine/tests-en.shtml The good news is that your results match those of Kye... except for advapi32. Help with untangling this one would be appreciated. The other bit of bad news is that Kye reported that the user32/sysparms test messes up the system settings somewhat on Windows XP. I noticed the same thing on Win 95. So I recommend caution before running that specific test (it is not invoked from the batch file for that reason). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The nice thing about meditation is that it makes doing nothing quite respectable -- Paul Dean

Dec. 9, 2002

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

by Kye Lewis

Well I've got XP Home SP1 here, I'm not going to go through a complete lot of specifications without having some idea of what to look for though :) Thanks, Kye Lewis kyethespy(a)liquid2k.com -----Original Message----- From: Francois Gouget [mailto:fgouget(a)free.fr] Sent: Tuesday, December 10, 2002 12:01 PM To: Kye Lewis Cc: wine-devel(a)winehq.org Subject: RE: Janitorial Projects -- conformance tests --recruiting volunteers On Tue, 10 Dec 2002, Kye Lewis wrote: > > C:\Downloads\Linux>advapi32_test.exe registry > > h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set > to > > 'xxxxxxxxxx' instead of 'Te' > > h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set > to > > 'xxxxxxx' instead of 'foobar' > > h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set > to > > 'xxxxxxx' instead of 'foobar' > > registry: 56 tests executed, 0 marked as todo, 3 failures. > > It is here that I notice a large discrepancy between this test and my > test on the same Operating System: > > h:\wine\wine\dlls\advapi32\tests\registry.c:80: Test failed: data_count > set to 24 instead of 7 > h:\wine\wine\dlls\advapi32\tests\registry.c:81: Test failed: type 2 is > not REG_SZ [...] I guess that means the test makes assumptions that are not valid. It would be interesting to find out what the differences are between your bo and Alberto's: Home Edition vs. Profesional, internationaliztion issues, etc. Could it be that the test did not cleanup after itself and failed on the subsequent runs? Do we have a volunteer for untangling this? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY

Dec. 9, 2002

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

by Francois Gouget

On Tue, 10 Dec 2002, Kye Lewis wrote: > > C:\Downloads\Linux>advapi32_test.exe registry > > h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set > to > > 'xxxxxxxxxx' instead of 'Te' > > h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set > to > > 'xxxxxxx' instead of 'foobar' > > h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set > to > > 'xxxxxxx' instead of 'foobar' > > registry: 56 tests executed, 0 marked as todo, 3 failures. > > It is here that I notice a large discrepancy between this test and my > test on the same Operating System: > > h:\wine\wine\dlls\advapi32\tests\registry.c:80: Test failed: data_count > set to 24 instead of 7 > h:\wine\wine\dlls\advapi32\tests\registry.c:81: Test failed: type 2 is > not REG_SZ [...] I guess that means the test makes assumptions that are not valid. It would be interesting to find out what the differences are between your bo and Alberto's: Home Edition vs. Profesional, internationaliztion issues, etc. Could it be that the test did not cleanup after itself and failed on the subsequent runs? Do we have a volunteer for untangling this? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY

Dec. 9, 2002

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

by Tom

My system is W2K Visual C++ 6.0 Built test on RedHat 7.3 and moved over to Win box These are build Errors on W2K Tom ---- advapi32_test.exe - 0 error(s), 0 warning(s) dsound_test.exe - 0 error(s), 0 warning(s) gdi32_test.exe - 17 error(s), 1 warning(s) kernel32_test.exe - 0 error(s), 0 warning(s) msvcrt_test.exe - 0 error(s), 0 warning(s) netapi32_test.exe - 0 error(s), 0 warning(s) ntdll_test.exe - 0 error(s), 0 warning(s) oleaut32_test.exe - 1 error(s), 0 warning(s) rpcrt4_test.exe - 0 error(s), 0 warning(s) shell32_test.exe - 0 error(s), 0 warning(s) shlwapi_test.exe - 0 error(s), 0 warning(s) urlmon_test.exe - 0 error(s), 0 warning(s) user32_test.exe - 0 error(s), 0 warning(s) wineruntests.exe - 17 error(s), 1 warning(s) winetest.lib - 0 error(s), 0 warning(s) wininet_test.exe - 0 error(s), 0 warning(s) winmm_test.exe - 0 error(s), 0 warning(s) ws2_32_test.exe - 0 error(s), 0 warning(s) Build Log --------------------Configuration: gdi32_test - Win32 Wine Headers-------------------- Command Lines Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP47.tmp" with contents [ /nologo /MTd /W3 /Gm /GX /ZI /Od /I "..\..\..\Output\\Win32_Wine_Headers" /I "..\..\..\include" /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_GDI32_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_Wine_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR"Output\Win32_Wine_Headers/" /Fo"Output\Win32_Wine_Headers/" /Fd"Output\Win32_Wine_Headers/" /FD /GZ /c "C:\include\wine\dlls\gdi\tests\generated.c" ] Creating command line "cl.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP47.tmp" Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP48.tmp" with contents [ gdi32.lib /nologo /subsystem:console /incremental:yes /pdb:"Output\Win32_Wine_Headers/gdi32_test.pdb" /debug /machine:I386 /out:"Output\Win32_Wine_Headers/gdi32_test.exe" /pdbtype:sept .\Output\Win32_Wine_Headers\generated.obj .\Output\Win32_Wine_Headers\testlist.obj ] Creating command line "link.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP48.tmp" Output Window Compiling... generated.c c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2061: syntax error : identifier 'OLDFONTENUMPROCA' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : 'constant' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : 'constant' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : ')' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2143: syntax error : missing ')' before 'string' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2143: syntax error : missing ')' before 'string' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2143: syntax error : missing '{' before 'string' c:\include\wine\dlls\gdi\tests\generated.c(2255) : error C2059: syntax error : '' c:\include\wine\dlls\gdi\tests\generated.c(2256) : error C2059: syntax error : '}' c:\include\wine\dlls\gdi\tests\generated.c(3787) : warning C4013: 'test_pack_OLDFONTENUMPROCW' undefined; assuming extern returning int Error executing cl.exe. Results gdi32_test.exe - 17 error(s), 1 warning(s) Build Log --------------------Configuration: oleaut32_test - Win32 Wine Headers-------------------- Command Lines Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP49.tmp" with contents [ /nologo /MTd /W3 /Gm /GX /ZI /Od /I "..\..\..\Output\\Win32_Wine_Headers" /I "..\..\..\include" /D "_DEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "_OLEAUT32_TEST_" /D "__WINE_USE_MSVCRT" /D __WINETEST_OUTPUT_DIR=\"Output\\Win32_Wine_Headers\" /D "__i386__" /D "_X86_" /D inline=__inline /FR"Output\Win32_Wine_Headers/" /Fo"Output\Win32_Wine_Headers/" /Fd"Output\Win32_Wine_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\RSP49.tmp" Creating temporary file "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP4A.tmp" with contents [ oleaut32.lib /nologo /subsystem:console /incremental:yes /pdb:"Output\Win32_Wine_Headers/oleaut32_test.pdb" /debug /machine:I386 /out:"Output\Win32_Wine_Headers/oleaut32_test.exe" /pdbtype:sept .\Output\Win32_Wine_Headers\vartest.obj .\Output\Win32_Wine_Headers\testlist.obj ] Creating command line "link.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\RSP4A.tmp" Output Window Compiling... vartest.c c:\include\wine\dlls\oleaut32\tests\vartest.c(656) : fatal error C1064: compiler limit : token overflowed internal buffer Error executing cl.exe. Results oleaut32_test.exe - 1 error(s), 0 warning(s)

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

On December 9, 2002 06:33 pm, Alexandre Julliard wrote: > Frankly, this ranks about as high on the priority list as the strcat > optimizations in makedep. Are there really no more real problems to > solve that we need to spend so much effort inventing new ones? You're obviously right Alexandre. I was just completing Francois thought here, it's not like I proposed it as a big problem that needs solving... :) And don't worry, I have patches comming your way, I'm just waiting for the ones that I've already submitted to go in (the others in the queue are quite dependand on those). <g> -- Dimi.

Dec. 9, 2002

Windows XP Conformance Test results...

by Kye Lewis

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.

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by Francois Gouget

On Mon, 9 Dec 2002 vkxzjq6lg(a)cswebmail.com wrote: > 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. If Wine is properly configured for a production environment the user would not be confronted to a debugger window. Instead the debugger would be invoked in non-interactive mode and dump a stack trace, list of running threads and such other useful information to stderr which would typically be captured and sent to a log file. The user can then be instructed to send that log file to whomever handles support. This provides that support person with the information needed for a first diagnosis. Of course the application still crashes which is a problem but it's pretty likely that if it did not, then either that problem would never have been uncovered, or it would have crashed a bit later, thus making it much harder to diagnose the real cause for the problem. Also, before putting Wine in a production environment, someone should take on the task of testing it and make sure it is suitable for the task at hand, i.e. that it won't crash every five minutes. [...] > 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. That prompts another issue. Currently Wine spews out so many spurious messages that there is no way to do what you say. Just running Solitaire would cause the above scheme to claim that very bad things happened during execution and the please could the user report the problems. It's not that the above is not a good idea. It's just that a lot of work remains to be done with the traces and debug messages issued by Wine before it becomes feasible (and it's sure to be somewhat controversial too :-( ). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Advice is what we ask for when we already know the answer but wish we didn't -- Eric Jong

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by vkxzjq6lg＠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. ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/

Dec. 9, 2002

Re: what to do with include/wine/obj_base.h?

by Francois Gouget

On Fri, 6 Dec 2002, Ove Kaaven wrote: [...] > 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. IIRC, one of the problems with the MS macros is that they force you to repeat all the inherited functions everytime. I.e. whenever you declare a new COM class you have to add the same QueryInterface, AddRef and Release lines over and over again. For DirectX this is even worse when Xxx8 inherits from Xxx7 which inehrits from Xxx6, etc <g>. The ICOM macros should be source and binary compatible with what's generated by the MSVC macros so I would just keep on using them since they should make the headers more readable and maintainable. Also I would not be surprised if the MS macros were less flexible than the ICOM macros and required that you have a compiler that can generate C++ classes with just the right binary layout. Concerning the array issue, isn't 'int[] a' equivalent to 'int a[]'? Then one could have things like: ICOM_METHOD2(HRESULT,Foo,REFIID[],, LPVOID[],) Or is it just that MSVC does not like the ',,' in macro invocations? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ $live{free} || die "";

Dec. 9, 2002

DOSMEM_Init VirtualProtect fails

by vkxzjq6lg＠cswebmail.com

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/

Dec. 9, 2002

Re: How to find out if file is loaded?

by Klaus Niederkrueger

On Mon, 9 Dec 2002, Francois Gouget wrote: > On Tue, 3 Dec 2002, Klaus Niederkrueger wrote: > [...] > > So it seems to me that the file tiles\TS01.BMP is loaded, but when I use > > "ltrace wine ..." I don't find any output regarding this file. Why is > > that? > > Maybe open operation is done by wineserver? > (then the filedesc is sent to wine via a Unix pipe) > > -- > Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ > Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly. > Oh, sorry, I forgot to send to the newsgroup that I already found out: "strace" does appearantly only show calls done by the first thread created. To see also the system-calls of the forked jobs you need the option "strace -f". Now I see that all files are opened though I'm a bit confused about the ioctl-line at the end. Does wine think that file Ts01.bmp is a sound-card??? [pid 26577] open("/usr/share/wine/drivec/Program Files/Dink Smallwood/dink/Tiles/Ts01.bmp", O_RDONLY|O_NONBLOCK|O_LARGEFILE) = 18 [pid 26577] fstat64(18, {st_mode=S_IFREG|0644, st_size=161080, ...}) = 0 [pid 26577] write(7, "\0\0\0\0\0\0\0\0X\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 26577] rt_sigprocmask(SIG_UNBLOCK, [HUP INT QUIT TERM CHLD], NULL, 8) = 0 [pid 26577] poll( <unfinished ...> [pid 26575] <... writev resumed> ) = 135 [pid 26575] read(5, "\0\0\0\0\0\0\0\0X\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 26575] rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 [pid 26575] rt_sigprocmask(SIG_BLOCK, [HUP INT ALRM IO], [RTMIN], 8) = 0 [pid 26575] write(4, "*\0\0\0\0\0\0\0\0\0\0\0X\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64 <unfinished ...> [pid 26577] <... poll resumed> [{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN, revents=POLLIN}, {fd=9, events=0}, {fd=10, events=0}, {fd=11, events=0}, {fd=12, events=0}, {fd=13, events=0}, {fd=14, events=0}, {fd=15, events=POLLIN}, {fd=18, events=0}], 11, -1) = 1 [pid 26577] rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM CHLD], NULL, 8) = 0 [pid 26577] read(6, "*\0\0\0\0\0\0\0\0\0\0\0X\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 26577] fstat64(18, {st_mode=S_IFREG|0644, st_size=161080, ...}) = 0 [pid 26577] ioctl(18, SNDCTL_TMR_TIMEBASE, 0xbffff9b4) = -1 ENOTTY (Inappropriate ioctl for device) In the end I would like to fix bug 1129. Any help would be appreciated a lot. Thanks again. Klaus

Dec. 9, 2002

Re: wpp

by Alexandre Julliard

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

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by Francois Gouget

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

Dec. 9, 2002

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

by Kye Lewis

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

Dec. 9, 2002

Re: How to find out if file is loaded?

by Francois Gouget

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

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad

by Francois Gouget

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

Dec. 9, 2002

Re: Non latin fonts and non local fonts

by Huw D M Davies

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

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad

by Francois Gouget

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

Dec. 9, 2002

Re: MSI (MS Installer)

by Shachar Shemesh

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

Dec. 9, 2002

Re: Wine startup problem

by Leonardo Giordani

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

Dec. 9, 2002

Re: Wine startup problem

by Bobby Bingham

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

Dec. 9, 2002

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

by Alberto Massari

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

Dec. 9, 2002

Re: Wine startup problem

by Uwe Bonnes

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

Dec. 9, 2002

Re: strcat+strcat+strcat == baaad"

by vkxzjq6lg＠cswebmail.com

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

Dec. 9, 2002

Re: MSI (MS Installer)

by Duane Clark

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

Dec. 9, 2002

Re: MSI (MS Installer)

by Shachar Shemesh

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

Dec. 9, 2002

Re: wpp

by Francois Gouget

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

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

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

Dec. 9, 2002

Re: Intel 8x0 and ALSA sound driver

by Nikolay Stefanov

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

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

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

Dec. 9, 2002

Wine startup problem

by Leonardo Giordani

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

Dec. 9, 2002

Re: wrc options

by Francois Gouget

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

Dec. 9, 2002

Re: MSI (MS Installer)

by Uwe Bonnes

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

Dec. 9, 2002

Non latin fonts and non local fonts

by Shachar Shemesh

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

Dec. 9, 2002

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

by Tony Lambregts

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

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Tony Lambregts

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

Dec. 9, 2002

Re: wpp

by Francois Gouget

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

Dec. 9, 2002

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

by Francois Gouget

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

Dec. 9, 2002

Re: MSI (MS Installer)

by Zsolt Rizsanyi

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

Dec. 9, 2002

Re: Turkish keyboard Support

by Zsolt Rizsanyi

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

Dec. 9, 2002

Re: Turkish keyboard Support

by Jeff Smith

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

Dec. 9, 2002

Re: Fix the winmm/wave tests

by Francois Gouget

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

Dec. 9, 2002

Re: Question about STRICT

by Francois Gouget

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

Dec. 9, 2002

Turkish keyboard Support

by Armish

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

Dec. 9, 2002

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

by Dustin Navea

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

Dec. 9, 2002

Re: regression: msvc4.0 install dies sooner now

by Dan Kegel

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

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Mike Hearn

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

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Shachar Shemesh

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

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Hetz Ben-Hamo

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

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Mike Hearn

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

Dec. 9, 2002

MSI (MS Installer)

by Scott Cote

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

Dec. 9, 2002

Re: Fix my broken WM_MOUSEHOVER patch

by Vincent Béron

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

Dec. 9, 2002

Re: Fix my broken WM_MOUSEHOVER patch

by Mike Hearn

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

Dec. 9, 2002

Re: Disassembly of the adobe svg plugin

by Hetz Ben-Hamo

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

Dec. 9, 2002

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

by Dan Kegel

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

Dec. 9, 2002

Disassembly of the adobe svg plugin

by Mike Hearn

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

Dec. 9, 2002

Re: Fix my broken WM_MOUSEHOVER patch

by Dimitrie O. Paun

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

Dec. 9, 2002

Re: Problem with DOSFS_OpenDevice

by Uwe Bonnes

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

Dec. 9, 2002

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

by Martin Wilck

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

Dec. 9, 2002

Problem with DOSFS_OpenDevice

by Gustavo Junior Alves

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

Dec. 9, 2002

Re: wpp

by Dimitrie O. Paun

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

Dec. 9, 2002