From: "Jeroen Besse" Received: from mxout3.mailhop.org ([63.208.196.167] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 291223 for os2-wireless_users@2rosenthals.com; Tue, 15 Aug 2006 12:10:19 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout3.mailhop.org with esmtp (Exim 4.51) id 1GD1Ua-000Jci-7a for os2-wireless_users@2rosenthals.com; Tue, 15 Aug 2006 12:10:12 -0400 Received: from nf-out-0910.google.com ([64.233.182.187]) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1GD1UZ-000LAC-9H for os2-wireless_users@2rosenthals.com; Tue, 15 Aug 2006 12:10:11 -0400 Received: by nf-out-0910.google.com with SMTP id p46so378168nfa for ; Tue, 15 Aug 2006 09:10:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HtBPdcXpQMYsB3qBBV3sv//shiR+4a2/jzgvkN9QoFdR2uahkcE3kJCoYCIC6E3Xm5jZVL8zS5+IG12MgeIyvl9M9YYyAN7YPbiIxvYbnPk9AvLmOm+8Ns5ZcRokAJwZ8E9zJ/bsh8Lfd+fncTMEtwUOHOZlGAH5YCV6Ly8Q83Y= Received: by 10.49.41.18 with SMTP id t18mr1594151nfj; Tue, 15 Aug 2006 09:10:10 -0700 (PDT) Received: by 10.78.139.6 with HTTP; Tue, 15 Aug 2006 09:10:10 -0700 (PDT) Message-ID: <7234a03c0608150910n781e4ad0yd13298c237d2b67c@mail.gmail.com> Date: Tue, 15 Aug 2006 18:10:10 +0200 To: "OS/2 Wireless Users Mailing List" Subject: Re: [OS2Wireless]Re: SOCKET.SYS crash - Dump Screen (was: I give up) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -1.3 (-) On 8/15/06, Rick R. wrote: > > > Jeroen Besse wrote: > >You also mentioned a trap E in an other driver before... > >which gives me the feeling it might be hardware related... > > > I did not say that (I already pointed out that I had the e-mail header mixed > up once). > PLEASE people stop blaming this on anything else but the OS/2 TCP/IP stack, > because THIS IS NOT HELPING! > Its not hardware, its not XPIs, its not little green men in the bushes or > the CIA. > Its the TCP/IP stack and NOTHING ELSE! > I had this problem occuring on 3 different systems!! > > And all the time it was triggered by high NW traffic, just like the IBM bug > report states! Thanks for the 'kind' yelling. No need to yell again, as I'll never help you again.