Jump to content

edo

Members
  • Content Count

    5
  • Joined

  • Last visited

About edo

  • Rank
    Newbie
  1. edo

    sabkutil again

    I hate to return to this dead horse, but despite all the things I like about SAS I've uninstalled it. Ver. 4.44.0.1000 is the latest I tried and I'm still getting incorrect registry calls to a nonexistent sabutil.sys . I don't know if these errant keys are causing various problems I'm having with my Vista x64, but their presence makes registry upkeep all that more onerous, and it's irritating to see the error show up in the event viewer. Is this glitch be attended to in ver. 5? thx edo
  2. Oops, you're right. Late-night typing... - edo
  3. Thanks for the helpful feedback DooGle. I don't generally enable RT SAS, just check offline periodically or when I suspect something. A quick search shows that the jury is out as to whether & how x86 machines are more vulnerable that 32-bit ones - if I get time I'll follow this up in the Sun VM and Firefox forums. I'm curious if there would be any more protection running a 32-bit MS OS w/ compatible virus & malware pgms. in a VM... - edo
  4. I've installed my SAS Pro (registered) on a new Vista machine. It seems to work OK, but the Event Viewer shows an error \??\C:\Program Files (x86)\SUPERAntiSpyware\SASKUTIL.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver. So I don't know how well SAS is catching malware. I also have a virtual W2K machine with Firefox installed running in Sun xVM on top of the Vista. Until the x64 driver that's been promised becomes available, would my protection be better if I installed SAS in the VM and did my online work there? Would it help to install it in Vista's Program Files rather than in Program Files (x86)? (All of my browsers in Vista are x86). Is there any info on when drivers will become available for Vista 64-bit? Thanks, edo
  5. I would appreciate a command-line patch, if such a thing is possible. With it I could batch-file a custom scan as part of my shutdown routine. At present I can only shutdown after scan if I run a quick or complete scan, both of which are too much. (running SAS 4.22.1014 Pro, which seems to be the the latest ver. I can run without problems or unacceptable slowdowns on W2K, 500 MHz, 256K RAM - an old machine, I know...)
×
×
  • Create New...