I had Wine-20050310 installed from FreeBSD ports. This version worked fine for me. But after upgrading to Wine-20050524 some applications don't work properly. E.g. Intranet Chat: http://www.softpedia.com/get/Internet/Chat/LAN-Messaging-Clients/Intranet-Chat.shtml. Running this applications I see a following message: fixme:system:SystemParametersInfoW Unimplemented action: 8193 (SPI_SETFOREGROUNDLOCKTIMEOUT) fixme:system:SystemParametersInfoW Unimplemented action: 4118 (SPI_GETTOOLTIPANIMATION) fixme:system:SystemParametersInfoW Unimplemented action: 4120 (SPI_GETTOOLTIPFADE) fixme:win:AnimateWindow partial stub fixme:system:SystemParametersInfoW Unimplemented action: 4132 (SPI_GETDROPSHADOW) Both config files are identical. Could somebody say about this problem resolution? ---- http://photo.optima.ua/
Recently I downgraded to Wine-20050310. I see same errors but application continues work while under Wine-20050524 does not. On Wed, 15 Jun 2005 12:15:32 +0300 "Oleksii Krykun" <okg@ua.fm> wrote:> I had Wine-20050310 installed from FreeBSD ports. This version worked fine > for me. > But after upgrading to Wine-20050524 some applications don't work properly. > E.g. Intranet Chat: > http://www.softpedia.com/get/Internet/Chat/LAN-Messaging-Clients/Intranet-Chat.shtml. > Running this applications I see a following message: > > fixme:system:SystemParametersInfoW Unimplemented action: 8193 > (SPI_SETFOREGROUNDLOCKTIMEOUT) > fixme:system:SystemParametersInfoW Unimplemented action: 4118 > (SPI_GETTOOLTIPANIMATION) > fixme:system:SystemParametersInfoW Unimplemented action: 4120 > (SPI_GETTOOLTIPFADE) > fixme:win:AnimateWindow partial stub > fixme:system:SystemParametersInfoW Unimplemented action: 4132 > (SPI_GETDROPSHADOW) > > Both config files are identical. > > Could somebody say about this problem resolution? > ---- > http://photo.optima.ua/ > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users---- http://photo.optima.ua/
It seems that wine20040419 is the most stable release (the one used by
wine-tools).
It is the only release which can run Lotus Notes without any problems.
But this version was released more than a year ago, and it should NOT be
more stable than a newer version.
Wine should be moving forward NOT backward!
-- Shadi
Hiji
<hijinio@yahoo.co To: Oleksii Krykun
<okg@ua.fm>, wine-users@winehq.org
m> cc:
Sent by: Subject: Re: [Wine]Wine-20050524
problem
wine-users-admin@
winehq.org
06/15/2005 11:29
AM
Sometimes the use of a newer versions doesn't always
constitute continued compatibility of applications.
Wine Tools, for example, uses a really old version of
Wine and doesn't work with newer versions.
Hiji
--- Oleksii Krykun <okg@ua.fm> wrote:
> Recently I downgraded to Wine-20050310. I see same
> errors but application
> continues work while under Wine-20050524 does not.
>
> On Wed, 15 Jun 2005 12:15:32 +0300
> "Oleksii Krykun" <okg@ua.fm> wrote:
> > I had Wine-20050310 installed from FreeBSD ports.
> This version worked fine
> > for me.
> > But after upgrading to Wine-20050524 some
> applications don't work properly.
> > E.g. Intranet Chat:
> >
>
http://www.softpedia.com/get/Internet/Chat/LAN-Messaging-Clients/Intranet-Chat.shtml
.> > Running this applications I see a following
> message:
> >
> > fixme:system:SystemParametersInfoW Unimplemented
> action: 8193
> > (SPI_SETFOREGROUNDLOCKTIMEOUT)
> > fixme:system:SystemParametersInfoW Unimplemented
> action: 4118
> > (SPI_GETTOOLTIPANIMATION)
> > fixme:system:SystemParametersInfoW Unimplemented
> action: 4120
> > (SPI_GETTOOLTIPFADE)
> > fixme:win:AnimateWindow partial stub
> > fixme:system:SystemParametersInfoW Unimplemented
> action: 4132
> > (SPI_GETDROPSHADOW)
> >
> > Both config files are identical.
> >
> > Could somebody say about this problem resolution?
> > ----
> > http://photo.optima.ua/
> > _______________________________________________
> > wine-users mailing list
> > wine-users@winehq.org
> > http://www.winehq.org/mailman/listinfo/wine-users
>
> ----
> http://photo.optima.ua/
> _______________________________________________
> wine-users mailing list
> wine-users@winehq.org
> http://www.winehq.org/mailman/listinfo/wine-users
>
M-Halo: Electronic Rock
http://www.mhalo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
wine-users mailing list
wine-users@winehq.org
http://www.winehq.org/mailman/listinfo/wine-users
>> It seems that wine20040419 is the most stable >> release (the one used by >> wine-tools). >> But this version was released more than a year ago, >> and it should NOT be >> more stable than a newer version. >> Wine should be moving forward NOT backward! > >My thoughts exactly. As grateful as I am for the >existence of Wine, I've been meaning to draft up a >short email to the development team about my concerns >about its progression. The primary concern is that >"yes. Wine should be moving forward"As I understand it, the problem with newer builds is with some core functionality rewrites (such as Windowing code). This is work that has needed to be done for some time, and should result in a far better Wine (once it is stabilized) than we had before. The unfortunate thing is that I make the *most* usage of Wine at work, running Lotus Notes, and that is a critical app needed full-time. So I cannot readily test the newer builds the way I should be.
Am Mi, Jun 15, 2005 at 11:46:20 -0400 schrieb Shadi Khasawneh:> > It seems that wine20040419 is the most stable release (the one used by > wine-tools).To correct you, it is version 20041019 and so it is only 8 month old and not a year. You can still use 20041201 with very small drawbacks and have a 6 month old version...> It is the only release which can run Lotus Notes without any problems.This is why I still stay with that version. The purpose of WineTools is to provide the user with easy installable more or less important Windows software. Not to be state of the art. Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"
>Am Mi, Jun 15, 2005 at 11:46:20 -0400 schrieb Shadi Khasawneh: >> >> It seems that wine20040419 is the most stable release (the one used by >> wine-tools).>To correct you, it is version 20041019 and so it is only 8 month old >and not a year. You can still use 20041201 with very small drawbacks >and have a 6 month old version...I'm a WINE fan, and my ONLY concern here is the stability and quality of WINE! I appreciate all the efforts of the WINE development team, and I know that WINE is still under development but I would suggest trying to improve the testing of new WINE RELEASES.>> It is the only release which can run Lotus Notes without any problems.>This is why I still stay with that version. The purpose of WineTools is >to provide the user with easy installable more or less important >Windows software. Not to be state of the art.
I was talking in general and not about Lotus Notes in specific. But there should be a way to test basic functionality. For example, the DirectX test program in MS Windows which draws a triangle on the screen and rotate it; It does NOT test everything, or every program/game that uses it - it tests basic and most common functions using different inputs and making sure that the output for each function is what is required. Lotus Notes failed because there is some specific function (among the many Windows API functions that WINE implements) has not been fully implemented yet in WINE or has some BUG. So there should be a way to test these basic functions (at the API level maybe) - Also a fixed number of applications that uses different types of libraries/functionalities provided by Windows can be tested for each release (not through CVS): One game, one network application, one word processing application... etc Again, it is only a suggestion; others may provide a better way or alternative to this. I agree that we should be submitting BUGS to the Bugzilla instead of only submitting it to mailing list. Finally, WINE might not be a huge project, as you said, but WINE developers are doing a huge and important work. All the best! Shadi Khasawneh schreef:> > I'm a WINE fan, and my ONLY concern here is the stability and quality > of WINE! I appreciate all the efforts of the WINE development team, and > I know that WINE is still under development but I would suggest trying > to improve the testing of new WINE RELEASES. > >Which is all very well and good, but how exactly is that supposed to be implemented? If somebody set up a team to test Lotus Notes, I'm sure that would be wonderful-- but you could test that till the end of time, and it wouldn't help me, because I've never used Lotus Notes, and doubt I ever will. So are Lotus Notes users more important than me? If so, then naturally I'm not going to be such a big fan of Wine as I used to be. If not, who's going to test the programs that *I* use? What about the ones my boyfriend would use if I could convince him to switch to Linux-- and which I therefore have to test to prove to him that he *can* switch? What about the programs other users on this list couldn't do without? No matter how obscure the program might be, if you need it, then it's important to you. I think the best plan on the table is the one currently being implemented: people need to sign up on the AppDB to maintain applications, and people need to post results with applications to the AppDB, so that bugs and regressions can get noticed and fixed in an organized manner. And the Wine project needs to publicize itself so that people know to contribute to the AppDB, which I see as the biggest fly in the ointment. People don't know to help, or how to help, so they don't help-- they just complain that somebody else should do it. With a project as small as Wine (there are not an infinite number of Wine developers, and volunteers are not the same as dedicated paid personnel), the strategy of "the squeaky wheel gets the most grease" is never going to work. Holly
Am Do, Jun 16, 2005 at 02:56:34 -0400 schrieb Shadi Khasawneh:> > I was talking in general and not about Lotus Notes in specific. But there > should be a way to testThis topic is something more for the dev list. To give a short answer: This is already done by the developer team. To give a long answer: The Windows API is baroque, incredible redundant and fail save in a very screwed up way. So there is not only one way to call an function and to give it parameters or to get results. Most of these ways are not documented and also the documented way not alway works the specified way or is simply buggy. As you can think, these many variants lead to as many variants of usage. So there are not simple tests to do, there are hundreds to do. And you have to do the tests on Windows as well to see the results. This is also done by the developers and some helpers. But you have to know that a program might fail in one function only reacting slightly different and so making the whole program unusable. As there are so many ways to use the API the only true test is to run programs... and this is why users should use the bug tracking system to describe the bugs. This is the only true test! Your suggestion to test with some specific programs, one for each of some defined area, will only test exactly these programs. If they work you have not won more than to know that your version works with these programs. You can not say a word out of that about other programs. An example: wine-20050419 worked with Excel, Access, Powerpoint, Outlook. But it broke WinWord! Hey, they come from the same company, using the same built system, same compilers and even the same base libraries. To come out of this API mess, the programmers at CodeWeavers concentrate on specific applications that are useful for many users. I have a similar approach with WineTools, trying to add apps as I have time to. And yes, Wine *is* a huge project and a high mountain to climb: It is implementing the Windows API! There is only one company in the world that did that before: Microsoft. And from a developer perspective they did not a very impressive work. Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"