September 2003 - Wine-devel

RE: wine/ tools/runtest misc/options.c include/mod ...
by Robert Shearman 26 Sep '03

26 Sep '03

> -----Original Message----- > From: wine-cvs-admin(a)winehq.com [mailto:wine-cvs-admin(a)winehq.com]On > Behalf Of Alexandre Julliard > Sent: 25 September 2003 21:34 > To: wine-cvs(a)winehq.com > Subject: wine/ tools/runtest misc/options.c include/mod ... > Removed the --dll option and replaced it by the WINEDLLOVERRIDES > environment variable. This will break a lot of HOWTOs on various sites that describe how to get apps working with Wine. Can we not have some period of time where we can use both methods and maybe remove the --dll option later (say when winecfg is ready)? Rob

3 3

winetests compile errors with MSVC and Wine headers
by Jakob Eriksson 26 Sep '03

26 Sep '03

I have upgraded all my include files and lib files in Visual Studio. ------ Build started: Project: msvcrt_test, Configuration: Wine Headers Win32 ------ Compiling... testlist.c scanf.c file.c Generating Code... Linking... testlist.obj : error LNK2001: unresolved external symbol _func_cpp .\Output\Win32_Wine_Headers/msvcrt_test.exe : fatal error LNK1120: 1 unresolved externals Build log was saved at "file://k:\c\Wine\wine\dlls\msvcrt\tests\Output\Win32_Wine_Headers\BuildLog.htm" msvcrt_test - 2 error(s), 0 warning(s) ------ Build started: Project: kernel32_test, Configuration: Wine Headers Win32 ------ Compiling... thread.c testlist.c profile.c process.c pipe.c path.c locale.c generated.c format_msg.c format_msg.c(35) : warning C4013: 'FormatMessageA' undefined; assuming extern returning int file.c environ.c drive.c directory.c console.c comm.c codepage.c atom.c alloc.c Generating Code... Linking... format_msg.obj : error LNK2019: unresolved external symbol _FormatMessageA referenced in function _doit .\Output\Win32_Wine_Headers/kernel32_test.exe : fatal error LNK1120: 1 unresolved externals Build log was saved at "file://k:\c\Wine\wine\dlls\kernel\tests\Output\Win32_Wine_Headers\BuildLog.htm" kernel32_test - 2 error(s), 1 warning(s) ------ Build started: Project: dsound_test, Configuration: Wine Headers Win32 ------ Compiling... testlist.c propset.c dsound.c Generating Code... Linking... dsound.obj : error LNK2001: unresolved external symbol _IID_IDirectSound3DListener dsound.obj : error LNK2001: unresolved external symbol _IID_IDirectSoundBuffer dsound.obj : error LNK2001: unresolved external symbol _IID_IDirectSound3DBuffer dsound.obj : error LNK2001: unresolved external symbol _IID_IDirectSoundNotify propset.obj : error LNK2001: unresolved external symbol _DSPROPSETID_DirectSoundDevice propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSoundPrivate propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSoundFullDuplex propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSoundCapture8 propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSoundCapture propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSound8 propset.obj : error LNK2001: unresolved external symbol _IID_IKsPropertySet propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSound .\Output\Win32_Wine_Headers/dsound_test.exe : fatal error LNK1120: 12 unresolved externals Build log was saved at "file://k:\c\Wine\wine\dlls\dsound\tests\Output\Win32_Wine_Headers\BuildLog.htm" dsound_test - 13 error(s), 0 warning(s) -- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -- -- If I add dxguid.lib to the project, the errors go down to: ------ Build started: Project: dsound_test, Configuration: Wine Headers Win32 ------ Linking... propset.obj : error LNK2001: unresolved external symbol _DSPROPSETID_DirectSoundDevice propset.obj : error LNK2001: unresolved external symbol _CLSID_DirectSoundPrivate .\Output\Win32_Wine_Headers/dsound_test.exe : fatal error LNK1120: 2 unresolved externals Build log was saved at "file://k:\c\Wine\wine\dlls\dsound\tests\Output\Win32_Wine_Headers\BuildLog.htm" dsound_test - 3 error(s), 0 warning(s) ---------------------- Done ---------------------- Build: 17 succeeded, 3 failed, 0 skipped

2 3

tests compiled with MSVC, MSVC headers.
by Jakob Eriksson 26 Sep '03

26 Sep '03

:-D ---------------------- Done ---------------------- Clean: 20 succeeded, 0 failed, 0 skipped

1 0

winetest.exe no results
by Tony Lambregts 26 Sep '03

26 Sep '03

I'm back after a long time just lurking. I was realy excited about the conformance testing program. Since I am the IT Administrator of a company that uses a wide variety of windows versions (no NT3 sorry) I will be able to submit a good number of tests results. The problem I have under windows 98 is that the zip file found here http://afavant.elte.hu/~wferi/wine/ produces an results.txt file but the (newer) exe found here http://vmlinux.org/jakov/Wine/ locks up without producing any output (even when redirected >). Both tests freeze at the same place. That is they both lock up during the console test (kernel32_crosstest.exe console) the test produces a blue "abc" in the top right hand corner of my dos prompt box and requires that I "Ctrl-C" to get out. The following is the output results kernel32.dll:console (test 7 of 55) abcdefgconsole.c:128: Test failed: At (0,0): expecting char 'a'/61 got ' '/20 console.c:128: Test failed: At (0,0): expecting attr 0012 got 0007 console.c:128: Test failed: At (1,0): expecting char 'b'/62 got ' '/20 console.c:128: Test failed: At (1,0): expecting attr 0012 got 0007 console.c:128: Test failed: At (2,0): expecting char 'c'/63 got ' '/20 console.c:128: Test failed: At (2,0): expecting attr 0012 got 0007 console.c:128: Test failed: At (3,0): expecting char 'd'/64 got ' '/20 console.c:128: Test failed: At (3,0): expecting attr 0012 got 0007 console.c:128: Test failed: At (4,0): expecting char 'e'/65 got ' '/20 console.c:128: Test failed: At (4,0): expecting attr 0012 got 0007 console.c:128: Test failed: At (5,0): expecting char 'f'/66 got ' '/20 console.c:128: Test failed: At (5,0): expecting attr 0012 got 0007 console.c:128: Test failed: At (6,0): expecting char 'g'/67 got ' '/20 console.c:128: Test failed: At (6,0): expecting attr 0012 got 0007 console.c:131: Test failed: Expected cursor at (7,0), got (0,0) I have looked at dlls/kernel/tests/console.c to see if it was something obvious but have not had anything jump out at me. From looking at the code the cursor should be at the top left of the screen but the text is written at the top RIGHT (-3)of it. Eric since you wrote the test could you shed some light on it. Tony Lambregts

3 9

Max Payne & resolution detection
by Sylvain Petreolle 26 Sep '03

26 Sep '03

To continue the resolution detection problems story, today comes Max Payne. My X resolution is 1280x1024x16. If run under desktop mode with a size of 640x480, Max Payne sees correctly video modes (640, 800, 1024 and 1280) but fails with a BadWindow error. Since this error is usually corrected by disabling desktop mode, I comment it into .wine/config. Now Max Payne sees only 1280x1024, all other modes arent listed anymore. Any comments/hints ? ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 2

Keyboard problems
by Salmela 26 Sep '03

26 Sep '03

Hi When running eg. notepad with latest wine cvs, wine doesn't correctly find out my Finnish keyboard. Instead it is using Latin American keyboard because it's getting the highest score when X11DRV_KEYBOARD_DetectLayout is choosing keymap. I've looked in wine/dlls/keyboard.c and noticed that in Latin American keymap there are not many Alt-Gr characters. Every Alt-Gr charater produces an error and lowers the score of even right keymap and that is why wrong keymap is selected. So it seems like there is a problem detecting the keys right. Any thoughts? I've attached a debuglog of wine -debugmsg +keyboard,+key notepad My system is RH 9 and /etc/sysconfig/i18n says: LANG="en_US.iso885915" SUPPORTED="en_US.iso885915:en_US:en" SYSFONT="latarcyrheb-sun16"

2 5

Re: shlwapi 405/406
by Rolf Kalbermatter 26 Sep '03

26 Sep '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> wrote: >> Please don't do that. Internal functions should use standard C >> calling conventions. We don't care about two bytes of extra code. > >Can do. Is there any reason why not though? After all, the entire >Win32 api does it... Alexandre may have its reasons, but basically stdcall is only almost exclusevly used for the exported Windows API. Internal Windows DLL functions use c and stdcall happily along each other as they see fit. Rolf Kalbermatter

1 0

DLL Overrides and Winecfg
by Matthew Davison 26 Sep '03

26 Sep '03

I have recently noticed the large number of Stub DLLs being Added to wine with minimal functionality, for example Msi, MSHTML (they don't work for me in any case). These additions have not for the most part been accompanied with a new "native, builtin" entry in samples/config. Due to the forthcoming removal of the config file, i assume this functionality will be added to winedefault.reg. This is less than ideal for people who track CVS or install from source with each new release since, as before, their registry will not be automatically updated to match winedefault.reg. Is there a mechanism for Wine dlls to specify a preferred override automatically (e.g. where the built-in DLL holds no functionality, whereas the native one works correctly, and if not how difficult would it be to implement this, (e.g By adding the entries to the registry in DllRegisterServer or some similar mechanism) -- Matthew (Jabba The Hutt) Davison <m.davison(a)virgin.net>

5 7

Re: Re: ntdll/kernel32: #36
by Pouech Eric DMI AEI CAEN 25 Sep '03

25 Sep '03

I.e. it's quite a fair play to assume that the user has correctly configured the system to work with his/her locale. That's exactly my point. If the user didn't correctly configure his/her locale wrt. The iocharset of the drive, then trouble's ahead. So, we can either suggest that it's up to the user to do it correctly (and in that case CP_UNIXCP is just fine for internal handling) ; or we don't (and this was, to my understanding, the need of the codepage option in drive configuration). Basically my question could be rephrased as do we really need this option, or can we remove it. My first (dumb) reaction was if it's in there, it means we need it for some cases. But, I don't want to support this codepage option for no real need, so if no one objects, we could remove it. A+

3 2

Re: Resend: LPT0 support for DOSFS_OpenDevice
by Alexandre Julliard 25 Sep '03

25 Sep '03

Ed Lea <ed(a)jellybaby.net> writes: > [parallelports] > "Lpt1" = "/dev/lp0" > > The code compliments the existing serial port support, however has been > kept seperate from that for conceptual and technical reasons. I have probably missed something, but could you please explain what these reasons are? As far as I can see your code is a complete duplicate of the serial support, with maybe 3 lines changed. It sure looks like it would be better to reuse the serial code instead. -- Alexandre Julliard julliard(a)winehq.com

1 0