http://bugs.winehq.org/show_bug.cgi?id=36480
Bug ID: 36480
Summary: Millenium Carillon Controller crashes on startup
Product: Wine
Version: 1.7.11
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lithiumfun(a)me.com
Created attachment 48544
--> http://bugs.winehq.org/attachment.cgi?id=48544
Back Trace
The program gives the error "Unable to load DLL 'FTD2XX.DLL': Exception from
HRESULT 0x8007007E". Program is Millennium Controller by Chimemaster Systems.
Uses .NET v2.0.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35615
Bug ID: 35615
Summary: Robin Hood Legend of Sherwood: Missing UI elements and
invisible cursor in-game
Product: Wine
Version: 1.7.12
Hardware: x86
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: devilhood(a)gmail.com
Classification: Unclassified
During gameplay, parts of the UI are either invisible or black, and the mouse
cursor is partly invisible.
Windows 8 users can only play this game using WineD3D. Without WineD3D it lags
to an unplayable degree. No other fixes are available and support has been
abandoned for this title.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=31055
Bug #: 31055
Summary: Sonic The Hedgehog 4 very slow on multicore cpu
Product: Wine
Version: 1.5.7
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: viny_viny304(a)hotmail.com
Classification: Unclassified
Sonic The Hedgehog 4 episode 1 and 2 is very slow on multicore cpus. Used
schedtool (to define the affinity. e.g. schedtool -a 0x1 -e wine ... ) the
performance improves considerably but still keeps a bit out of normal.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=20232
Summary: mciwave breaks on MSDN example
Product: Wine
Version: 1.1.30
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
I'm reviewing mciwave and mciseq and found numerous issues. Concurrently, I'm
augmenting the MCI testsuite. I've attached my current mciwave
work-in-progress tests to give you an early insight into my work.
The tests so far confirm my model of MCI: I view it like an old-fashioned tape
deck with buttons, which you can press in any order. Still there's error
checking, e.g. you can't resume when stopped. Like a tape deck, you can switch
from playing to recording at any time.
Oddly, you can combine fast forward and play in one command, but not rewind
with play.
The attached tests work fine on (at least one machine with) MS-Windows, but
cause Wine to fail and hang in multiple ways. You've been warned!
I'd be pleased if people could run the tests on more instances of MS-Windows.
I plan to strip down this test file until it at least does not hang anymore in
Wine. Then only can it be submitted. Concurrently, I can submit patches to
the mci* codebase.
Current issues with the mci code in Wine are:
- not distinguishing between STOPPING and STOPPED, PLAYING and GOING TO PLAY,
etc.;
- seriously broken asynchronous execution;
- non-error-proof use of InterlockDecrement. It must only be called
when waveInAddBuffer and waveOutWrite succeed, as those cause
callbacks to happen;
- RIFF .wav file not always correctly written;
- the mmio is as much as resource as the wave device and must be
properly released (mmioAscend, not only when saving);
- many items here and there:
+ bogus 44000Hz frequency;
+ premature return (in mcicda);
+ conversion between #bytes and samples;
+ switching fInput while playing;
+ copy&paste errors (InterlockedDecrement need be initialised
differently when recording and playing)
The major issue is concurrency. There I'm not sure how to proceed and rewrite
mciwave (and mciseq and mcicda).
o One model, Erlang-like, which the OSS driver also implements, is one thread
per play and exclusively using message passing to receive commands. This would
simplify NOTIFY everywhere. It clearly offers the advantage of being closest
to the sequential execution model that is easy to reason about. IMHO, it does
not play nicely with the pause command (state machine).
o Continue as currently written, but then think twice and even 3-7 times about
how to perform locking among the concurrent threads:
- Put InterlockIncrement() to more uses?
- Put Events to more uses?
- Unlike mciavi, there's no CriticalSection in mciwave and mcicda, yet
I'm unconvinced that the current synchronisation via volatile dwStatus
can suffice.
- But then, identifying the critical sections will be tedious and error prone.
o Combinations of both, e.g. one thread per play or record (not unlike the
present code), and dealing (correctly) with PAUSE, STOP and RESUME inside it
(via e.g. events to restart a paused thread, or indirectly, by relying on the
callbacks+events sent when invoking waveOutRestart and waveInStart -- is it
legal at all to call those from a different thread)?
o Is there any other concurrency model suitable in Wine?
Regards,
Jörg Höhle
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=35823
Bug ID: 35823
Summary: Widl should check for duplicated uuids when generating
typelib
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Duplicated uuids in a typelib will cause troubles with typeinfo lookup. Midl
refuses to generated such typelibs, but it looks like it might have a more
strict constraint - uuid should be unique in a file, and we don't want it to be
that strict (see bug 27718).
--
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.
http://bugs.winehq.org/show_bug.cgi?id=31232
Bug #: 31232
Summary: The Way Things Work 2.0 installer froze after finished
copying files
Product: Wine
Version: 1.1.21
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Nachanon_Vetjasit(a)hotmail.com
Classification: Unclassified
Regression SHA1: 54d7c8012d1d7369a56779955ced5a09e448a1cd
When started The Way Things Work 2.0 installer (setup.exe),
the setup proceeds normally, through the welcome screen,
quicktime installer prompt (though QuickTime 16bit 2.1.1 installation didn't
work [bug #18260]),
installation options (express/custom), files copying progress window.
But as soon as the file copying window disappeared, the installer froze, no
screen repainting, no message from WINE's console.
(Normally this stage should be creating program groups and ends at the 'Setup
Complete' window)
54d7c8012d1d7369a56779955ced5a09e448a1cd is first bad commit
commit 54d7c8012d1d7369a56779955ced5a09e448a1cd
Author: Dmitry Timoshkov <dmitry(a)codeweavers.com>
Date: Wed Apr 29 15:17:35 2009 +0900
explorer: Initialize the Progman DDE interface when starting explorer.
:040000 040000 4a347655bb6f41b8b8377d8e3e3e25c1551d1730
05513d15b76a99fe5033c4422a82008667425088 M programs
With WINE before this commit, the installation would continue, with WINE's
Program Manager (progman)
popped up with a dialog from the setup program: "Unable to start DDE
communication with Program Manager." [Abort/Retry/Ignore]
If clicked 'Ignore' (aka. continue despite the error), this step will be
repeated for another five time, each time leaving one Program Manager window
opened (6 window total at the end).
And finished with 'Setup Complete' window.
Note:
The Way Things Work is a 16-bit application, and supports Windows 3.1.
Tested using WINE's Windows version 98.
WINE: wine-1.1.21 source distribution
System: Debian GNU/Linux 5.0 "Lenny" i386 (Intel Pentium 4 2.66GHz)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=36871
Bug ID: 36871
Summary: Chronology with native .NET is postage stamp sized
Product: Wine
Version: 1.7.21
Hardware: x86
URL: http://store.steampowered.com/app/269330/
OS: Linux
Status: NEW
Keywords: dotnet
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
This is with 'winetricks dotnet20' in a 32-bit prefix.
Chronology appears to run OK, except that it creates a large black window with
a tiny image in the upper-left corner. Maybe it's the title screen? It's too
small to be sure.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=36648
Bug ID: 36648
Summary: Alt+F4 key function error
Product: Wine
Version: 1.7.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: szilipeter(a)freemail.hu
1. settings winecfg:
-- Graphics: Emulate a virtual desktop (UNCHECK)
When I run a program, for example "winecfg", and
- Select "Drives"
- Select "Add"
- press "Alt-F4"
This time : Close "Select Drive Letter" window, and focused the "Wine
configuration" windows.
When I setting 2. version:
-- Graphics: Emulate a virtual desktop (CHECK)
When I run a program, for example "winecfg", and
- Select "Drives"
- Select "Add"
- press "Alt-F4"
This time : Close the "winecfg" application. Why ?
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35813
Bug ID: 35813
Summary: SolidWorks 2013: Crash at the beginning
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukasz.wojnilowicz(a)gmail.com
Created attachment 47811
--> http://bugs.winehq.org/attachment.cgi?id=47811
Crash window
Steps to reproduce:
1) remove ~/.wine
2) winetricks vcrun2010 dotnet40
3) install SolidWorks 2013
4) wine SLDWORKS.exe
Behaviour:
Crash (See attachment)
Expected behaviour:
No crash.
Additional info:
1) Window from attachment is "sldexitapp.exe"
2) "sldProcMon.exe" started by "SLDWORKS.exe" takes all CPU resources
--
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.