http://bugs.winehq.org/show_bug.cgi?id=5954
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |1434, 2012, 3354
nThis| |
Status|RESOLVED |CLOSED
------- Additional Comments From Speeddymon(a)gmail.com 2007-16-03 17:47 -------
Closing
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7698
------- Additional Comments From l_bratch(a)yahoo.co.uk 2007-16-03 17:25 -------
This does actually happen for me at 1280x1024 after all, but not in the same places.
ie. I've found a method that _always_ causes the crash at 1600x1200, which is to
headshot a T as a CT, when they are in the underpass on de_dust.
However that never seems to crash it at 1280x1024, even though later on after a
while of playing it does indeed happen.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=5721
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From Speeddymon(a)gmail.com 2007-16-03 17:13 -------
Yes wine should receive an access denied and print a warning to the console. I
will post note to wine-devel. For now could you file a new bug for that issue?
Something like "Tomb Raider Legends crashes when user doesnt have r/w access to
/dev/input/event*"
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5556
------- Additional Comments From Speeddymon(a)gmail.com 2007-16-03 17:07 -------
The fixme is probably NOT the issue as the original report only lists this
problem when DirectInput is enabled.. Jason, since bug 1410 is now resolved,
can you check if this occurs with current wine version.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1410
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From Speeddymon(a)gmail.com 2007-16-03 17:04 -------
The patches applied only fix the issue for some games. Reopening.. Please file
bugs for each game that has this mouse always recentered problem and make sure
to set bug xxxx blocks 1410
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7766
------- Additional Comments From focht(a)gmx.net 2007-16-03 16:53 -------
Hello,
by looking at wine GetSystemInfo() implementation (dlls\kernel32\cpu.c) it seems
the "dwActiveProcessorMask" isnt retrieved on "linux" platform at all.
The "apple" platform code used following code:
--- snip ---
if (sysctlbyname ("hw.activecpu", &value, &valSize, NULL, 0) == 0)
cachedsi.dwActiveProcessorMask = value;
--- snip ---
Maybe there is no easy linux way to do this?
Instead the default "dwActiveProcessorMask = 1" is returned.
Windows has KeActiveProcessors field (kernel) which is bit set for each usable
processor on the system
The list of *active* processor entries/nodes is walked and each processor id bit
get or'ed into bit field, basically: loop with KeActiveProcessors |= 1 << Id;
Thats how "dwActiveProcessorMask" is basically determined there.
Looking at my linux box (intel core duo2) it seems there is processor topology
information in "/proc/cpuinfo".
"processor"
"vendor id"
"physical id"
"siblings"
"core id"
"cpu cores"
... and the like
Its seems possible to determine all active physical and logical processors/cores
using this info and building processors mask (bit field).
But it seems this stuff is pretty new and older linux does not have all of these
fields (in /proc/cpuinfo).
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5314
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From Speeddymon(a)gmail.com 2007-16-03 16:51 -------
Closing
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.