http://bugs.winehq.org/show_bug.cgi?id=8854
--- Comment #56 from Valeriy Malov <jazzvoid(a)gmail.com> 2010-02-11 01:27:12 ---
(In reply to comment #54)
> That's unfeasible, especially for systems without xi2.
Systems without xi2 don't use recent versions of wine and xi2 should be
avaliable now even for debian testing
--
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=8854
--- Comment #55 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-02-11 01:24:56 ---
(In reply to comment #53)
> > A fix which would solve the problem for both native and built-in dinput would
> > seem ideal.
> This won't happen - Wine uses hooks to deliver mouse and keyboard messages to
> dinput. Hooks won't work without message loop. Not without complete rewrite at
> least. And making it work another way means implementing fake drivers which
> will be complete waste of time.
That confirms what I've said in the comment #48: Wine due to its architecture
should implement this differently.
--
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=8854
--- Comment #54 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-02-11 01:23:00 ---
(In reply to comment #51)
> > I suspect that won't work on Windows either.
> Yes it will - dinput talks directly to kbd/mouse/joystick drivers. In fact this
> whole bug is exactly about these cases - when window is created in the
> different thread then the one asking and/or the thread that created window has
> no message loop at all or during the game play.
Is there a test case for that to confirm this behaviour?
> The only proper way to fix this is the same as fixing dinput mouse - use xi2 to
> get raw keyboard events from X.
That's unfeasible, especially for systems without xi2.
--
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=6971
Jared Sutton <jpsutton(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|jpsutton(a)gmail.com |
--
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=6971
--- Comment #326 from Jouni Järvinen <jounijarvis(a)gmail.com> 2010-02-11 01:12:55 ---
(In reply to comment #325)
> He said that it covers three Unreal Engine generations, and that's basically
> what's being affected by this bug. Of course, if it doesn't work in windowed
> mode, it is a hack, but it's still better than nothing.
>
> If you believe that it's better to post all of the patches/hacks in a Wiki,
> then you could create a page for it and give the link here, otherwise there's
> not much use of patches scattered all over the Internet.
>
> By the way, why is this bug still unassigned? It seems that the status should
> be anything but "New" given that nearly 4 years have passed since the initial
> bug report...
I agree with you totally.
I predict a specific response from Vitaliy ...
--
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=6971
--- Comment #325 from GreatEmerald <pastas4(a)gmail.com> 2010-02-10 14:25:32 ---
He said that it covers three Unreal Engine generations, and that's basically
what's being affected by this bug. Of course, if it doesn't work in windowed
mode, it is a hack, but it's still better than nothing.
If you believe that it's better to post all of the patches/hacks in a Wiki,
then you could create a page for it and give the link here, otherwise there's
not much use of patches scattered all over the Internet.
By the way, why is this bug still unassigned? It seems that the status should
be anything but "New" given that nearly 4 years have passed since the initial
bug report...
--
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=6971
Dennis Schridde <devurandom(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|devurandom(a)gmx.net |
--
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=8854
--- Comment #53 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2010-02-10 08:50:15 ---
(In reply to comment #52)
> A fix which would solve the problem for both native and built-in dinput would
> seem ideal.
This won't happen - Wine uses hooks to deliver mouse and keyboard messages to
dinput. Hooks won't work without message loop. Not without complete rewrite at
least. And making it work another way means implementing fake drivers which
will be complete waste of time.
--
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=6971
Clarence Risher <sparr0(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|sparr0(a)gmail.com |
--
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=21674
Summary: IWD2: mounted ISO is not recognized
Product: Wine
Version: 1.1.38
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=26180)
--> (http://bugs.winehq.org/attachment.cgi?id=26180)
Trying to starting the game on Wine 1.1.38
I'm using Fedora 12 32 bit with Wine 1.1.38.
The problem is that Icewind Dale 2 (Polish 2 CD version) doesn't recognize
second CD mounted with fuseiso when I want to play that game.
Steps to reproduce:
1) Mount CD1 and CD2
fuseiso -p "ICEWIND2_1.iso" ~/ICEWIND2_1/
fuseiso -p "ICEWIND2_2.iso" ~/ICEWIND2_2/
2) start winecfg and set ICEWIND2_1 and ICEWIND2_2 to CD-ROMS
3) Install the game (full option)
4) Try to start the game from root directory of the game by
wine IWD2.exe
5) Get and error with please insert second CD
ISO images are good because they allow me to play on MS Windows XP. According
to ISOMaster first ISO image has
"Volume Name=ICEWIND2_1"
"Filename types: RockRidge, Joliet"
The game hasn't got any special protection apart from CD-check. The game works
when I use NO-CD workaround. I'm attaching terminal output when game doesn't
recognize second CD.
--
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.