The RAM figure presented in your graphic...is misleading, it does not represent the amount of RAM installed.
To see the amount of RAM installed...Start/Run...type msinfo32 and hit Enter. Last line in the window to the right...Total Phyical Memory.
The differential between that number and what's reflected at My Computer/Properties...is the fact that onboard video and a few essential Windows functions use some RAM and these amounts are taken away from the installed to produce the figure reflected in Computer/Properties right-click.
Better explanation follows, courtesy of
http://home.comcast.net/~SupportCD/XPMyths.html.
"
Myth - "Windows XP does not support 4GB of RAM"
Reality - "On any 32-bit Operating System (not only Windows), you only have access to 4GB of address space by default. A 32-bit Operating System can actually handle 4GB of memory. The issue is the way in which the hardware allocates memory for its own resources. The hardware needs to allocate memory space to use for things like the PCI bus, BIOS, the video card and others. It allocates this from the address space presented to it, which is not necessarily the same as the amount of physical RAM installed. Also of note, it allocates this memory from top to bottom. The problem is, when you have 4GB of RAM installed, the amount of physical memory installed is the same as the address space. If you have 4GB RAM, and the hardware needs to allocate a large chunk of memory for its own use, and it does this from top to bottom, the memory that is blocked off starts at 4GB and allocates downwards. So, the final amount of RAM the OS will be able to see is the difference. This is because when it actually allocates for the physical RAM in the system, it has to skip the chunk that was blocked off by the hardware. Since a 32-bit OS can only see 4GB, the rest of the RAM is invisible because it is above the 4GB barrier. By using the /PAE switch, you enable the OS to see above this barrier, and you can see all of your RAM, sometimes. The real problem comes back to hardware. The OS can only handle whatever resources are shown to it by the hardware BIOS. If the hardware does not support a large enough addressing range, then it simply won't report anything above that so the OS is in the dark. If the hardware supports 36-bit PAE Intel Extensions or the AMD equivalent, and you use an OS that supports PAE, you should be able to enable both and see all of the RAM."
I looked at some of the processes you have running. I can't say that there is anything dramatically wrong with your selection of programs to install but I will say...every time that you install a piece of fluff on your system, there's a good chance that you are also installing an unnecessary startup item (some update opportunity/monitor that is not really needed/useful).
With every piece of fluff that you install...that's another set of files which can go wrong and possibly cripple your system.
http://www.file.net/process/searchindexer.exe.html
If you have installed Windows Search 4.0, I suggest you uninstall it, if you have XP. Since you are posting in the XP forum...I'll assume that you are running XP. This program was created for Vista, not XP...and has been known to result in system slowdowns, if nothing else.
You have ATI video so problems may pop up at any time. ATI inflicts a number of files on a system and when some of these files become damaged, they create "mysterious" problems that may seem to have no cause. Usually involves more troubleshooting by user. If no indication of problem, assume all is well.
I would remove/change the configuration for:
ACService.exe 1304 ArcSoft Connect Service ArcSoft Inc. This is probably an update service for installed graphics software, no reason for it to be running all the time, I would remove it from the startup items.
AppleMobileDeviceService.exe 1452 Apple Mobile Device Service Apple Inc. avp.exe 1592 Not sure what this is, take a read at
http://www.what-is-exe.com/filenames/apple...ervice-exe.html.
mDNSResponder.exe 1612 Bonjour Service Apple Inc. I suggest uninstalling this,
http://www.raymond.cc/blog/archives/2008/0...nsresponderexe/
searchindexer.exe 1904 Microsoft Windows Search Indexer Microsoft Corporation If you have Windows Search 4.0 installed, I suggest uninstalling it.
Acrotray.exe 3848 AcroTray Adobe Systems Inc. I would eliminate this, but I don't know what programs you have installed (I don't install Adobe programs, other than Flash...I don't like the way Adobe strews files on a system).
ACDaemon.exe 3964 ArcSoft Connect Daemon ArcSoft Inc. Remove from startup.
FLVSrvc.exe 4028 FLV Service for Ask and Record Toolbar Applian Technologies, Inc. I would remove this because I find all toolbars to be more of a pain than any are worth.
FreeRAM XP Pro.exe 3332 FreeRAM XP Pro (YourWare Solutions) YourWare Solutions ™ RAM optimizer? I would suggest uninstalling.
GoogleToolbarNotifier.exe 2348 GoogleToolbarNotifier Google Inc. Another toolbar.
Launchy.exe 816 Another program installed of dubious value.
JetMM.exe 864 jetMailMonitor JetAudio, Inc.
realplay.exe 2996 RealPlayer RealNetworks, Inc. AND
realsched.exe 5288 RealNetworks Scheduler RealNetworks, Inc. Unless something has changed, Real, Adobe, Quicktime and iTunes...head my list of Most Unwanted
.
After reviewing all that you have installed and running...I have to say that you should be grateful that it only goes slowly occasionally, you have some real resource hogs installed
.
Generally speaking, you probably need to review your Startup items, using an application called Autoruns.
You need only be concerned with the Logon tab, do not change anything on the others.
Eliminating/disabling an item in startup does nothing but remove it from starting/running when the system boot. The program/process is still available via normal use of the program, it's just not "warming up" forever.
AutoRuns for Windows -
http://technet.microsoft.com/en-us/sysinte...s/bb963902.aspx
Louis
Help
Back to top
