Jump to content

HAN

Members
  • Content Count

    26
  • Joined

  • Last visited

About HAN

  • Rank
    Member
  • Birthday 01/01/1970
  1. 4.22.1014 has solved my CPU spikes. Great job SAS developers/Nick!
  2. I have them too. I assume that Comodo's Defense+ is "protecting" itself from SAS Pro's real-time scanner. I'm pretty sure that Comodo CIS places it's own files/folders in the My Protected Files section by default. IMO, I don't think it's anything to be concerned about. I just ignore them myself. I suppose you could make an exception in the D+ settings for SAS Pro if you wanted to...
  3. Nick/Pandato: Any news to share with us on this issue? Have you been able to confirm any of this? I'm not asking for specifics... It's just that we haven't had any kind of feedback since Aug 10.
  4. It happened again tonight. Everything related to auto updating is unchecked but from boot, right before the SAS splash, the dialup connection box popped up and the small SAS update box was on the display behind it. This is version 4.20.1046 and was a fresh/clean installation created earlier in the day. Is there a registry setting that controls updates? Or are these settings in some kind of INI file? I'm pretty confused how SAS can continue to try to update if all of the update settings are switched off???
  5. I can confirm that SAS Pro does appear to have issues with NVIDIA. I have two laptops, one with NVIDIA and one with ATI. The NVIDIA PC CPU bangs away from 5 to 8 or 9 percent CPU every other second and the ATI one is much quieter with only 1 or 2 percent every now and then. I'm not home now but I am using one of the 4.2.x builds. I too hope this can be addressed in a future SAS build...
  6. I used the uninstall tool and removed 4.15.1000. I then installed the latest 4.2 build. I'll let you all know if I have any more issues. (FWIW, the uninstall tool only removed the Application Data files from the Admin account. My other Limited User account SAS Pro files had to be hand deleted. Something that surprised me. Normally, a special removal tool catches everything, even when the regular uninstaller won't. )
  7. Yeah, it's been rebooted lots of times. I'll work on a reinstall as soon as I can...
  8. Any ideas? Could it be something messed up regarding the install? I just had another update popup tonight.
  9. Yes, all 3 boxes are unchecked. (This is a recent, new installation of 4.15.1000 on a new Dell Vostro laptop.)
  10. As I am on a very slow dialup connection, I have auto updates and the auto update reminder turned off. That said, I have access to a high speed connection a couple of times a week. So, when I'm there, I download the latest definitions to a USB flash drive and bring them home. So far, this has worked well for me. The question I have is that even though I have auto updates turned off, SAS Pro occasionally tries to bring up the dialup connection box on it's own (the SAS updater window is running when this happens.) Is the program set so that even if auto updates are turned off, it will attempt to update itself every "xx" many days? Today was the 15th day since it was last updated from the PC itself and it tried again this morning.
  11. To my knowledge, cookies are only cleaned up by running the on demand/manual scan.
  12. Well, at first a re-install didn't help, but in the end, it did! It appears that the SAS Pro shortcut I was clicking to re-start SAS Pro (after the manual update) was somehow invoking the MSI installer. Once I stopped using it, and used the one in the Program Group, the installer no longer attempted to run. If I had discovered this before the re-install, I'm thinking I wouldn't have needed to re-install. As to how the shortcut became linked to the MSI installer, I haven't a clue...
  13. I manually updated another SAS Pro PC and did NOT have the MSI issue. So, I will start over on the PC with the problem and see how it goes...
  14. After installing SAS Pro, I always update manually (download to a PC at another location and install later at home.) Prior to version 4.x, I never had any issues. But starting with 4.0, manual updates no longer seem to work correctly. 4.0 would not update the Core and Trace versions without deleting the Processlist.bin file first. And now, when manually updating 4.1, the MSI installer runs every time. I've tried the manual update 3 or 4 times. The Windows installer runs, re-creates the SAS Pro shortcut on the desktop (which I always delete) and then exits. It does update the Core and Trace version numbers, but this seems like a very long way to go to get things up to date. I have not yet tried another install (since I have to take the PC to another location) but before I did, I wanted to check and see if I'm the only one having manual update oddities...
  15. HAN

    SAS Pro

    Yeah, beginning with version 4, real-time SAS Pro uses very little RAM. From what I've seen, the bulk of the rest of the needed memory is in virtual memory.
×
×
  • Create New...