January 2006 - Wine-Devel - list.winehq.org

Problems with references to drive Z: in registry's User Shell Folders
by Michael Jung Jan. 25, 2006

Jan. 25, 2006

Hi, when shell32.dll is registered during wineprefixcreate, it puts a lot of paths based on Z:\ in HKLM/HKCU Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders. This is due to resolving CIDL_PERSONAL to the DOS path corresponding to $HOME. If people remove the Z: drive afterwards, this leads to a lot problems (One being that the Desktop shellfolder won't initialize any more, which breaks the complete shell namespace and thus the file dialogs). I'm proposing to add two more environment variables: %PERSONAL%, which would be expanded to the DOS path corresponding to $HOME if this exists, or to %USERPROFILE%\\My Documents if not (with "My Documents" resource based, of course). And %DESKTOP%, which would be expanded to DOS_PATH_OF($HOME)\\Desktop if existent and to %USERPROFILE%\\Desktop, if not. Does someone see a problem with this approach? Bye, -- Michael Jung mjung(a)iss.tu-darmstadt.de

1 0

[Lostwages] Re: lostwages/templates/en download.template
by Tony Lambregts Jan. 25, 2006

Jan. 25, 2006

Jeremy Newman wrote: > ChangeSet ID: 22527 > CVSROOT: /opt/cvs-commit > Module name: lostwages > Changes by: jnewman(a)winehq.org 2006/01/24 14:26:23 > > Modified files: > templates/en : download.template > > Log message: > based on patch from: Sven Paschukat <Sven.Paschukat(a)t-online.de> > add a note to the WineTools link > > Patch: http://cvs.winehq.org/patch.py?id=22527 > > Old revision New revision Changes Path > 1.72 1.73 +8 -3 lostwages/templates/en/download.template > > Index: lostwages/templates/en/download.template > diff -u -p lostwages/templates/en/download.template:1.72 lostwages/templates/en/download.template:1.73 > --- lostwages/templates/en/download.template:1.72 24 Jan 2006 20:26:23 -0000 > +++ lostwages/templates/en/download.template 24 Jan 2006 20:26:23 -0000 > @@ -122,13 +122,18 @@ for post-installation instructions.</b>< > </a> > </td> > <td align=left bgcolor="#ffffff"> > - > <b><a href="http://www.von-thadden.de/Joachim/WineTools/">Wine Tools</a></b> - > WineTools is a menu driven installer for installing Windows programs. > This software lets you install the following Windows software: DCOM98, > IE6, Windows Core Fonts, Windows System Software, Office & Office Viewer, > - Adobe Photoshop 7, Illustrator 9 and many other programs. > - By <a href="http://www.von-thadden.de/Joachim/WineTools/">Joachim von Thadden</a>. > + Adobe Photoshop 7, Illustrator 9 and many other programs.<br /> > + By <a href="http://www.von-thadden.de/Joachim/WineTools/">Joachim von > + Thadden</a>.<br /> > + <div style="margin: 10px; padding: 5px; border: 1px solid #C0C0C0; background-color: #F0F0F0;"> > + <b>Note:</b> WineTools only recommended if installation or operability of > + Windows software failed on pure Wine or because the Wine developers need > + your feedback from testing. > + </div> > </td> > </tr> > </table> > > > Wine developers do not want feed back of bugs in programs with winetools installed Change Log: update note to the WineTools link Files Changed: lostwages/templates/en download.template Index: templates/en/download.template =================================================================== RCS file: /home/wine/lostwages/templates/en/download.template,v retrieving revision 1.73 diff -u -r1.73 download.template --- templates/en/download.template 24 Jan 2006 20:26:23 -0000 1.73 +++ templates/en/download.template 25 Jan 2006 03:27:01 -0000 @@ -131,8 +131,9 @@ Thadden</a>.<br /> <div style="margin: 10px; padding: 5px; border: 1px solid #C0C0C0; background-color: #F0F0F0;"> <b>Note:</b> WineTools only recommended if installation or operability of - Windows software failed on pure Wine or because the Wine developers need - your feedback from testing. + Windows software failed on pure Wine. Since winetools radically alters your + Wine configuration please do not report bugs in programs with WineTools + installed. </div> </td> </tr>

1 0

Re: [Fwd: WineTools is in need of some major house cleaning!]
by Joachim von Thadden Jan. 25, 2006

Jan. 25, 2006

Dear developers and all others reading this list, from Sven Paschukat I was informed about the discussion of removing the WineTools link from the winehq website. I read all remarks made to that hotly discussed topic and I am willing to tell you all a bit about the purpose and history of WineTools as well as I will answer the questions made by Tom Wickline. So this will be a little longish mail and I beg your pardon for that and hope you have enough patience to read it all. To start from the beginning, I took over the remainings of a project winetools initially started by Frank Hendriksen <frank(a)frankscorner.org> which was somehow orphaned. The very reason I did that was that in autumn 2004 I had to write an article in the well known German computer magazine c't. After fiddling with wine for a long time only to install a stable IE6 or Office, I found that it was so absolute complicated to describe all the steps needed only to install the IE6 (which is much better now) and that also following these steps was very erroneous, that I started to rewrite the winetools script for the readers of this article. I never meant it to become so famous and wide spread, but the download statistics after only two month showed me that there was a massive demand for such a tool. So this is how it started and it shows very clearly that it was always an installer to make certain important applications easily usable under Linux. It was never meant for testing or developing. It was always meant for the end user being able to use his software. At the time of the first releases it was almost impossible to install or work with many applications without using native DCOM and/or many of the builtin DLLs that come with the IE6. To find a configuration for as many apps as possible was one of the goals. Not to force users (with very low skills) to have many different wine installations *and* many wine user directories was a second goal. So this is the reason why, until now, everything in WineTools is based on this native M$ software (DCOM, IE6). And believe me, no one would be more happy to wipe this DCOM, IE6 and MSI stuff completely from his harddisk than me! So as so many programs rely on parts of M$ software (MFC, VB and MDAC are other important examples) and because to install and use this software leads to so many restrictions in the wine usage, I had to pin wine to the emulation of Win98 and also had to massively tamper around with DLLOverrides. The goal was to built up an environment, that can install and use as many Windows programs as possible. This did in no way regard to the fact that it is not very helpful for the wine developers. It was just a practical decision. >From time to time, Sven Paschukat and me are testing wine versions to figure out, whether we can skip some of the M$ stuff. We have not been very successful with that until now, so this is why there are so many remainings of the first start of the project in the concept. But again: This tool is for the average windows user. And believe me, I tested this with my brothers, who are just normal users. And they never ever got a piece of windows software running with wine without my heavy intervention. With WineTools they just need to click on some buttons and got their software downloaded, installed and configured. With an amount of many thousand downloads a month, not calculating the distribution inclusions of WineTools, I get almost the same number of direct mails about problems with the software as are coming into the list. And I get massive positive resonance from users who were for a long time trying to get their stuff running with plain wine and are now happy that it just works with WineTools. I must admit, that there raise problems out of the fact, that the same users are trying to install not WineTools-tested software with the setup of WineTools and coming then to the list. And your are right that this is an undebuggable situation. The only way around that is to smoothly migrate WineTools to more and more builtin features as long as this does not make the programs uninstallable or unusable. > Betreff: WineTools is in need of some major house cleaning! > Datum: Fri, 30 Dec 2005 03:31:43 -0500 > Von: Tom Wickline <twickline(a)gmail.com> > An: wine-devel <wine-devel(a)winehq.org> > > Hello Everyone, > > Anyone who reads the posting on this list already knows that I stood up for > the wineTools project and almost made a couple enemies... But me and Vitaliy > came to a half way agreement on whether or not we should keep the link > on our downloads page to WineTools.... > > I feel I need to ask a couple questions here about the future of WineTools. > > 1) Are the concerns that Vitaliy brought up being looked into? Sven Paschukat suggested to implement a mode for WineTools to install without native components and without that tampering in the registry. This allows automatic installations *and* insight for developers if something goes wrong. We can also add a debugging mode to enable the logging of wines debug channels, to make a mailable report of bugs. Also the other suggested corrections will be looked over and changed if applicable. > 2) On sourceforge there are still downloads of version 1.30 from > December 3, 2003 why is this? and do you plan to cancel this project > or at least update it? > sourceforge site: > http://sourceforge.net/project/showfiles.php?group_id=61341 > > 3 )Freshmeat list WineTools latest version at 2.1.0 and last updated 1 > year, 4 months ago > do you plan to update this site and list new versions as there released? > http://freshmeat.net/projects/winetools/?branch_id=51159&release_id=164227 I personally had never anything to do with these versions. The one on Sourceforge is Frank Hendriksen's. He was already contacted by Sven Paschukat to remove the project, but Sourceforge does not allow to remove projects. So instead he already pointed a link to the official WineTools site. I don't see what we can do more here. The one on Freshmeat was taken over and is maintained by Sven Paschukat. Also Freshmeat does not allow the removal of projects. But Sven will update the versions there and we will try to keep it uptodate. We might also move the whole download section to Freshmeat to unburden my download server. > 4) Could the maintainers of WineTools help new users in #winehq on > irc? or start a new channel #wine-tools (or something to that effect) > and help WineTools users? Can you list either the #winehq channel or a > new channel on your site and ask experienced users to help new users? I am very astonished about this request. If you look through the mailing list you will find, that Sven and me are already giving support on the wine-users mailing list. That we will not and can not maintain a channel should be clear as we are not earning our money by looking at channels. Also the demand by Vitaly to provide rapid fixes to requests on such a channel or the list is something that can be only meant as a joke!!! If Vitaly is a man of independent means it is nice for him but we are a free time project and can only work for WineTools, as the name suggests, in our *free* time. And we have also a family, friends, mistresses and other hobbies... > I am not trying to be critical..... I hope winehq keeps the link to > your project but you guys may need help more on winehq, and also keep > information sites more up to date for this to take place. and also > look in to Vitaliy's concerns. Well, we also do not like winehq to remove the project's link. As for the support I already wrote a line above about that. Note that there is a massive amount of users using Wine via WineTools. Almost all users coming from Windows are using this software if they like to use their programs. This might lead to more and more end user questions on the list. As a possible solution for that, if you think this gets the upper hand, I would suggest to have a new mailing list wine-winetools and to redirect all users to that one. We will propagate then this list in the readmes and on the WineTools sites. And for sure we will sit on this list like spiders lurking for our prey... At least I want to thank all wine developers for their absolute fantastic work! In my opinion this is one of the most interesting and most ambitious projects in the community of open source software. And it really works astonishingly good. Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"

3 3

Should the AppDB make public the number of unique page views each app gets?
by Scott Ritchie Jan. 25, 2006

Jan. 25, 2006

This was an idea we discussed in IRC for a short bit, and I think it would be good to bring it up here. Essentially, if the AppDB displayed the number of page views each app got it would go a long way towards estimating the demand for particular applications, whether they work or not. It seems fair to say that someone looking an app up in the AppDB either wants to run it in Wine or wants to know if it's doable should he switch to Wine. Coincidentally, this also helps solve the voting problem - since votes for gold apps are supposed to be replaced with votes for apps that work should be done on, we now have a mechanism to sort the Gold list other than by votes. Sorting the gold list by page views would also greatly help navigation from the front page of the AppDB, as it would place the most popular applications at the top. Then again, maybe there's something I've overlooked. Thoughts? -Scott Ritchie

4 3

Re: [Fwd: WineTools is in need of some major house cleaning!]
by Juan Lang Jan. 25, 2006

Jan. 25, 2006

Hm. Felt I needed to offer a counterpoint to Vitaliy's rather enthusiastic response. I support winetools, though I don't use it myself. Not only as a matter of principle (this is open source we're talking about, and one of the beauties is we don't get to constrain how it's used.) Also because it's in line with the aims of the Wine project: run Windows apps. Wine is nice in that it doesn't require you to have any MS license to run Windows apps, but it can use MS software if you have a licensed copy. So winetools offers folks with MS licenses a relatively easy way to get apps to run. Still, while that's nice for the users, it's not so nice for us Wine developers, because it's hard to get widespread testing of things we're improving if they're not being widely used. So, as Vitaliy suggested, it would be nice for us if you guys, who know what problems you encounter running with builtin DLLs, could file bug reports in bugzilla for us. That way at least we have a chance to say, hey, that problem's now fixed, consider using builtin OLE (or whatever) in the next release of winetools. Now for specifics. For instance, you use native advpack in all cases, but that's seen some more work recently. What bugs do you encounter if you use builtin instead? Same with ole32. Ideally, each of the apps that has a native override should have a bug report associated with it, what goes wrong if you use the builtin version instead. Also, the default override, "*"="native,builtin" seems wrong. If we don't have a DLL at all, we use a native version of course. I don't think it should be the policy to assume the Wine version isn't up to snuff by default. This could even cause problems, e.g. I don't believe any native version of netapi32.dll will work on Wine, yet you don't specify to use the builtin version. Also, you direct users to http://winehq.org/site/forums. That's fine since this is community support anyway, and it is often the case that winetools knowledgeable people are around (like you guys.) But it would be nicer if you could be clearer about it. Like, that we developers had nothing to do with it, and may be unfriendly to it if we're in a bad mood, or it's a Tuesday :) It'd also be nice (for us, even though no one actually reads anything these days) if you could be clearer about what it does. That it installs MS components, that it uses these instead of the builtin versions sometimes, that you can change how it does this using winecfg, etc. That'd make it easier for us to help folks that have only used winetools that want support, because often the first question we ask is, what version of wine, and what DLLs are you using? --Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

Problem with WineD3D Surface Locking
by Stefan Dösinger Jan. 24, 2006

Jan. 24, 2006

Hello, I've spotted a bug in WineD3D's surface locking, and I have no clue how to fix this. The problem is that unlocking the back buffer causes it to become completely black, no matter what's written to it's memory or what has been there before. I have written a small D3D9 test app which shows this behavior: Compile it with "winemaker .", followed by make, and run it. Pressing ESC will cause it to quit, pressing any other keys makes IDirect3DDevice9::Clear call on the back buffer, with a color value based on the pressed keys. A click anywhere will LockRect() the whole backbuffer, write 0xff into the whole locked memory, and UnlockRect() it. The screen should become completely white, but instead it goes black. With the fglrx driver and 24 bit color depth it shows the correct behavior, but with any other driver(radeon, software rendering) or 16 bit color depth, it doesn't work. The bug is somehow related to some GL calls in UnlockRect(glPixelZoom and glOrtho), but I couldn't find anything specific. I hope you can help me, I am quite stuck here, Stefan

2 4

Winelib debugging with eclipse in fc4
by Michael Ost Jan. 24, 2006

Jan. 24, 2006

A while back I posted a question about how to get debugging working with eclipse in fedora 4. I am having some success, so if anyone else out there is interested here's how it is set up. In regedit: * disabled auto winedbg by renaming AeDebug I changed HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/AeDebug to AeDebug-DISABLED. Without this gdb doesn't seem to be able to get a hold of SEGFAULTs. In eclipse's Run/Debug dialog box: * set the c/c++ application to WINE_SRC/loader/wine-pthread WINE_SRC points to a compiled version of wine. For me, I got the wine src rpm and ran rpmbuild -bb. This is where main() is, which eclipse looks for at start up. * put your .exe.so file on the Arguments tab * choose the GDB Debugger on the Debugger tab * add WINE_SRC on the Source tab as a "Filesystem directory with subdirectories" The only weirdness so far is that sometimes (not always) the debugger suspends when a new thread is created. I just resume (F8) past that. And I am not sure what impact bypassing wine-preload's exec-shield workaround will have on me. More on that if I learn more. But I gotta say that having a functioning IDE with integrated debugging on Linux is a major relief and, for me at least, a long time coming! ... mo PS: I installed FC4, and then did yum update. eclipse is version 3.1.1 updated from the eclipse UI from the version that came with FC4.

2 5

Re: user: Don't drop owned windows in WIN_EnumChildWindows.
by Dmitry Timoshkov Jan. 24, 2006

Jan. 24, 2006

On Tue, 2006-01-24 at 12:56 -0700, Vitaliy Margolen wrote: > ChangeLog: > user: Don't drop owned windows in WIN_EnumChildWindows. > Add few tests to test this. It would be interesting to add IsChild calls in there and see what they return. We have at least one failing test in msg.c, test_DestroyWindow() which shows that our IsChild implementation is not entirely correct. -- Dmitry.

1 0

Re: LostWages: add a note to the WineTools link
by Dmitry Timoshkov Jan. 24, 2006

Jan. 24, 2006

On Tue, 2006-01-24 at 21:01 +0100, Sven Paschukat wrote: > as Vitaly noted it is not always clear that WineTools is not a > requirement for using Wine, so let the users decide if they want to test > or just want to use Wine. > "... or if you want to get best chances of success ..." I'd suggest to remove this wording, that's not (necessary) true. -- Dmitry.

1 0

[patch] riched20 conformance test
by tkho＠ucla.edu Jan. 24, 2006

Jan. 24, 2006

Greetings, I have started writing a conformance test for the rich edit control (riched20). The purpose is for students in UCLA's CS 130 Software Engineering course to first extend this conformance test to test conformance to unimplemented features, and then later implement their chosen features. You can find the patch here: http://www.seas.ucla.edu/~kho/wine/patches/riched20_test_20060119.patch Any comments would be much appreciated! For the curious, you can find background at http://www.kegel.com/wine/sweng/ and http://www.seas.ucla.edu/~kho/wine/ Best, Thomas Kho

3 2

RE: Windows manager
by Phil Lodwick Jan. 24, 2006

Jan. 24, 2006

Ok, I think I solved my own problem. In x11drv/window.c we see that "full-screen popup windows are managed". If I don't rotate the screen we are no longer a "full-screen" pop-up. My bad. Phil -----Original Message----- From: wine-devel-bounces(a)winehq.org [mailto:wine-devel-bounces(a)winehq.org] On Behalf Of Phil Lodwick Sent: Tuesday, January 24, 2006 11:47 AM To: wine-devel(a)winehq.org Subject: Windows manager I have an application that does not seem to appear to the Window Manager. I am using fvwm. To confirm I am running fbpanel which basically does a: XGetWindowProperty(GDK_DISPLAY(), GDK_ROOT_WINDOW, a_NET_CLIENT_LIST, 0, 0x7fffffff, 0, XA_WINDOW, ...); and the window never appears on its list. The strange thing is if I rotate the screen in my XF86Config-4 file, the window DOES appear on the list and I can use fbpanel to select the window, bring it to the front, etc. Anybody have an idea as to what difference rotating the screen would make? Thanks, Phil

1 0

Winhelp - Derive 6
by felix＠derklecks.de Jan. 24, 2006

Jan. 24, 2006

Hi, I have been trying to get the Winhelp to work for weeks now. But I just do not have any success. Derive is using winhelp with an extension RoboEx32 [1]. Derive reports "could not open help" and on the console I see following: # wine ~/.wine/drive_c/Programme/TI\ Education/Derive\ 6/Derive6.exe err:winhelp:HLPFILE_Uncompress3 buffer overflow (0x4169c3f9 > 0x4169c3f5) err:winhelp:HLPFILE_Uncompress3 buffer overflow (0x4169dbbc > 0x4169dbb8) err:winhelp:HLPFILE_Uncompress3 index in phrases 10807/5554 err:winhelp:HLPFILE_Uncompress3 buffer overflow (0x416dc2da > 0x416dc2d3) err:winhelp:HLPFILE_Uncompress3 index in phrases 10625/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10871/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10625/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10625/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10807/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10655/5554 fixme:winhelp:HLPFILE_AddParagraph Got an embedded element RoboEx32.dll, WinHelp2000, fixme:winhelp:WHD_GetInfo NIY 8 fixme:winhelp:WHD_Open ("c:/windows/" 2) fixme:winhelp:WHD_LLInfoFromFile () fixme:winhelp:WHD_OpenBag (0xffffffff |SYSTEM 2) fixme:winhelp:WHD_API () fixme:winhelp:MACRO_Search () fixme:winhelp:WHD_Close (0xffffffff) Is winhelp supposed to be able to handle these help files? It is listed in the appdb as gold-supported. There are several other errors I see using derive, but I will have to do some more research. An easy bug is probably that the user just gets a black window after clicking on "about wine". Do you need any other information? Felix [1] - http://www.knopf.com/resources/help/winhelp2k.html

3 3

Regarding Implementation of Microsoft Speech SDK using wine
by Kalpit Shah Jan. 24, 2006

Jan. 24, 2006

Hi, I want to implement the Microsoft Speech SDK using wine on Fedora Core 3. How feasible is this.....can anyone give me an insight on how do i go about doing this..... please give me some orientation..... Waiting for a reply, Regards, Kalpit

3 2

Windows manager
by Phil Lodwick Jan. 24, 2006

Jan. 24, 2006

I have an application that does not seem to appear to the Window Manager. I am using fvwm. To confirm I am running fbpanel which basically does a: XGetWindowProperty(GDK_DISPLAY(), GDK_ROOT_WINDOW, a_NET_CLIENT_LIST, 0, 0x7fffffff, 0, XA_WINDOW, ...); and the window never appears on its list. The strange thing is if I rotate the screen in my XF86Config-4 file, the window DOES appear on the list and I can use fbpanel to select the window, bring it to the front, etc. Anybody have an idea as to what difference rotating the screen would make? Thanks, Phil

1 0

Re: iphlpapi: remove one IP address per interface restriction
by Robert Shearman Jan. 24, 2006

Jan. 24, 2006

Juan Lang wrote: >+/* Enumerates the IP addresses in the system using SIOCGIFCONF, returning >+ * the count to you in *pcAddresses. It also returns to you the struct ifconf >+ * used by the call to ioctl, so that you may process the addresses further. >+ * Free ifc->ifc_buf using HeapFree. >+ * Returns NO_ERROR on success, something else on failure. >+ */ >+static DWORD enumIPAddresses(PDWORD pcAddresses, struct ifconf *ifc) >+{ >+ DWORD ret; >+ int fd; >+ >+ fd = socket(PF_INET, SOCK_DGRAM, 0); >+ if (fd != -1) { >+ int ioctlRet = 0; >+ DWORD guessedNumAddresses = 0, numAddresses = 0; >+ caddr_t ifPtr; >+ >+ ret = NO_ERROR; >+ ifc->ifc_len = 0; >+ ifc->ifc_buf = NULL; >+ /* there is no way to know the interface count beforehand, >+ so we need to loop again and again upping our max each time >+ until returned < max */ >+ do { >+ HeapFree(GetProcessHeap(), 0, ifc->ifc_buf); >+ if (guessedNumAddresses == 0) >+ guessedNumAddresses = INITIAL_INTERFACES_ASSUMED; >+ else >+ guessedNumAddresses *= 2; >+ ifc->ifc_len = sizeof(struct ifreq) * guessedNumAddresses; >+ ifc->ifc_buf = HeapAlloc(GetProcessHeap(), 0, ifc->ifc_len); >+ ioctlRet = ioctl(fd, SIOCGIFCONF, ifc); >+ } while (ioctlRet == 0 && >+ ifc->ifc_len == (sizeof(struct ifreq) * guessedNumAddresses)); >+ >+ if (ioctlRet == 0) { >+ ifPtr = ifc->ifc_buf; >+ while (ifPtr && ifPtr < ifc->ifc_buf + ifc->ifc_len) { >+ numAddresses++; >+ ifPtr += ifreq_len((struct ifreq *)ifPtr); >+ } >+ } >+ else >+ ret = ERROR_INVALID_PARAMETER; /* FIXME: map from errno to Win32 */ >+ if (!ret) >+ *pcAddresses = numAddresses; >+ else >+ { >+ HeapFree(GetProcessHeap(), 0, ifc->ifc_buf); >+ ifc->ifc_buf = NULL; >+ } >+ } >+ else >+ ret = ERROR_NO_SYSTEM_RESOURCES; >+ return ret; >+} >+ > > You leak an fd in this function. -- Rob Shearman

1 0

Re: wine 0.9.6 segfaults-Found the problem but not the solution (was :Re: wine 0.9.5 - segmentation fault with some apps)
by penna＠bb.com.br Jan. 24, 2006

Jan. 24, 2006

Hi Mike, >> The problem seems to be with the name of the executable: >> "user.exe" (sounds crazy, but it was I could realize after some tests). > > That's quite possible. user.exe is a 16 bit part of user32.dll, and > Wine treats it in a special way. In fact there are a little more with same problem: start.exe and sound.dll (as reported in bugs 3950, 4351 and 4311) > > You might be able to add a dll override entry in winecfg like this: > > *user.exe = native, builtin However "winecfg" does not allow me to input free form strings (at least I try and could not find a way). It does only allow me to navigate throught the file system and choose the application. And the "Libraries" tab, in winecfg, it is only for DLL's - I guess! (Am I wrong?) The only solution I tried is using "vi" to edit ~/.wine/user.reg but I think I made a mistake because wien still segfaults. Here is the KEY I have put: [Software\\Wine\\AppDefaults\\*user.exe\\DllOverrides] 1138094570 "*"="native,builtin" I have also tried a variation of it .... but it still segfaults when calling "wine user.exe": [Software\\Wine\\AppDefaults] 1138094570 "*user.exe"="native,builtin" Thanks --------------------------------------------------------- Ulisses de Sousa Penna Analista Consultor - Banco do Brasil Fone: +55-61-3310-6320 Fax: +55-61-3310-6435 ---------------------------------------------------------

2 1

Re: d3d8: CreateDevice should try the parent if the current window fails
by Alexandre Julliard Jan. 24, 2006

Jan. 24, 2006

Jan Zerebecki <jan.wine(a)zerebecki.de> writes: > Changelog: > d3d8: CreateDevice should try the parent if the current window fails > because it doesn't have the property __wine_x11_whole_window . > Fixes bug #4341 . What you really want to use here is GetAncestor(GA_ROOT). -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: LostWages: remove third party downloads section from our download page
by Jeremy Newman Jan. 24, 2006

Jan. 24, 2006

Did we decide if we wanted to do this? I can't remember. A.D.D. you know. On Fri, 2006-01-20 at 02:22 -0500, Tom Wickline wrote: > Hello, > > Tom > > Changelog: > Remove third party downloads section from our download page

6 5

Re: server: Initial inotify support.
by Hans Leidekker Jan. 24, 2006

Jan. 24, 2006

On Tuesday 24 January 2006 10:57, Mike McCormack wrote: > This isn't ready yet because it cause a regression test to fail. The > failure is related to calling RemoveDirectory on an open directory > handle, so isn't a fault in this code. You must be referring to my evil change notification test here? Another interesting case that I didn't test would be moving a directory that has change notifications registered for it. I see you don't map IN_MOVE_SELF, which would allow us to detect this case. Any particular reason for that? -Hans

2 1

wined3d: support for WINED3D_A8B8G8R8
by Christoph Frick Jan. 24, 2006

Jan. 24, 2006

hi there, this patch adds support for WINED3DFMT_A8B8G8R8 to wined3d. this fixes the textures in the Demo_Grass, Demo_Smoke and the logo for all demos in OGRE 1.0.6 [1] demos using dx9 renderer. [1] http://www.ogre3d.org/ -- cu License: LGPL ChangeLog: 2006-01-24 Christoph Frick <frick(a)sc-networks.com> * dlls/wined3d/utils.c: wined3d: Support for WINED3DFMT_A8B8G8R8 --- dlls/wined3d/utils.c.orig 2005-11-26 09:31:21.000000000 +0100 +++ dlls/wined3d/utils.c 2006-01-23 22:19:14.000000000 +0100 @@ -35,6 +35,7 @@ FMT_TO_STR(WINED3DFMT_UNKNOWN); FMT_TO_STR(WINED3DFMT_R8G8B8); FMT_TO_STR(WINED3DFMT_A8R8G8B8); + FMT_TO_STR(WINED3DFMT_A8B8G8R8); FMT_TO_STR(WINED3DFMT_X8R8G8B8); FMT_TO_STR(WINED3DFMT_R5G6B5); FMT_TO_STR(WINED3DFMT_X1R5G5B5); @@ -1613,6 +1614,7 @@ case WINED3DFMT_A8R8G8B8: retVal = GL_RGBA8; break; case WINED3DFMT_A2R10G10B10: retVal = GL_RGBA8; break; case WINED3DFMT_X8R8G8B8: retVal = GL_RGB; break; + case WINED3DFMT_A8B8G8R8: retVal = GL_RGBA8; break; /* to see */ case WINED3DFMT_A8: retVal = GL_ALPHA8; break; @@ -1678,6 +1680,7 @@ case WINED3DFMT_A8R8G8B8: retVal = GL_BGRA; break; case WINED3DFMT_A2R10G10B10: retVal = GL_BGRA; break; case WINED3DFMT_X8R8G8B8: retVal = GL_BGRA; break; + case WINED3DFMT_A8B8G8R8: retVal = GL_RGBA; break; /* to see */ case WINED3DFMT_A8: retVal = GL_ALPHA; break; /* Depth + Stencil */ @@ -1740,6 +1743,7 @@ case WINED3DFMT_A8R8G8B8: retVal = GL_UNSIGNED_INT_8_8_8_8_REV; break; case WINED3DFMT_A2R10G10B10: retVal = GL_UNSIGNED_INT_2_10_10_10_REV; break; case WINED3DFMT_X8R8G8B8: retVal = GL_UNSIGNED_INT_8_8_8_8_REV; break; + case WINED3DFMT_A8B8G8R8: retVal = GL_UNSIGNED_INT_8_8_8_8_REV; break; /* to see */ case WINED3DFMT_A8: retVal = GL_ALPHA; break; /* Depth + Stencil */ @@ -1783,6 +1787,7 @@ case WINED3DFMT_A8R8G8B8: retVal = 4; break; case WINED3DFMT_A2R10G10B10: retVal = 4; break; case WINED3DFMT_X8R8G8B8: retVal = 4; break; + case WINED3DFMT_A8B8G8R8: retVal = 4; break; /* Paletted */ case WINED3DFMT_P8: retVal = 1; break; case WINED3DFMT_A8P8: retVal = 2; break;

1 0

Wine and DJGPP sources
by Uwe Bonnes Jan. 24, 2006

Jan. 24, 2006

Hallo, while looking at problems with wine's msvcrt (_sys_errlist, atof), pieces from DJ Delorie DJGPP source code, like used in the REACTOS sources would come handy. Is copying.dj compatible with our license? Also not explicie telling LPGL, copying.dj says: * objects and libraries linked into an application may be distributed without sources. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

Re: wine 0.9.6 segfaults-Found the problem but not the solution (was :Re: wine 0.9.5 - segmentation fault with some apps)
by penna＠bb.com.br Jan. 24, 2006

Jan. 24, 2006

Hi all, I have posted a comment at http://bugs.winehq.org/show_bug.cgi?id=4351 The problem seems to be with the name of the executable: "user.exe" (sounds crazy, but it was I could realize after some tests). Regards. --------------------------------------------------------- Ulisses de Sousa Penna Analista Consultor - Banco do Brasil Fone: +55-61-3310-6320 Fax: +55-61-3310-6435 ---------------------------------------------------------

2 1

Compile failure [dlls/dinput/joustick.c:177 ... _dfDIJoystick]
by Morten Welinder Jan. 23, 2006

Jan. 23, 2006

Hi there, on a more-or-less default SuSE 9.3 system I have been getting this error for a while. Ideas? M. make[3]: Entering directory `/home/welinder/wine/dlls/dinput/tests' ../../../tools/winegcc/winegcc -B../../../tools/winebuild -mconsole joystick.o \ keyboard.o mouse.o testlist.o -o dinput_test.exe.so -L../../../libs/port -lwi\ ne_port -L../../../dlls -L../../../dlls/dinput -L../../../dlls/ole32 -L../../..\ /dlls/version -L../../../dlls/user32 -L../../../dlls/kernel32 -L../../../libs -\ ldinput -lole32 -lversion -luser32 -lkernel32 -ldxguid -luuid -ldxerr8 joystick.o(.text+0x666): In function `EnumJoysticks': /home/welinder/wine/dlls/dinput/tests/joystick.c:177: undefined reference to `c\ _dfDIJoystick' joystick.o(.text+0x6b0):/home/welinder/wine/dlls/dinput/tests/joystick.c:181: u\ ndefined reference to `c_dfDIJoystick2' collect2: ld returned 1 exit status winegcc: gcc failed. make[3]: *** [dinput_test.exe.so] Error 2 make[3]: Leaving directory `/home/welinder/wine/dlls/dinput/tests'

2 2

Re: Jtagserver
by Vitaliy Margolen Jan. 23, 2006

Jan. 23, 2006

Hello Uwe, Monday, January 23, 2006, 4:23:17 AM, you wrote: > Hallo again, > > I don't expect Jtagserver to actually work, it requires some driver to > access Jtag programming hardware connected somwhow to the PC e.g via the > parallel port. But I would appreciate if jtagserver would either exit > gracefully or otherwise communicate as expected with the rest of the suite > to let quartus finally start up... > Bye Well I found the problem: 0009:Call kernel32.CreateEventW(00000000,00000001,00000000,7fd1e9a8 L"__wineservice_JTAGServer") ret=7f9ac9e0 0009: create_event( access=001f0003, attributes=000000c0, rootdir=0x50, manual_reset=1, initial_state=0, name=L"__wineservice_JTAGServer" ) 0009: create_event() = 0 { handle=0x58 } 000c:Call kernel32.CreateEventW(00000000,00000001,00000000,7fcfe9a0 L"__wineservice_Altera JTAG Server") ret=7f98c9e0 000c: create_event( access=001f0003, attributes=000000c0, rootdir=0x4c, manual_reset=1, initial_state=0, name=L"__wineservice_Altera JTAG Server" ) 000c: create_event() = 0 { handle=0x50 } It looks like we are using different names when we creating this events. There is nothing wrong with operation timing out. We actually waiting on either process exit (service) or signaled event ^. We don't get either and timing out (in service_start_process). So all you need to figure out why are we using wrong service name <g> So in the end service could work. Vitaliy

1 0

Re: MSI: Fix msi_dup_record_field for Integer Records
by Alexandre Julliard Jan. 23, 2006

Jan. 23, 2006

Robert Shearman <rob(a)codeweavers.com> writes: > ChangeLog: > Make msi_dup_record_field not fail when dealing with integer records by > calling MSI_RecordGetStringW instead of MSI_RecordGetString, as the > former does conversion. It fails make test: ../../../tools/runtest -q -P wine -M msi.dll -T ../../.. -p msi_test.exe.so format.c && touch format.ok format.c:128: Test failed: size wrong format.c:132: Test failed: size wrong format.c:133: Test failed: wrong output format.c:146: Test failed: size wrong format.c:147: Test failed: wrong output format.c:241: Test failed: size wrong 0 format.c:242: Test failed: wrong output() format.c:663: Test failed: size wrong (0) format.c:664: Test failed: wrong output() -- Alexandre Julliard julliard(a)winehq.org

1 0