4 replies
by henryk Accepted solution
by older mycroft Accepted solution
Open a command window (it's not really a DOS window) and then call up the Task Manager, check the Processes tab, clicking the 'CPU' column to get the biggest numbers running from the top.
Try typing into the command window and watch what other processes are using up the processor cycles.
There'll be something causing it ( [b]a more profound statement I doubt I've ever typed[/b] :D ).
It might be 'File Indexing' or even 'Windows BitDefender' scanning the directories of the hard drive, because when you open a command window - XP is doing nothing itself - so the above processes invariably wait for idle time before starting.
by henryk Accepted solution
by older mycroft Accepted solution
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending