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

Re: CxxFrameHandler problem
by John K. Hohm April 11, 2003

April 11, 2003

Alexandre Julliard <julliard(a)winehq.com> wrote: > Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > > > Appended program uses CxxFrameHandler and crashes in wine with builtin > > msvcrt, but not with native. Compile as Release version and include the > MFC > > dll. Can somebody compile for Alexandre? Alexandre, is this a start or do > > you need something complete? > > That's a start, yes, thanks. I'll need a more complete example with > nested try blocks, destructors all over the place, typed exceptions, > etc. to make sure I understand all the compiler internal structures; > but I can at least try to make that simple case not crash... Although this may duplicate effort, I am familiar with several strange combinations of exception handling that I know work with Visual C++ 6.0; I will put them a test program for you. You can never have too many test programs, right?

1 1

Right button clicks
by Fabian Cenedese Sept. 18, 2002

Sept. 18, 2002

Hi Does Wine support right mouse button double clicks? I have an App with a dialog (in fact an overridden MFC CDialog for about infos) in which I can double click with the right mouse button to show some additional info. But they never show up. After +relay tracing the messages I found that only WM_RBUTTONDOWN and WM_RBUTTONUP messages are generated, none of them get converted into clicks or even double clicks, no matter how fast I click. Does anyone have an idea? Thanks Fabi

2 3

Re: Wine Hides On-board RAM
by Ian D. Stewart Sept. 16, 2002

Sept. 16, 2002

On 2002.08.18 12:21 Andreas Mohr wrote: > On Sun, Aug 18, 2002 at 11:32:54AM -0400, Ian D. Stewart wrote: > > I have recently noticed an unusual side-effect of running Wine. > When I > > first start up my system, /proc/meminfo reports MemTotal as 256892 > kb. > > After running Wine for awhile, /proc/meminfo reports MemTotal as > 32680 > > kb. The system performs as if it only had 32 MB of RAM. A reboot > of > > the system resets total memory to the proper value. > > > > My question is: > > > > 1) Has anybody else encountered this? > > 2) Does anyone know what causes this, or better yet how to avoid it? > > 3) Is there anyway to recover the lost RAM short of a reboot? > > Huh ? This is very, very, VERY strange ! > Something like this should never happen. > Are you sure it's caused by Wine only, or maybe it is due to faulty > memory > instead ? (and thus the board/Linux notices that only 32MB are useable > and resorts to accessing 32MB only). Well I can't say with absolute certainty that it's caused by Wine, but the system runs without any problems for extended periods of time so long as I don't run Wine, and consistently 'loses' memory when I *do* run wine. I don't know exactly what's going on. I do know that there appears to be some sort of threshold that is reached at which point the memory hiding occurs (e.g., the same issue arises whether I run Wine for 5 hours at one shot or for 30 minutes a day for 10 days) and the threshold isn't 'reset' until I reboot. > > Again, I'm utterly puzzled when hearing such a story. > Or maybe Wine accesses some Linux memory management function in some > way > that causes Linux to tamper with the value for some reason ? > This wouldn't be the first time that Wine is the only program to > reveal > some severe bug in Linux memory management... > > Definitely try upgrading your kernel, too. I have no problem with upgrading, but I would like to know *why* I am upgrading (i.e., what bug is causing the problem, and how does the new kernel address the bug). To do otherwise strikes me as being equivelant to the tendency in the Windows community whenever something odd happens. Thanx for the input, Andreas. Ian

5 8

Re: Re:can windows be reparented?
by Dmitry Timoshkov Sept. 13, 2002

Sept. 13, 2002

<us(a)the-edmeades.demon.co.uk> wrote: > To be honest I never investigated further once I commented out the SetParent call, > as I was continuing to fix oleaut32 and left the gui side to someone else! > > I know it was being called in the failing case, and removing it allowed the > windows to pop up, BUT they were still wrong as you could access the 'parent' > whereas you should not be able to Could you please test patch posted by Bill Medland to wine-patches today? It's not entirely correct though. My tests show that SetWindowLong(GWL_HWNDPARENT) call changes simultaneously both parent and owner for top level windows and returns old value (not sure old owner or parent it is). But top level windows created by Visual Vasic are special: they have no parent, but only owner according to Spy++. In my tests I can't reproduce it yet. A bit of investigation of Wine source revealed that some places use GetAncestor(hwnd, GA_PARENT), while others use GetParent(hwnd). Since their behaviour is different in respect of top level and child windows, some major clean up in that area in Wine is needed. -- Dmitry.

4 5

re: RFC: 'test' bugzilla keyword
by Dan Kegel Sept. 9, 2002

Sept. 9, 2002

Francois Gouget wrote: > if we make it easy to track > conformance test issues in Bugzilla, we may get new contributers (sure I > realize it's not a magic bullet either). Thus I propose to add a 'test' > keyword to make it easy to find such issues in bugzilla for people > specifically interested in conformance tests. Excellent idea. The keyword 'test' might be a bit confusing -- some bug tracking systems use that word as a state. How about something short that has very few hits on Google? Like, um, "apifail" or "unitfail"? - Dan

4 6

[PATCH] winemaker fixes
by Martin Wilck Sept. 9, 2002

Sept. 9, 2002

Hi, the patch below fixes a few things in winemaker. It seems to work with my app, but needs more testing, especially for MFC apps. Modified files: tools: winemaker documentation: winemaker.man Changelog: - adapt winemaker to the new way winebuild handles imports. - fix crashes due to winemaker-generated wrapper app closing libraries (is this one correct??) - Fix some minor bugs in the wrapper.c template. - change semantics of --nomfc option such that it overrides automatic setting of --mfc if stdafx.h or stdafx.cpp are found. (this may cause problems to some people. For me the old behaviour was a pain in the neck, because VC++ generates stdafx.h always, even for pure C projects). Feedback, please ! - Add --nodlls option to suppress auto-generated import list for simple apps. - Adapt man page. -- 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 Index: tools/winemaker =================================================================== RCS file: /home/wine/wine/tools/winemaker,v retrieving revision 1.39 diff -u -r1.39 winemaker --- tools/winemaker 14 Apr 2002 19:31:23 -0000 1.39 +++ tools/winemaker 22 May 2002 16:49:18 -0000 @@ -233,6 +233,14 @@ my $TF_MFC=4; ## +# User has specified --nomfc option for this target or globally +my $TF_NOMFC=8; + +## +# --nodlls option: Do not use standard DLL set +my $TF_NODLLS=16; + +## # Initialize a target: # - set the target type to TT_SETTINGS, i.e. no real target will # be generated. @@ -435,23 +443,37 @@ push @{@$target[$T_LIBRARY_PATH]},$option; } elsif ($option =~ /^-l/) { push @{@$target[$T_LIBRARIES]},"$'"; - } elsif (@$target[$T_TYPE] != $TT_DLL and $option =~ /^--wrap/) { - @$target[$T_FLAGS]|=$TF_WRAP; - } elsif (@$target[$T_TYPE] != $TT_DLL and $option =~ /^--nowrap/) { - @$target[$T_FLAGS]&=~$TF_WRAP; - } elsif ($option =~ /^--mfc/) { - @$target[$T_FLAGS]|=$TF_MFC; + } elsif ($option =~ /^--wrap/) { if (@$target[$T_TYPE] != $TT_DLL) { @$target[$T_FLAGS]|=$TF_WRAP; + } else { + print STDERR "warning: option --wrap is illegal for DLLs - ignoring"; + }; + } elsif ($option =~ /^--nowrap/) { + if (@$target[$T_TYPE] != $TT_DLL) { + @$target[$T_FLAGS]&=~$TF_WRAP; + } else { + print STDERR "warning: option --nowrap is illegal for DLLs - ignoring"; } + } elsif ($option =~ /^--mfc/) { + @$target[$T_FLAGS]|=$TF_MFC; + @$target[$T_FLAGS]&=~$TF_NOMFC; } elsif ($option =~ /^--nomfc/) { @$target[$T_FLAGS]&=~$TF_MFC; - @$target[$T_FLAGS]&=~($TF_MFC|$TF_WRAP); + @$target[$T_FLAGS]|=$TF_NOMFC; + } elsif ($option =~ /^--nodlls/) { + @$target[$T_FLAGS]|=$TF_NODLLS; } else { print STDERR "error: unknown option \"$option\"\n"; return 0; } } + if (@$target[$T_TYPE] != $TT_DLL && + @$target[$T_FLAGS] & $TF_MFC && + !(@$target[$T_FLAGS] & $TF_WRAP)) { + print STDERR "info: option --mfc requires --wrap"; + @$target[$T_FLAGS]|=$TF_WRAP; + } return 1; } @@ -541,7 +563,7 @@ } elsif ($dentry =~ /\.c$/i and $dentry !~ /\.spec\.c$/) { push @sources_c,"$dentry"; } elsif ($dentry =~ /\.(cpp|cxx)$/i) { - if ($dentry =~ /^stdafx.cpp$/i) { + if ($dentry =~ /^stdafx.cpp$/i && !(@$project_settings[$T_FLAGS] & $TF_NOMFC)) { push @sources_misc,"$dentry"; @$project_settings[$T_FLAGS]|=$TF_MFC; } else { @@ -551,7 +573,7 @@ push @sources_rc,"$dentry"; } elsif ($dentry =~ /\.(h|hxx|hpp|inl|rc2|dlg)$/i) { push @sources_misc,"$dentry"; - if ($dentry =~ /^stdafx.h$/i) { + if ($dentry =~ /^stdafx.h$/i && !(@$project_settings[$T_FLAGS] & $TF_NOMFC)) { @$project_settings[$T_FLAGS]|=$TF_MFC; } } elsif ($dentry =~ /\.dsp$/i) { @@ -774,10 +796,13 @@ push @exe_list,$target; } # This is the default link list of Visual Studio, except odbccp32 - # which we don't have in Wine. Also I add ntdll which seems - # necessary for Winelib. - my @std_dlls=qw(advapi32.dll comdlg32.dll gdi32.dll kernel32.dll ntdll.dll odbc32.dll ole32.dll oleaut32.dll shell32.dll user32.dll winspool.drv); - @$target[$T_DLLS]=\@std_dlls; + # which we don't have in Wine. + my @std_dlls=qw(advapi32.dll comdlg32.dll gdi32.dll kernel32.dll odbc32.dll ole32.dll oleaut32.dll shell32.dll user32.dll winspool.drv); + if (@$target[$T_FLAGS] & $TF_NODLLS == 0) { + @$target[$T_DLLS]=\@std_dlls; + } else { + $target[$T_DLLS]=[]; + } push @{@$project[$P_TARGETS]},$target; # Ask for target-specific options @@ -982,7 +1007,8 @@ @$wrapper[$T_TYPE]=@$target[$T_TYPE]; @$wrapper[$T_INIT]=get_default_init(@$target[$T_TYPE]); @$wrapper[$T_FLAGS]=$TF_WRAPPER | (@$target[$T_FLAGS] & $TF_MFC); - @$wrapper[$T_DLLS]=[ "kernel32.dll", "ntdll.dll", "user32.dll" ]; + @$wrapper[$T_DLLS]=[ "kernel32.dll", "user32.dll" ]; + push @{@$wrapper[$T_LIBRARIES]}, "dl"; push @{@$wrapper[$T_SOURCES_C]},"@$wrapper[$T_NAME]_wrapper.c"; my $index=bsearch(@$target[$T_SOURCES_C],"@$wrapper[$T_NAME]_wrapper.c"); @@ -1634,32 +1660,10 @@ $rcname =~ s+([^/\w])+\\$1+g; print FILEO "rsrc $rcname.res\n"; } - print FILEO "\n"; - my %dlls; - foreach $dll (@{$global_settings[$T_DLLS]}) { - if (!defined $dlls{$dll}) { - print FILEO "import $dll\n"; - $dlls{$dll}=1; - } - } - if (defined $project_settings) { - foreach $dll (@{@$project_settings[$T_DLLS]}) { - if (!defined $dlls{$dll}) { - print FILEO "import $dll\n"; - $dlls{$dll}=1; - } - } - } - foreach $dll (@{@$target[$T_DLLS]}) { - if (!defined $dlls{$dll}) { - print FILEO "import $dll\n"; - $dlls{$dll}=1; - } - } # Don't forget to export the 'Main' function for wrapped executables, # except for MFC ones! - if (@$target[$T_FLAGS] == $TF_WRAP) { + if ((@$target[$T_FLAGS]&($TF_WRAP|$TF_WRAPPER|$TF_MFC)) == $TF_WRAP) { if (@$target[$T_TYPE] == $TT_GUIEXE) { print FILEO "\n@ stdcall @$target[$T_INIT](long long ptr long) @$target[$T_INIT]\n"; } elsif (@$target[$T_TYPE] == $TT_CUIEXE) { @@ -1867,6 +1871,7 @@ generate_list("${canon}_LIBRARY_PATH",1,@$target[$T_LIBRARY_PATH]); generate_list("${canon}_LIBRARIES",1,@$target[$T_LIBRARIES]); generate_list("${canon}_DEPENDS",1,@$target[$T_DEPENDS]); + generate_list("${canon}_IMPORTS",1,@$target[$T_DLLS]); print FILEO "\n"; generate_list("${canon}_OBJS",1,["\$(${canon}_C_SRCS:.c=.o)","\$(${canon}_CXX_SRCS:.cpp=.o)","\$(EXTRA_OBJS)"]); print FILEO "\n\n\n"; @@ -1952,7 +1957,7 @@ print FILEO "\t-\$(STRIP) \$(STRIPFLAGS) \$\@\n"; print FILEO "\n"; print FILEO "\$(${canon}_SPEC_SRCS:.spec=.spec.c): \$(${canon}_SPEC_SRCS) \$(${canon}_SPEC_SRCS:.spec=.tmp.o) \$(${canon}_RC_SRCS:.rc=.res)\n"; - print FILEO "\t\$(LD_PATH) \$(WINEBUILD) -fPIC \$(${canon}_DLL_PATH) \$(WINE_DLL_PATH) -sym \$(${canon}_SPEC_SRCS:.spec=.tmp.o) -o \$\@ -spec \$(SRCDIR)/\$(${canon}_SPEC_SRCS)\n"; + print FILEO "\t\$(LD_PATH) \$(WINEBUILD) -fPIC \$(${canon}_DLL_PATH) \$(WINE_DLL_PATH) -sym \$(${canon}_SPEC_SRCS:.spec=.tmp.o) -o \$\@ -spec \$(SRCDIR)/\$(${canon}_SPEC_SRCS) \$(${canon}_IMPORTS:%=-l%)\n"; print FILEO "\n"; my $t_name=@$target[$T_NAME]; if (@$target[$T_TYPE]!=$TT_DLL) { @@ -2168,7 +2173,7 @@ print STDERR "Usage: winemaker [--nobanner] [--backup|--nobackup] [--nosource-fix]\n"; print STDERR " [--lower-none|--lower-all|--lower-uppercase]\n"; print STDERR " [--lower-include|--nolower-include]\n"; - print STDERR " [--guiexe|--windows|--cuiexe|--console|--dll]\n"; + print STDERR " [--guiexe|--windows|--cuiexe|--console|--dll|--nodlls]\n"; print STDERR " [--wrap|--nowrap] [--mfc|--nomfc]\n"; print STDERR " [-Dmacro[=defn]] [-Idir] [-Pdir] [-idll] [-Ldir] [-llibrary]\n"; print STDERR " [--interactive] [--single-target name]\n"; @@ -2181,9 +2186,6 @@ exit (2); } - -project_init(\@main_project,""); - while (@ARGV>0) { my $arg=shift @ARGV; # General options @@ -2244,11 +2246,13 @@ $opt_flags&=~$TF_WRAP; } elsif ($arg eq "--mfc") { $opt_flags|=$TF_MFC; - $opt_flags|=$TF_MFC|$TF_WRAP; $needs_mfc=1; } elsif ($arg eq "--nomfc") { - $opt_flags&=~($TF_MFC|$TF_WRAP); + $opt_flags&=~$TF_MFC; + $opt_flags|=$TF_NOMFC; $needs_mfc=0; + } elsif ($arg eq "--nodlls") { + $opt_flags|=$TF_NODLLS; # Catch errors } else { @@ -2263,6 +2267,11 @@ usage(); } } + + if ($opt_flags & $TF_MFC && $opt_target_type != $TT_DLL) { + print STDERR "info: option --mfc requires --wrap\n"; + $opt_flags |= $TF_WRAP; + }; } if (!defined $opt_work_dir) { @@ -2278,6 +2287,8 @@ print_banner(); } +project_init(\@main_project,""); + # Fix the file and directory names fix_file_and_directory_names("."); @@ -3094,6 +3105,8 @@ * This is either CUIEXE for a console based application or * GUIEXE for a regular windows application. */ +#define GUIEXE 0 +#define CUIEXE 1 #define APP_TYPE ##WINEMAKER_APP_TYPE## /** @@ -3138,11 +3151,11 @@ int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, PSTR szCmdLine, int iCmdShow) #else -int WINAPI Main(int argc, char** argv, char** envp) +int WINAPI main(int argc, char** argv, char** envp) #endif { void* appLibrary; - HINSTANCE hApp,hMFC,hMain; + HINSTANCE hApp = 0, hMFC = 0, hMain = 0; void* appMain; char* libName; int retcode; @@ -3212,7 +3225,7 @@ } /* Get the address of the application's entry point */ - appMain=(WinMainFunc*)GetProcAddress(hMain, appInit); + appMain=GetProcAddress(hMain, appInit); if (appMain==NULL) { char format[]="Could not get the address of %s (%d)"; char* msg; @@ -3232,11 +3245,6 @@ #endif /* Cleanup and done */ - FreeLibrary(hApp); - if (hMFC!=NULL) { - FreeLibrary(hMFC); - } - dlclose(appLibrary); free(libName); return retcode; Index: documentation/winemaker.man =================================================================== RCS file: /home/wine/wine/documentation/winemaker.man,v retrieving revision 1.5 diff -u -r1.5 winemaker.man --- documentation/winemaker.man 2 Oct 2001 17:47:34 -0000 1.5 +++ documentation/winemaker.man 22 May 2002 16:49:19 -0000 @@ -17,7 +17,7 @@ ] .br [ -.IR "--guiexe " "| " "--windows " "| " "--cuiexe " "| " "--console " "| " "--dll " +.IR "--guiexe " "| " "--windows " "| " "--cuiexe " "| " "--console " "| " "--dll " "| " "--nodlls " ] .br [ @@ -121,6 +121,14 @@ i.e. for which it does not know whether it is an executable or a library, it should assume it is a library. .TP +.I --nodlls +This option tells winemaker not to use the standard set of winelib libraries +for imports. That is, any DLL your code uses must be explicitly passed to +winemaker with -i options. +The standard set of libraries is: advapi32.dll, comdlg32.dll, gdi32.dll, +kernel32.dll, odbc32.dll, ole32.dll, oleaut32.dll, shell32.dll, user32.dll, +winspool.drv. +.TP .I --wrap Specifies that executable targets should be built as libraries and a small executable wrapper generated for them. This technique is sometimes required @@ -137,7 +145,9 @@ generates wrappers for these targets that are executables. .TP .I --nomfc -Specifies that targets are not MFC-based. This is the default. +Specifies that targets are not MFC-based. This option disables use of MFC libraries +even if winemaker encounters files "stdafx.cpp" or "stdafx.h" that would cause it +to enable MFC automatically if neither --nomfc nor --mfc was specified. .TP .I -Dmacro[=defn] Adds the specified macro definition to the global list of macro definitions. @@ -149,8 +159,7 @@ Appends the specified directory to the global library path. .TP .I -idll -Adds the Winelib library to the global list of Winelib libraries to import -in the spec file. +Adds the Winelib library to the global list of Winelib libraries to import. .TP .I -llibrary Adds the specified library to the global list of libraries to link with.

2 5

Press: Running Windows Games with WineX 2.1
by Francois Gouget Sept. 8, 2002

Sept. 8, 2002

* August 29, 2002 - LinuxOrbit Break out Your Games Library: Running Windows Games with WineX 2.1 http://www.linuxorbit.com/modules.php?op=modload&name=Reviews&file=index&re… -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ War doesn't determine who's right. War determines who's left.

3 5

Problem with regression tests getting stuck
by Paul Millar Sept. 4, 2002

Sept. 4, 2002

Hi everyone, I've had the regression tests freeze on me again (see [1] for previous report). Sylvain has reported problems with the wininet regression tests (described in [2]). The symptoms are the same, but for me the problem is only intermittent. This time I caught the problem with gdb and obtained the following info: [...] Loaded symbols for /lib/libresolv.so.2 0x402e7744 in __libc_close () at __libc_close:-1 -1 __libc_close: No such file or directory. in __libc_close (gdb) bt #0 0x402e7744 in __libc_close () at __libc_close:-1 #1 0x400ec9a4 in __DTOR_END__ () from /home/paulm/WINE-cvs/wine/dlls/libntdll.dll.so #2 0x400b3df5 in WaitForMultipleObjectsEx (count=0, handles=0x0, wait_all=0, timeout=100, alertable=0) at ../../scheduler/synchro.c:257 #3 0x400b3b88 in Sleep (timeout=100) at ../../scheduler/synchro.c:178 #4 0x40358747 in winapi_test (flags=268435456) at tests/http.c:121 #5 0x40358b36 in func_http () at tests/http.c:184 #6 0x40358f9d in run_test (name=0xbffffc63 "http.c") at wtmain.c:244 #7 0x40357037 in __wine_exe_main () at wininet_test.exe.spec.c:133 #8 0x400aff84 in start_process () at ../../scheduler/process.c:528 #9 0x400b3f3f in call_on_thread_stack (func=0x400afd2c) at ../../scheduler/sysdeps.c:108 So, to summarise (with some extra bits of information): The problem occurs when wininet/tests/http.c is testing asynchronous HttpSendRequest(), so flags > 0. The problem is triggered at line 121 of http.c, i.e.: 120 while ((flags)&&(!goon)) 121 Sleep(100); Sleep(), in turn, just calls WaitForMultipleObjectsEx(). From scheduler/synchro.c: 176 VOID WINAPI Sleep( DWORD timeout ) 177 { 178 WaitForMultipleObjectsEx( 0, NULL, FALSE, timeout, FALSE ); 179 } WaitForMultipleObjectsEx() has problems when it gets to 257: 256 SERVER_END_REQ; 257 if (ret == STATUS_PENDING) ret = wait_reply( &cookie ); 258 if (ret != STATUS_USER_APC) break; ret is 1079729528, btw. AFAIK, __DTOR_END__ (see near bottom of stack) is the destructor for a function call in ntdll. I'm probably missing something obvious, but I don't see the connection between scheduler/synchro.c:257 and ntdll. The closest is wait_reply() (in scheduler/client.c) calls wait_reply_data (in same file), which calls NtCurrentTeb(), which is commented as an NTDLL function. But there doesn't seem to be an implementation of NtCurrentTeb in ntdll. Any ideas? Cheers, Paul. [1] http://www.winehq.com/hypermail/wine-devel/2002/08/0006.html [2] http://www.winehq.com/hypermail/wine-devel/2002/07/0386.html PS, I'll create a bugzilla in a bit. ---- Paul Millar

2 4

Quartz DLL
by tom Sept. 3, 2002

Sept. 3, 2002

Hello, I was looking at the WineX cvs version on sourceforge and it looks as if they have a quartz.dll based on ffmpeg. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/winex/wine/dlls/quartz/ What are the odd's of this work being put into the main wine tree ? As the old quartz.dll got pulled........ Tom

6 6

ALSA 0.9 sound problems
by TJ Sept. 2, 2002

Sept. 2, 2002

Hi =) I have ALSA 0.9 with OSS compat modules. I recently got DeusEx to run (on Wine w/ openGL, not talking about WineX) However using winealsa.drv sound is very laggy and lots of nasty clicks and hissing occurs, but if I use wineoss.drv sound is fine?? (note OSS driver will be talking to ALSA via the snd-pcm-oss compat module) Also when using the wineoss module and the game (not just DeusEx but most games I got working) is setting up sound it seems to freeze, all i do then is ctrl+z, fg, in controling term and things run fine from then on. -TJ

3 4

winedbg
by admiral coeyman Sept. 1, 2002

Sept. 1, 2002

Group, I am not the only developer who has trouble reading the wine debugger screen. The solution which was pointed out will not work for me since I do not run wine that way. We should have a real solution rather than one that is bodged together anyway. What I'm getting at is, are any developers already working on making the debugger screen more readable? Since I cannot do much until this is fixed, I'll take a crack at it if somebody can give me some pointers on changing the concole appearance settings, size/font/etc. Ideally, I'd like this to be controlled by a few variables in the wine configuration file, or registry so that they can be adjusted. My personal preference would be to redirect the debugger to an unsued virtual terminal because I can read those. God Bless, --Robert 'Admiral' Coeyman -- --- May you live as long as you wish and age but a single day. http://www.dotguy.net/ admiral(a)corner.net Webmaster/ Linux Administrator Computer Co-Op/CornerNet

2 3

ReactOS PSAPI released as LGPL
by Steven Edwards Aug. 31, 2002

Aug. 31, 2002

Hi all. To help share code with WINE I have asked some of the ReactOS developers to license thier work as LGPL where possible. ReactOS is distributed under the GPL with certain sources being LGPL or X11/BSD. In case anyone wants to work on PSAPI in wine feel free to leech whatever. I will keep wine-devel up to date if anything else is relicensed. CVSROOT: /CVS/ReactOS Module name: reactos Repository: reactos/lib/psapi/misc/ Changes by: hyperion(a)mok.lvcm.com 02/08/31 08:36:56 Modified files: reactos/lib/psapi/misc/: dllmain.c malloc.c win32.c reactos/lib/psapi/: psapi.def psapi.edf reactos/lib/psapi/enum/: module.c process.c reactos/lib/psapi/include/internal/: psapi.h reactos/lib/psapi/: makefile psapi.def psapi.edf reactos/lib/psapi/misc/: stubs.c win32.c Log message: PSAPI: all the annoying stuff (enumeration and search, basically) has been taken care of. Only profiling remains to be implemented. PSAPI (re)licensed under LGPL to be shared with WinE, as per Steven's request. Interfaces (headers and import library definitions) and trivial sources put in the public domain Check out the subsystem-independent routines in enum/ (FWIW: the whole DLL only imports two calls from kernel32.dll, SetLastError and AreFileApisANSI): they've been tested, and they could make for a great static library, to implement task manager, tlist, ToolHelp API, etc. Maybe a future addition to mingwnt? __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

1 0

removing mp3 code
by Marcus Meissner Aug. 31, 2002

Aug. 31, 2002

Hi, Apparently distributing even mp3 decoders is not royaltee free anymore, according to the slashdot thread and the Thomson MultiMedia pages. So we probably should remove the msacm mp3 decoder we include. :( Ciao, Marcus

8 10

quartz.dll
by Hidenori Takeshima Aug. 31, 2002

Aug. 31, 2002

I'm original developer of quartz. I don't want my quartz code to be restored. There seems to be many patented algorythms. Many codecs like MPEG-1/2/4 are patented. The ffmpeg library seems to use many patented codes. And the legal state of quartz interfaces is unclear for me. I can't accept any liability. Please add all codes in CVS explicitly: The code has been removed since the original author requests 'please remove my quartz codes' explicitly. The original author don't accept any liability. __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

2 2

Re: PATCH: rename WIN_Handle{16,32} to HWND_{16,32}
by Alexandre Julliard Aug. 31, 2002

Aug. 31, 2002

Michael Stefaniuc <mstefani(a)redhat.de> writes: > - rename WIN_Handle{16,32} to HWND_{16,32} to make it consistent > with the other handle <--> handle16 macros I think you should keep WIN_Handle32 as it is, to make it clear that it does more that simply cast the handle to the right type. Especially since we will need an HWND_32 macro in other dlls that does what its name suggests. Otherwise it's going to be very confusing to have HWND_32 be sometimes a simple macro and sometimes a complex function. -- Alexandre Julliard julliard(a)winehq.com

1 0

MYOB 3.5.2 autorun
by Anand Kumria Aug. 31, 2002

Aug. 31, 2002

I just tried out MYOB (a popular financial program used widely in Australia). The autorun program on the CD attempts to start programs using WinExec as WinExec("whatnews\\whatnews.exe") Unfortunately the FILE_contains_pathW function belueves that is a full path which causes (in files/directory.c): if (FILE_contains_pathW(name)) { ret = DOSFS_GetFullName( name, TRUE, full_name ); goto done; } to fail and return an error to WinExec and subsequently not do anything. The below patch fixes this problem (for me) and lets me install a number of ancillory programs. Unfortunately MYOB install uses InstallShield6 as its installer, so I've had no success with the actual program. Is there a better way to do this patch? Thanks, Anand -- `` We are shaped by our thoughts, we become what we think. When the mind is pure, joy follows like a shadow that never leaves. '' -- Buddha, The Dhammapada --- files/directory.c Sun Sep 1 01:27:00 2002 +++ files/directory.c Sun Sep 1 01:26:02 2002 @@ -821,12 +821,11 @@ } /* If the name contains an explicit path, everything's easy */ + /* But only jump if we successfully found it */ - if (FILE_contains_pathW(name)) - { - ret = DOSFS_GetFullName( name, TRUE, full_name ); + if ( FILE_contains_pathW(name) && + DOSFS_GetFullName(name, TRUE, full_name) ) goto done; - } /* Search in the specified path */

1 0

Re: seg fault compiling wine
by Sebastian 'yath' Schmidt Aug. 31, 2002

Aug. 31, 2002

On Tue, May 07, 2002 at 08:40:20PM -0500, Mason Kidd wrote: > Hi everyone, Hi, > I'm getting a segmentation fault compiling wine. This is the error > message: > [...] I got the same error. > wine-20020411 release of wine and got the same error. I am assuming > that > there is something wrong with my setup, because I compiled the CVS > source about 2 weeks ago without problems, which was after the > wine-20020411 release. Any ideas? It seems the configure-script is broken; it detects mmap64(), but there isn't mmap64(). So size_t gets 32 bits and off_t 64 bits. fstat() returns a structure with a member of type off_t, which is handed over to mmap(), which wants a size_t. mmap() gets 0 as size, returns a NULL-pointer, and in check_header(), where get_dword() the program receives a segmentation fault. Fix: change the "#define _FILE_OFFSET_BITS 64" in config.h to "#undef _FILE_OFFSET_BITS" and recompile. Sebastian -- pub 1024D/5A13B048 2001-08-28 Sebastian Schmidt (yath) <yathen(a)web.de> Key fingerprint = 8D25 C96B 3DE0 C7D0 AE01 6824 BC15 6273 5A13 B048 VI VI VI The editor of the beast.

1 0

Re: Wine Ma os X port
by Francois Gouget Aug. 30, 2002

Aug. 30, 2002

On Wed, 28 Aug 2002, Lionel Ulmer wrote: [...] > Anyway, if you do that, you would need to simulate also a full Linux kernel > on this emulator (as otherwise, on what system would emulated Wine run). Not necessarily. What you propose to do for Wine can be done for the C and X11 libraries. Then you get an emulator that lets you run x86 Linux applications on a PPC machine... including Wine. It is similar, though more complex, to FreeBSD's Linux emulation mode. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ $live{free} || die "";

2 3

Re: Check accelerator descriptions in CreateAcceleratorTableA
by Vincent Béron Aug. 30, 2002

Aug. 30, 2002

Le mar 13/08/2002 à 09:52, Steven K. a écrit : > Was looking for something to get me started with Wine, > and a message kept coming up that accelerator > descriptions should be checked in > CreateAcceleratorTableA, this is a patch to hopefully > do that. Like I say this is my first, so please be > gentle with me ;) > > Changelog: > Check accelerator descriptions are valid in > CreateAcceleratorTableA. > Please use the -u option for diff (normal diff or cvs diff). It's much easier to merge should somebody else had also changed the file, and it's the only format that Alexandre will accept anyway :) If you use cvs diff, you can add it to your .cvsrc as "diff -u". Vincent

2 1

trying to draw off-screen
by Bill Medland Aug. 30, 2002

Aug. 30, 2002

Does anyone know who constrains a window to be on the screen? Our application, in order to minimise flicker, does the hard work with a container application deliberately positioned well off-screen (enormous negative coordinates I think). This works under Windows. However under WINE the initial window appears in the top right corner of my screen (I think I've seen it appear in other corners too on other computers). It then resizes , keeping the same top left corner (with parts of the window off-screen) before correctly repositioning itself into the middle of the screen. Does anyone know which code is doing the initial positioning in the top right corner? Is this deliberate? Bill

2 2

wine regression - win16 file read problem!?
by Rizsanyi Zsolt Aug. 30, 2002

Aug. 30, 2002

Hi! I have recently upgraded wine cvs and done a recompile and install. But now one of the programs I'm using does not work. My last cvs update was about 2 weeks ago. Its an old dictionary program (win16). It starts up ok, but when it tries to open the dictionary data, it says, that it is not found, and I should specify a location. I have looked at the +file debug channel output, and it does not even contain the location I have specified. Does that mean, that it does not even tries to open the file? Does somebody has some ideas where the problem could come from? Or which debug channel should I turn on to get some info about the problem? I just would like to ask for ideas before I start more serious debugging... Thanks Zsolt

1 0

Re: Wine Status
by Andriy Palamarchuk Aug. 30, 2002

Aug. 30, 2002

[skipped] > I am new to the Wine Project and I am in need of some > assistance to make > sure all changes are corrct and accurate. > Over the next week or so I plan to read over the change > log's for the > last year > so I will have a feel of the changes that have been > made. A couple of good sources of information about changes in Wine: 1) Wine Weekly News articles http://www.winehq.com 2) Notes in the release ANNOUNCE file http://cvs.winehq.com/cvsweb/wine/ANNOUNCE Good luck, Andriy Boston, MA, USA __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

3 2

Re: DOSFS_FindUnixName and "unix" filesystem (was: Re: (HELP) ...)
by Duane Clark Aug. 30, 2002

Aug. 30, 2002

Martin Wilck wrote: > > In any case this is relatively minor and we can live without. If we > don't patch, we need to be prepared that other people stumble into the > problem I had, though. I am still feeling dumb - my wine development was > practically stuck for 2 months because of that "wine" file. Since I also was stumbled for a long period on a similar problem, due to specifying a "unix" filesystem, perhaps it would be appropriate in the documentation to put some large warnings on that option.

3 3

RE: Added H_SRCS (used by msvcmaker)
by Patrik Stridvall Aug. 29, 2002

Aug. 29, 2002

> Patrik Stridvall <ps(a)leissner.se> writes: > > > Perhaps files such as include/winuser.h should be included > > for USER32 for example? > > > > Anyway what do you think about adding H_SRCS to > > every Makefile.in file? > > I don't think we want that, especially if you want to add all relevant > includes it's going to be a nightmare to maintain. Yes, I'm a little worried about that myself, but then the C_SRCS doesn't change that often and the H_SRCS are likely to change MUCH less. Futhermore it doesn't really matter if it out out sync either. If somebody developing in MSVC misses a file he can add it. It not like Wine won't build correctly. > And make depend (or > some perl equivalent) can easily determine that information for you. Well, if you just want all .h files the DLL depends on MSVC already have that in a automatically generated "folder" called External dependencies. The H_SRCS is mostly for the .h files that you are likely to want to look at or modify while developing the DLL under MSVC. But it is not strictly nessary. It is more a convenience sort of thing. Another reason that I proposed it is that maybe H_SRCS could be used fo something else though I can't think of anything right now... But sure I can search for the .h files in the director{y,ies} of each DLL. However for a DLL like ntdll files like include/wine/exception.h is very much relevent and won't be included is such a case. Not that it really matters that much but still...

1 0

Re: Added H_SRCS (used by msvcmaker)
by Alexandre Julliard Aug. 29, 2002

Aug. 29, 2002

Patrik Stridvall <ps(a)leissner.se> writes: > Perhaps files such as include/winuser.h should be included > for USER32 for example? > > Anyway what do you think about adding H_SRCS to > every Makefile.in file? I don't think we want that, especially if you want to add all relevant includes it's going to be a nightmare to maintain. And make depend (or some perl equivalent) can easily determine that information for you. -- Alexandre Julliard julliard(a)winehq.com

1 0