Recommended Posts

If you are receiving any 4226 errors in your event log I would definitely patch it.

586194710[/snapback]

These kind of statements drive me nuts. You shouldn't just run out and grab the patch. Handing information like that on a tech board is just giving newbies bad advise.

You should FIRST investigate where the problem is coming from. It could be a program your using but it could also be a virus. If it is a virus you shouldn't patch and go on with your merry life.

If it is a Virus then 4226 errors are the least of your worries. I'm not worried about getting infected are you? I keep my system patched, have updated AV and a firewall. All my clients have the same thing. There is nothing dangerous about this patch, stop trying to imply that there is.

The patch really does nothing to help your p2p downloads. I investigated it myself and honestly, this is a lot of fuss for nothing. You can do everything you wanted just fine. At least this is the case for me.

Yes it will still work but initial server queries can be slower when you initiate a search. It all depends on the P2P client. Most of them have resume features that can be seriously hampered by this if the computers you are connecting to are off line.

Edit... never mind I figured it out.

The patch really does nothing to help your p2p downloads. I investigated it myself and honestly, this is a lot of fuss for nothing. You can do everything you wanted just fine. At least this is the case for me.

586216708[/snapback]

Same here. Patch is pointless.

You should FIRST investigate where the problem is coming from.  It could be a program your using but it could also be a virus.  If it is a virus you shouldn't patch and go on with your merry life.

586223148[/snapback]

Exactly. The system doesn't place a "warning" in the Event Log for nothing. A warning means Windows is telling you there's something you should investigate. Windows is basically saying "this might be nothing but if there is a problem, you should fix it".

Exactly which means use the patch. Seriously, this "warning" means one of your internet applications is being hindered by the limit.

586225063[/snapback]

It does not! Do you understand TCP/IP? Do you realize that the types of connections it limits aren't... Nevermind, it seems there's no chance of proving you wrong.

It does not! Do you understand TCP/IP? Do you realize that the types of connections it limits aren't... Nevermind, it seems there's no chance of proving you wrong.

I just explained this. Say you are trying to resume 100 seperate downloads (usually from multiple sources). If most of them are offline it will take you alot longer to resume or even show they are offline because you have to wait for it to do only 10 (that are not responding) at a time.

Edited by Mastertech

Sounds like a little something called a placebo to me. Also sounds like someone trying to make a name for themselves. :whistle:

Currently unpatched, running bittorrent as I post this, and I'm getting download rates of in excess of 250 KB/s. I have tcp/ip errors in my event log, and I could care less. I'm not too terribly concerned about half-open connections being dropped. Every P2P application I've used works just peachy.

Why exactly is Mastertech so adamant about people patching this non-issue, exactly?

Simple I don't want any limit hindering my internet connection in any way and that includes limiting half-open connections. This has nothing to do with download rates so please stop bringing that up. I also want people aware that this in no way improves YOUR security.

BTW the people installing this patch are not the problem, it is the average user who doesn't even know about Neowin, which are already patched if they have SP2. So it is a non issue. And for anyone concerned about my "advice" which includes nothing short of installing ALL Windows Security updates, running a firewall and an UPDATED Antivirus program they can relax.

Other than P2P download rates, can you give me a scenario where your internet connection is "hindered" by limiting half-open connections? What other type of usage would require that many active connection attempts in that short period of time, that would be adversely affected by being queued?

Why don't you just answer my question? You're incredibly vague with your responses and reasoning behind the neccessity for this "patch", other than "if you have errors in your event viewer then I recommend you patch" or "if you run any sort of fileserving software", with no regards whatsoever to recommending to anyone that they should first attempt to find out what application is causing the error, and determining if the software in question even needs this "patch". I think you drastically overestimate the knowledge level of the individuals that peruse this site and will blindly patch thinking it will speed up their kazaa.

Edited by mugwhump

I didn't bother to read all your replies because they seem to be nothing more than half-assed advice such as;

If you are receiving any 4226 errors in your event log I would definitely patch it.

Which is blatanty stupid without first recommending to the person that they attempt to at least discover what application they are using that is creating these errors. It's like taking your car to a mechanic to get an engine knock diagnosed and having them want to immediately sell you a new engine without opening the hood. I've asked what applications or scenarios would cause this error, and you tell me to backtrack your responses. I see several times you say that this won't effect download speeds in P2P applications, but you're giving the advice to people having errors from running P2P applications. It simply doesn't make sense, and you seem hell-bent on hammering home that this patch is the best thing since sliced bread, when for the vast majority of users out there, it's completely wortheless. Nothing more than a shoddy placebo. You seem to care far more about this issue since you've consistently argued it's validity for going on 16 pages now, and I'm just curious as to WHY you care so much?

I could honestly care less if people patch or not, but I also must admit I don't enjoy people that might not know better being scammed.

The patch can improve search and resume speeds. Not the speed at which it downloads the resumed file but the speed at which it restablishes the connection or tells you the source is not available, if you have over ten sources, which is quite common with P2P. I will have to check exactly which P2P applications but I have seen them put limits to below ten for simultaneous connection attempts. With this patch you can increase that.

Here is how it can actually improve speeds indirectly. Say you have a P2P app attempting to find a file or resume a download, if you can connect to the source before someone else, you download the file and are not qued on their end. The more sources you download from the faster the download. Placebo my ass.

The fact I am making such a big deal out of this is certain people are trying to scare others into not patching based on false security concerns. The patch does nothing to improve YOUR security.

The fact I am making such a big deal out of this is certain people are trying to scare others into not patching based on false security concerns. The patch does nothing to improve YOUR security.

586226145[/snapback]

How about I'm trying to tell people that hex-editing files is a bad idea because you're never really sure what you're changing; and if you make a wrong change, you won't know what could/will happen.

This thread reminds me of a soap opera.

Everyone has different opinions on the TCP/IP patch. If someone wants to use it, then let them. It's up to the user to decide what to do. If the user thinks their connection has improved with the patch, then let them think that. Do I use the patch? No. But, I also don't use P2P programs.

No point in wasting Neowin's hard drive space on a discussion which is obviously going nowhere.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The sweet release of death has never looked more appealing.
    • Meh, just another dongle-haven downgrade compared to my Surface Pro 7+. Whenever I decide to upgrade in the next decade or so, it certainly won't be another microslop Surface with this enshitification trend they've been having after the Surface Pro 7+. Hopefully a future generation of the Framework 12 will be a real upgrade...
    • This could exactly be how our Sun ends but it's not as simple by Sayan Sen Image by Drew Rae via Pexels An international team led by Université de Montréal (University of Montreal) PhD student Érika Le Bourdais has found that the ancient white dwarf star LSPM J0207+3331 is still pulling in planetary debris, even though it has been cooling for about three billion years. White dwarfs are dense, Earth-sized stellar remnants left behind when Sun-like stars exhaust their nuclear fuel and shed their outer layers. The star, located 145 light-years away in the constellation Triangulum, is the oldest and coldest white dwarf known to have a surrounding disk of dust. The star was first spotted in 2019 by a citizen scientist through the Backyard Worlds: Planet 9 project. Its cool temperature immediately suggested that it was very old, since white dwarfs gradually lose heat over time. Using the W. M. Keck telescopes in Hawaii, astronomers later confirmed that the star shows infrared signals consistent with dust rings formed by asteroids breaking apart under its strong gravity. Such infrared excesses occur when a star emits more infrared light than expected, often because warm dust surrounding it absorbs and re-radiates energy. “This discovery challenges our understanding of planetary system evolution,” said Le Bourdais. “The fact that we still see planetary debris being accreted three billion years after the star became a white dwarf suggests that asteroids, comets, and even planets can remain in orbit around these stars for a very long time.” Spectroscopic analysis—a technique that studies light to identify the chemical elements present in an object—revealed thirteen heavy elements in the star’s atmosphere: sodium, magnesium, aluminium, silicon, calcium, titanium, chromium, manganese, iron, cobalt, nickel, copper, and strontium. Normally, heavy elements sink quickly in hydrogen-rich white dwarfs, making them hard to detect. “We expected to see only a few elements, but we found dozens!” explained Le Bourdais. The research paper adds more detail. The absence of carbon features suggests the debris came from a carbon-volatile-depleted source. The abundance pattern shows slight deficits of magnesium and silicon compared to iron but otherwise resembles Earth-like material. This points to a differentiated rocky body—one whose materials have separated into distinct layers such as a metallic core and rocky mantle—with a metallic core fraction higher than Earth’s. In other words, the star is accreting the remains of a large rocky object, similar in structure to Earth or the asteroid Vesta. “White dwarfs offer one of the only ways we can directly measure the composition of exoplanets,” said Patrick Dufour, co-author and professor at Université de Montréal. “When planetary debris come too close, they are torn apart by the star’s gravity and end up polluting its atmosphere, leaving a detailed chemical fingerprint of its composition.” The team also detected weak Ca II H & K line core emission, making this only the second known isolated polluted white dwarf to show this feature. These are specific spectral signatures produced by ionised calcium and can indicate unusual physical activity in a star’s upper atmosphere. The finding suggests that extra physical processes may be happening in or above the star’s upper atmosphere. The study stresses the importance of including heavy elements in model atmosphere calculations, since leaving them out can distort the inferred structure and lead to inaccurate stellar parameters. Earlier work suggested the star’s infrared excess came from two dust rings. The new analysis shows that a single silicate dust disk—a ring composed largely of rock-forming minerals rich in silicon and oxygen—can explain the observed signal at 11.6 μm, simplifying the picture of the system’s structure. The question of how debris ended up falling into the star so late remains open. One idea is that giant planets in the system slowly destabilised smaller bodies over billions of years. Another possibility is that a passing star disturbed the orbits of debris. “Future observations with the James Webb Space Telescope or archival data found in the European Space Agency’s Gaia mission could help distinguish between a planetary rearrangement and the gravitational effect of a close stellar encounter,” said John Debes, co-author and researcher at the Space Telescope Science Institute. Dufour noted that hydrogen-rich white dwarfs are the most common type, and the coolest among them are the oldest stars in the galaxy. “We didn't have the habit of looking for signs of accretion in them. This unique case motivates us to expand our search to more of these stars.” The findings show that even after billions of years, planetary systems can remain active and complex. Substantial accretion events—the gradual accumulation of surrounding material onto a celestial object—can still occur long after a star’s death, offering a rare window into the composition and fate of distant worlds. Source: University of Montreal, IOPScience This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Doesn't DDG mainly use Bing?
  • Recent Achievements

    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
    • Week One Done
      eurospharma62 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      228
    3. 3
      Skyfrog
      65
    4. 4
      FloatingFatMan
      56
    5. 5
      monterxz
      55
  • Tell a friend

    Love Neowin? Tell a friend!