Vendredi 22 mai 2009 5 22 /05 /Mai /2009 04:01
The best way to trim down the amount of processor time the indexing service uses is by trimming down the amount of files being indexed. For instance, if you don't regularly search through your C: drive, there's really no need to be indexing it.

Type Indexing into the control panel search or the start menu search box, and you should see an item called Indexing Options.



Now you can see the current list of locations that are being indexed. If you want to modify or remove locations, use the Modify button.



All you have to do to remove a location from being indexed is uncheck the box. You might have to click the Show All Locations button to see some of the default locations.



If you wanted to remove the start menu indexing, you'll need to click on Start Menu in the summary list at the bottom, and it'll automatically navigate to the item in the tree.



The start menu indexing really doesn't take much processing time though, so I wouldn't bother removing that.

Completely Disable Indexing

If you'd prefer to completely disable the indexing service, you can disable it entirely by turning off the service.

Open up Services through control panel, or by typing services.msc into the start menu search box. Find "Windows Search" in the list of services and double-click on it to open it.



Change the Startup type of the service to Disabled, and then click the Stop button to stop the service.



Now At this point the Windows Search service is completely disabled.
Par Tutorialsland Staff - Publié dans : Windows VistaTutorials - Communauté : Windows Tutorials
Ecrire un commentaire - Voir les 0 commentaires
Vendredi 22 mai 2009 5 22 /05 /Mai /2009 04:00
As We Know, Windows XP is Too Slow when You shtdown it, usually what is happening is one or more applications is hanging up to 20 seconds (in the Registry all values are set to milliseconds) while the OS tries to shutdown. Before making any changes to the Registry it is highly advisable to create a backup.

The first thing we need to do is access the Registry by going to Start \ Run and type in “regedit” (no quotes) then click OK.



With the Registry Editor open the first change we want to make is under HKEY_CURRENT_USER \ Control Panel \ Desktop scroll down to HungAppTimeout and change the default 5000 to 1000 then click OK.



Scroll down to WaitToKillAppTimeout from 20000 to 1000 then click OK. Keep the Registry Editor open as we have 3 more values to change in two different sections.



Now We go to HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control and double click on WaitToKillServiceTimeout to 1000 then click OK.



In the end, we need to navigate to HKEY_USERS \ DEFAULT \ Control Panel \ Desktop and change HungAppTimeout to 1000 and click OK.



Then scroll down to WaitToKillAppTimeout to 1000 and click OK.



While you see lower timeout times in this post you might want to start with say 20000 to 10000 as some programs may be performing cleanup maintenance. No matter what you change the values to, make sure they are uniform throughout each setting.
Par Tutorialsland Staff - Publié dans : Windows XP Tutorials - Communauté : Windows Tutorials
Ecrire un commentaire - Voir les 0 commentaires
Vendredi 22 mai 2009 5 22 /05 /Mai /2009 03:57
those of them who are used to web interface, like Webmin, will delete their old kernels but won’t be able to proceed with the installation of a new Linux kernel. Interestingly enough, great Webmin just does not show all installed kernels. Some kind of a bug, I guess.

Well, your solution is to open the terminal and find out how many kernels are there anyways. So you need to type up:
rpm -q kernel | sort

Then you need to find out which kernel is the default one on your machine. So invoke the following command on your terminal:

uname -r

Then while whistling some funny melody, start uninstalling one by one all useless kernels. Here is the command:

rpm -e kernel(and its version)

Don’t forget to reboot. The alert would not bother you anymore.

Note: Please, be careful with uninstallation. Don’t erase all kernels, leave at least a couple of them in case a new update is gonna cause you problems. In that case, you will just switch back to the old kernel and wait for another kernel update.
Par Tutorialsland Staff - Publié dans : Linux Tutorials - Communauté : Linux Tutorials
Ecrire un commentaire - Voir les 0 commentaires

Présentation

Créer un Blog

Recherche

Calendrier

Février 2012
L M M J V S D
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29        
<< < > >>
Créer un blog gratuit sur over-blog.com - Contact - C.G.U. - Rémunération en droits d'auteur - Signaler un abus