Jump to content

alphaa10

Members
  • Content count

    6
  • Joined

  • Last visited

About alphaa10

  • Rank
    Newbie
  1. When SAS does its scan, many of us prefer to let it run at maximum speed by dropping all other running applications. But that creates a problem, since we soon become impatient, and must find little tasks to do while SAS finishes. After a while, all the waiting makes us wish for a definite time of completion. Unfortunately, there is no way to determine that unless we know the number of files in the system, or have memorized the time required. On networks, the problem is multiplied. Familiarity with many machines and their respective configurations is almost impossible. A direct, easy solution is to feature a progress bar for at least the full-system scans. With a quick glance at the screen, we can estimate how much time remains, and structure our time accordingly.
  2. Offer a new option for SAS Professional to shut down after a manual scan. This feature enormously benefits those who run their SuperAntiSpyware scans after they finish a Windows session, rather than during a session. As many users have discovered, running SAS during a session often imposes a performance penalty, even while running in the background. This new option also resolves the obvious problem with after-session scanning-- leaving the system running after scan completion. It might be as much as 24 hours, or even longer, before the user returns. The auto-shutdown option is also a hardware saver, since it minimizes the time a system is left running after hours. When a storm sends surges through the power grid, an idle system can be damaged by such power variations. In addition, auto-shutdown is a security feature, since many users forget to terminate access to the internet when they leave a running system. Of course, users will need to set SAS beforehand to take care of whatever malware it finds-- the usual choice is to have SAS quarantine all items found for later review. Quite a few SAS Professional users with unpredictable work patterns find it difficult to schedule system scans. They need to be able to work at maximum speed while in their Windows session, and the time for their end-of-session scan varies wildly from day to day. For them, manual scans are the only way they can use SAS effectively.
  3. My SASPro will not update itself. When update failure began three days ago, the attached screen message appeared at every attempt to update (by the context menu), warning that regular features of SASPro will terminate in seven days unless the product is activated. At first, I believed SASPro had been hit by malware and disabled, but the message to "upgrade" SASPro appears to lead to the regular SAS corporate site. Parenthetically, I suspect this event is related to the gift of SASPro which I licensed for a family member. When my sister began to use her new computer (at last) only a few days ago, her own licensed copy of SASPro (Lifetime) notified SAS of its installation and use. If SAS management uses only a simple system to monitor installed instances of SASPro, it probably would not distinguish between legitimate and illegitimate use and attempted updates. However, the license number used for my sister is unique and was purchased for her exclusive use (see below), so there should not no questions about licensure. If your automated system cannot distinguish between legitimate and illegitimate installations of SASPro-- especially since we have the option to "transfer" the license to another computer (thank you!), perhaps it is time to devise a better approach. In any case, please establish the facts, and let me know what is going on. .%5C%5Cdesktop%5CMy%20documents%5Cuploads%5C130914%20SASPro%20upgrade%20message.jpg
  4. Many of us scan in manual mode, not by schedule. This is preferable because our office routines are too unpredictable for scheduled scans, in most cases. Typically, we leave the computer on a full system scan as we leave in the evening, to scan after hours. Since a full system scan takes no longer than three hours to complete, the machine is left idle and running the rest of the night, after scan completion. This is not a desirable situation for most users. Aside from general considerations of power waste and vulnerability to nighttime storms / lightning / power interruptions, an auto-shutdown is good general practice-- an idle, running machine is a more vulnerable system. Suggestion-- in paid ("Lifetime") versions, provide a feature with manual, full-system scans to permit automatic system shutdown on completion. This should not be difficult, since the only option offered now (on scan completion) is to "Take care of threats" (or words to that effect)-- initiated by a single button. This seems a useful, well-managed forum, and developers give prompt attention to most requests. Among all the submitted ideas are some really good ones, and I hope SAS developers continue to be receptive. A product team with a healthy attitude toward its customer base is a product which will continue to grow. As Microsoft discovered much earlier, there is no better situation than a paying "beta" user base for product refinement and improvement.
  5. To avoid repeated entries of the same suggestion type, it would be good to have a button users could click to produce a listing of previous messages posted and suggestions made.
  6. Provide a progress bar

    A simple horizontal bar showing scan progress would be helpful. Unless we know the approximate file count, we cannot estimate completion time.
×