Jump to content

delerious

Members
  • Content Count

    11
  • Joined

  • Last visited

About delerious

  • Rank
    Member
  • Birthday 01/01/1970

Profile Information

  • Interests
    SUPERANTISPYWARE
  1. Running SuperAntiSpyware 5.0.1150 Free Edition on Windows 2000. When I try to do a "Check for Updates", it says: Authenticating Connection: Complete Checking for Definition Updates: Failed Definitions Update ERROR: FAILED Don't think this is a network problem, because I can do an update fine on my Windows XP machine. It's just not working on my Windows 2000 machine.
  2. delerious

    2 questions about cookies detection

    I imagine that would be each user's HKCU tree, which is stored in their ntuser.dat file.
  3. delerious

    2 questions about cookies detection

    I just ran SAS on a computer using one of the Administrator accounts (let's call him admin1). It only found tracking cookies under C:\Documents and Settings\admin1\Cookies. Then I ran SAS on the same computer using a different Administrator account (let's call him admin2). It only found tracking cookies under C:\Documents and Settings\admin2\Cookies. Why does SAS only find cookies in the current user's profile folder? Why doesn't it check other users' profile folders? I'd like to be able to run a scan with one Administrator and have it scan the whole machine, instead of having to run a scan with every single user on the machine. I do know that tracking cookies aren't a big deal, however, the fact that SAS is missing tracking cookies in other users' directories makes me wonder if SAS might be missing more serious malware in other users' directories.
  4. I have run a "complete scan" on 3 separate occasions now, and all 3 times SAS has only found cookies under C:\Documents and Settings\Administrator\Cookies. The thing is that I rarely use my Administrator account (I only use it if I need to install something). Over 95% of my browsing is done with a limited user account, so I wonder why SAS never finds any of the cookies under C:\Documents and Settings\\Cookies? Also, isn't the C:\Documents and Settings\username\Cookies directory where IE stores its cookies? Because I rarely use IE, I almost always use Firefox. I thought that Firefox stores its cookies under C:\Documents and Settings\username\Application Data\Mozilla\Firefox\Profiles\.default\cookies.sqlite. Does SAS not know how to scan the cookies.sqlite file?
  5. delerious

    SAS causing Fatal System Error?

    I am resurrecting this thread because I am considering purchasing the Pro version for my Windows 2000 machine. But that machine's hard drives are running off a RAID controller, so if I were to experience this SASWINLO.DLL problem on that machine, there would be no way for me to access the drive without logging in to Windows, and the machine would be totally screwed. If the autoupdate updates both program files and definitions, then how is it that the SASWINLO.DLL was not updated, and I ran into the incompatibility problem that caused me to be unable to log in?
  6. delerious

    SAS causing Fatal System Error?

    I don't go to crack sites. I think I probably did install it in late 2006. I guess your Update feature only updates the definitions and not the program files?
  7. delerious

    SAS causing Fatal System Error?

    dagap: THANK YOU!!! THANK YOU!!! I used the Knoppix CD to rename that file, and now I can log in! SuperAntiSpy: I just checked, and it is version 3.3.1020. Guess I should uninstall that and install the latest version?
  8. I have a Windows XP Pro computer with SP2 on it. It was working fine, and then I ran a SuperAntiSpyware scan. SAS found a bunch of adware cookies and nothing else. I told SAS to remove the cookies, and then SAS wanted to restart the computer, so I clicked OK. I got the following BSOD on startup, before the login screen: STOP: c000021a {Fatal system error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000005 (0x00000000 0x00000000). The system has been shut down. It happens every time I try to start up Windows now, even if I try Safe Mode or the Last Known Good Configuration option. So I can't login to the computer anymore. I don't know for sure that SAS caused this, but certainly it is suspicious that the computer worked fine until I ran SAS. Is there any chance that SAS could have done something to any system files?
×