September 2007 - Wine-Devel

Re: I need help, please

by Reece Dunn

On 28/09/2007, David Outteridge <dajo(a)frii.com> wrote: > Thank you for the reply, Dan, a reply is appreciated. > > I must write that I am surprised by this response - your website seems > to be asking for help at all levels. Help *is* needed at all levels. Wine needs testers to test their favorite applications and report bugs. Without the bug reports, the developers don't know (or will miss) regressions or features that are not supported in Wine yet. It is also a good idea to add an entry to the AppDB (and possibly to the equivalent one over at www.codeweavers.com for the CrossOver version of Wine). This helps the developers know where to focus their attention to get the best coverage. Note that this does not mean that because your application is not popular it will not be fixed. This is where people like you can come in and help improve the support for running Windows applications on Wine. > I am not quite convinced that > months of work is needed (mainly because corelDRAW version 11 works); > but maybe you know something I do not - the main point of my posting, > of course. In general, applications that run on Windows 98 or earlier should (in theory) run without problems. The more recent the version of Windows an application wants to use, the less likely it will run, or run well. Newer versions of an application will tend to take advantage of newer features in Windows and start requiring more recent versions, increasing the chances that it will run into areas that are not implemented, or partially implemented in Wine. For example, the latest version of Wine has added support for side-by-side manifests for installing different versions of a DLL with the same name. This was introduced in Windows XP and is required by newer applications. Also, GDIPlus - an extended drawing interface - was also introduced in XP and has only recently been partially supported in Wine. The effort to support iTunes 7 took several months to complete, even though earlier iTunes were working. So getting CorelDraw 13 to work is likely not to be an easy task. Once the program installs, there are likely to be regressions with CorelDraw itself. > Largely, I was asking for policy information; i.e., *what* > to do, not *how* to do it, which I feel I can handle. I would suggest raising bug reports for each issue that you encounter as this will help developers track the problems that CorelDraw 13 has on Wine. Also, try and help maintain the application on the Wine AppDB and CodeWeavers application support page. And keep testing! HTH, - Reece

Sept. 28, 2007

Re: I need help, please

by David Outteridge

Thank you for the reply, Dan, a reply is appreciated. I must write that I am surprised by this response - your website seems to be asking for help at all levels. I am not quite convinced that months of work is needed (mainly because corelDRAW version 11 works); but maybe you know something I do not - the main point of my posting, of course. Largely, I was asking for policy information; i.e., *what* to do, not *how* to do it, which I feel I can handle. Good Luck with the project. dajo

Sept. 28, 2007

Re: address space layout

by Alexandre Julliard

Tijl Coosemans <tijl(a)ulyssis.org> writes: > It appears that the only solution is to locate wine somewhere after > 0x80000000 instead of at 0x7bf00000 and to allow mmap to allocate > memory there. Then the data segment size limit can be set to 256Mb or > something instead of 32Mb. The problem is then that builtin dlls are > mmapped (by the runtime linker) well beyond 0x80000000. Now I'm > thinking, would it be possible to load dummy dlls somewhere in the > first 2Gb of address space? Through which API calls can a program > determine a dll is above 0x80000000 by the way? It can be any address located in the dll; normally it's the module handle, but it can also be functions or variables. Also there are copy protection tools that check that the dll code is really inside the module, so you can't create a dummy dll and put the real code somewhere else. -- Alexandre Julliard julliard(a)winehq.org

Sept. 28, 2007

Re: msvcrt: move error condition before memory allocation (found by Smatch) [1/3, resend]

by Alexandre Julliard

Lionel_Debroux <lionel_debroux(a)yahoo.fr> writes: > _wfullpath leaks some heap memory in an error paths. Found in Michael > Stefaniuc's list of Wine potential bugs detected by Smatch. > Fixed by moving the error treatment before the allocation, since the > error treatment doesn't fire up if there was a memory allocation (due to > size = MAX_PATH; assignment). > > Is there anything wrong with this patch ? Yes, you are using the size before checking if the buffer is NULL (in which case the size is meaningless), and as you said yourself the error treatment isn't used if there was an allocation, so there's no leak to fix here. -- Alexandre Julliard julliard(a)winehq.org

Sept. 28, 2007

Re: Wine gets exposed in Norway :)

by Tomas Zijdemans

> Please note that this is a secret website, so we Norwegians cannot send the > website address to the list. :) > > > Alexander N. Sørnes > I get the satire... Here: http://www.hardware.no/ :)

Sept. 28, 2007

AntiAliasing for Source Based games

by christine.youngson＠clear.net.nz

Hi everyone, I'm exceptionally new to posting messages on mailing lists (ie its my first time) so please forgive me in advance if I've done something wrong! My question for the wine developers is, why is Anti Aliasing not supported for Source based games? I play Day of Defeat Source everyday, and many wine gamers play steam based source engine games such as DoDs and Counterstrike Source, and its nearly at windows xp level fps wise, but the main nuisance for us is that there is no AA! AA greatly improves the look of games, and it seems that there is an emphasis on making the games look nice by adding functionality such as shaders and glsl, so in this respect, a basic feature of games such as AA should be considered to be made. Also Team Fortress Two is coming out fairly shortly and AA would be a nice feature to implement for when it comes out :) I would consider learning C etc myself to try and get this functionality (I learned Java as part of my degree) up and running, but sadly I probably don't have the skills to contribute. Anyways, keep up the excellent work wine developers, you guys do a tremendous job, but please consider adding this one feature, as it would mean a lot to myself and many many others who play steam based source games etc using wine on Linux! Take care!

Sept. 28, 2007

Re: version resource for ole2nls.dll

by Dmitry Timoshkov

"Dmitry Timoshkov" <dmitry(a)codeweavers.com> wrote: > "Stefan Leichter" <Stefan.Leichter(a)camline.com> wrote: > >> This patch fixes Bug 9747 >> >> ChangeLog >> --------- >> added version resource for ole2nls.dll > >> +#define WINE_FILEVERSION_STR "2.10.3050.1" >> +#define WINE_FILEDESCRIPTION_STR "Wine OLE dll" >> +#define WINE_FILENAME_STR "OLE2NLS.DLL" >> + >> +#include "wine/wine_common_ver.rc" > > Why do you define WINE_FILEVERSION_STR but not WINE_FILEVERSION? > That not creates a confusion but could lead to hard debuggable > problems with application which test only one of them. The above should be read as: That not only creates a confusion but could lead to hard debuggable problems with application which test only one of them. -- Dmitry.

Sept. 28, 2007

Re: version resource for ole2nls.dll

by Dmitry Timoshkov

"Stefan Leichter" <Stefan.Leichter(a)camline.com> wrote: > This patch fixes Bug 9747 > > ChangeLog > --------- > added version resource for ole2nls.dll > +#define WINE_FILEVERSION_STR "2.10.3050.1" > +#define WINE_FILEDESCRIPTION_STR "Wine OLE dll" > +#define WINE_FILENAME_STR "OLE2NLS.DLL" > + > +#include "wine/wine_common_ver.rc" Why do you define WINE_FILEVERSION_STR but not WINE_FILEVERSION? That not creates a confusion but could lead to hard debuggable problems with application which test only one of them. -- Dmitry.

Sept. 28, 2007

Re: bits[1/3]: Minimal Background Intelligent Transfer Service (bits) implementation

by Alexandre Julliard

Roy Shea <roy(a)cs.hmc.edu> writes: > As far as I can tell the Bitsprx2.dll is generated from Bits.Idl, that > is equivalent to the bits.idl I'm developing. Since my dll is not > acting as a proxy, at least as I understand proxy dlls (I'm still > digging through COM books), I thought it would be more accurate to not > include the "prx" in the name of my dll. Simply changing the name > from bits.dll to bitsprx2.dll is easy enough, but I worry that the > semantics between a regular dll and a proxy dll would cause confusion > or problems. The only way to avoid confusion and problems is for your dll to have the same name, and behave the same way, as the Windows one. -- Alexandre Julliard julliard(a)winehq.org

Sept. 27, 2007

Re: iTunes 7.4.2 doesn't even install for me

by Juan Lang

Hi Paul, > I saw your bug 9765 but I don't even get that far. The install crashes for me > with something that appears to be connected to a driver: Actually, I see that crash too. I meant to log a bug for it, but never did. Would you mind? (snip) > L"C:\\windows\\System32\\Drivers\\GEARAspiWDM.sys" (native) at 0x460000 > trace:module:process_attach (L"GEARAspiWDM.sys",(nil)) - START > trace:module:MODULE_InitDLL (0x460000 L"GEARAspiWDM.sys",PROCESS_ATTACH,(nil)) - > CALL > trace:seh:raise_exception code=c0000005 flags=0 addr=0x464010 > trace:seh:raise_exception info[0]=00000001 > trace:seh:raise_exception info[1]=00460038 > trace:seh:raise_exception eax=0046137e ebx=7bc90dc8 ecx=0000001c edx=00460000 > esi=7bc87f5b edi=00460038 That address (0x00460038) is suspect. It looks like part of a Unicode string. Something about how this driver is loaded is buggy, I'm guessing ntoskrnl.exe is a bit too stubby for it yet. Nevertheless, iTunes starts for me after this crash, it just warns about the registry entries needed for CD/DVD drives being missing, and I suspect that's due to this driver not being registered correctly. I just ignore that warning. > As your so busy with iTunes these days, I thought I contact you directly. I don't mind, but I'm actually off it now. I've tried to stay up to date this week, but no guarantees now that I'm back in school. --Juan

Sept. 27, 2007