http://bugs.winehq.org/show_bug.cgi?id=421
nh2(a)deditus.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nh2(a)deditus.de
--- Comment #309 from nh2(a)deditus.de 2010-01-22 16:06:41 ---
@ Thomas:
You're right, I think this is not the bug for Starcraft regressions, but could
you do a regression test (http://wiki.winehq.org/RegressionTesting)? This will
help you to find the commit which made Starcraft run slowly. I would suggest
bisecting with full Wine releases first (because they will compile fine) and if
you know the regression is between two releases, you can git-bisect to find the
guilty commit and open a bug for the regression.
--
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=21137
Summary: Venetica 1.02 crashes at startup
Product: Wine
Version: 1.1.35
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mcflow-forum(a)gmx.net
Created an attachment (id=25383)
--> (http://bugs.winehq.org/attachment.cgi?id=25383)
wine Venetica.exe
When launching Venetica 1.02 there appears a message on the desktop, that there
appeared an error in the application.
I attached an attachment with the output from Terminal.
Version 1.01 and the demo are launching.
Tested on
AMD Athlon 64 X2 4200+
2 GB Ram
Nvidia 8600GTS (NVIDIA 185.18.36)
Ubuntu 9.10
--
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=7803
Dylan Taylor <aliendude5300(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aliendude5300(a)gmail.com
--- Comment #13 from Dylan Taylor <aliendude5300(a)gmail.com> 2010-01-22 14:34:23 ---
Still present in 1.1.37
--
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=421
Thomas <kronisk(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kronisk(a)hotmail.com
--- Comment #308 from Thomas <kronisk(a)hotmail.com> 2010-01-22 14:13:40 ---
I just compiled wine 1.1.37 from scource (git) with Max' patches -- only
possible with Bernhards update, though! First time around, I didn't use the
update and that resulted in this error
"WINEDIB=ON wine StarCraft.exe gave the error => err:driver:Load_Dib_Driver
Couldn't load DIB Engine."
Second time around, when I used the update, I could load the dib driver.
Unfortunately, there is no performance increase what so ever in StarCraft.
There is one topic I would like to bring up, and excuse me if this is not the
right place to do it, I'm not sure..
Awhile ago, I found out that if one uses an old version of wine (0.9.14)
StarCraft performance is 99.99% of that of I remember it being in XP. I then
did some lurking in the wine changelogs, and it seems that the DirectDraw
underwent alot of updated/updrades -- and unfortunately it was in such a way,
that StarCraft got left behind..
My specs:
GPU: ATi Radeon X850XT Platinum (PCi:E, which is unsupported by legacy drivers)
flgrxinfo:
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON X850 XT Platinum Edition
OpenGL version string: 2.1.8543 Release
Thus I am indeed using the lastest ATi drivers with 3D support for my legacy
card... nVidia here I come!
--
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=3817
elad <el.il(a)doom.co.il> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |el.il(a)doom.co.il
--- Comment #37 from elad <el.il(a)doom.co.il> 2010-01-22 12:11:29 ---
Wine should determine the prefix's file system, and check if it is in a list of
known case-insensitive file system's (ntfs, fat, ciopfs and such). It should be
easy to implement this small check.
Integrating ciopfs into wine is a grate idea. native apps usually doesn't
writes into ~/.wine. We can mount all the prefixes on login as suggested above.
Please fix this bug ASAP.
--
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=21331
Summary: Stars! crash on "New Game"
Product: Wine
Version: 1.1.35
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nisselarsson(a)home.se
Stars![1] crash when one clicks on "New Game". An error dialog saying an error
occurred in winevdm.exe.
[1] http://appdb.winehq.org/objectManager.php?sClass=application&iId=238
--
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=21320
Summary: wine/list.h has namespace conflicts with sys/queue.h
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeremyhu(a)freedesktop.org
sys/queue.h on FreeBSD, darwin, etc provide LIST_ENTRY macros which conflict
with those in wine/list.h ... this has led to problems such as:
http://trac.macports.org/ticket/22342
A workaround for this was pushed into wine a while back, but it is merely a
hackish workaround. If you permute the order in which headers are included, or
if system headers happen to add an include on sys/queue.h, you may end up not
being able to build wine. This is what happened in the above external ticket.
If you simply add a '#include <sys/queue.h>' to
/usr/include/dispatch/dispatch.h, wine stops building here on darwin. I'm sure
it would be easy to find a similar case on FreeBSD.
One fix is to avoid conflicting with the sys/queue.h namespace and use
something like WINE_LIST_ENTRY
--
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=21291
Summary: System call "dup2" doesn't retain text vs binary mode
Product: Wine
Version: 1.0.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: simon(a)josefsson.org
Hi again, here is another "dup2" problem.
The attached code example behaves different in Wine compared to Windows XP.
Under Wine it will print:
is_mode 1
dup2 3 => 0
is_mode 0
Note the last 'is_mode 0' which is the actual error. On Windows XP it prints:
is_mode 1
dup2 3 => 0
is_mode 1
The bug in the Wine "dup2" implementation appears to be that it doesn't copy
the text/binary setting to the new file descriptor. Fixing it may be rather
simple.
/Simon
jas@mocca:~$ cat foo2.c
#include <unistd.h>
#include <errno.h>
#include <fcntl.h>
#include <stdio.h>
#if (defined _WIN32 || defined __WIN32__) && ! defined __CYGWIN__
/* Get declarations of the Win32 API functions. */
# define WIN32_LEAN_AND_MEAN
# include <windows.h>
#endif
/* Return non-zero if FD is open in the given MODE, which is either
O_TEXT or O_BINARY. */
static int
is_mode (int fd, int mode)
{
int value = setmode (fd, O_BINARY);
setmode (fd, value);
return mode == value;
}
int
main (void)
{
const char *file = "test-dup2.tmp";
int fd = open (file, O_CREAT | O_TRUNC | O_RDWR, 0600);
setmode (fd, O_TEXT);
printf ("is_mode %d\n", is_mode (fd, O_TEXT));
printf ("dup2 %d => %d\n", fd, dup2 (fd, fd + 1));
printf ("is_mode %d\n", is_mode (fd + 1, O_TEXT));
return 0;
}
jas@mocca:~$ i586-mingw32msvc-gcc -o foo2.exe foo2.c
jas@mocca:~$ wine --version
wine-1.0.1
jas@mocca:~$ wine ./foo2.exe
is_mode 1
dup2 3 => 0
is_mode 0
jas@mocca:~$
--
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=21289
Summary: System call "dup2" returns 0 for negative inputs, thus
behaving different from real Windows
Product: Wine
Version: 1.0.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: simon(a)josefsson.org
The program below when run under Wine will print:
rc 0
When I run the same binary on Windows XP, I get:
rc -1
The problem appears to be that the "dup2" system function doesn't do proper
input checking.
This is causing self-tests errors for projects (including several GNU projects)
that use some gnulib modules.
/Simon
jas@mocca:~$ cat foo.c
#include <unistd.h>
#include <stdio.h>
#include <errno.h>
#include <fcntl.h>
/* Get declarations of the Win32 API functions. */
# define WIN32_LEAN_AND_MEAN
# include <windows.h>
int
main (void)
{
const char *file = "test-dup2.tmp";
char buffer[1];
int fd = open (file, O_CREAT | O_TRUNC | O_RDWR, 0600);
int rc;
rc = dup2 (fd, -2);
printf ("rc %d\n", rc);
return 0;
}
jas@mocca:~$ i586-mingw32msvc-gcc -o foo.exe foo.c
jas@mocca:~$ wine ./foo.exe
rc 0
jas@mocca:~$ wine --version
wine-1.0.1
jas@mocca:~$
--
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.