Jump to content


  • Content Count

  • Joined

  • Last visited

About KNRover

  • Rank
  1. I thought this issue had been addressed, but apparently not. The vast majority of the programs on my computers pay attention to ALL user preferences when updates are installed. SAS doesn't -- at least it doesn't for one item: Start SAS when Windows starts. I provide tech support to a number of friends and try to keep the number of programs that load at startup to a minumum to minimize startup time and maximize performance. These friends are barely computer literate and, after updating SAS, call to tell me that "this SAS screen keeps coming up now when I turn the computer on." I then lead them thru Preferences to uncheck that checkbox. They then ask, "Well, how did it get checked? I didn't check it. . . the screen didn't start appearing until after I installed the update!" I'm then a little embarrassed to tell them that the updates for SAS, which I recommended and put on their computer, ARE NOT PROGRAMMED PROPERLY; THEY DO NOT RETAIN THE USER'S PREFERENCE FOR THE 'START WHEN WINDOWS STARTS' OPTION! They then come back with, "Well, why don't they fix that?" My sentiments exactly: Why can't you fix that?
  2. My last post to this thread indicated that by unchecking and rechecking the first "Ignore" checkbox in the Scanning Controls would make that selection work. Well, I just downloaded and installed the latest program update (ver. 5.0.1136) and that no longer works. The program now ignores anything you enter into the Scanning Control tab. Message to the programmers: This is a major gaf. You need to fix it post haste. 2nd message to the programmers: This may not be happening in all versions of Windows, so I will tell you that I'm experiencing this on a desktop running Win XP SP-3.
  3. Well, guess what, folks? I just spent the last 20 minutes or so testing two of the exclusion preferences in SAS -- the 'Ignore files >4MB' and the folder exclusion list. I had not tested the 'Ignore files >4MB' (which has always been checked), so I unchecked it AND removed the one folder I added to the folder exclusion list. A Quick Scan under these settings took 6:38 -- way more than the 2:59 it has been taking. I then reset the preferences, re-checking the 'Ignore files >4MB' AND adding my C:\My Temp folder back to the excluded folder list, and ran a Quick Scan. 2:02!!! And I watched the files-being-scanned line closely to see if I saw any of the files in C:\My Temp being scanned. NOPE!; no longer being scanned. Conclusion: The exclusionary preferences in the new SAS (ver. 5) can apparently become corrupted, and are thereby ignored. When I removed or added back the folder to the folder exclusion list, it made no difference, so that won't fix it. BUT, if you uncheck the 'Ignore files >4MB', close SAS, reopen it, then recheck that checkbox, it makes the exclusions -- both big files and the folder exclusion -- work. It seems odd to me that >4MB checkbox and the folder exclusion list would in any way be linked, but I trust somebody will look into how they can corrupt. In the meantime, if you run into the same issue, just do the unchecking and re-checking I described, and that should fix it.
  4. No -- no detections. I noticed that Quick Scans were taking longer than I thought they should, so ran one and closely watched the files-being-scanned line. I could see that it was not only scanning the zip files in C:\My Temp\Backups, but every individual file within the zip files. The three zip files in that subfolder total ~1.4GB, which lengthens the scan time substantially (approximately doubles it). After adding C:\My Temp to the excluded files list (only item in the list), I reran a Quick Scan. SAS still scanned all the files in that folder, including every individual file within the zip files. I also did timed tests. Quick Scan time with above folder excluded: 2:59. Time with no exclusions in exclusion list: 2:59. I also have checked "Ignore files larger than 4MB", so SAS is also ignoring that. Perhaps I should reiterate that I'm using the FREE version of the program. Although I get no message saying this, does the folder exclusion list only work in the PAID version?
  5. I was running a Quick Scan. I seldom run full scans, but did one today just to see if it would pay attention to the exclude list. It does not. It does not scan the folder on the exclude list if I run a Critical Point scan, but that's to be expected; CP scans are only for system32 and the like, not non-system files.
  6. Since I have installed a couple of PROGRAM updates since ver. 5 was release, I didn't think uninstalling and reinstalling would solve the problem. Unfortunately, I was right; it still ignores the exclusion list. Something is fundamentally wrong with the product.
  7. I use the free version of SAS. I notice that the new version (I have 5.0.1134) ignores the Excluded Folders list. Is this a bug or does that list only work in the paid version?
  8. Because no single AS program finds ALL the spyware, I used three: SAS, Malwarebytes and Ad-aware. I recently ran a test for some friends for whom I provide computer tech support involving Smiley Central. I had told them to stay away from that program because it was loaded (an understatement) with spyware. However, the wife just loved the emoticons and kept bugging me about using it. To show her what it would do to her computer, I ran full scans with SAS and Malwarebytes to ensure there was no spyware on the computer, then installed the Smiley Central program, then repeated the SAS and Malwarebytes scans. Both, of course, found HUGE numbers of "infected objects", and finally convinced the friend to stay away from Smiley Central. However, I noticed a major difference in what each AS program counted as an "infected object". Malwarebytes found 822(!) while SAS found only 171. But I know that both found all the spyware, so my question is why the big difference in infected-object count? Is it just that Malwarebytes counts every individual item (every cookie, every registry entry, etc.) as an "object" while SAS counts groups of related items (e.g., a file and all of its registry entries) as one "object"?
  9. Thank you, all. I believe, however, that I'll refrain from reinstalling SAS until after a few Avira updates, one of which will hopefully contain the fix.
  10. P.S. Forgot to mention that I removed SAS, since Avira had already zapped SAS.exe, so the program no longer functioned. I do not intend to reinstall it until I get confirmation on this forum or from SAS directly that their download server is not infected.
  11. My AV is Avira. When I brought my computer out of hibernation this morning, it alerted me to a trojan by the name "FakeAlert.BZ". Each time I picked "Delete", it alerted again -- 4 additional times -- and I deleted each time. When I looked at the Avira log, it showed "trojan FakeAlert.BZ" 5 times, but what's really bothering me is that it showed the source to be SUPERANTISPYWARE.EXE!!! I updated SAS yesterday, and am wondering if SAS's download server got infected by this trojan, and was downloaded with my update. Anybody else experience anything like this?
  12. I noticed today that I have some quarantined spyware dated 6/28/09. It got me to wondering if SAS had a maximum setting for retention of quarantined files (e.g. 30, 60, 90, etc. days). IOW, a setting that would make it unnecessary to periodically clean out the quarantine chest manually. If it does, I can't find it, so please let me know how to access it. If it doesn't, it would make a nice addition to the next version.
  13. If the file is infected, Windows should detect it as "corrupted". Assuming your friend has her original Windows installation CD or recovery CD(s) if her computer came with no Windows CD and she created the recovery CD(s), she can click Start, Run and type "sfc /scannow". "sfc" stands for "system file checker". Windows will check for both missing and corrupted Windows files, and replace them from the CD. If it needs to replace a file, it will ask her to put the CD in her optical drive.
  • Create New...