On 3/21/06, Bryan Mayland <[EMAIL PROTECTED]> wrote:
> Dan Kegel wrote:
> > Yes. Make the code as small and simple as possible
> > to check that one limit.
> >
> I've sent the patch to wine-patches as suggested at winehq. I'm not
> subscribed to that list though, so let me know if there are a
Dan Kegel wrote:
Yes. Make the code as small and simple as possible
to check that one limit.
I've sent the patch to wine-patches as suggested at winehq. I'm not
subscribed to that list though, so let me know if there are any problems
receiving it or you don't like the test case.
Th
On 3/21/06, Bryan Mayland <[EMAIL PROTECTED]> wrote:
> ...My test app is 150 lines of ugly
> code whose purpose was to narrow down where the problem was, which was
> that MAXIMUM_WAIT_OBJECTS weren't supported. You probably don't want to
> put all that socket code in just to test the event system.
Dan Kegel wrote:
Congratulations, sounds like you found a bug in Wine!
Yay! I'm glad I'm not crazy.
Looks like it should be changed.
You've helped greatly with your post.
You could help even more by posting a patch
that modifies dlls/kernel/tests/sync.c to incorporate your test
and also
Bryan Mayland wrote:
> dlls/kernel/sync.c:173:
> 176 if (count >= MAXIMUM_WAIT_OBJECTS)
> 177 {
> 178 SetLastError(ERROR_INVALID_PARAMETER);
> 179 return WAIT_FAILED;
>
> Windows supports up to and including that number, wine only supports up
> to that number.
Congratulatio
I've been digging into why versions of uTorrent greater than 1.1.3 do
not work under the latest wine and tracked it down to their use of
WSAEventSelects to receive socket notifications. I created a small test
application which mimics this behavior which works under WindowsXP but
not wine.
Th
