I'm wondering what QoS does, under WinXP Home. Anyone know?
You can find this setting at both:
Tools/Internet Options/Connections tab/Settings/Properties/Networking tab
and
Control Panel/Network Connections/Local Area Connection. Right-click on LA Connection and select Properties. Scroll through the box there.
It's obviously a Quality of Service option and, in WinXP Home, it's simply checkable or non-checkable. But what would you sacrifice if you didn't opt to check this entry?
I gather that, in WinXP Pro, the QoS option opens out into further settings and that using some of those settings can sometimes improve browsing speed.
Page 1 of 1
WinXP and Quality of Service setting
#2
Posted 08 January 2007 - 06:31 PM
http://www.tweakxp.com/article37125.aspx
Although it's suggested there is no need to disable it, I have it disabled, and it's going to stay that way.
Although it's suggested there is no need to disable it, I have it disabled, and it's going to stay that way.
The lightning flashes through my skull; mine eyeballs ache and ache; my whole beaten brain seems as beheaded, and rolling on some stunning ground.
AMD Athlon64 3700+ @2.64ghz 240/11 (stock air, lapped) 1.475V
DFI LanParty Ultra-D PCI-E (Modded to SLI)
2X eVGA 7600GT CO @645/850 (Volt Modded)
OCZ Platinum EL 2X512 2-3-3-6 1T Dual Channel @220mhz
WD Caviar SE 80G 7200rpm 8MB
Sony CD burner
AMD Athlon64 3700+ @2.64ghz 240/11 (stock air, lapped) 1.475V
DFI LanParty Ultra-D PCI-E (Modded to SLI)
2X eVGA 7600GT CO @645/850 (Volt Modded)
OCZ Platinum EL 2X512 2-3-3-6 1T Dual Channel @220mhz
WD Caviar SE 80G 7200rpm 8MB
Sony CD burner
#3
Posted 26 January 2007 - 09:05 PM
It is another background program that most don't use. Here is an important service that needs to be looked at. It is called RPC - Remote Procedure Call - you have activate Admin tools on program list by right click on taskbar - go to start/advanced/ show admin tools. once done go to admin tools start/programs/administration tool.
Go to services/Remote procedure call [ may be 2 listed] go to recovery and set 1 and 2 to 'Do Nothing'
This prevents repetitive unrequested restarts which has plagued windows for years when conflicts arise from certain software/hardware installs -esp symantec/norton products.
Another tip - if have symantec/norton products installed be aware that MS malicious removal tool can deactivate them and wipe out your licence even if new subscription. Symantec is aware of this - or some there are.
Go to services/Remote procedure call [ may be 2 listed] go to recovery and set 1 and 2 to 'Do Nothing'
This prevents repetitive unrequested restarts which has plagued windows for years when conflicts arise from certain software/hardware installs -esp symantec/norton products.
Another tip - if have symantec/norton products installed be aware that MS malicious removal tool can deactivate them and wipe out your licence even if new subscription. Symantec is aware of this - or some there are.
#4
Posted 27 January 2007 - 12:45 AM
The lightning flashes through my skull; mine eyeballs ache and ache; my whole beaten brain seems as beheaded, and rolling on some stunning ground.
AMD Athlon64 3700+ @2.64ghz 240/11 (stock air, lapped) 1.475V
DFI LanParty Ultra-D PCI-E (Modded to SLI)
2X eVGA 7600GT CO @645/850 (Volt Modded)
OCZ Platinum EL 2X512 2-3-3-6 1T Dual Channel @220mhz
WD Caviar SE 80G 7200rpm 8MB
Sony CD burner
AMD Athlon64 3700+ @2.64ghz 240/11 (stock air, lapped) 1.475V
DFI LanParty Ultra-D PCI-E (Modded to SLI)
2X eVGA 7600GT CO @645/850 (Volt Modded)
OCZ Platinum EL 2X512 2-3-3-6 1T Dual Channel @220mhz
WD Caviar SE 80G 7200rpm 8MB
Sony CD burner
#5
Posted 27 January 2007 - 04:09 AM
There are a number of people who do not understand this. QoS is very misleading but translates into "Quality of Service".
Refer to: http://support.microsoft.com/kb/316666
Actually, as the Intel chipset for ethernet does not natively support VLAN tagging, this is M$ solution or an answer to 802.1q VLAN tagging.
You may either enable or disable this. The only time it will really matter to you is if you use your Windows machine as a "gateway" for other machines on your network. BTW, I would not recommend you do this as support for port 443 (HTTPS) is faulty.
Refer to: http://support.microsoft.com/kb/316666
Actually, as the Intel chipset for ethernet does not natively support VLAN tagging, this is M$ solution or an answer to 802.1q VLAN tagging.
You may either enable or disable this. The only time it will really matter to you is if you use your Windows machine as a "gateway" for other machines on your network. BTW, I would not recommend you do this as support for port 443 (HTTPS) is faulty.
#6
Posted 28 January 2007 - 02:27 PM
What do you mean by ".....I would not recommend you do this, as ......"? Do you mean "I would not recommend you use QoS", or do you mean "I would recommend you do NOT use QoS"?
Share this topic:
Page 1 of 1

Help










