https://bugs.winehq.org/show_bug.cgi?id=39674
--- Comment #17 from Sergey Isakov isakov-sl@bk.ru --- (In reply to Austin English from comment #16)
(In reply to Sergey Isakov from comment #14)
This workaround is also valid for wine-staging-1.8rc2.
Looks like Futuremark SystemInfo doesn't like fake Bluetooth.cpl
I see no evidence of that here. The previous information in the bug is about fltmgr.sys and bthprops.cpl, not bluetooth.cpl (and that info has changed a few times). There is no reference to bluetooth.cpl in the relay log either.
For me, with -nosysteminfo, 3dmark03 launches fine, as it did in 1.7.54. I suspect your regression test is wrong, as you've mentioned it may be timing/load related.
Additionally, bluetooth wasn't in Windows when 3DMark03 was released (it came in XP SP2, released in 2004), so I highly doubt 3DMark03 has any knowledge of bluetooth (additionally, why would a d3d benchmark need/use bluetooth).
No, I am right. First see the commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a contents ~~~~ +++ b/dlls/bthprops.cpl/bthprops.cpl.spec @@ -0,0 +1,65 @@ +@ stub BluetoothAddressToString +@ stub BluetoothAuthenticateDevice +@ stub BluetoothAuthenticateDeviceEx +@ stub BluetoothAuthenticateMultipleDevices +@ stub BluetoothAuthenticationAgent ~~~ It is Bluetooth Properties Control Panel as I think.
Second, I made careful regression test. I saved all intermediate wine-1.7.54-xxx and can check again with any of them.
Third, I checked that reverting this commits in wine-1.8rc2 allows me to start 3DMark03, 3DMark05 and 4DMark06 in different installations without the argument -no-systeminfo.
Without this argument the application Futuremark SystemInfo is called. To success we need version 428 of the application. The trick is described on this site: - Install 3DMark05. Full installation. - Uninstall followed Futuremark SystemInfo provided with it. - Install Futuremark SystemInfo -4.2.8 $ md5 Futuremark_SystemInfo_v428_installer.msi MD5 (Futuremark_SystemInfo_v428_installer.msi) = 4fdc487ed5948703e63011aa28e05447 Take wine-1.7.54. Now you can start 3DMark05 with SystemInfo. For wine versions >= 1.7.55 you have to revert commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a Tested several times on several configurations.
The bug has no any relation to bug 20296.