http://bugs.winehq.org/show_bug.cgi?id=15866
Summary: MechCommander 2: DSERR_CONTROLUNAVAIL errors
Product: Wine
Version: 1.0.1
Platform: PC
URL: http://www.mechcommander.org
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: directx-dsound
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: georg298(a)gmx.de
Starting the game with
WINEDLLOVERRIDES="dpnet=n" wine MC2Rel.exe -window /gosnoblade /gosusehw
it will display many
FAILED (0x8878001e - DSERR_CONTROLUNAVAIL) - SetPan(0x8fa89a0: 0)
errors. These errors occur each time a sound notification or similar (e.g.
hovering the mouse over a button in the menu or firing a weapon inside the
game) is played.
The reason is the function
IDirectSoundBufferImpl_SetPan
inside buffer.c from dsound dll.
The following code is the reason:
/* You cannot use both pan and 3D controls */
if (!(This->dsbd.dwFlags & DSBCAPS_CTRLPAN) ||
(This->dsbd.dwFlags & DSBCAPS_CTRL3D)) {
WARN("control unavailable\n");
return DSERR_CONTROLUNAVAIL;
}
Is the logic here correct?
Shouldn't "if(!A || B)" really be if(!(A || B)) ?
However the comment "You cannot use both pan and 3D controls" doesn't make any
sense in both cases, I think.
If I change it accordingly, it will work (not display these errors any more):
/* You cannot use both pan and 3D controls */
if (!((This->dsbd.dwFlags & DSBCAPS_CTRLPAN) ||
(This->dsbd.dwFlags & DSBCAPS_CTRL3D))) {
WARN("control unavailable\n");
return DSERR_CONTROLUNAVAIL;
}
Changing it according to the comment to if(A && B) doesn't work.
I hope I provided enough information. I don't really know what I did there.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37308
Bug ID: 37308
Summary: GDI performance regression after Ubuntu 12.04 to 14.04
upgrade; incl. testable app
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: gustep12(a)yahoo.com
Thank you for working on Wine. I love the fact that Wine occasionally works
better (much faster and yet accurate rendering) for legacy Windows XP
applications than newer Windows versions!
For example, here is a legacy CAD application which is easy to install and run
in Wine, but which is very GDI intensive. As such, it is a good test for GDI
speed issues. When you open a complex CAD file, this app runs nicely in Windows
XP, but 5x or 10x slower in Windows Vista and later. Fortunately, it runs at
least the same or faster in Wine than it does in WinXP!
In fact, I guess I run this app half the time just to see how and if Wine is
working.
The application in question is PCB123 v2.1.0.7000, you can search for it online
or get the 7MB installer here. It always installs easily and works well in
Wine:
pcb123installer.exe (v2.1.0.7000, ~7MB):
https://stanford.box.com/s/69ijfwjf7qc95bq6bh2m
I purposely use this older version of PCB123 because, compared to versions that
came later, it has significantly faster display rendering performance with
complex PCB designs, such as this one, which I made:
PCB123-v2-complex-testfile.123, ~800kB:
https://stanford.box.com/s/3kmfcif91c1e909ak7jc
If you open this *.123 PCB design file and turn the mousewheel to zoom in or
out, it triggers a complete screen redraw. A screen redraw can take from one to
five seconds on sub-optimal software (Windows Vista/7/8, newest Wine), but
should take only a fraction of a second with good software (Windows XP, earlier
Wine).
If the scree re-draw takes too long, you can hide the filled copper planes of
the PCB. This speeds up redraws significantly, but the general issue (rendering
is now slower than it used to be, decreasing productivity) remains:
PCB123-v2-complex-testfile-nofill.123, ~800kB:
https://stanford.box.com/s/08zamniq0gx3imlwhi76
This software was originally released in the Windows XP years. It ran much
worse on Windows 7. It ran super-fast on Wine, regardless of hardware and/or
Linux version, I believe. Over time, I ran this software under Wine on a few
different Linux distros (Fedora, Mint, Ubuntu), and different hardware (older
Thinkpad with slow IGP, newer desktop with GTX660), the results were always
great under Linux+Wine, and much poorer under Windows 7.
Most recently, I had it running smoothly on Ubuntu 12.04 LTS, probably with
Nvidia binary driver 319 and whatever Wine version was up to date.
Then, about three days ago, I let Ubuntu proceed with the upgrade to 14.04 LTS.
Initially, PCB123 worked quickly, but then another set of Ubuntu 14.04 updates
came in, probably including the Nvidia driver update v331. Somehow this
un-installed Wine, and I couldn't re-install it - same issue as described here:
http://askubuntu.com/questions/449507/nvidia-libopencl1-331-has-to-be-remov…
Following the instructions on that page, I then did this:
sudo apt-get install nvidia-cuda-toolkit #Need to get 250 MB of archives; 774
MB of additional disk space will be used
sudo apt-get install ocl-icd-opencl-dev #this will remove nvidia-libopencl1-*
and nvidia-opencl-dev
sudo apt-get install wine #Need to get 121 MB; 342 MB of additional disk space
will be used.
Then I reinstalled Wine successfully, but then somehow the display performance
of PCB123 got much, much slower. I estimate the screen redraw speed is now at
least 20x to 50x slower than it used to be.
I am now trying to roll back the Nvidia drivers, the Wine versions, and so
forth, to narrow down where the problem lies. No luck so far, PCB123 remains
slow. I may even try to install Ubuntu 12.04 LTS again just to see if this
fixes it. Any advice on how I can force different versions of Wine or relevant
DLLs for testing?
Any tips on how I can support fixing this issue?
Best regards,
Sebastian
--
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=24388
Summary: Exposure crashes while creating exposure image
Product: Wine
Version: 1.3.2
Platform: x86
URL: http://www.nimisis.com/projects/exposure.php
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
this handy little app creates an image out of a webcamcapture or avi-file, as
if you would take a picture with a camera with a long shuttertime.
Steps to reproduce: i did:
1.winetricks allcodecs
2.Run exposure, and choose "From AVI --> Browse"
3. Select an AVI-file , then do "Load from AVI"
It crashes right away; with native avifil32 the crash is gone. There is no
avifil32 component in bugzilla. I'll attach a +relay,tid,+seh log
--
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=27165
Summary: ffdshow A/V config tool: drop-down list doesn't appear
Product: Wine
Version: 1.3.20
Platform: x86
URL: http://sourceforge.net/projects/ffdshow-tryout/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
In ffdshow's audio/video configuration window you can choose which decoder you
want to use for different A/V formats.
A drop-down menu should appear automatically when you select a decoder for the
desired format.
The menu doesn't appear in current Wine.
Actually, there is a way to make the menu appear: press and hold left mouse
button on the selected field (under Decoder tab). While LMB is still pressed,
move the mouse up or down by a couple of pixels.
Workaround: native comctl32.
This 'feature' worked correctly in Wine-1.1.2:
098dc7b3302f39c5500d644615a6f4c37d328ce0 is the first bad commit
commit 098dc7b3302f39c5500d644615a6f4c37d328ce0
Author: Lei Zhang <thestig(a)google.com>
Date: Mon Aug 18 16:05:27 2008 -0700
comctl32: Set listview focus on WM_LBUTTONUP instead of WM_LBUTTONDOWN.
:040000 040000 ab9cd9294cee7fd398296c68872b1661d28953c2
e40db8f62a0588aac662bc68d5f6b1aafe86e42e M dlls
To reproduce the issue in the application:
1) Install the app as usual: at the end of installation choose the option to
run the config tool automatically.
2) Under the Decoder tab select a field (containing either disabled or
libavcodec) >> the drop-down list doesn't appear.
The config tool can also be launched by:
wine rundll32.exe ffdshow.ax configure
--
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=35330
Bug ID: 35330
Summary: Typo: "in a separate windows" on the Man Page (at
http://www.winehq.org/docs/wine )
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: documentation
Assignee: wine-bugs(a)winehq.org
Reporter: shlomif(a)shlomifish.org
Classification: Unclassified
Hi all,
there's a typo in the man page (at http://www.winehq.org/docs/wine and "man
wine" from wine-1.6.1):
[QUOTE]
For running CUI executables (Windows console programs), use wineconsole
instead of wine. This will display all the output in a separate
windows (this requires X11 to run). Not using wineconsole for CUI
programs
will only provide very limited console support, and your program might
not function properly.
[QUOTE]
"in a separate windows" should be "in a separate window".
Regards,
-- Shlomi Fish
--
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=9491
Summary: CListCtrl:GetSubItemRect doesn't work for the label row
Product: Wine
Version: 0.9.44.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bgp(a)cs.elte.hu
When I call CListCtrl::GetSubItemRect with m_item = -1, it supposed to handle
the label row. It works in windows. Under wine, it doesn't work, ref will
contain garbage.
res = CListCtrl::GetSubItemRect(m_item,m_subitem,LVIR_BOUNDS,ref);
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36345
Bug ID: 36345
Summary: TGB Dual 8.3: A Windows Videogame emulator that
crashes when loading a ROM.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: swordofsilence(a)gmail.com
Created attachment 48413
--> http://bugs.winehq.org/attachment.cgi?id=48413
The backlog provided after TGB Dual 8.3 crashed.
When loading a videogame ROM with TGB Dual V8.3 open, such as Pokemon Crystal,
it crashes. If I attempt to load the Pokemon Crystal ROM directly, it will fail
to load with the message "There is no Windows program configured to open this
type of file."
Pokemon Crystal File was this type: Pokemon - Crystal Version (USA,
Europe).gbc.
The log that appears when I try to load it while TGB Dual V8.3 is open is
provided as an attachment.
Link for TGB Dual V8.3 Download:
http://www.emuparadise.me/Nintendo_Gameboy_Advance_Emulators/Windows/TGB_Du…
--
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=15083
Summary: ReadConsoleInputW() returns wrong values for CTRL+SPACE
Product: Wine
Version: 1.1.3
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dg(a)cowlark.com
On the Windows console, if I use ReadConsoleInputW() to read user input and the
user types CTRL+SPACE, wine returns wVirtualKeyCode=VK_SPACE, UnicodeChar=0
where Windows XP returns wVirtualKeyCode=VK_SPACE, UnicodeChar=32.
--
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=34086
Bug #: 34086
Summary: MS Paint shows some images messed up.
Product: Wine
Version: 1.6-rc5
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bammzilla(a)astronomy.com.ph
Classification: Unclassified
Created attachment 45322
--> http://bugs.winehq.org/attachment.cgi?id=45322
If this picture is opened in MS Paint in WinXp, the transparent portions become
black. In older wine versions behave the same way (therefore do it correctly).
In wine 1.6-rc5 it's ruined.
In Wine 1.6-rc5, Windows XP MS Paint messes up some images with transparency.
In previous versions of Wine, it behaves correctly (meaning, same behavior as
running MS Paint on WinXP) by showing the transparent color as black.
--
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=32621
Bug #: 32621
Summary: Mouse pointer jumps on opening/closing WinUAE settings
window
Product: Wine
Version: 1.5.20
Platform: x86-64
URL: http://www.winuae.net/files/InstallWinUAE2510.exe
OS/Version: Windows
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
Testing with wine-1.5.20-22-ga701528 on Lubuntu 11.10 x86-64.
There is an issue with bogus mouse movement which shows up with the WinUAE
Amiga emulator. This seems to be a regression somewhere between
wine-1.5.17-252-g8ba4c31 and wine-1.5.17-270-ga0f039a.
WinUAE captures the mouse when emulation is running. The Windows mouse pointer
is made invisible and mouse movement is passed through to the emulated machine.
With emulation running, press F12 to open the settings window, and click the
Cancel to close it. The mouse pointer of the emulated machine jumps to a new
position when the settings window closes. It's as if Wine has queued up mouse
movement between your pressing F12 and clicking Cancel.
To reproduce:
- Download and run the WinUAE installer. Run WinUAE.
- Optional: When the settings window opens, click CPU and FPU in the tree-view
then select Fastest possible under CPU Emulation Speed.
- Click Start. After a few seconds you should see something in the emulation
window and there is a red mouse pointer which you can move. Move it around a
bit.
- Noting where the red mouse pointer is, press F12 to open the settings window.
- Click Cancel to close the settings window. The red mouse pointer jumps in
position. The difference between new and old positions may be related to the
amount you moved the Windows mouse pointer in order to click Cancel.
I ran a regression test but it wasn't entirely successful.
wine-1.5.17-252-g8ba4c31 GOOD
wine-1.5.17-270-ga0f039a BAD
In between those two commits, running WinUAE did not allow the emulation window
to be activated. Keyboard input went to the terminal window instead.
The last commit for wine-1.5.17-253-g841214d was:
user32: Don't check for driver events before normal messages in PeekMessage.
author: Alexandre Julliard <julliard(a)winehq.org>
Wed, 21 Nov 2012 18:20:27 +0000 (19:20 +0100)
commit: 841214ddb4d4dc620e6b51dfe6655b585d423edc
The last commit for wine-1.5.17-270-ga0f039a (which presumably fixed the
can't-activate-window issue) was:
user32: Fix the wait event mask in PeekMessage.
author Alexandre Julliard <julliard(a)winehq.org>
Thu, 22 Nov 2012 10:57:15 +0000 (11:57 +0100)
commit a0f039a6049641cc2be8fa32f2afa3c3f394a99b
--
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.