About that time. I believe itunes and some other programs
were seeing 100% cpu usage at that time. Apparently they
got fixed but I was disappointed when the NFS3 problem
didn't go away.
Could you try the attached experimental patch and see
if it eliminates the NFS3 problem?
Cheers,
Jer
? dlls/msi
Oliver Stieber wrote:
I've had a look through the code and can't spot any
problems with managing the linked list which would
point to problems with TIME_TimersList but when the
crash occurs ptimer != &TIME_TimersList
I looked as well, and couldn't see anything obvious.
The only 'flaw' I saw was tha
The latest news on the frontpage has a incorrect link,
"Read more" points to : http://www.winehq.org/?announce=1.95
when it should be 1.96
I'm away from my Linux box tonight or I would send a patch...
Can someone fix this?
Tom
Hello guys, I have the impression the inactive warning messages have
been sent out again, I was convinced they were only sent once, followed
a month later by a closed account notification. In any case please solve
the problem,
I can't take 500+ bounces in my mail box every other day, I'm planning
Solution: the function checks the Length member of the struct,
not the real length of the string.
Ivan.
Jeremy White wrote:
Removing the Yield fixes a regression in Need For Speed III
where the loader and server consume 100% of the CPU. This
is with RH 9 which is a 2.4 kernel.
When did that regression first start? The mmtime and
ntdll/sync.c code has been this way since late last fall.
About that
Removing the Yield fixes a regression in Need For Speed III
where the loader and server consume 100% of the CPU. This
is with RH 9 which is a 2.4 kernel.
When did that regression first start? The mmtime and
ntdll/sync.c code has been this way since late last fall.
The Yield is, imho, correct, exc
RtlCompareUnicodeString should return 0 if it receives two identical string.
But for some strange reason this code
http://rafb.net/paste/results/e3tHCg40.html
prints this output
http://rafb.net/paste/results/SS5U2N81.html
Is it a mistake I've missed, or is this a bug in the implementation of
RtlCo
Jeremy White wrote:
You might try putting traces around the
conditional YieldExecution on line 730
of ntdll/sync.c and see if that chews up time;
if it does, removing the Yield might help.
Removing the Yield fixes a regression in Need For Speed III
where the loader and server consume 100% of the CP
Great! I had no idea if it was a single or multiple dlls that made up
winsock2, this looks like a great way to detect it. I'm almost certain that
there is NSIS code that can check for the ability to load up a dll. I'll put
that in.
Chris
On Friday 11 February 2005 7:53 am, you wrote:
> On
Holly Bostick wrote:
Well, all of it is blowing your own horn... which is fine, you should
do more of it.
But, in this case, apps like WinZip or Mozilla, both of which
specifically are more likely to be run in native versions by new users
than via Wine-- WinZip we've already been through, and o
(3rd of 3)
Chris Morgan wrote:
Then vote for what you really want or need... I want to see 100 games
working but if I had to pick one
it would be HL2. And if you give me 20 or 30 votes there *diluted* votes
from the get-go!
I agree. Maybe 5 votes per-user is a good number so each one counts but
(2nd of 3)
Tom wrote:
Chris Morgan wrote:
Having a single vote per-person makes the assumption that the person
has a single application that they want working. Often users have a
handful of them. I'd prefer multiple votes per-person.
Then vote for what you really want or need... I want to see 10
How you guys managed to hit "Reply to all" and somehow not include the
list, I don't know, but I'll forward :-) ... (1st of 3 such)
Chris Morgan wrote:
- Voting for app version ( not app family).
- only one vote per person per version.
- more total votes, say 10-20 instead of 3.
I would like to
[EMAIL PROTECTED] wrote:
Holly Bostick wrote:
Leaving aside the fact that there is no real reason to even run WinZip
under Wine (given that zip is provided by default with every
distribution, so *.zip files are already handled, WinZip doesn't
handle *.rar files or *.ace files, iirc, and in any c
While people are thinking about mmtimer I've got a
question, or more a problem.
Sometimes, mainly when escape from Bink videos (or
they run to the end) the linked list in time.c is
getting corrupt. (this happens about 1 in 5 times)
i.e.
TIME_MMSysTimeCallback()
EnterCriticalSection(&i
Hmm. Actually, both cases are broken; you should have a min/max
that hovers right around the target period. This is what I get
on a 2.6.9 kernel:
timer.c:59:wPeriodMin = 1, wPeriodMax = 65535
timer.c:110:period = 1, resolution = 0
timer.c:136:min = 0, max = 2, average = 1.00
timer.c:110:perio
I just posted a revised test which also prints out the standard deviation.
Same results, 1 and 20 ms have a small deviation and 10 ms has a
deviation of around 10.
Jeremy White wrote:
Hmm. When I run it, I see only the expected behavior,
both on a 2.4 and 2.6 kernel.
Here is what I get with an up to date RH9 on a Dell Dimension 8300
with latest CVS:
Without ntdll/sync.c patch:
timer.c:59:wPeriodMin = 1, wPeriodMax = 65535
timer.c:110:period = 1, resolution =
I just posted a simple mmtimer test for the regression tests.
Hmm. When I run it, I see only the expected behavior,
both on a 2.4 and 2.6 kernel.
Note that the resolution setting is completely meaningless;
the only setting that matters is the period.
And, as far as I can tell, it exactly reproduce
> Hey, we won by a large margin!
>
>
http://www.linuxquestions.org/questions/showthread.php?s=&threadid=272137
>
> Wine 293 42.59%
> Crossover Office 139 20.20%
> Cedega131 19.04%
> VMware
Not all You can every write in c/c++. Sometime You need a call for a
library function. I think, that can be one and I think, not only
TlsAlloc use a zero_bit_scan.
It must be
first zero_bit in the first 'bytecount' DWORD from the bitmap addr.
Dietrich
On Thu, 10 Feb 2005 18:59:21 +0100, Dietrich Te
[EMAIL PROTECTED] wrote:
You are probably correct here. Certainly voting for an application
version makes more sense to me. However voting for any app makes no
"real" difference to the developers at this time.
The voting system is an indication of how popular (important?) a
program is. I do thi
Not all You can every write in c/c++. Sometime You need a call for a
library function. I think, that can be one and I think, not only
TlsAlloc use a zero_bit_scan.
Dietrich
On Thu, 10 Feb 2005 18:59:21 +0100, Dietrich Teickner wrote:
>> I have a suggestion for a faster implementation of the zero
Mike Hearn wrote:
Hey, we won by a large margin!
Congratulations!!! You've earned it, and you deserve it!!
http://www.linuxquestions.org/questions/showthread.php?s=&threadid=272137
Wine 293 42.59%
Crossover Office 139 20.20%
Cedega 131 19.04%
V
Holly Bostick wrote:
Jonathan Ernst wrote:
[snip]
Le lundi 07 février 2005 à 01:16 +0100, Holly Bostick a écrit :
I had to go through 4 links just to get to the main application page.
First, the sidebar link from the main site to the appdb front page. This
[FIXED] I sent a patch to replace "Appli
On Thu, Feb 10, 2005 at 08:12:39PM +, Mike Hearn wrote:
> On Thu, 10 Feb 2005 18:59:21 +0100, Dietrich Teickner wrote:
> > I have a suggestion for a faster implementation of the zero_bit_scan in
> > RtlFindClearBits[EMAIL PROTECTED]
> > (rlbitmap.c) for e.g. TlsAlloc()
> > The main is the u
Jeremy White wrote:
I'm taking a public thread that I responded to privately back
to public view:
Robert Reif wrote:
Jeremy White wrote:
Putting traces into the mmtimer thread loop shows
WaitForSingleObject is sleeping for about 20 ms and then
calling the callback twice to catch up.
Well, that me
Hey, we won by a large margin!
http://www.linuxquestions.org/questions/showthread.php?s=&threadid=272137
Wine293 42.59%
Crossover Office139 20.20%
Cedega 131 19.04%
VMware 101 14.68%
Win4li
I'm taking a public thread that I responded to privately back
to public view:
Robert Reif wrote:
Jeremy White wrote:
Putting traces into the mmtimer thread loop shows
WaitForSingleObject is sleeping for about 20 ms and then
calling the callback twice to catch up.
Well, that means mmtimer is right.
On Tue, 8 Feb 2005, Chris Morgan wrote:
Oh, that's mostly because I was lazy. I'm pretty sure the text says
that "if you are on windows95 you should install winsock2". I'm not
sure how to detect whether the user needs to install winsock2 or not
by looking at dlls.
[...]
Maybe something lkie th
Ok so I'm going through the User Guide's getting/installing/compiling
chapters.
Essentially my idea is to cannibalize most of it, since the information
is outdated, wrong, or at best duplicitous.
However, while combing through the User Guide, I realized that there's
some stuff I don't know much a
32 matches
Mail list logo
