Jump to content

TrDo

Members
  • Content Count

    11
  • Joined

  • Last visited

About TrDo

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Athens
  1. TrDo

    SAS Portable

    OK Nick. I'm sorry about b4. Did not mean to be disrespectful. I know you try your best. Thanks so much. Take care. TrDo.
  2. TrDo

    SAS Portable

    Thanks. As usual this forum rocks with the pluralism of provided answers. Please disregard my comment.
  3. Hi everyone, I would appreciate if anyone who knows can tell me how to keep the same settings in SAS Portable. 1)Every time I open it, I have to re-enter the entire list of excluding folders, re-set all the settings/preferences, etc. 2)Further, after SAS Portable finishes the scan, if I "Allow" items found, the next time I re-open it, they have disappeared. 3)Also, I cannot find find the log file, because I think it does not keep one. Thanks much in advance guys. All the best. TrDo
  4. I'm running on Win7 x64,as you have gathered by now, and I need the correct uninstaller please, to completely get rid of SAS Pro 4.33.100. I'm willing to try the SAS 4.90 (x64) prelease. I would appreciate the correct link for the unistaller. Thanks. TrDo.
  5. Unless my English is not good, I can't think of another reason for people misreading my post. I said, and say again, that in the Event Viewer the pattern is evident between the SAS triggered errors and the BSODs. This is not only obvious chronologically but also as a procedural pattern. The system dump files are also another hardcore clue of SAS triggering the blackout. SAS Pro is not available as a native release for Windows x64 (64-bit) operating systems. Microsoft has extended the core of the operating system kernel in the x64 editions of Windows with KPP (Kernel Patch Protection - informally known as PatchGuard) in such a way that self-checks are routinely performed to detect tampering. The proactive protection provided by SAS Pro is not supported by the Windows x64 kernel. SAS Pro must make changes to the kernel to implement proactive protection. These changes are detected by PatchGuard as tampering, so the system will crash soon after SAS Pro is trigeered. Further to this, SAS was triggering the nvlddmkm error, which was causing the BSOD. Clear and simple... now. But then when it was happening it was a pain to try to pinpoint the cause. As I said, I have been using SAS Pro for quite sometime on my other x86 operating system without having any issues whatsoever. But the x64 operating system is a different story. SAS Pro is not fitted for such action. Only thing I was asking-and expecting from SAS Developers- is a bit more responsible action regarding their support site statements...Look at the first post and you'll understand. Please do not blame your customers' pcs and systems, like the 18 years old telephone-support girls do. I sympathise with them because they don't know and they do as they are told. But here in this forum I was expecting a more responsible answer and action. Our systems, for some of us, are not black boxes where we cannot find what's going on. Please, re-arrange your site's statements about the x64 capabilities of SAS Pro 4.33.100, or at least warn your customers, or at leat apologize for causing such issues. Thank you. TrDo. P.S. Please do not use capital letters in your posts. It's called yelling and is not polite.
  6. Hi JohnBurns, It looks as though we're not getting any answers about our problems, operating SAS Pro in our Win7 x64 systems. All we get at the moment are idiotic statements from Bob, who still hasn't found anything else to do. I would appreciate if anyone could take a responsible position and answer about SAS Pro Compatibility issues in Win7 x64 systems. At the moment I have uninstalled SAS Pro, and running MBAM Pro, without issues whatsoever. Thanks. TrDo. PS. I'm sure Bob is highly related to siliconman01.
  7. Well it's nice to know that you run without problems Nem187. Good for you. But this is not a gallop we are conducting here. SAS Pro 4.33 is not designed to operate with a dedicated native 64 driver, cos it does not have one. I just believe that we should have been warned about the possible implications. Accepting responsibility and recognizing our mistakes makes all move forward. Anyway, thank you for sharing your experiences with the rest of us. TrDo.
  8. What causes me Bob, to act like that Bob, are 3 BSODs on a brand new system Bob. One week's old, Bob. And general comments, like your friend's above, do not apply, unless you want to add to the count of the posts below your name. And further Bob, what's it to you? Are you his lawyer or his cousin? Please mind your own business. That is, if you have one Bob. If not please try and get one, and make your self useful. Here the problem is specific Bob. We did not ask for your opinion Bob on ad hominem dimensions of the issue, Bob. Thanks Bob for jumping in. You're very constructive Bob. PS. BoB, how come you are registered since 2006 Bob, and you only have 3 posts, out of which 1 was here today Bob? I wonder who are you Bob?
  9. You have no idea what you're talking about, have you? Who said anything about a simultaneous drivers loading? Not me. The best thing you could before you blame my system would be to ask for the dump files. I have examined them, and their story confirmes my claims. If you're a dump file expert, I'll be glad to send them to you. I guess you're not. Because if you were you would have asked them. Your behavior is the typical reaction of someone who defends his small world. I wonder what your job in this forum is? To answer out of the blue without examining and asking for the clues? If that is your role, then please stay out my thread. I would like to speak with someone who knows what he speaks of. The Event viewer shows clearly the pattern, that in-between SAS Pro Errors, 3 BSODs occured. The Pattern. Do you understand that? I see it with my eyes. Further, the dump files show that clearly. Of course they are not the cause, directly. They were firing up the nvldddmkm.sys. Because SAS Pro 4.33.100 drivers are not fully x64 compatible. Of course there was a conflict in my system. It's what I said. And SAS Pro caused it. Please stay out of it. Stop trying defending something you don't know. It doesn't look serious on your behalf. Thank you. TrDo.
  10. Hi all, It's been along time since my last visit, and it was for the best of course, since I didn't face any serious issues while running my SAS Pro. Running SAS Pro for a couple of years now, in my Vista Home Premium x86, was a delight, since all things were going fine and well. I remember, first time I installed it, I had spoken to Nick , and we had made the adjustments to SAS first hand in order to be optimised. I have a lifetime subscription, and decided--didn't give it much thought really--, to keep SAS on my new laptop. This one came with Windows 7 x64 and since according to SAS Developers site: SUPERAntiSpyware.com software is compatible with 2000, XP Home/Professional, 2003, Server 2008, Vista and Windows 7. SUPERAntiSpyware will work in 32-bit mode under 64-bit versions of Windows. We will have native 64-bit drivers later this year. We offer an older version 4.24 that works with Windows 98, 98SE, and ME. Our software is not compatible with the Mac OS at this time , (reference:https://www.superantispyware.com/supportfaqdisplay.html?faq=6) I decided to install it in my new pc. Well, what a dump idea that was. Disaster struck three times in three days, with 3 respectives BSODs. At first of course, I could not make out what hit my new laptop. Event Viewer gave me the clues. After about 50-60 error messages(yes that's right) in 3 days, reporting that: "Application popup: : \??\C:\Program Files (x86)\SUPERAntiSpyware\SASKUTIL.sys failed to load, and at the same time messages like "\??\C:\Program Files(x86) \SUPERAntiSpyware\SASDIFSV.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.", or "Application popup: : \??\C:\Program Files (x86)\SUPERAntiSpyware\SASDIFSV.SYS failed to load", etc. or "\??\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", and somewhere in between, I had 3 instances of BSODs. Of course, as soon as I made the connection I unistalled SAS Pro, and since the day before yesterday all is quite. As it should be. It's a pitty really that the right and early warnings did not come from the SuperAntispyware site, and Nick himself, regarding compatibility issues of this serious nature. I'm not here to ask any kind of compensation other than the fact that I had the belief that Nick should have warned us about that. Us, I mean all users and most of all the faithful customers and supporters of this product. I hope they get their act together soon, because it's a pitty to ruin the reputation of the product for short term misguided insights. Thanks. TrDo.
×
×
  • Create New...