|
12-31-2007, 02:26 PM
|
|||
|
|||
|
Quote:
If you look at steps 1 and 2 of my guide, you'll see that is what I did. Calling the command gpedit.msc is just that, with setting it to 0; that disables Qos Packet Scheduler. 
|
|
01-01-2008, 06:40 AM
|
|||
|
|||
Sorry, i am just confused a bit on that since theres something i noticed. I've turned off Qos Packet Scheduler before directly through the Network Connections area in the Control Panel and I see it unchecked in the properties....
 but then this trick....  doesn't make the system literally show that the scheduler is off....  so as far as i know, that still means that the Qos Packet Scheduler is still on, but without the bandwith being reserved, so i suspect that just means that it still manages the data packets that come in and out of your computer, but the Qos Packet Scheduler will have a harder time doing its job. And just to tell ya', i have Bellsouth DSL, so it would be best to say that im just testing out this stuff. But, this doesn't mean im saying this doesn't work, im just showing what i saw and what might possibly be an error or the such. Oh, and just a side-note, Ive seen a lot of your guides and they're all good, so i give you a "thanks" for the help you've given to everyone. Last edited by plague10; 01-01-2008 at 06:46 AM.
|
|
01-01-2008, 11:28 AM
|
|||
|
|||
|
Is it not working for you?
The way that I've known this to work is as long as it's disabled, the %tage of bandwidth is released. I believe its that way because those using XP HOme don't have the option for either or, disable and uninstall, but I can't confirm that because I don't have an XP Home OS to test it on.'' As far as I know, doing it either way works in XP Pro. Now if its not working for you...please let me know and I'll do a lil research and testing on my own. Depending on your DSL connection, the notice in change may not be that intense in comparison to a cable type connection or stronger. Thanks for the kind words. Glad my guides have been of some help to you.
|
|
01-01-2008, 01:10 PM
|
||||
|
||||
|
Did a little checking, I think this might explain it, straight from the explain this portion of the limit reservable bandwidth tab:
Quote:
__________________
 Quote:
|
|
01-01-2008, 01:53 PM
|
|||
|
|||
|
Thank you for the explanation on that guys. Yeah, i haven't noticed any change in my comp.'s internet connection, and i do have Windows XP Professional on my computer. There are several other questions i have, but those can wait for a while. So, thank you again for the info
 .Oh, and as far as i know, it works (if only a little).
|
|
08-31-2008, 03:21 AM
|
|||
|
|||
Here are a couple of articles I found on the subject.
Myth: Windows XP reserves 20% of the network bandwidth for itself, making it unavailable for Internet and LAN access. Fact: XP doesn't reserve any bandwidth. 100% of the network bandwidth is available. Explanation: See the Microsoft Knowledge Base article Windows XP Quality of Service (QoS) Enhancements and Behavior. "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."
|
|
08-31-2008, 11:37 PM
|
||||
|
||||
|
Very true ManeMan! But windows does restrict connections. That will only effect people that uses torrent, P2P, high traffic games and for people who uses 20+ applications which requires internet connection at the same time. Sure enough, you can change, and remove the limitation.
http://www.lvllord.de/download.php?u...tch223d-en.zip
__________________
Xbox 360 - 2 Games - 2 Controllers - 120GB Elite - Dead PS3 - 23 BD Games - 13 PSN Games - 9 Controllers - 320GB - Alive Wii - 6 Games - 4 Wiimotes - Alive PC - Overkill - 3DMark06 [15316]- God like :] PC - New Build - 3DMark06 [32092]  Gaming Generations | XnogarD Production - Soon!!!
|
|
09-01-2008, 09:59 AM
|
||||
|
||||
|
Yep, I used the lvllord patch on my parent's PC with XP Home. This tweak only works with XP Pro, otherwise lvllord is the only way. Also, nlite provides the option to apply the lvllord patch when building a custom xp iso, so that's a nice way to do it for a fresh install.
__________________
Quote:
|
 |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Reply: Increase Your Bandwidth
Linear Mode
