Jump to content

JohnBurns

Members
  • Content Count

    22
  • Joined

  • Last visited

About JohnBurns

  • Rank
    Member
  • Birthday 01/01/1970
  1. Thanks - used Chrome - no problem. Appreciate your response and efforts.
  2. Still getting this as of TODAY (10/02) Is there a fix still in the works?
  3. I agree, however it is unusual to go 2 days without an update. Maybe a server problem?
  4. Thanks for reply - my SAS Alternate Start Tool looks identical to yours. I have contacted SuMo for more information....appreciate your response. Update 05/30 No longer a problem - SuMo has corrected it - thanks for your input.
  5. My updater app (SuMo) indicates an update is available for SAS Alternate Start Tool - version 1.0.0.26, but I can't seem to find it - and SAS Automatic Update does not install it. Please advise if this is an error by my updater app, or if there is in fact an update which I can manually update. Thanks.
  6. This morning I can't update definitions - either manually or automatically - is there a problem on the server? Never mind - updates have now processed - problem resolved.
  7. Can anyone tell me what Version 5.1.0.1002 is? It is currently on many download sites but the latest version at SAS is 5.0.0.1150, which is what I presently have installed. Just curious....
  8. Thanks for your help. I downloaded the pre-release (with no problem) and the event errors appear to have stopped. I appreciate your effort and patience with me. It's all a constant learning process for me. Thanks again!
  9. I did not intend to imply that the event viewer errors caused the problems. In my case it was the conflict between PerfectDisk and SuperAntiSpyware at boot time which caused the problems. Once I stopped SAS drivers from conflicting with PD by installing PD's Blocked List Registry "fix", that problem ceased. It was THEN that the event viewer errors started showing - which was a result of my action of blocking SAS Drivers with the "fix" I am pleased that a 64bit SAS is soon being released. In the interim, I don't mind "living" with the multiple event viewer errors.................sorry I added to the heated discussion in this thread. We just need to exercise some patience and try to understand things happen in spite of everyone's good efforts and intentions. Thanks for the information provided.
  10. This thread seems to be going nowhere - and I wish it could. I also am having problems with SuperAntiSpyware on my Windows 7 Home Premium 64bit OS. Part of my problem is with SuperAntiSpyware and PerfectDisk boot defrag, I know. I had to apply a patch from PD to block the drivers of SAS at boot in order to perform a boot defrag. See: http://www.perfectdisk.com/support/kb/823 This has solved BSOD's however the event viewer still shows Critical events os SASENUM, SASDIFSV.SYS, SASDIFSV and SASKUTIL at boot. Apparently the blocked list from PD is blocking these drivers at boot in order to perform boot-time defrag. I don't know if this even relates to the problem in this thread, however, I would like to know if there is a way to stop the event viewer from continuing to show repeated errors in my event viewer log. I hope this might help some for the previous posts - and help me find a solution to the problem I am experiencing. BTW, I am not a troll............lol! Thanks
  11. Thanks, Robin - just updated to Core 4374, Trace 2214, restored file, and ran scan...........everything is ok again. Appreciate all the help in here.
  12. Thanks for posting, weighty44 - at least I know I'm not the only instance of this problem......
  13. Thanks, Robin..............appreciate your post, HOWEVER, I updated SuperAntispyware after reading your post (to Core 4373, Trace 2214) - restored the file, and ran SuperAntispyware scan again - and there it is.......back again, just like before. Glad you got your pc's cleared, but I'm afraid mine is still in "limbo".
  14. Even it this is a "false positive", can someone tell me if it's ok to remove it? If, in fact, it is related to PC Pitstop utility, which i haven't used in a couple years, it would seem that it isn't needed. In searching the Net for an answer, it appears as though this is left-over crap from the PC Pitstop tests which I ran at one time in the past. SuperAntiSpyware hasn't flagged it before, however, even if it isn't spyware, I'd like to remove it unless it causes problems by removing it. So far, putting it in Quarantine has not presented any problems. Appreciate any input in this regard, also. Thanks.
×
×
  • Create New...