wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Get calling stack after application crash
by BiGgUn 29 Sep '03

29 Sep '03

Hi folks, How can i get the calling stack of program after its crash ? Running the program in winedbg doesn't give me anything. Using --debugmsg +xxx ... doesn't give me useful info. I give up with the +relay solution because it generates too big file. Thanks in advance. Stephan

2 1

winebuild & Winelib
by Dimitrie O. Paun 29 Sep '03

29 Sep '03

I am sorry, but I'm going to ask this without RTF{M,C}: 1. Building Winelib DLLs We need the .spec file, I know. But can we also use a .def file instead (without relay support, of course). My understanding is that the extra information in the .spec file is needed only for relay debugging... If we are to ask people for extra work to create Winelib DLLs, I think we can get away with a .def file, but not with a .spec file (no tool support in Windows, etc.) 2. Linking Winelib apps with Windows (PE) DLLs Is this possible? We will not be able to use the original import libs, we should be able to make do with a .def file. Is this supported by winebuild? I am trying to understand this a bit better for (a) winegcc support for building DLLs (b) updating the Winelib docs Thanks! -- Dimi.

3 5

regression - display mode detection - more exanples
by hatky 29 Sep '03

29 Sep '03

I don't know why I didn't think of giving you more examples of what the last change of resolution changing did but here they are: gta2 manager now detects these resolutions twice: 640x480 800x600 1024x786 1152x864 1280x960 and the 1400x1050 4 times (This manager only displays resolutions without dept) Gta2 itself now crashes but I am not sure if that is related or not p.s. gta2 = grand theft auto 2 as I said Unreal Tournament 2003 no longer finds any valid display modes (I the traces to some of you and to wine-devel) dam, I thought I had more games installed... and you have the Max Payne problem from Sylvain Petreolle (http://www.winehq.org/hypermail/wine-devel/2003/09/0948.html) I really think this should either be fixed somehow or reverted (if you want more broken reports you can release a version :) ) Sorry I didn't find anymore test cases for now, If you want more traces just ask, Hatky. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

4 7

tools/translations_status
by Dimitrie O. Paun 29 Sep '03

29 Sep '03

Here is a little script that can help translators to keep their languages up to date. It already helped get the French translation updated :))) ChangeLog New tool for displaying the translation status. --- /dev/null 2003-01-30 05:24:37.000000000 -0500 +++ tools/translations_status 2003-09-20 11:34:05.000000000 -0400 @@ -0,0 +1,65 @@ +#!/bin/sh +# Copyright 2003 Dimitire O. Paun +# Simply run it from the root of your wine CVS tree: +# $ tools/tools/translations_status + +MASTER_LANG=En +MASTER_FILES=`find . -name "*$MASTER_LANG.rc"` + +list_translations() +{ + MASTER_FILE=$1 + TRANSLATIONS=`ls ${MASTER_FILE%$MASTER_LANG.rc}??.rc` + for translation in $TRANSLATIONS; do + LANG=`echo "$translation" | sed 's/.*$..$\.rc/\1/'` + if [ "$LANG" != 'xx' ]; then echo "$LANG"; fi + done +} + +seconds_since_epoch() +{ + FILE="$1" + STATUS="`cvs status $FILE 2>/dev/null | grep 'Working revision:'`" + if ! echo "$STATUS" | grep -q "No entry for"; then + DATE="`echo "$STATUS" | sed 's/[^0-9]*[^ ]* *//'`" + date -d "$DATE" '+%s' + fi +} + + +echo "Legend:" +echo " '.' -- translation appears to be uptodate" +echo " 'x' -- translation needs updating" +echo " '?' -- unknown status (file not under CVS control)" +echo " ' ' -- translation missing" +echo "Master language is $MASTER_LANG" +echo + +ALL_LANGS=`(for file in $MASTER_FILES; do list_translations "$file"; done) | sort -u` + +echo " Module / Language " $ALL_LANGS + +for master in $MASTER_FILES; do + MASTER_TIMESTAMP=`seconds_since_epoch "$master"` + APP=`echo "${master%/*}" | sed 's/..//'` + printf "%25s" "$APP" + for lang in $ALL_LANGS; do + LANG_FILE="${master%$MASTER_LANG.rc}$lang.rc" + if [ -f "$LANG_FILE" ]; then + if [ -z $MASTER_TIMESTAMP ]; then + STATUS="?" + else + LANG_TIMESTAMP=`seconds_since_epoch "$LANG_FILE"` + if [ "$LANG_TIMESTAMP" -lt "$MASTER_TIMESTAMP" ]; then + STATUS="x" + else + STATUS="." + fi + fi + else + STATUS=" " + fi + echo -n " $STATUS " + done + echo +done -- Dimi.

2 6

Script to compile Wine programs on Windows
by Pavel Roskin 28 Sep '03

28 Sep '03

Hello! The attached script makes it possible to compile many programs from Wine under Windows. The only software needed on Windows is Cygwin with MinGW libraries and some other utilities (flex, bison). Simply run setup.exe from www.cygwin.com and make sure to select MinGW development tools. Then get Wine sources, and run the attached script in the Cygwin shell while in the Wine top-level source directory. There is one minor fix that needs to be applied to the sources to fix compatibility with MinGW headers (run autoconf and autoheader after applying): http://www.winehq.org/hypermail/wine-patches/2003/09/att-0347/01-spawnvp.di… The configure script is rather slow in Cygwin, so it's instructed not to create makefiles, only config.h. Then the necessary libraries are compiled. The next step is to link wrc, the Wine resource compiler. Once wrc is ready, the script starts compiling programs. I cannot get windres to compile most Wine's resources directly, so there are compiled from *.rc to *.res by wrc and then from *.res to *.o by windres. Programs currently compiled by the script: clock.exe cmdlgtst.exe notepad.exe progman.exe regedit.exe start.exe view.exe wcmd.exe winefile.exe winemine.exe winhelp.exe winver.exe Yes, you can play winemine on Windows now ;-) -- Regards, Pavel Roskin

7 26

Re: Wine programs for windows released on sourceforge
by Ivan Leo Murray-Smith 28 Sep '03

28 Sep '03

>I don't have the full env to test it myself. Can you test whether the >following patch solves this? "change font" in the propitious menu wasn't clickable before this patch, and the patch didn't change anything, but I don't have win xp, I have windows server 2003 (20030324). Yes I'm using CVS. It hasn't been a great day, first a 13 hour black out (And laptop battery down thanks to my idea of running seti 24/7), then mail service down, anyway the about problem is probably caused by the fact that the about display just calls %systemroo%system32\winver.exe In wine we have winever.exe.so, but if you compile that in windows and run it, you get the gui of %systemroot%system32\winver.exe. Also, in windows server 2k3 I can't overwrite that file, as there's that file restore service, I don't know if I can kill/disamble it, I'll give it a go (Let me know if there is a way to get rid of this great feature). The solution may be to get the wine winver to work correctly on windows without displaying something like Wine 20030911 Copyright 2003 Microsoft Corporation Then it could be named winever and placed in %systemroot%\system32\winever.exe and wine programs could call it directly when running on windows.

1 0

"Start menu"
by Robert van Herk 28 Sep '03

28 Sep '03

Hi people, It is said that there is some kind of start menu that should appear for Wine. I myself am using Slackware 9/KDE and on my system it does not show up though. Furthermore, I do not think the wine start menu, if it exists, is currently being synchronized with the files in the Start Menu directory (Windows\\Start Menu) that Wine has. Since I am not exactly sure what already exists, I don't know if it's a good idea to make a application (kicker applet?) that reads the .lnk files from the start menu dir and makes a menu out of that, so people can easily access Windows executables. A great advantage of synchronizing with the Start Menu would be that after every installation the executables will appear on your desktop as people are used to from using Windows. This might make Wine more intuitive to use... So, my question is: To what extend does wine already do something like this, and, moreover, how should I turn that on . If it does not has a functionality like this: do you agree that making this in a kicker applet is a good idea? Greetings, Robert

1 0

"Start menu"
by Robert van Herk 28 Sep '03

28 Sep '03

Hi people, It is said that there is some kind of start menu that should appear for Wine. I myself am using Slackware 9/KDE and on my system it does not show up though. Furthermore, I do not think the wine start menu, if it exists, is currently being synchronized with the files in the Start Menu directory (Windows\\Start Menu) that Wine has. Since I am not exactly sure what already exists, I don't know if it's a good idea to make a application (kicker applet?) that reads the .lnk files from the start menu dir and makes a menu out of that, so people can easily access Windows executables. A great advantage of synchronizing with the Start Menu would be that after every installation the executables will appear on your desktop as people are used to from using Windows. This might make Wine more intuitive to use... So, my question is: To what extend does wine already do something like this, and, moreover, how should I turn that on :-). If it does not has a functionality like this: do you agree that making this in a kicker applet is a good idea? Greetings, Robert

1 0

Wine programs for windows released on sourceforge
by Ivan Leo Murray-Smith 28 Sep '03

28 Sep '03

Patches and scripts are useless for most users, and cygwin isn't software you install quickly with a analog modem, so I've uploaded a build of the wine programs for windows on our sourceforge page.

4 4

Re: winedos / Fix BIOS segment address under Win16
by kd6qog40m＠comcast.net 28 Sep '03

28 Sep '03

the wine routine works but int 10 is only on amd prossesors > BIOS data area is not necessarily at a fixed location. > Win16 programs that do not jump into real mode code > may have NULL pointer catching block at low linear memory > and BIOS data area has been moved elsewhere. This patch > should make sure that correct linear pointer is used > for accessing BIOS data area. > > This should fix bug 1732 and I have also seen this bug with > some Win16 programs. > > Pending stuff that I should be fixing when I have more time: > > - DPMI async event handling is subject to stalls and deadlocks > because instruction emulation is no longer protected > from signals. > - DPMI/RM performance is poor because the number of exceptions has > dramatically increased. This is due to send_debug_event > calling server during each exception. > - Fixes to mouse driver (hide/show, virtual size, mouse range). > These are ready but require cleaning and synchronizing with CVS. > - RMCB calls. Working thing exists but it uses interrupt hooks. > Perhaps fixing WOWCallback16Ex return path to support more > registers would be better... > > > > > Changelog: > Use correct linear pointer when accessing BIOS data area. > > > > > Index: dlls/winedos/devices.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/devices.c,v > retrieving revision 1.9 > diff -u -r1.9 devices.c > --- dlls/winedos/devices.c 25 Aug 2003 01:01:01 -0000 1.9 > +++ dlls/winedos/devices.c 27 Sep 2003 19:22:16 -0000 > @@ -219,7 +219,7 @@ > { > int *scan; > REQUEST_HEADER *hdr = get_hdr(SYSTEM_STRATEGY_CON,(void **)&scan); > - BIOSDATA *bios = BIOS_DATA; > + BIOSDATA *bios = DOSVM_BiosData(); > WORD CurOfs = bios->NextKbdCharPtr; > DOS_LISTOFLISTS *lol = DOSMEM_LOL(); > DOS_DATASEG *dataseg = (DOS_DATASEG *)lol; > > > > > Index: dlls/winedos/dosexe.h > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/dosexe.h,v > retrieving revision 1.32 > diff -u -r1.32 dosexe.h > --- dlls/winedos/dosexe.h 17 Sep 2003 22:45:46 -0000 1.32 > +++ dlls/winedos/dosexe.h 27 Sep 2003 19:33:42 -0000 > @@ -100,8 +100,6 @@ > #define VIF_MASK 0x00080000 > #define VIP_MASK 0x00100000 > > -#define BIOS_DATA ((void *)0x400) > - > #define ADD_LOWORD(dw,val) ((dw) = ((dw) & 0xffff0000) | > LOWORD((DWORD)(dw)+(val))) > > /* module.c */ > @@ -123,6 +121,7 @@ > extern void WINAPI DOSVM_PIC_ioport_out( WORD port, BYTE val ); > extern void WINAPI DOSVM_SetTimer( UINT ticks ); > extern UINT WINAPI DOSVM_GetTimer( void ); > +extern BIOSDATA *DOSVM_BiosData( void ); > > /* devices.c */ > extern void DOSDEV_InstallDOSDevices(void); > > > > > Index: dlls/winedos/dosvm.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/dosvm.c,v > retrieving revision 1.52 > diff -u -r1.52 dosvm.c > --- dlls/winedos/dosvm.c 17 Sep 2003 20:23:33 -0000 1.52 > +++ dlls/winedos/dosvm.c 27 Sep 2003 19:22:28 -0000 > @@ -707,6 +707,26 @@ > > > /********************************************************************** > + * DOSVM_BiosData > + * > + * Get pointer to BIOS data area. This is not at fixed location > + * because those Win16 programs that do not use any real mode code have > + * protected NULL pointer catching block at low linear memory and > + * BIOS data has been moved to another location. > + */ > +BIOSDATA *DOSVM_BiosData( void ) > +{ > + LDT_ENTRY entry; > + FARPROC16 proc; > + > + proc = GetProcAddress16( GetModuleHandle16( "KERNEL" ), > + (LPCSTR)(ULONG_PTR)193 ); > + wine_ldt_get_entry( LOWORD(proc), &entry ); > + return (BIOSDATA *)wine_ldt_get_base( &entry ); > +} > + > + > +/********************************************************************** > * DllMain (DOSVM.Init) > */ > BOOL WINAPI DllMain( HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved ) > > > > > Index: dlls/winedos/int09.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/int09.c,v > retrieving revision 1.8 > diff -u -r1.8 int09.c > --- dlls/winedos/int09.c 5 Sep 2003 23:08:28 -0000 1.8 > +++ dlls/winedos/int09.c 27 Sep 2003 19:22:32 -0000 > @@ -150,7 +150,7 @@ > */ > void WINAPI DOSVM_Int09Handler( CONTEXT86 *context ) > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > BYTE ascii, scan = DOSVM_Int09ReadScan(&ascii); > BYTE realscan = scan & 0x7f; /* remove 0x80 make/break flag */ > BOOL modifier = FALSE; > > > > > Index: dlls/winedos/int10.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/int10.c,v > retrieving revision 1.31 > diff -u -r1.31 int10.c > --- dlls/winedos/int10.c 8 Apr 2003 19:41:03 -0000 1.31 > +++ dlls/winedos/int10.c 27 Sep 2003 19:22:37 -0000 > @@ -789,7 +789,7 @@ > */ > static void INT10_HandleVESA( CONTEXT86 *context ) > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > > switch(AL_reg(context)) { > > @@ -954,7 +954,7 @@ > */ > void WINAPI DOSVM_Int10Handler( CONTEXT86 *context ) > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > > INT10_InitializeVideoMode( data ); > > @@ -1403,7 +1403,7 @@ > */ > void WINAPI DOSVM_PutChar( BYTE ascii ) > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > unsigned xpos, ypos; > > TRACE("char: 0x%02x(%c)\n", ascii, ascii); > > > > > Index: dlls/winedos/int16.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/int16.c,v > retrieving revision 1.11 > diff -u -r1.11 int16.c > --- dlls/winedos/int16.c 2 May 2003 20:12:52 -0000 1.11 > +++ dlls/winedos/int16.c 27 Sep 2003 19:22:40 -0000 > @@ -87,7 +87,7 @@ > case 0x02: /* Get Shift Flags */ > > /* read value from BIOS data segment's keyboard status flags field */ > - data = BIOS_DATA; > + data = DOSVM_BiosData(); > SET_AL( context, data->KbdFlags1 ); > > TRACE("Get Shift Flags: returning 0x%02x\n", AL_reg(context)); > @@ -159,7 +159,7 @@ > */ > int WINAPI DOSVM_Int16ReadChar(BYTE *ascii, BYTE *scan, CONTEXT86 *waitctx) > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > WORD CurOfs = data->NextKbdCharPtr; > > /* check if there's data in buffer */ > @@ -194,7 +194,7 @@ > > int WINAPI DOSVM_Int16AddChar(BYTE ascii,BYTE scan) > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > WORD CurOfs = data->FirstKbdCharPtr; > WORD NextOfs = CurOfs + 2; > > > > > > Index: dlls/winedos/int1a.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/int1a.c,v > retrieving revision 1.3 > diff -u -r1.3 int1a.c > --- dlls/winedos/int1a.c 15 Jul 2003 20:50:34 -0000 1.3 > +++ dlls/winedos/int1a.c 27 Sep 2003 19:22:44 -0000 > @@ -40,7 +40,7 @@ > { > case 0x00: /* GET SYSTEM TIME */ > { > - BIOSDATA *data = BIOS_DATA; > + BIOSDATA *data = DOSVM_BiosData(); > SET_CX( context, HIWORD(data->Ticks) ); > SET_DX( context, LOWORD(data->Ticks) ); > SET_AL( context, 0 ); /* FIXME: midnight flag is unsupported */ > > > > > Index: dlls/winedos/timer.c > =================================================================== > RCS file: /home/wine/wine/dlls/winedos/timer.c,v > retrieving revision 1.3 > diff -u -r1.3 timer.c > --- dlls/winedos/timer.c 17 Sep 2003 22:45:46 -0000 1.3 > +++ dlls/winedos/timer.c 27 Sep 2003 19:22:48 -0000 > @@ -131,7 +131,7 @@ > */ > void WINAPI DOSVM_Int08Handler( CONTEXT86 *context ) > { > - BIOSDATA *bios_data = BIOS_DATA; > + BIOSDATA *bios_data = DOSVM_BiosData(); > CONTEXT86 nested_context = *context; > FARPROC16 int1c_proc = DOSVM_GetRMHandler( 0x1c ); > > > > > -- > Jukka Heinonen <http://www.iki.fi/jhei/> >

1 0

How to run program without wine ?
by flyker 28 Sep '03

28 Sep '03

Can i compile my program to executable file that can be run without wine ?

6 8

Re: PATCH: stop crashes in desktop mode
by Dimitrie O. Paun 28 Sep '03

28 Sep '03

On September 27, 2003 11:41 pm, Alex Pasadyn wrote: > + ERR("CWSibling specified, but\n"); > + ERR(" parent1 = %lx\n", parent_ret); > + ERR(" parent2 = %lx\n", parent2_ret); > + ERR(" --> ignoring CWSibling\n"); If you split error messages like this, they can get messed up by different threads. Besides, it is not common idiom, we don't usually have such things. It is best avoided. -- Dimi.

1 0

Re: interactive dsound tests fail && winealsa problem
by Sylvain Petreolle 27 Sep '03

27 Sep '03

Thanks for your recent patches. Now OSS dsound test is ok, only capture tests fail. alsa dsound test fail : it hangs in emulated acceleration mode and give circa 90 Mb log without emulation. ===== 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

1 0

documentation/status
by Eric Pouech 27 Sep '03

27 Sep '03

as Dimi is cleaning documentation/status out, documentation/status/dde is completly out of date, and can be simply removed. (and documentation/status as well) A+ -- Eric Pouech

2 1

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

27 Sep '03

> -----Original Message----- > From: wine-cvs-admin(a)winehq.com [mailto:wine-cvs-admin@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 27 Sep '03

27 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 26 Sep '03

26 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

Re: new shlwapi tests
by Alexandre Julliard 25 Sep '03

25 Sep '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > +static const StrFormatSizeResult StrFormatSize_results[] = { > + { -1023, "-1023 bytes", "0 KB"}, > + { -24, "-24 bytes", "0 KB"}, > + { 309, "309 bytes", "1 KB"}, > + { 10191, "9.95 KB", "10 KB"}, > + { 100353, "98.0 KB", "99 KB"}, > + { 1022286, "998 KB", "999 KB"}, > + { 1046862, "0.99 MB", "1,023 KB"}, > + { 1048574619, "999 MB", "1,023,999 KB"}, > + { 1073741775, "0.99 GB", "1,048,576 KB"}, > + { 1073741822286, "999 GB", "1,048,575,999 KB"}, > + { 1099511626395, "0.99 TB", "1,073,741,823 KB"}, > + { 1099511627774619, "999 TB", "1,073,741,823,999 KB"}, > + { 1125899906841576, "0.99 PB", "1,099,511,627,775 KB"}, > + { 1125899906842623285, "999 PB", "1,099,511,627,776,000 KB"}, > + { 1152921504606845595, "0.99 EB", "1,125,899,906,842,623 KB"}, Please don't use long long constants, that's not portable, they should be computed instead. Check the ntdll tests for how this can be done. -- Alexandre Julliard julliard(a)winehq.com

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel