wine and winuae

[hit]

http://www.winuae.net/files/b/winuae_1600b16.zip -> seems broken: "Service Temporarily Unavailable"

Problem: was running 1.5.3 using wine 1.1.15 (got updated yesterday) and window-only emulation got totaly unuseable, so i found this one: `wine explorer /desktop=x winuae.exe` -> which opens a virtual desktop - never seen that option before. using fullscreen mode here.
problem here:
fixme:d3d:IWineD3DDeviceImpl_CreateSwapChain The app requests more than one back buffer, this can't be supported properly. Please configure the application to use double buffering(=1 back buffer) if possible

is there an option to cope with that?

Edit: btw. do you use different approches when opening the config window, either using F12 or the mouse-botton on the lower window bar? using f12 doesn't let the window quit, it just comes back after clicking "ok" - needs to get "restart" & "ok" then you can "quit". works well using the mouse-button on the lower buttons (Power) (01) (02).

[Toni Wilen]

Not really beta related

1. WinUAE should default to doublebuffering if triplebuffer fails. (probably not very well tested or perhaps wine returns something weird in this case..)

2. http://eab.abime.net/showpost.php?p=457841&postcount=12

[hit]

well yes, not only affecting beta. wine suxx, but running vmware or vbox doesnt make it any faster on this box here, so ...

1) "requests more than one back buffer" means, wine just can deal with "single buffer" ?

2) oh, havnt seen this. wonder why noone filed a bug-report on winehq.

thnx.

[Toni Wilen]

Originally Posted by hit

well yes, not only affecting beta. wine suxx, but running vmware or vbox doesnt make it any faster on this box here, so ...

1) "requests more than one back buffer" means, wine just can deal with "single buffer" ?

I guess it means it can only handle single backbuffer (=front and back buffer = doublebuffered)

Include both wine and winuae logs, thanks.

2) oh, havnt seen this. wonder why noone filed a bug-report on winehq.

It is (but it looks like nobody cares)

[hit]

wasnt sure, if i should open a new thread, but this has been fixed it seems

here is the wine output and winuae logfile:

wine explorer /desktop=x winuae.exe

fixme:system:SetProcessDPIAware stub!
fixme:reg:GetNativeSystemInfo (0xa0f680) using GetSystemInfo()
fixme:win:EnumDisplayDevicesW ((null),0,0x33f62c,0x00000000), stub!
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x142608,0x142508): stub
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x142598,0x142508): stub
fixme:win:GetRawInputDeviceList (pRawInputDeviceList=(nil), puiNumDevices=0x33fac0, cbSize=8) stub!
fixme:shell:SHAutoComplete SHAutoComplete stub
fixme:shell:SHAutoComplete SHAutoComplete stub
fixme:win:RegisterDeviceNotificationW (hwnd=0x10030, filter=0x33f6e0,flags=0x00000000),
        returns a fake device notification handle!
fixme:win:RegisterDeviceNotificationW (hwnd=0x20044, filter=0x33e248,flags=0x00000000),
        returns a fake device notification handle!
fixme:d3d:IWineD3DDeviceImpl_CreateSwapChain The app requests more than one back buffer, this can't be supported properly. Please configure the application to use double buffering(=1 back buffer) if possible
fixme:volume:GetVolumePathNameW (L"AmigaSYS\\Work", 0x33ec78, 2000), stub!
fixme:volume:GetVolumePathNameW (L"Z:\\tmp\\amiga\\WinUAE\\W0rk", 0x33ec78, 2000), stub!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:win:RegisterDeviceNotificationW (hwnd=0x30044, filter=0x33e158,flags=0x00000000),
        returns a fake device notification handle!
fixme:d3d:IWineD3DDeviceImpl_CreateSwapChain The app requests more than one back buffer, this can't be supported properly. Please configure the application to use double buffering(=1 back buffer) if possible
fixme:win:RegisterDeviceNotificationW (hwnd=0x2003c, filter=0x33f620,flags=0x00000000),
        returns a fake device notification handle!
fixme:win:RegisterDeviceNotificationW (hwnd=0x3003c, filter=0x33f620,flags=0x00000000),
        returns a fake device notification handle!
fixme:win:RegisterDeviceNotificationW (hwnd=0x4003c, filter=0x33f620,flags=0x00000000),
        returns a fake device notification handle!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:win:GetRawInputDeviceList (pRawInputDeviceList=(nil), puiNumDevices=0x33fb30, cbSize=8) stub!
fixme:win:RegisterDeviceNotificationW (hwnd=0x40044, filter=0x33f6e0,flags=0x00000000),
        returns a fake device notification handle!
fixme:avifile:AVIFileExit (): stub!

[hit]

sorry for *bumping* but does it help, if i can tell, that it seems a problem only in native amiga modes?! its flickering when booting (bootmenu, for example) but gets a stable picture when running in rtg mode. using fullscreenmode in native & rtg (since window mode got useless in wine 1.1.15).

[Toni Wilen]

Native and RTG display rendering is very different. Enabling filter may help, or wait for wine update..

[hit]

ok. i already watch the updates-testing repositories (fedora updates)

Edit: filter was a good point (never used before). using "null filter" made the native screen non-flickering. the above errormessages are still present, but its useable now (fullscreen) cool

Edit: i've compiled a src.rpm of 1.1.17 - window mode is working again. the F12 issue is still there, but using the gadgets of the window ("power" button) works .