WinXP Pro SP2, Pentium 4, 2.6GHz, 1GM RAM.
Is there any way can I control the order or priority in which items are loaded into the system tray during startup (when the desktop is first shown) after the login screen?
History and Background on this problem:
This first became a problem right after installing Asian language support files and then ignorantly deciding to try and add every language on the available list of languages to the language bar. Well that royally screwed things up for a while until I uninstalled all language support and started over from scratch by only installing the few language support files I needed for school and correspondence. With that problem fixed and working properly Windows Explorer began crashing during startup after the login screen. This crash typically happens during population of the System tray. Running memory tests for 3 days did not turn up any problems with the system memory. I posted threads on two separate Computer Help sites, and both help techs came to the same conclusion; that WinXP needed to be reinstalled in order to fix Windows Explorer from crashing after the login screen when the desktop is first shown. Ok thats all fine and good, but there are still a few things I'd like to try first before biting the reinstall bullet. Especially because this computer is so close to running just fine after explorer crashes a few times. This is where your help and expertise will hopefully come in handy.
Security software being used:
Avast v4.7 Home edition
PeerGuardian2 consistently becomes unhooked from the system because Windows Explorer crashes during PeerGuardian2's startup process. As a result Explorer never gives PeerGuardian2 a window by which the user can interface with the program. The OS is nice enough to show an icon for PeerGuardian2 in the System tray, but it doesn't get as far as giving that icon a right click menu, or a window to manipulate or bring to the foreground. In other words the only option I have left is to kill PeerGuardian2's process and start it over after uninstalling its drivers from memory. This of course crashes Windows Explorer and causes the whole problem over again.
Current Solution Theory:
PeerGuardian2 is the last item in the System Tray to load. If I could somehow make it load after Avast loads then I might get a chance to open its window before Explorer crashes. Its window should stay open even while explorer crashes and restarts because this works for items that are loading 1st 2nd or 3rd in the system tray. If this works then the system crashes will become a mute point because Explorer works fine after it crashes however many times it feels like crashing after startup (Typically only once or twice). Note: Completely uninstalling PeerGuardian2 does not stop Explorer from crashing after startup.
PeerGuardian2 and Avast were working fine and playing quite well together on my computer before the language support file fiasco. They should still be compatible now, and they actually do work one time and one time only after a complete and thorough uninstall and reinstall of PeerGuardian2. In other words after installing PeerGuardian2 it works fine for the first startup, but all subsequent PeerGuardina2 startups fail because of the Explorer crashes.
Possible infection notes:
There is a question of infection on this computer because the WinXP actually crashes if I try to use any of the online scanners. The first time that happened I did catch a glimpse of some kind of Trojan right before WinXP crashed and I lost the window before I could read which Trojan it was reporting (I think it was Panda's online scanner that reported this). Subsequent online scans cause WinXP to crash before the scan completes.
I apologize for the length of this post due to being clear, specific, thorough, and almost in need of hospitalization due to an obvious overdoes of caffeine... its been a while since I've had any coffee, and clearly I've had way to much.