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. I ran Ccleaner, which picked up the key under obsolete software, and I removed it that way. So I've answered my own question, effectively. Thanks again.
  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 found an old forum link which might be relevant here, but don't understand Christian's instructions. I can get as far as opening a command prompt, and then I'm lost.)
  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, and with a million things to do, I don't have time to resolve these issues or risk messing things up. Of course I've benefited so much from your expertise in the past, Lynx, that I know very well you'd help me over this, and I expect that as you say I'll be back to seek out your help again before long. But right now I really, really need my computer to be working without problems, and can't afford to be distracted by the tangle of the transition from a2free to its new manifestation. So for the present, my wisest course seems to be to lean more heavily on my alternative scanners. Best, as ever, Alan
  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 any of what's being discussed in this thread, but it seems to me that the transfer from the old to the new is decidely user-unfriendly - well, certainly unfriendly to this user, at any rate. All this talk of possible conflict with the Windows Security Centre? Three-day trials? Opening an account? What account? Why? I don't think I want to go down this road, with all this uncertainty and complication stacked up. I certainly don't want to risk my Windows Security Centre being messed up. So, suddenly, after all these years, I have no Emsi software on my computer. So thanks for all that protection in the past, guys - it's been invaluable. But I think this may be where I have to drop out.
  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 my machine is clean than I do when scanning with anything else. One can grumble from time to time about 'too many fps' (as I have done), or about slow scan times, but through all this, I stick with a2 because it is exceedingly reassuring when it gives a clean scan.
  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 when it's battling against other residents, and the results of your proposed test would be interesting - it would be a more properly controlled experiment. To look at this a different way: a-squared's 'Quick scan' is the fastest 'ready-made' scan of all my scanners (takes less than 2 minutes), and I use it every day. As a quick but sensitive check with a virtually instant result, none of my other scanners can compete with that (though I'm aware that this isn't a level playing field either, for different reasons). Like Lynx, I hardly ever use a2's 'deep scan', so whether it's fast or slow isn't really an issue for me.
  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 HD have suggested. Switch off all other real-time residents before you run a scan, not just with a2, but with any scanner. Happy New Year, everyone. May your false positives be few and your clear scans many.
  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 can't recommend that they use it, simply because I know they would find it hard to cope with the persistent FP problem. In truth, it's got to the stage where I'm finding it hard to cope with, myself, and I'm wondering at what point the frequency of FPs outweighs the advantage of a2's high detection rate. It's getting too close to call. And I say this not for the sake of grumbling, nor because I'm ungrateful for what, after all, is a free program, but because I think it's important feedback from a long-term user who is very favourably inclined towards the product.