Hi all,
Still working on this issues, I have a lot of (confusing) test results,
will not post it all here.
I will definitely post the outcome of the investigation.
For now a question. For me it seems atm that about half of the machines
I install now simply give this strange behavior.
I would
I just made a nice discovery. I found out that I had another machine (same
model, but mini tower) sitting here somewhere. I checked, and the problem
does not show there.
So I took the hard drive from the not working one and put it in the
working one and it booted nicely (since hardware is iden
On 7/13/2011 15:43, Merijn Bosma wrote:
On 7/13/2011 15:07, Francois PIETTE wrote:
Thanks for the links, it's an interesting read. What still goes
beyond me though, is that all I see in the diagram seems to be
hardware independent stuff, so how could it ever happen that it
behaves different on
On 7/13/2011 15:07, Francois PIETTE wrote:
Thanks for the links, it's an interesting read. What still goes
beyond me though, is that all I see in the diagram seems to be
hardware independent stuff, so how could it ever happen that it
behaves different on different machines?
That's the point:
Thanks for the links, it's an interesting read. What still goes beyond me
though, is that all I see in the diagram seems to be hardware independent
stuff, so how could it ever happen that it behaves different on different
machines?
That's the point: IMO the issue comes from the software which
On 7/13/2011 13:17, Francois PIETTE wrote:
I agree that it's not a hardware issue. Do you know what layers are
there approximately? I've already ruled out the driver of the NIC
itself.
I was mentioning the chipset since there is also software applicable
(driver of the chipset). Also strange is
I don't think it is a hardware issue. It is likely a software issue. One
of the layer between winsock and the network card has a bug. That is why
you see it on one computer and not another.
Determining which layer is faulty will be a difficult task ! I don't know
what to say to help you :-(
On 7/13/2011 11:46, Francois PIETTE wrote:
AFAIR the workaround was to do your own ARP request first in order
to check whether the destination exists or not, utilizing the IP
Helper API.
Yes, that what I did.
How can I confirm that this is what's happening with me?
In my case, the blocki
AFAIR the workaround was to do your own ARP request first in order
to check whether the destination exists or not, utilizing the IP
Helper API.
Yes, that what I did.
How can I confirm that this is what's happening with me?
In my case, the blocking was occuring in the main thread. TO see i
On 7/13/2011 7:23, Francois PIETTE wrote:
AFAIR the workaround was to do your own ARP request first in order
to check whether the destination exists or not, utilizing the IP
Helper API.
Yes, that what I did.
How can I confirm that this is what's happening with me?
In my case, the block
AFAIR the workaround was to do your own ARP request first in order
to check whether the destination exists or not, utilizing the IP Helper
API.
Yes, that what I did.
How can I confirm that this is what's happening with me?
In my case, the blocking was occuring in the main thread. TO see i
How can I confirm that this is what's happening with me?
Merijn
On 7/12/2011 21:49, Francois PIETTE wrote:
Was Francois able to find a way to make sure this is the case, or a
work around?
AFAIR the workaround was to do your own ARP request first in order
to check whether the destination exis
Was Francois able to find a way to make sure this is the case, or a
work around?
AFAIR the workaround was to do your own ARP request first in order
to check whether the destination exists or not, utilizing the
IP Helper API.
Yes, that what I did.
--
francois.pie...@overbyte.be
The author of
13 matches
Mail list logo
