http://bugs.winehq.org/show_bug.cgi?id=57415 Andrew Nguyen <arethusa26@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal URL| |https://www.romcenter.com/d | |ownloadfile.php?file=romcen | |ter32_4.1.1.exe Ever confirmed|0 |1 Regression SHA1| |9c1ffb545f350743e71cdfcc0da | |e5e98324d10ee Status|UNCONFIRMED |NEW Keywords| |download --- Comment #11 from Andrew Nguyen <arethusa26@gmail.com> --- I can confirm that the issue with Romcenter still persists with the default version of Wine Mono (10.4.1) in wine-11.0. For reference, here's how I reproduced the problem: 1. Install Romcenter using the romcenter32_4.1.1.exe installer. 2. Download MAME from https://github.com/mamedev/mame/releases/download/mame0284/mame0284b_x64.exe and run the executable to extract MAME to a directory. MAME is needed as a new database source for Romcenter. 3. Launch Romcenter and answer No to the "Removed rom strategy" prompt. 4. Press the New button on the ribbon menu of the main window. 5. Select mame.exe in the extracted MAME directory for the source datafile. 6. To avoid an out-of-memory condition, update the filter settings to enable "Games filtering" and select Drivers -> CPS 1, uncheck Samples and Disks for Type, and uncheck No dumps and Bad dumps for Status. 7. Press the create button to generate a new database. I can also confirm that Wine Mono 8.0.0 did not have the reported issue, but Wine Mono 8.1.0 did. It turns out that the fix for bug 49804 introduced the regression in Romcenter, presumably by allowing more code to run when the System.Windows.Controls.Ribbon control became available. The same reported issue is tracked in Wine Mono at https://github.com/wine-mono/wine-mono/issues/205 where a change has been made to fix the reported problem. I can confirm that Wine Mono built from the latest main allows Romcenter to create a new database successfully, and I expect that this bug will be fixed when the default version of Wine Mono is updated to include the WPF fix. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
