Hi all, I found that some applications does not work more. The last successfull version was 20050310. For testing I can propose one example : http://hem.bredband.net/alivor/ichat121b6.exe Now I try to use wine 0.9.1 under FreeBSD (KDE 3.4.0). The application above is installed fine but during start I see: fixme:system:SystemParametersInfoW Unimplemented action: 8193 (SPI_SETFOREGROUNDLOCKTIMEOUT) I switch to application window: fixme:system:SystemParametersInfoW Unimplemented action: 4118 (SPI_GETTOOLTIPANIMATION) fixme:system:SystemParametersInfoW Unimplemented action: 4120 (SPI_GETTOOLTIPFADE) fixme:win:AnimateWindow partial stub These messages appears repeatedly. I go to options page: err:mmio:MMIO_ParseExtA No . in szFileName: "MenuPopup" and window does not appear. Could anybody help me? I have other applications doesn't work after 200503xx. IChat is an example only. Thanks, Kryol
Hi all,> > I found that some applications does not work more. The last successfull version was20050310.> For testing I can propose one example : http://hem.bredband.net/alivor/ichat121b6.exe > > Now I try to use wine 0.9.1 under FreeBSD (KDE 3.4.0). > The application above is installed fine but during start I see: > > fixme:system:SystemParametersInfoW Unimplemented action: 8193 > (SPI_SETFOREGROUNDLOCKTIMEOUT) > > I switch to application window: > > fixme:system:SystemParametersInfoW Unimplemented action: 4118 > (SPI_GETTOOLTIPANIMATION) > fixme:system:SystemParametersInfoW Unimplemented action: 4120 (SPI_GETTOOLTIPFADE) > fixme:win:AnimateWindow partial stub > > These messages appears repeatedly. > > I go to options page: > > err:mmio:MMIO_ParseExtA No . in szFileName: "MenuPopup" > > and window does not appear. > > Could anybody help me? > > I have other applications doesn't work after 200503xx. IChat is an example only. > > Thanks, > Kryol >I found that this problem takes place with Delphi applications. What changed with delphi after 200503xx?
On Tue, 15 Nov 2005 11:20:10 +0200, in gmane.comp.emulators.wine.user you wrote:> Hi all, > >I found that some applications does not work more. The last successfull version was 20050310. >For testing I can propose one example : http://hem.bredband.net/alivor/ichat121b6.exeIn general if an application did work in the beginning of this year and not now, you should try setting the windows version to win98. That used to be the default, but in the recent versions it has become win2000.> >Now I try to use wine 0.9.1 under FreeBSD (KDE 3.4.0). >The application above is installed fine but during start I see: > >fixme:system:SystemParametersInfoW Unimplemented action: 8193 >(SPI_SETFOREGROUNDLOCKTIMEOUT) > >I switch to application window: > >fixme:system:SystemParametersInfoW Unimplemented action: 4118 >(SPI_GETTOOLTIPANIMATION) >fixme:system:SystemParametersInfoW Unimplemented action: 4120 (SPI_GETTOOLTIPFADE) >fixme:win:AnimateWindow partial stub > >These messages appears repeatedly. > >I go to options page: > >err:mmio:MMIO_ParseExtA No . in szFileName: "MenuPopup" > >and window does not appear. >All these messages are probably harmless. But if I press the "chat options" button it works most times. But I get in some cases (just keep trying the options window): |wine client error:14: read: Resource temporarily unavailable |err:ntdll:RtlpWaitForCriticalSection section 0x7befaf00 "server.c: fd_cache_section" wait timed out in thread 000b, blocked by 0014, retrying (60 sec) or |wine client error:12: read: Bad file descriptor |err:ntdll:RtlpWaitForCriticalSection section 0x7befaf00 "server.c: fd_cache_section" wait timed out in thread 000b, blocked by 0012, retrying (60 sec) After one of these messages the program is not responding anymore. CC'ing to the developer list. Hopefully someone there can give a suggestion. Rein.
> I found that some applications does not work more. > The last successfull version was 20050310.Unfortunately, this is the nature of Wine and the development of it. Applications (and things) which did work wonderfully in the past may not necessarily work in future versions. *Sometimes* they do, but it may take months or years to get that functionality back. I'm not saying the situation is right (I certainly don't think it is), but it's definately how things are. As far as this topic goes, "it's a dead horse that's been beaten many times." Though, who knows... maybe a few more swift kicks in the chest will revive it. ;) Hiji __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
CxxUnit is your friend. I have found that writing testcases _before_ fixing code speeds development cycles and prevents backwards steps. Write test case, prove it fails Fix code prove testcase passes Next pass, you run all of the testcases that have ever been made and confirm that you haven't broken anything else. Before release, all tests must pass. If a test fails, you must determine whether the test is broken or the code is broken, and fix whichever is broken. Over time, even doing this on an adhoc basis, you end up with a fairly complete automated test suite that "proves" all of the areas that have ever been problems. It still takes time to run these tests. However, four hours of the machine running all-out can run a lot more test scenarios than I could manually. Automating the test setup, execution, and teardown means that I can guarantee the scenario I want to test - there is no guesswork or falling into patterns (in the long run). I have an app that runs roughly 700 million dollars of business per year that has had zero support personnel for two years. The use of open source automated regression testing frameworks written in the programming language of the product has allowed the department responsible for the product to thoroughly re-test any outside impacts even though they have no programmers on staff familiar with its programming environment or language. Tying the open source testing library to the product has allowed me to build intelligent diagnostics, which in turn allows the product to explain to the user what is wrong, who to contact, and/or what to do to fix the problem themselves. CxxUnit is your friend.