Message-ID: <35369CF8.BFE50E5C@wr.com.au>
Date: Fri, 17 Apr 1998 10:06:16 +1000
From: Michael Norman <mnorman@wr.com.au>
Reply-To: mickn@ozemail.com.au
X-Mailer: Mozilla 4.03 [en] (Win95; I)
MIME-Version: 1.0
Newsgroups: comp.dcom.modems,rec.games.computer.quake.misc,wr.quake
Subject: Re: NET_SENDPACKET ERROR: 10049
References: <3535dc40.0@nachos.wr.com.au> <6h4tdt$skv$1@noc1.gwi.net> <353609ad.0@nachos.wr.com.au> <353613d9.0@nachos.wr.com.au>
Content-Type: multipart/alternative; boundary="------------4232E41CDF8981FA5ED919A0"
NNTP-Posting-Host: 203.12.42.129
X-NNTP-Posting-Host: 203.12.42.129
Organization: Customer of World Reach Internet Access
Lines: 127
Path: clanworld.com!news.webspan.net!news.tacom.army.mil!news.he.net!newsxfer.visi.net!WCG!windy.ourworld.net!news.syd.fl.net.au!news.syd.ausbone.net!nachos.wr.com.au!203.12.42.129
Xref: clanworld.com rec.games.computer.quake.misc:27776


--------------4232E41CDF8981FA5ED919A0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Now I know why it rang a bell ... I had exactly the same problem when I upgraded
to DUN 1.2 ... the solution for me was to eliminate it :)

I got it confused with the 56k issue because I had the problems on the same day.

Regards,
Reap.

Balaji Rao wrote:

> Ok I found the page Steven is talking about:
> http://finger.planetquake.com/qfplan.asp?userid=xian&id=5133
>
> And, by God, did he hit the nail on the head or what. Found that I have an
> out of date winsock for the version of DUN that I use.
>
> Balaji Rao wrote in message <353609ad.0@nachos.wr.com.au>...
> >This sounds very good. Only prob is I can' t find the article referred to.
> >Steven is right, I only got the crashes after installing the DUN upgrade.
> >
> >Going to 33.6 worked fine too. Although a bit too slow for my tastes.
> >
> >>Yes..I know what it means..You do not need to slow your connect down to
> >33.6,,i mean, you just
> >>got a 56k modem..right? I had these problems too, after upgrading to a 56k
> >modem, and the problem
> >>is with the windows95 tcp/ip stack. You need to go to planetquake and read
> >disruptors plan update
> >>for january 9th I believe, and you will see a step by step list of
> >solutions there, and all of
> >>them worked for me.
> >>
> >>The problem, BTW, is that when you update the windows95 tcp/ip stack, the
> >new patches by
> >>microsoft dont update ALL of the files on your harddrive..There is a bug
> in
> >the upgrade patch
> >>installer. disrupter has a file there, called QFEcheck, that will check
> the
> >verions of all your
> >>tcp/ip files. then, he offers a winsock SDK that when installed, will
> >update ALL of your tcp/ip
> >>files to the latest, bug-free version. I did this yesterday and have had
> >over 11 hours play
> >>without a single lockup.
> >>
> >>Steven (easykill)
> >>
> >
> >



--------------4232E41CDF8981FA5ED919A0
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<HTML>
Now I know why it rang a bell ... I had exactly the same problem when I
upgraded to DUN 1.2 ... the solution for me was to eliminate it :)

<P>I got it confused with the 56k issue because I had the problems on the
same day.

<P>Regards,
<BR>Reap.

<P>Balaji Rao wrote:
<BLOCKQUOTE TYPE=CITE>Ok I found the page Steven is talking about:
<BR><A HREF="http://finger.planetquake.com/qfplan.asp?userid=xian&id=5133">http://finger.planetquake.com/qfplan.asp?userid=xian&amp;id=5133</A>

<P>And, by God, did he hit the nail on the head or what. Found that I have
an
<BR>out of date winsock for the version of DUN that I use.

<P>Balaji Rao wrote in message &lt;353609ad.0@nachos.wr.com.au>...
<BR>>This sounds very good. Only prob is I can' t find the article referred
to.
<BR>>Steven is right, I only got the crashes after installing the DUN upgrade.
<BR>>
<BR>>Going to 33.6 worked fine too. Although a bit too slow for my tastes.
<BR>>
<BR>>>Yes..I know what it means..You do not need to slow your connect down
to
<BR>>33.6,,i mean, you just
<BR>>>got a 56k modem..right? I had these problems too, after upgrading
to a 56k
<BR>>modem, and the problem
<BR>>>is with the windows95 tcp/ip stack. You need to go to planetquake
and read
<BR>>disruptors plan update
<BR>>>for january 9th I believe, and you will see a step by step list of
<BR>>solutions there, and all of
<BR>>>them worked for me.
<BR>>>
<BR>>>The problem, BTW, is that when you update the windows95 tcp/ip stack,
the
<BR>>new patches by
<BR>>>microsoft dont update ALL of the files on your harddrive..There is
a bug
<BR>in
<BR>>the upgrade patch
<BR>>>installer. disrupter has a file there, called QFEcheck, that will
check
<BR>the
<BR>>verions of all your
<BR>>>tcp/ip files. then, he offers a winsock SDK that when installed,
will
<BR>>update ALL of your tcp/ip
<BR>>>files to the latest, bug-free version. I did this yesterday and have
had
<BR>>over 11 hours play
<BR>>>without a single lockup.
<BR>>>
<BR>>>Steven (easykill)
<BR>>>
<BR>>
<BR>></BLOCKQUOTE>
&nbsp;</HTML>

--------------4232E41CDF8981FA5ED919A0--

