Troppo nascondiglio di Windows Vista, ting difettoso? Bene, apparentemente sì, con eccessivo nascosto scriva l'ingresso/uscita e l'ingresso/uscita colto nascosto eccessivo. Come probabilmente sapete ormai, il nascondiglio è collegato con l'amplificazione delle prestazioni dei processi di accesso ai dati che designano gli strumenti di memorizzazione come bersaglio pigri. In un piano d'azione ideale, i dati o le pagine di codice completamente sarebbero posizionati all'interno della memoria di sistema. La velocità a cui i dati sono raggiunti, nella RAM fisica, eccede di gran lunga quella dei processi simili che coinvolgono un disco rigido, entro circa 1 milione volte. Ma, a causa della quantità solitamente limitata di RAM, il sistema operativo dovrà occuparsi del nascondiglio del sistema. (più…)

Anche se virtualmente è andicappato in termini di opzioni realmente fornisce all'utente rispetto a Windows XP, il programma di utilità di defragmentation del disco rigido in Windows Vista è uno sviluppo dell'equivalente dal sistema operativo del predecessore. Ma gli aumenti rientrano essenzialmente nel cappuccio dell'attrezzo. In questo contesto, il motore reale di defragmentation è stato sintonizzato in su, come pure l'amministrazione del processo di frammentazione.

“Per difetto, i defragments dell'attrezzo del defrag soltanto archivia più piccolo di 64 megabyte (mb). Di conseguenza, il mb di 64 delle lime più in gran parte non è spostato inutilmente. In earlier versions of Windows operating systems, if the defrag engine was in the middle of a large move request, it could take lots of time to cancel defragmentation. In Windows Vista, the defrag engine processes input and output requests in smaller portions. Therefore, you can avoid situations where the defrag engine is busy with processing large move requests when you cancel a defragmentation session”, Microsoft explained. (more…)

When troubleshooting any version of Windows, learning what applications and processes are loading on startup is a critical step. To this end, the old and faithful MSCONFIG application is a great help, and it’s definitely present in Windows Vista too. Just go Start, Run, MSCONFIG and you’re there.

However times change, and while MSCONFIG is a very useful little utility, there are better options available. Enter Autoruns. Developed by Mark Russinovich and Bryce Cogswell of Winternals (now Sysinternals and owned by Microsoft), Autoruns is a fantastic freeware app which does a full scan of your system and presents you with a total rundown of everything that happens on system startup and system logon. (more…)

Every once in a while you notice that your hard drive is working extra hard for what seems like no reason. A background process has taken your hard drive hostage, forcing it to thrash loudly as it struggles to keep up with the high rate of reads and writes. Your computer responds slowly as the process overloads the physical limitations of your drive. What are you to do?

The solution is simple, although a little tricky at times: identify and stop the process that is killing your drive. There are two methods and tools that you can use to identify the process. (more…)

Previously (here and here), I've written about isolating shared services so that they run in their own process, with a specific focus on the Windows Update Automatic Updates Service (wuauserv) that typically runs in the NETSVCS SVCHOST.EXE instance. One thing that can be done once this is accomplished is to lower the priority of the process so that when the service winds up consuming 100% of the CPU, the system doesn't become unresponsive.

Since we're dealing with a service, setting the priority of such a SVCHOST.EXE process can become problematic - the service may already be running, or, because it is a service, it is not started as non-service processes are, so one is not able to use START / [LOW NORMAL HIGH REALTIME ABOVENORMAL BELOWNORMAL] to impose a priority when the process starts. One can use a utility like Task Manager or Process Explorer to set the priority of a process on an ad hoc basis, but when the service restarts or the system reboots one has to remember to set the priority again.

Though not an ideal solution the following scripts (VBS using WMI, and PowerShell) can be used to set the