The system optimization method can not use

. The problem of today's system is naturally the most concerned issue. Some users have found many system optimization techniques for this purpose. Some people even use the method directly without using the method. In this way, if you use the wrong optimization method, it will damage your computer, so everyone must go out of the misunderstanding of system optimization.

Myth #1: Limited 20% Speed ​​

Run Gpedit.msc, open Windows XP Group Policy, and then find & ldquo;Computer Configuration & Rarr; Administrative Template & Rarr; Network & Rar; QoS The packet scheduler, modified to 0%, can remove 20% of the network bandwidth reserved by Windows XP. This "technique" misleads many people. In fact, this 20% bandwidth is only used when writing applications that use the QoS application programming interface requires access to the network. If these applications that use the QoS API do not have access to the network, the reserved bandwidth can still be used by other applications. Microsoft specifically addressed this issue and detailed it in the knowledge base. The modified value in the group policy refers to the maximum amount of bandwidth that can be used when the QoS API writer needs to access the network. If we set it to 0%, it means that the application written by the QoS API has to be combined with other The application competes for limited bandwidth, with the potential that data that requires priority communication is not prioritized.

Myth 2: Setting up Ghost, the hard disk capacity is getting bigger

Two hard drives and one Ghost software can expand the hard disk capacity by a factor of two. The 80GB hard disk suddenly becomes 120GB or more. many. On this issue, after reading the above method, Symantec related technicians said that a new partition generated by this method is definitely not available. If data is written to the partition, other normal partitions may be damaged. The main reason for this phenomenon is that many hard disk partition table files are not certified by Microsoft technology, which causes Ghost to misidentify the hard disk partition in the Windows operating system due to some operation, and generate the hard disk. Misidentification of the partition table. Such a problem is most likely to occur in mirror backup and recovery operations between two different brands of hard drives, but this is a more accidental phenomenon.