http://bugs.winehq.org/show_bug.cgi?id=8440 Summary: Heavy Weather runs too slow / possible serial port baud rate issues? Product: Wine Version: 0.9.33. Platform: PC-x86-64 URL: http://www.heavyweather.info/new_english_us/index.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: vortex1111vortex(a)gmail.com When running HeavyWeather inside of wine - the app starts - but when the app comes up - it uses 100% of the CPU. And it's really really slow. When the GUI comes up - it makes requests via the serial port to get the data for about 15 different fields that are displayed. With an older version of wine (same hardware) - this took about 2 seconds to get all 15 fields. Now, it takes about 5 seconds _per field_ to get the data. Eventually, all of the fields fill in - but CPU usage stays locked at 100% - and any interaction that I try to have with the application is really slow. The application then crashes within 3 to 4 minutes. While the application is running, this is printed out on the terminal: err:file:GetOverlappedResult PENDING status after waiting! err:file:GetOverlappedResult PENDING status after waiting! err:file:GetOverlappedResult PENDING status after waiting! The trace (that I'll attach shortly) indicates a really slow baud rate has been selected: 000d:trace:comm:dump_dcb bytesize=8 baudrate=2400 fParity=0 Parity=0 stopbits=1 The application doesn't provide any configuration for baud rate. It's basically unusable in its present form - and this is a regression - it used to run much better in wine. On the mailing list Detlef Riekenberg indicated:
If the App has no options to configure the Serial Port, it may use the default COM-Settings.
Old Wine versions returned always 38400 as Baud-Rate and Hardware-Handshake for the Flow-Control. This was fixed recently.
Not sure if that has anything to do with the slowdown. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.