b8late

Member
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About b8late

  • Rank
    New Member

Profile Information

  • Gender
    Not Telling
  1. @ Sammo The link you provided leads to the old version of the Comodo Uninstall tool from 2009. The link that ctrlaltdelete provided in post #6 leads to the new version of the tool, which was developed for use through version 5.4. According to the more recent posts in the link, the developer is due to release the newest version of the tool, with compatibility for versions 5.5 & 5.8, in the next month or so. I think I'll just wait for this newest version, rather than run a very old version of the tool. Thanks for your help, though.
  2. I would like to say thanks to ctrlaltdelete for the insight and recommendations. After reading this sticky thread in the Online Armor Forum, http://support.online-armor.com/showthread.php?t=12769, I started to search my system for any remnants of Comodo left behind after the uninstall. I found no evidence of driver remnants in Device Manager, Show Hidden Devices, Non Plug and Play Drivers. I then searched for Comodo in Program Files, and App Data, found an App Data folder and deleted it. Finally, I used the "find" feature in Regedit to search for Comodo, and found 16 registry keys. I have used the Comodo Uninstall Tool in Normal Mode in the past, but at this point I ran it again in Safe Mode. After the reboot, I searched Regedit again and the keys were still there. At this point, I can't tell if these keys were left behind by Comodo FW, or if they were put in place by the Uninstall tool. CCleaner registry cleaner does not detect them. The idea of manually deleting keys from the registry makes me very nervous. Could Comodo registry keys alone, with no Program Files, no App Data, and no driver remnants cause a conflict with OA? Do you think that manually deleting any registry keys tied to Comodo is safe? Is this necessary? I suspect that the slow startup I'm experiencing is related to the loading of the OA drivers. I should also report that I did reboot twice in between the uninstall and reinstall of OA. My PC currently has 5 startup entries enabled (OA, Avast, Java Updater, Adobe reader updater, Windows Task Manager), and 25 running processes at idle (18 Windows, 4 OA, 2 Avast, 1 Java). I'd like to be clear and say that these issues are not a deal breaker for me. I like OA and plan to keep using it. The original intent of this post was to report possible bug(s), and see if others were experiencing the same issues. At any rate, I do appreciate the comments. Thanks.
  3. OK, so you're saying the OA memory usage on my system is normal, that's fine. It was the combination of the information on the Emsisoft website, and the following past forum topic that led me to believe that OA was not functioning properly on my system. http://www.emsisoft.com/en/software/oa/ http://support.emsisoft.com/topic/5888-oa-51-ram-usage-high/ In regards to the slow startup, my symptoms are very similar to what the user was experiencing in this past forum topic. http://support.emsisoft.com/topic/6078-installing-online-armor-free-version-windows-xp-start-up-slow/
  4. I would like to report that since my original post I have determined that these issues are not caused by Avast in any way. I went through the process of uninstalling OA, uninstalling Avast, and cleaning the temp files and registry with CCleaner. Then I only reinstalled OA, and with no AV installed, OA behaved the exact same way as before (High RAM usage, slow startup, slower programs launch). I just did a fresh, clean install of XP SP3 32bit 5 months ago, and have not had any blue screens, random shutdowns, etc. The OS has been running great. The only other thing I can think of that might be in conflict with OA is that I have Iobit Advanced System Care 3.8.0 and Iobit Game Booster 3.0 installed and have utilized the system optimization tweaks of these programs, which have altered OS registry settings and stopped unnecessary services.
  5. I recently made the switch from Comodo FW 5.8.211697.2124, and installed OA Free 5.1.0.1331. The uninstallation of Comodo, and the installation of OA went smoothly with no problems. I like OA very much, but I'm also having the problem of higher than advertised Memory usage (OA sys. req. says 20 MB free Ram). At idle, with no other programs launched except Avast Free 6.0.1289, Windows Task Manager consistently reports the following Memory Usage (working set): oacat.exe ~ 2 MB oahlp.exe ~ 1 MB oasrv.exe ~ 37 MB oaui.exe ~ 5 MB A total of ~ 45 MB at idle? Does this seem normal? In addition, OA has noticeably slowed my startup time. My PC now pauses for a good 10 - 15 seconds at the blue Welcome screen, whereas before this install the pause was maybe 1 - 2 seconds. Also, Trusted (green) programs take a few seconds longer to launch when compared to what I was used to before this install. Have many others reported these same issues? Are these known bugs that are being worked on? Is there anything I can do on my end to resolve these issues? XP SP3, P4 2.5 GHz, 2 GB RAM Avast has been excluded in OA, and vice versa