Jump to content

Alan D

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Alan D

  • Rank

Profile Information

  • Gender
  • Location
  1. I think, judging from what Fabian says there, that I'll wait a few days for the release of the next version, Lynx. Thanks again for being, as always, one of the most helpful people on the planet!
  2. Thanks for taking the time for all this Lynx. I've managed to get all of the way through to uninstalling the service, restarting, and deleting the folder in program files. I even managed to navigate through the registry to the point where I had a little folder symbol for Emsi Software GMbH, and then on opening that, got another little folder symbol, a-squared. I presume this is the 'key' that you mention? So I right-clicked on that and deleted it. However, I'm still left with the little folder symbol ('Emsi Software GMbH') that 'contained' it. Do I delete that as well? Later - it's OK Lynx.
  3. I'm having precisely the same problem myself. In my case the a-squared Free Folder is still present in program files after the uninstall. I presume the folder is still there for you, too? The issue, then, is how to complete the faulty uninstall. There are some instructions about how to do this here, but I don't understand them. You may do better than I, but in fact Lynx is offering to help me with this, so watch this space... [Lynx, if you reply to me here instead of PM, our friend Flak - and anyone else in the same predicament - would benefit as well as me.]
  4. Actually, the transition has been even more unhappy than I thought. This morning I thought I'd better check that a2free had in fact uninstalled correctly during yesterday's transitional mess, and discovered that it hadn't. It's no longer listed under 'Add/Remove Programs', but the a-squared Free folder (95MB)is still present in C:\program files, and the a2 free service is still running. I've disabled the service, but how do I complete the uninstallation properly? Is it enough, having disabled the service, to just delete the a-squared Free folder in program files? (I presume it isn't. I've f
  5. Well perhaps so, Lynx - but my bewilderment yesterday was perfectly genuine. I'd had no warning of the muddle of what was going to happen after I did the update. (Of course if I'd come here first, I'd have seen Fabian's pinned note and got the necessary warning, but I didn't.) From the point of view of a non-specialist user like myself, the mechanism of the changeover hasn't been well handled, and I think the guys at Emsi need to have that feedback. Then I found the difficulties that have been discussed in this thread, and that made me very hesitant about proceeding further. Having been away,
  6. Been away for a while - came back, tried to update asquared free. Got the huge Ikarus update download (as I half-expected), but that was followed by a panel offering a bewildering two options, neither of which I felt I wanted, and in any case didn't know enough to be able to choose. It seemed I had to choose to do something, so I chose to uninstall asquared free. When I did so, I was presented not with an effortless way of installing the new product, but with a questionnaire asking why I'd uninstalled it? So I abandoned everything and came here to see what's up. Truth is, I understand hardly
  7. Sure enough, all sorted now. Thanks Lynx.
  8. Ikarus is alerting on two SuperAntiSpyware files (deupx.dll and SASSEH.dll) as false positives this morning, after the latest a-squared update (scan report attached). As a precaution I uploaded each file to the Jotti online scanner, but Ikarus is the only scanner that reports anything. I've submitted the files to emsi using the GUI facility.
  9. Back to normal here now, and updating fine.
  10. Thanks Lynx. One of the great benefits of this forum is the rapid feedback on questions like these (which otherwise could occupy a lot of unnecessary investigation time). @tbonic: I think we can be quite certain that somebody is.
  11. I haven't been able to update a2free for the last 24 hours. When I click the update button, within a second or two I get the message: 'Could not connect to the update server. Please check your internet connection or proxy settings.' Could I just check if anyone else is experiencing this? I'm not having any difficulty updating anything else (eg Superantispyware, or MBAM), so I'm wondering if this is a server problem at the emsi end rather than here.
  12. Yes that's true Lynx - though I suppose what is being tested by JerryM is the situation that, in practice, a 'typical user' will experience on running a deep/complete scan - so in that sense it's a fair test 'in the field' because it's what most users will in fact encounter when they scan without further enquiry. You're very right to point out though, that SAS achieves its fast scan time primarily by not scanning big files (in default mode)! There's another 'silent' factor in all this, that can't be quantified. When I run a scan with asquared and get a zero result, I feel more confident that
  13. This proposed test would be much more illuminating, since what is being recommended, both by myself and others, is to switch off all the other real-time residents when any one of them is scanning (MBAM, for instance, scans very noticeably more slowly if I leave the AVG resident shield switched on.) If scan times really bother you, then switching off the real-time residents while you scan would bring a smile to your face, I should think. I know of no good reason for leaving them all to battle it out between them. Also, I have no idea whether a2's scan is more or less affected than SAS or MBAM w
  14. Just to endorse what others are saying - to have all that real-time resident protection is almost certain to pose problems. If you're not convinced, set asquared to do a scan and monitor the processes using Task Manager. All those real-time monitors will be following every move that asquared makes while it's scanning. This will slow down the scan significantly, and furthermore you run the risk that if an infection is found, you'll have (at least potentially) not one program trying to deal with it, but probably several, all at once. The potential for trouble is clear. Please try what Lynx and
  15. The good news is that the FP is already fixed, with the latest update. Thanks to the emsi team for such a fast response. My main point remains, though: I'm still disturbed by the sheer frequency of FPs that have been turning up in these recent months. No other malware scanner I use comes even close to this frequency of false alerts. This is important not just because of the inconvenience for the user, but also for a2's reputation. When friends and family ask me what I recommend (I know little enough in this area myself, but they know even less), I tell them that although I use a2 myself, I ca
  • Create New...