User Tools

Site Tools


kb_windows

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
kb_windows [2013/11/21 18:13] – [Can I delete MSOCache?] atlkb_windows [2018/04/02 06:25] (current) – [**__Windows 10__**] atl
Line 1: Line 1:
-====== **__Windows__** ======+====== **__Windows 10__** ======
  
-===== Can I delete MSOCache? =====+[[https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/|How to Install and Use the Linux Bash shell on Windows 10]]
  
-cf. http://superuser.com/questions/216300/can-i-delete-msocache 
  
-Way to go would be Junction Point.+====== **__Windows 7__** ======
  
-For example if you have 120 GB SSD Drive as C:, and 3TB Drive (Magnetic)HDD as D:+  * [[http://sysadminspot.com/windows/how-to-fix-sidebar-exe-using-lots-of-memory/|How to Stop sidebar.exe Using Lots of Memory]] [[http://sysadminspot.com/windows/windows-sidebar-exe-memory-leak/|Windows sidebar.exe Memory Leak]] 
 + - 2011-05-03
  
-  * on drive D: create sub folder named C +<code>
-  * cut and paste folder MSOCache to sub folder C located on drive D: +
-  * run CMD +
-  * type: CD \ +
-  * type: MKLINK /J MSOCache D:\C\MSOCache +
-  * type: EXIT +
-  * after this you will have entire content of MSOCache folder in path C:\MSOCache, but physically files would be located on D:\C\MSOCache. +
- +
-that was the answer about MSOCache folder on C drive. Now let us talk about real problem, the same one I experienced few hours ago. +
- +
-NOT ENOUGH SPACE ON SSD DISK AS C: DRIVE +
-... +
-====== **__Windows 7__** ====== +
- +
-  * [[http://sysadminspot.com/windows/how-to-fix-sidebar-exe-using-lots-of-memory/|How to Stop sidebar.exe Using Lots of Memory]] + [[http://sysadminspot.com/windows/windows-sidebar-exe-memory-leak/|Windows sidebar.exe Memory Leak]] - 2011-05-03<code>+
 How to Stop sidebar.exe Using Lots of Memory How to Stop sidebar.exe Using Lots of Memory
 Posted on March 7, 2011 by Brendan in Windows Posted on March 7, 2011 by Brendan in Windows
 One of my readers, TED has made a suggestion as to a hack fix to the sidebar.exe memory problem (as documented in my blog post Windows sidebar.exe Memory Leak). With some spare time at the moment, I’ve been able to implement his suggestion and confirm it works. One of my readers, TED has made a suggestion as to a hack fix to the sidebar.exe memory problem (as documented in my blog post Windows sidebar.exe Memory Leak). With some spare time at the moment, I’ve been able to implement his suggestion and confirm it works.
  
-I’ve written a batch script, and confirmed this works in Windows 7 (should work in Windows Vista too). I created a batch file called restart-sidebar.bat, and stored it in c:\users\brendan – contents of the file below:+I’ve written a batch script, and confirmed this works in Windows 7 (should work in Windows Vista too). I created a batch file called restart-sidebar.bat, and stored it in c:usersbrendan – contents of the file below:
  
 @echo off @echo off
Line 39: Line 25:
 The idea is it will kill the process called / task with the image name of, sidebar.exe, forcefully. It will then wait two seconds before starting the process again. The idea is it will kill the process called / task with the image name of, sidebar.exe, forcefully. It will then wait two seconds before starting the process again.
  
-To complete the setup, create a new scheduled task specifying the path to your newly created batch file (mine was c:\users\brendan\restart-sidebar.bat). Run the scheduled task as your own user. I have it scheduled to run once a day at 5pm. I prefer to have it run when I’m not using the computer, more of a scheduled maintenance task that goes on behind the scenes. If you find that’s not enough, schedule it to run a few times a day.+To complete the setup, create a new scheduled task specifying the path to your newly created batch file (mine was c:usersbrendanrestart-sidebar.bat). Run the scheduled task as your own user. I have it scheduled to run once a day at 5pm. I prefer to have it run when I’m not using the computer, more of a scheduled maintenance task that goes on behind the scenes. If you find that’s not enough, schedule it to run a few times a day.
  
 For your information – I’ve encountered on only a few occurrences problems in the past when shutting. The sidebar process has stalled the shutdown procedure and Windows has forcefully killed the process. On login again I’ve lost a few sidebar settings. While I’ve not encountered this running the above batch script, it’s possible you may encounter this. If you’re concerned about it, drop the /f from the taskkill line in the above script (as to not force it) and increase the timeout value from 2, to up to 20 seconds to allow it to safely exit. For your information – I’ve encountered on only a few occurrences problems in the past when shutting. The sidebar process has stalled the shutdown procedure and Windows has forcefully killed the process. On login again I’ve lost a few sidebar settings. While I’ve not encountered this running the above batch script, it’s possible you may encounter this. If you’re concerned about it, drop the /f from the taskkill line in the above script (as to not force it) and increase the timeout value from 2, to up to 20 seconds to allow it to safely exit.
Line 54: Line 40:
  
 ====== **__Windows XP__** ====== ====== **__Windows XP__** ======
- 
  
 ===== WINDOWS XP SHUTDOWN & RESTART TROUBLESHOOTING ===== ===== WINDOWS XP SHUTDOWN & RESTART TROUBLESHOOTING =====
  
-  * [[http://www.thinktechno.com/2008/04/22/how-to-format-a-usb-drive-with-ntfs-file-system/|How to format a USB drive with NTFS file system]] - www.thinktechno.com+  * [[http://www.thinktechno.com/2008/04/22/how-to-format-a-usb-drive-with-ntfs-file-system/|How to format a USB drive with NTFS file system]] 
 + [[http://www.thinktechno.com|www.thinktechno.com]]
  
   * [[http://www.technize.com/2008/12/22/4-ways-to-shutdownrestart-the-system-at-a-specific-time-in-windows/|4 Ways To Shutdown/Restart The System At A Specific Time In Windows]] | Technize - Be Techdated   * [[http://www.technize.com/2008/12/22/4-ways-to-shutdownrestart-the-system-at-a-specific-time-in-windows/|4 Ways To Shutdown/Restart The System At A Specific Time In Windows]] | Technize - Be Techdated
  
 ==== Shares Access Denied & IRPStackSize ==== ==== Shares Access Denied & IRPStackSize ====
-   * [[http://www.howtonetworking.com/winissues/irpstacksize.htm|How to increase  the  IRPStackSize value]] + 
-shares problems can be solved by the method of "increase the  IRPStackSize value in the registry" if your event viewer mentions it!+  * [[http://www.howtonetworking.com/winissues/irpstacksize.htm|How to increase the IRPStackSize value]] 
 + 
 +shares problems can be solved by the method of "increase the IRPStackSize value in the registry" if your event viewer mentions it!
  
   - Run regedit.   - Run regedit.
   - Navigate to the following key:   - Navigate to the following key:
-<code>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters</code>+ 
 +<code> 
 +HKEY_LOCAL_MACHINESystemCurrentControlSetServicesLanmanServerParameters 
 +</code> 
   - In the right pane, double-click the IRPStackSize value.   - In the right pane, double-click the IRPStackSize value.
-     NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it: + 
-     a. In the Parameters folder of the registry, right-click the right pane. +NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it: 
-     b. Point to New, and then click DWord Value. + 
-     c. Type IRPStackSize. +<code> 
-     IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive. +   a. In the Parameters folder of the registry, right-click the right pane. 
-  - Change the Base to decimal. +   b. Point to New, and then click DWord Value. 
-  - In the Value Data box, type a value that is larger than the value that is listed.+   c. Type IRPStackSize. 
 +   IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive. 
 +- Change the Base to decimal. 
 +- In the Value Data box, type a value that is larger than the value that is listed. 
 +</code> 
 If you created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and then click OK. If you created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and then click OK.
 +
   - Close the Registry Editor and restart the computer.   - Close the Registry Editor and restart the computer.
  
Line 83: Line 81:
  
 If you are running Windows NT 4.0, and the problem persists after you complete the preceding procedure, you may have to apply Windows NT Service Pack 4 or Service Pack 5. If you are running Windows NT 4.0, and the problem persists after you complete the preceding procedure, you may have to apply Windows NT Service Pack 4 or Service Pack 5.
- 
  
 ==== HID Input Service failed to start ==== ==== HID Input Service failed to start ====
 +
   * [[http://www.aumha.net/viewtopic.php?t=30774|HID Input Service failed to start with...]]   * [[http://www.aumha.net/viewtopic.php?t=30774|HID Input Service failed to start with...]]
 +
 <code> <code>
 Event Viewer: Event Viewer:
Line 100: Line 99:
 Description: Description:
 The HID Input Service service terminated with the following error: The HID Input Service service terminated with the following error:
-The system cannot find the file specified. +The system cannot find the file specified.
 </code> </code>
 +
 The following could be a solution The following could be a solution
  
   - "Start", then "Run"   - "Start", then "Run"
   - Type "regedit" without the quotes, click "OK"   - Type "regedit" without the quotes, click "OK"
-  - Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentC­ ontrolSet\Services\HidServ\Paramet­ers+  - Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentC­ ontrolSetServicesHidServParamet­ers
   - In the right pane, right-click in the blank area and select "New" and "Expandable String Value"   - In the right pane, right-click in the blank area and select "New" and "Expandable String Value"
   - Name the value "ServiceDll" without the quotes. Note: it is spelled S E R V I C E D L L but you enter it exactly as shown between the quotation marks.   - Name the value "ServiceDll" without the quotes. Note: it is spelled S E R V I C E D L L but you enter it exactly as shown between the quotation marks.
-  - Double-click the new entry and enter **"%SystemRoot%\System32\hidserv.dll­"** without quotes as its value+  - Double-click the new entry and enter **"%SystemRoot%System32hidserv.dll­"**  without quotes as its value
   - Click OK, and close the registry window   - Click OK, and close the registry window
 +
 Exclamation Reboot. Exclamation Reboot.
  
Line 116: Line 117:
  
 Using your mouse, Highlight the entire contents of the code box below, including any blank lines. Then do a Right-click | "Copy": Using your mouse, Highlight the entire contents of the code box below, including any blank lines. Then do a Right-click | "Copy":
 +
 <code> <code>
 Windows Registry Editor Version 5.00 Windows Registry Editor Version 5.00
  
-[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidServ\Parameters+[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHidServParameters
-"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\ +"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f, 
-  00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\+  00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,
   68,00,69,00,64,00,73,00,65,00,72,00,76,00,2e,00,64,00,6c,00,6c,00,00,00   68,00,69,00,64,00,73,00,65,00,72,00,76,00,2e,00,64,00,6c,00,6c,00,00,00
 </code> </code>
  
-Open a new Notepad session. Click Format and make certain that Word Wrap is disabled. Do a Right-click | "Paste" of the code box contents. Click File, click "Save as..." and enter as the filename (including quotation marks): "c:\fix_regs.reg".+Open a new Notepad session. Click Format and make certain that Word Wrap is disabled. Do a Right-click | "Paste" of the code box contents. Click File, click "Save as" and enter as the filename (including quotation marks): "c:\fix_regs.reg".
  
-Exit Notepad. Double click your new file, fix_regs.reg[/b] and agree to the registry merge when asked. +Exit Notepad. Double click your new file, fix_regs.reg[/b] and agree to the registry merge when asked. Reboot.
-Reboot.+
  
- +[[http://www.aumha.org/win5/a/shtdwnxp.htm|WINDOWS XP SHUTDOWN & RESTART TROUBLESHOOTING]]
-[[http://www.aumha.org/win5/a/shtdwnxp.htm|WINDOWS XP +
-SHUTDOWN & RESTART +
-TROUBLESHOOTING]]+
  
 ==== SHUTDOWN WORKS, BUT IT’S REAL SLOW ==== ==== SHUTDOWN WORKS, BUT IT’S REAL SLOW ====
Line 146: Line 144:
  
 ===== How to change Terminal Server's listening port ===== ===== How to change Terminal Server's listening port =====
 +
 [[http://support.microsoft.com/kb/187623|How to change Terminal Server's listening port]] [[http://support.microsoft.com/kb/187623|How to change Terminal Server's listening port]]
  
- SUMMARY +SUMMARY By default Terminal Server and Windows 2000 Terminal Services uses TCP port 3389 for client connections. Microsoft does not recommend that this value be changed. However, if it becomes necessary to change this port, follow these instructions.
-By default Terminal Server and Windows 2000 Terminal Services uses TCP port 3389 for client connections. Microsoft does not recommend that this value be changed. However, if it becomes necessary to change this port, follow these instructions.+
  
 +MORE INFORMATION
  
- MORE INFORMATION +<code> 
-  WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.+WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. 
 +</code>
  
 To change the default port for all new connections created on the Terminal Server: To change the default port for all new connections created on the Terminal Server:
-  1. Run Regedt32 and go to this key: 
-HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp 
-NOTE: The above registry key is one path; it has been wrapped for readability. 
  
-  2. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.+<code> 
 +1   Run Regedt32 and go to this key: 
 +</code>
  
-To change the port for a specific connection on the Terminal Server: +HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp NOTE: The above registry key is one path; it has been wrapped for readability.
-• Run Regedt32 and go to this key: +
-HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection +
-NOTE: The above registry key is one path; it has been wrapped for readability+
-  3. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.+
  
-  NOTE: Because the use of alternate ports has not been fully implemented for Terminal Server 4.0, support will be provided as "reasonable effort" only, and Microsoft may require you to set the port back to 3389, if any problems occur.+<code> 
 +2.    Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value. 
 +</code> 
 + 
 +To change the port for a specific connection on the Terminal Server: • Run Regedt32 and go to this key: HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal ServerWinStationsconnection NOTE: The above registry key is one path; it has been wrapped for readability. 
 + 
 +<code> 
 +3.    Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value. 
 +</code> 
 + 
 +<code> 
 +NOTE: Because the use of alternate ports has not been fully implemented for Terminal Server 4.0, support will be provided as "reasonable effort" only, and Microsoft may require you to set the port back to 3389, if any problems occur. 
 +</code>
  
 To Alter the Port on the Client Side To Alter the Port on the Client Side
-  1. Open Client Connection Manager. + 
-  2. On the File menu, click New Connection, and then create the new connection. After running the wizard, you should have a new connection listed there. +<code> 
-  3. Making sure that the new connection is highlighted, on the File menu, click Export. Save it as name.cns. +1.    Open Client Connection Manager. 
-  4. Edit the .cns file using Notepad changing "Server Port=3389" to "Server Port=xxxx" where xxxx is the new port that you specified on Terminal Server. +2.    On the File menu, click New Connection, and then create the new connection. After running the wizard, you should have a new connection listed there. 
-  5. Now import the file back into Client Connection Manager. You may be prompted to overwrite the current one, if it has the same name. Go ahead and overwrite it. You now have a client that has the correct port settings to match your change Terminal Server settings.+3.    Making sure that the new connection is highlighted, on the File menu, click Export. Save it as name.cns. 
 +4.    Edit the .cns file using Notepad changing "Server Port=3389" to "Server Port=xxxx" where xxxx is the new port that you specified on Terminal Server. 
 +5.    Now import the file back into Client Connection Manager. You may be prompted to overwrite the current one, if it has the same name. Go ahead and overwrite it. You now have a client that has the correct port settings to match your change Terminal Server settings. 
 +</code>
  
 ===== Supprimer le dossier de partage du poste de travail ===== ===== Supprimer le dossier de partage du poste de travail =====
-[[http://www.commentcamarche.net/faq/sujet-4456-wlm-supprimer-le-dossier-de-partage-du-poste-de-travail|Supprimer le dossier de partage du poste de travail]] 
-A l'installation de Windows Live Messenger, un "dossier de partage" est créé dans le poste de travail, ce qui permet de partager plusieurs documents avec certains contacts. 
-Pour ceux qui n'utilisent pas cette fonction et qui veulent supprimer cet élément du poste de travail, voici la marche à suivre. 
-Supprimer le dossier de partage 
  
-    * Faites Démarrer => Exécuter et tapez regsvr32 -u "%ProgramFiles%\MSN Messenger\fsshext.dll" +[[http://www.commentcamarche.net/faq/sujet-4456-wlm-supprimer-le-dossier-de-partage-du-poste-de-travail|Supprimer le dossier de partage du poste de travail]] A l'installation de Windows Live Messenger, un "dossier de partageest créé dans le poste de travail, ce qui permet de partager plusieurs documents avec certains contactsPour ceux qui n'utilisent pas cette fonction et qui veulent supprimer cet élément du poste de travail, voici la marche à suivreSupprimer le dossier de partage
-    * Si cela ne fonctionne pas, allez voir dans le répertoire d'installation de Windows Live Messenger et relevez le nom du fichier de la forme "fsshext.8.x.xxxx.xx.dll"+
-          o Même opération : Démarrer => Exécuter et tapez regsvr32 -u "%ProgramFiles%\MSN Messenger\fsshext.8.x.xxxx.xx.dll" (en remplaçant par le nom du fichier que vous avez relevé).+
  
 +  * Faites Démarrer ⇒ Exécuter et tapez regsvr32 -u "%ProgramFiles%\MSN Messenger\fsshext.dll"
 +  * Si cela ne fonctionne pas, allez voir dans le répertoire d'installation de Windows Live Messenger et relevez le nom du fichier de la forme "fsshext.8.x.xxxx.xx.dll".
  
-Le dossier a disparu ! +o Même opération : Démarrer ⇒ Exécuter et tapez regsvr32 -u "%ProgramFiles%\MSN Messenger\fsshext.8.x.xxxx.xx.dll" (en remplaçant par le nom du fichier que vous avez relevé).
-Rétablir le dossier de partage+
  
-    * Faites Démarrer => Exécuter et tapez regsvr32 -c "%ProgramFiles%\MSN Messenger\fsshext.8.x.xxxx.xx.dll" (en remplaçant par le nom du fichier que vous avez relevé, voir ci-dessus).+Le dossier a disparu ! Rétablir le dossier de partage
  
 +  * Faites Démarrer ⇒ Exécuter et tapez regsvr32 -c "%ProgramFiles%\MSN Messenger\fsshext.8.x.xxxx.xx.dll" (en remplaçant par le nom du fichier que vous avez relevé, voir ci-dessus).
  
 Le dossier réapparait alors dans le poste de travail. Le dossier réapparait alors dans le poste de travail.
  
 ===== L'explorateur plus stable ! ===== ===== L'explorateur plus stable ! =====
 +
 [[http://www.zebulon.fr/astuces/tip83-0/L-explorateur-plus-stable.html|L'explorateur plus stable !]] [[http://www.zebulon.fr/astuces/tip83-0/L-explorateur-plus-stable.html|L'explorateur plus stable !]]
  
-Astuce performances système : **L'explorateur plus stable !** +Astuce performances système : **L'explorateur plus stable !**  Notre cher Windows gère l’explorateur, le bureau et la barre des tâches au sein d’un seul processus multithreads. Lorsque l’explorateur se fige, c’est alors l’ensemble de la machine qui trinque. Cette astuce permet de lancer l’explorateur au sein d’un autre processus, le bureau et la barre des tâches étant gérés eux via un second processus. Cela permet une plus grande stabilité de la machine, le plantage de l’explorateur ne figeant pas la totalité de l’OS.
-Notre cher Windows gère l’explorateur, le bureau et la barre des tâches au sein d’un seul processus multithreads. Lorsque l’explorateur se fige, c’est alors l’ensemble de la machine qui trinque. Cette astuce permet de lancer l’explorateur au sein d’un autre processus, le bureau et la barre des tâches étant gérés eux via un second processus. Cela permet une plus grande stabilité de la machine, le plantage de l’explorateur ne figeant pas la totalité de l’OS.+
  
 Attention tout de même, la création d’un nouveau processus gérant l’explorateur consomme plus de mémoire. Astuce à éviter si votre RAM est insuffisante. Attention tout de même, la création d’un nouveau processus gérant l’explorateur consomme plus de mémoire. Astuce à éviter si votre RAM est insuffisante.
  
-    Ouvrir regedit +<code> 
-    Allez dans HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer +  Ouvrir regedit 
-    Créez la valeur DWORD DesktopProcess et donnez lui la valeur 1. 0 est la valeur par défaut (les processus ne sont pas séparés).+  Allez dans HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorer 
 +  Créez la valeur DWORD DesktopProcess et donnez lui la valeur 1. 0 est la valeur par défaut (les processus ne sont pas séparés). 
 +</code>
  
 ---- ----
  
 ===== Windows XP soudainement lent ! ===== ===== Windows XP soudainement lent ! =====
 +
 [[http://www.zebulon.fr/astuces/tip130-0/Windows-XP-soudainement-lent.html|Windows XP soudainement lent !]] [[http://www.zebulon.fr/astuces/tip130-0/Windows-XP-soudainement-lent.html|Windows XP soudainement lent !]]
  
-Astuce performances système : **Windows XP soudainement lent !** +Astuce performances système : **Windows XP soudainement lent !**  Il peut arriver que Windows devienne lent alors qu’il fonctionnait très bien auparavant. Avant de vouloir réinstaller votre OS, essayez d’appliquer cette astuce !
-Il peut arriver que Windows devienne lent alors qu’il fonctionnait très bien auparavant. Avant de vouloir réinstaller votre OS, essayez d’appliquer cette astuce !+
  
 Attention ! L’utilisation de cette astuce peut dans certains cas créer un plantage complet de la machine ! A utiliser donc en dernier recours avant de passer par un reformatage ! Attention ! L’utilisation de cette astuce peut dans certains cas créer un plantage complet de la machine ! A utiliser donc en dernier recours avant de passer par un reformatage !
Line 222: Line 230:
 Pour cela, vous devez effectuer la manipulation suivante : Pour cela, vous devez effectuer la manipulation suivante :
  
-Faire un clic droit sur le Poste de Travail, allez dans Propriétés, Matériel, Gestionnaire de périphériques, Contrôleurs ATA/ATAPI IDE. Faire ensuite un clic droit sur Canal IDE Principal et choisissez Désinstaller. +Faire un clic droit sur le Poste de Travail, allez dans Propriétés, Matériel, Gestionnaire de périphériques, Contrôleurs ATA/ATAPI IDE. Faire ensuite un clic droit sur Canal IDE Principal et choisissez Désinstaller. Redémarrer ensuite votre machine.
-Redémarrer ensuite votre machine.+
  
 Ainsi, Windows reconnaîtra à nouveau l’IDE principal en Ultra DMA et non plus en PIO, votre PC retrouvera alors sa vitesse d’exécution d’origine ! Ainsi, Windows reconnaîtra à nouveau l’IDE principal en Ultra DMA et non plus en PIO, votre PC retrouvera alors sa vitesse d’exécution d’origine !
  
 ---- ----
- 
  
 ===== Démarrer XP plus vite ===== ===== Démarrer XP plus vite =====
Line 240: Line 246:
 Cette astuce, pourtant assez connue, peut-être mal utilisée. En effet, nombreuses sont les personnes qui préfèrent activer la défragmentation du boot. Pourtant, si vous utilisez régulièrement un défragmenteur, la défragmentation du boot ralentie alors le démarrage (elle est inutile). La désactivation de cette défragmentation va donc accélérer le démarrage de Windows XP. Cette astuce, pourtant assez connue, peut-être mal utilisée. En effet, nombreuses sont les personnes qui préfèrent activer la défragmentation du boot. Pourtant, si vous utilisez régulièrement un défragmenteur, la défragmentation du boot ralentie alors le démarrage (elle est inutile). La désactivation de cette défragmentation va donc accélérer le démarrage de Windows XP.
  
-    Ouvrez regedit (menu Démarrer, Exécuter... et taper regedit) +<code> 
-    Allez à HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction +  Ouvrez regedit (menu Démarrer, Exécuter... et taper regedit) 
-    Modifiez la valeur de la clé Enable à N (Y par défaut) +  Allez à HKEY_LOCAL_MACHINESOFTWAREMicrosoftDfrgBootOptimizeFunction 
-    Redémarrer. +  Modifiez la valeur de la clé Enable à N (Y par défaut) 
 +  Redémarrer. 
 +</code>
  
 Attention : si vous ne pratiquez pas de défragmentation régulière comme indiqué plus haut, il est conseillé de laisser Enable à Y. Attention : si vous ne pratiquez pas de défragmentation régulière comme indiqué plus haut, il est conseillé de laisser Enable à Y.
 +
 ---- ----
  
Line 253: Line 261:
   * [[http://www.hotline-pc.org/|hotline-pc.org]]   * [[http://www.hotline-pc.org/|hotline-pc.org]]
   * [[http://www.sysopt.com/|SysOpt.com - System Optimization and PC Performance]]   * [[http://www.sysopt.com/|SysOpt.com - System Optimization and PC Performance]]
 +
  
kb_windows.1385075596.txt.gz · Last modified: by atl