Important MessageYou are browsing the archived Lancers Reactor forums. You cannot register or login. |
WinXP essential background apps
This is where you can ask questions and get and give help about hardware related issues. This Forum will be moderated by Taw with help from some other experts. So feel free to ask any questions you may have about computers.
10 posts
• Page 1 of 1
In playing games and using other high demand applications I loose a good deal of my system resources to some thirty eight background programs that are constantly running. I know that back in the days of Win 95/98 you were safe with a cntrl-alt-delete and closing all programs except explorer and systray to free up that extra bit of power. However, this system seems to have gone out the door with the change to XP. Which progams do I need to leave open to avoid a crash when closing these things down?
Explorer.exe
svchost.exe (ALL OF THEM)
winlogon.exe
smss.exe
csrss.exe
wdfmgr.exe
spoolsv.exe
lsass.exe
mdm.exe
Those are all the bare winrun apps that are going on my computer. apart from 'system'. Typically Windoes will not let you terminate a vital systems app (Explorer excluded), try and kill services.exe, and it wont let you (Task manager wont let you, 3rd-party process explorers will).
Pretty much everything else that is running will be a different process like messenger.
I would reccomend the process explorer program from Sysinternals to check it out. it lays the processes out in a nice hierachal dependancy tree.
svchost.exe (ALL OF THEM)
winlogon.exe
smss.exe
csrss.exe
wdfmgr.exe
spoolsv.exe
lsass.exe
mdm.exe
Those are all the bare winrun apps that are going on my computer. apart from 'system'. Typically Windoes will not let you terminate a vital systems app (Explorer excluded), try and kill services.exe, and it wont let you (Task manager wont let you, 3rd-party process explorers will).
Pretty much everything else that is running will be a different process like messenger.
I would reccomend the process explorer program from Sysinternals to check it out. it lays the processes out in a nice hierachal dependancy tree.
For Virtual Memory it depends on how much hard drive space you're willing to sacrifice. For example: I have a 200 GB hard drive, so I use 2 GB as Virtual Memory. In contrast, my friend Peter has a 40 GB and only uses about a gig of it because he lacks the spare space.
One way to save hard drive space is to reduce the size of the recycle bin and system restore features.
One way to save hard drive space is to reduce the size of the recycle bin and system restore features.
You may want to see what is actually using your system resources before you try to shut it down but some process names aren't very clear so you may want to try a program called Process Explorer, latest version that I know of is 9.12
Here's a link if you want from Download.com Process Explorer 9.12
Another program is MKN TaskExplorer 2005 SR2 2.3
TaskExplorer provides diagrams for each process containing CPU- or memory-usage of the process, which is helpful for finding the applications slowing down your system.
Both are free by the way.
Here's a link if you want from Download.com Process Explorer 9.12
Another program is MKN TaskExplorer 2005 SR2 2.3
TaskExplorer provides diagrams for each process containing CPU- or memory-usage of the process, which is helpful for finding the applications slowing down your system.
Both are free by the way.
For Virtual Memory it depends on how much hard drive space you're willing to sacrifice. For example: I have a 200 GB hard drive, so I use 2 GB as Virtual Memory. In contrast, my friend Peter has a 40 GB and only uses about a gig of it because he lacks the spare space.
exactly why i have two 80 gig drives in my comp i won't run out of virtual memory anytime soon
10 posts
• Page 1 of 1