How to do the Bandwith Fix for XP


Recommended Posts

1. Logon as ADMINISTRATOR (NOT just an administrator equiv.)

2. start - run - type gpedit.msc

3. expand the "local computer policy" branch

4. expand the "administrative templates" branch

5. expand the "network branch"

6. Highlight the "QoS Packet Scheduler" in left window

7. in right window double click the "limit reservable bandwidth" setting

8. on setting tab check the "enabled" item

9. where it says "Bandwidth limit %" change it to read 0

10. go to your Network connections (start->connect to->show all connections). right click on your connection then under the General or the Networking tab (where it lists your protocols) make sure QoS packet scheduler is enabled.

11. reboot if you want to but not necessary on some systems your all done. Effect is immediate on some systems. some need re-boot.

Link to comment
Share on other sites

Originally posted by Qarth

Just to let you know that the %20 thing that everyone was freaking about does absolutly nothing to affect your bandwidth.

I put that in the subject of my responce. Work or not, it doesn't hurt anything else. So, if you *FEEL* like it worked / helped ... then it will make you happy! :)

Link to comment
Share on other sites

Qark you are wrong it does work, what it is is i reckon is when XP wants to send something out or is set up to send receive stuff it takes 20% of ur bandwidth away to sufficiently receive it at a reasonable rate.

All i new is my connection absolutely flew like bitch on heat chasing aftre a sausage, but i installed Tweak XP "optimized" my connection and now its back to be ok and nothing like it was before :(

Link to comment
Share on other sites

XP Bandwidth Freedom is a Myth

Scribbled by Mike Byrns

Yet another news outlet innocently spreading disinformation. It was wrong then, and no matter how many times it's written up as Gospel, it's still wrong. From the article, "XP seems to want to reserve 20% of the bandwidth for itself even with QoS disabled." I don't see any mention of the test methodology. I'd attribute that to the fact that no testing was actually done at all. The tweak author found a seemingly interesting setting, thought he understood it and began to boundlessly pontificate on the greatness of his "tweak." The truth is, unless you are running both QoS on a given network connection AND QoS-aware applications that are currently asking to reserve bandwidth on that connection, NO bandwidth is reserved. None. Nada.

Even when said applications are reserving bandwidth, they only do it before initiating a QoS-aware stream and they release it after. Try this for yourself: transfer a large file across your LAN while watching the bandwidth monitor in task manager. Now apply this self-proclaimed "tweak." Repeat the file transfer. Unless your copy of Windows XP contains different networking code than mine and the other few dozen folks who I've had try this over the past few weeks, you won't see a difference.

In order to rule out task manager "hiding" this bandwidth as was suggested to me by a few of the Microsoft conspiracy theorists, I had my LAN admin measure bandwidth between my port and the port my test machine was connected to by monitoring bandwidth usage at the Cisco switch that connects us. He says it's even QoS compliant. Guess what? NO DIFFERENCE. Please let your readers know! XP and Microsoft get enough bad press as it is, some of it (admittedly) well deserved.

http://www.lockergnome.com/issues/daily/20011221.html

any1 says it makes any difference is fooling themself

topic closed.

Link to comment
Share on other sites

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

    • No registered users viewing this page.