April 2011 - Wine-Bugs - list.winehq.org

[Bug 1348] RegisterHotKey and UnregisterHotKey are not implemented. (Affects e.g. Adobe Photoshop.)
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=1348 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch --- Comment #25 from Austin English <austinenglish(a)gmail.com> 2011-04-10 15:06:24 CDT --- Still unimplemented. -- 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.

1 0

[Bug 26422] New: Wine and Dosbox use different MS-DOS (8.3) file names
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=26422 Summary: Wine and Dosbox use different MS-DOS (8.3) file names Product: Wine Version: 1.3.15 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dos AssignedTo: wine-bugs(a)winehq.org ReportedBy: spammis(a)spam.la MS-DOS and 16-bit Windows programs require file names to consist of 8 letters followed by a 3-digit extension (known as "MS-DOS file names" in Windows 95, sometimes also called 8.3 filenames). Wine and Dosbox both emulate MS-DOS file names, but they do it differently. Long name: C:\Program Files Wine name: C:\PROG~FBU Dosbox name: C:\PROGRA~1 Thus, a Windows program, running under Wine, may refer to a file as "C:\PROG~FBU\SOMEFILE.TXT" whereas a DOS program, running under Dosbox using Wine's Dosbox implementation, would know the same file as "C:\PROG~FBU\SOMEFILE.TXT". This means trouble if the Windows and DOS programs are trying to interact. In order to view Wine's MS-DOS names, use certain 16-bit Windows programs (such as the Windows 3.1 file manager). In order to view Dosbox's MS-DOS names, use "DIR" in Dosbox or any DOS program. Dosbox only uses MS-DOS names, so it won't show any other names. -- 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.

1 5

[Bug 18292] New: Make 8.3 names for LFNs more "Windows-like"
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=18292 Summary: Make 8.3 names for LFNs more "Windows-like" Product: Wine Version: 1.1.20 Platform: PC URL: http://source.winehq.org/source/dlls/kernel32/path.c OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk When Windows creates 8.3 names for long file names, it does so in the form Progra~1 and increments the number by one with each new creation of a similar filename. So, Program Files --> Progra~1 Programmers --> Progra~2 Program Blah blah --> Progra~3 and so on. Under Wine, the 8.3 filenames seem somewhat random (PROG~HAE for example). Is it possible to implement this behaviour? It would make it easier to guess short path names, which makes it easier to add paths to the registry (when needed for workarounds, for example). -- 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.

1 8

[Bug 22059] New: when /dev/input/event* device is accessible, wine fails to consider calibration and correction factors of the linux joydev driver
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=22059 Summary: when /dev/input/event* device is accessible, wine fails to consider calibration and correction factors of the linux joydev driver Product: Wine Version: 1.1.40 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: corvus-wine(a)cybertrench.com Created an attachment (id=26862) --> (http://bugs.winehq.org/attachment.cgi?id=26862) joydev log with event file accessible Linux provides the possibility to correct joystick raw values automatically when accessing /dev/input/js* devices, both autodetected/scaled and "hand-calibrated" with tools like "jscal" if wine uses /dev/input/js* for joystick access, it also takes the correction factors into account, so a joystick that has been calibrated under linux, will be calibrated correctly under wine. However if the /dev/input/event* file corresponding to the joystick device is accessible (at least for reading) wine seems to bypass the joydev driver and accesses the device on a lower (event) level, thus unaware of the calibration data and correction factors - whether manually set and autodetected! As a result programs run under wine that use a joystick but offer no inbuilt calibration option (which is most, since under native win32 joysticks are calibrated system wide in the input device area of the control center) will behave strangely as joysticks are potentially off-centered - mis-scaled - axis flipped - or even unable to cross the zero position at all. Depending on the actual joystick hardware and the required corrections. the attached log1.txt shows the output of a joystick using program (il2fb flightsim) started with dinput WINEDEBIUG output grep'd for "joydev" when the event device is accessible (and the joystick is unusable due to miscalibration > WINEDEBUG=+dinput wine il2fb.exe 2>&1 |grep joydev log2.txt shows the same output with /dev/input/event5 (the joystick event device) chmodded to 000 in this case the axis and buttons are mapped completely different, but centered and scaled correctly (given that the jopystick had been calibrated under linux using jscal) for obvious reasons this bug is only visible if the axis values reported by the event device, especially min and max: ... > cur=97, min=0, max=255, fuzz=0, flat=15 ... are not equal to the actually reachable minimum and maximum values. newer joysticks often autoscale in hard/firmware and actually reach those min/max values with little need for calibration, while some, especially older models, are in dire need of correction values since the actual range (as in this case) is more like 30 to 120 -- 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.

1 5

[Bug 26700] New: Oblivion InstallShield Crashes
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=26700 Summary: Oblivion InstallShield Crashes Product: Wine Version: 1.3.16 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: travissidelinger(a)gmail.com Created an attachment (id=34000) --> (http://bugs.winehq.org/attachment.cgi?id=34000) Wine and InstallShield outputs Found a new bug here. While trying to install Elder Scrolls Oblivion I cannot get past an InstallShield crash. Error Code: -5006 : 0x8000ffff I've tried a lot of things and nothing has worked: - 32bit and 64bit installs - Pre-installed directx - Pre-installed fonts - Pre-installed the game's shipped version of directx - Thinking my original DVD could have been bad, I've download a new ISO and installed from my HD - I've run wine through "strace -f 2>&1 | grep open" looking for missing files. OS distro: Fedora 14 x86_64 $ uname -a Linux gandalf.ravenloft.mist 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ wine --version wine-1.3.16 See the attached files for my wine and installshield outputs. -- 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.

1 6

[Bug 9190] Warhammer: Dark Omen doesn't launch
by wine-bugs＠winehq.org April 9, 2011

April 9, 2011

http://bugs.winehq.org/show_bug.cgi?id=9190 --- Comment #22 from Michael Curran <curran.michaelp(a)gmail.com> 2011-04-09 16:21:15 CDT --- Created an attachment (id=34013) --> (http://bugs.winehq.org/attachment.cgi?id=34013) Console log with +ddraw,+tid -- 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.

1 0

[Bug 9190] Warhammer: Dark Omen doesn't launch
by wine-bugs＠winehq.org April 9, 2011

April 9, 2011

http://bugs.winehq.org/show_bug.cgi?id=9190 --- Comment #21 from Michael Curran <curran.michaelp(a)gmail.com> 2011-04-09 16:20:28 CDT --- Looks like the back buffer/front buffer problem has been resolved! But... the game still crashes during startup, still during ddraw calls. No major errors (log is attached with +ddraw,+tid), all I see is: 0021:trace:ddraw:ddraw_surface3_AddAttachedSurface iface 0x103c5bc, attachment 0xeed5dc. 0021:warn:ddraw:ddraw_surface3_AddAttachedSurface Invalid attachment combination. . . . 0021:trace:ddraw:IDirect3DDeviceImpl_1_CreateExecuteBuffer iface 0x1063a9c, buffer_desc 0x33f958, buffer 0xeede28, outer_unknown (nil). 0021:trace:ddraw:IDirect3DDeviceImpl_1_CreateExecuteBuffer Returning IDirect3DExecuteBuffer at 0x10a4148, implementation is at 0x10a4148 wine: Unhandled page fault on write access to 0x00000010 at address 0x44ee66 (thread 0021), starting debugger... -- 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.

1 0

[Bug 9190] Warhammer: Dark Omen doesn't launch
by wine-bugs＠winehq.org April 9, 2011

April 9, 2011

http://bugs.winehq.org/show_bug.cgi?id=9190 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #20 from joaopa <jeremielapuree(a)yahoo.fr> 2011-04-09 15:28:13 CDT --- at maikwagner> Use the nvidia official driver, not the Nouveau driver. -- 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.

1 0

[Bug 9190] Warhammer: Dark Omen doesn't launch
by wine-bugs＠winehq.org April 9, 2011

April 9, 2011

http://bugs.winehq.org/show_bug.cgi?id=9190 maikwagner(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maikwagner(a)yahoo.com --- Comment #19 from maikwagner(a)yahoo.com 2011-04-09 11:48:37 CDT --- I would like to confirm this bug. I am currently trying to get this game to work but it fails with an "unrecoverable error" after switching resolution and that a file called "regengl.exe" (?) is not working. I filed an AppDB entry and the previous report also has a problem with this .exe-file. Wine version is: wine-1.3.14 Linux kernel is: 2.6.35.6-45.fc14.i686 (Fedora 14) Graphics: Onboard Intel Chipset Settings: Windows 95 -- 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.

1 0

[Bug 9190] Warhammer: Dark Omen doesn't launch
by wine-bugs＠winehq.org April 9, 2011

April 9, 2011

http://bugs.winehq.org/show_bug.cgi?id=9190 --- Comment #18 from maikwagner(a)yahoo.com 2011-04-09 11:44:35 CDT --- Created an attachment (id=34010) --> (http://bugs.winehq.org/attachment.cgi?id=34010) Warhammer Dark Omen Output on Fedora 14 using Win95 settings -- 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.

1 0