You miss my point.
No, it's more likely we're in violent agreement.
Dan Kegel wrote:
On 7/24/06, gslink <[EMAIL PROTECTED]> wrote:
What you say is correct but the result is the same. The combination of
NDISWRAPPER and any other program fails. In this case it is Wine. This
is not the fault of Wine in any way but it happens. It is a good idea
to keep this beh
On 7/24/06, gslink <[EMAIL PROTECTED]> wrote:
What you say is correct but the result is the same. The combination of
NDISWRAPPER and any other program fails. In this case it is Wine. This
is not the fault of Wine in any way but it happens. It is a good idea
to keep this behavior in mind as ND
Francois Gouget wrote:
On Tue, 11 Jul 2006, gslink wrote:
The most common problem with Ndiswrapper is that it requires more than
a 4k stack. The result you are getting may be coming from a stack
overflow caused by a combination of Wine and Ndiswrapper.
The 4k stack issue you are talking ab
On Tue, 11 Jul 2006, gslink wrote:
The most common problem with Ndiswrapper is that it requires more than a 4k
stack. The result you are getting may be coming from a stack overflow caused
by a combination of Wine and Ndiswrapper.
The 4k stack issue you are talking about is a kernel stack. Wi
The most common problem with Ndiswrapper is that it requires more than a
4k stack. The result you are getting may be coming from a stack
overflow caused by a combination of Wine and Ndiswrapper. Compile and
install the native drivers for your lan card and see if that makes a
difference. The
Jacob wrote:
[I use both Wine and NDISWRAPPER. After a while, my network breaks.
Is this a bug in Wine, or in NDISWRAPPER?]
I don't know where the bug is, but it's not in Wine.
Wine is a pure user-level app, it *can't* break the
system's networking.
It's either a bug in NDISWRAPPER or in the
