[Bug 21980] ImgBurn: no recognized drives
wine-bugs at winehq.org
wine-bugs at winehq.org
Tue Mar 9 12:55:17 CST 2010
http://bugs.winehq.org/show_bug.cgi?id=21980
--- Comment #3 from A Wine user <RandomAccountName at mail.com> 2010-03-09 12:55:17 ---
Created an attachment (id=26719)
--> (http://bugs.winehq.org/attachment.cgi?id=26719)
Terminal output
Alright, I think I can confirm this bug. I have two burners installed - one
works with SPTI + Wine, the other doesn't. In 1.1.39, ImgBurn could detect the
problematic drive if I switched the burning interface option to ASPI, but this
no longer works in 1.1.40. Sounds like the same problem you describe.
I did a regression test myself and got this:
6d4cf67a56dee87180d447eae3562d35798ba75c is first bad commit
commit 6d4cf67a56dee87180d447eae3562d35798ba75c
Author: Alexandre Julliard <julliard at winehq.org>
Date: Mon Mar 1 14:02:16 2010 +0100
kernel32: Create the hardware registry keys one at a time, and bail out if
the main key already exists.
:040000 040000 d4368060b1003e43f7057448876e07055d40515d
4d8677c56a8c852c0a1a5ffdea4e50a986d5d731 M dlls
--
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.
More information about the wine-bugs
mailing list