tashi
Member of Team Spybot
I would not be surprised if that becomes a non-event once Vista rolls out to the public early 2007.
Announcing betas: TeaTimer / Updater / Vista integration
- Thread starter PepiMK
- Start date
@diverdan: Just received this from AVG:
The whole WSC details are under a NDA anyway, so I won't say anything further on the topic
Regarding Windows 95, 1.4 failed since Borland removed support for Windows 95 from its Developer Studio. I recently gave up on hoping they would adjust, and patched everything myself (the reason they removed support was really really silly: see the toolbar with the gradient on the white/blacklist window of the new TeaTimer? Just for the possibility of using this, they gave up 95 compatibility... we were able to work around that though, without even giving up the gradients on 98 and newer). And I think I tested the new TeaTimer myself on various Win95 virtual machines we have here to make sure all the patching works. Some people may laugh at making stuff backwards compatible to operating systems older than 10 years, but recently I actually even worked towards ReactOS and Wine compatibility as well.
@noel-pr7: are you using "schedules" and "Microsoft" in the same sentence?
The whole WSC details are under a NDA anyway, so I won't say anything further on the topic Regarding Windows 95, 1.4 failed since Borland removed support for Windows 95 from its Developer Studio. I recently gave up on hoping they would adjust, and patched everything myself (the reason they removed support was really really silly: see the toolbar with the gradient on the white/blacklist window of the new TeaTimer? Just for the possibility of using this, they gave up 95 compatibility... we were able to work around that though, without even giving up the gradients on 98 and newer). And I think I tested the new TeaTimer myself on various Win95 virtual machines we have here to make sure all the patching works. Some people may laugh at making stuff backwards compatible to operating systems older than 10 years, but recently I actually even worked towards ReactOS and Wine compatibility as well.
I too have AVG Antivirus 7.5 Free Edition installed on my WinXP SP2 computer and have no problems with the sbsdtools15beta.exe file. maybe diverdan downloaded the file from a bad web site. try getting it from the Spybot web site instead of a mirror site.
PepiMK, I did try out Teatimer 1.5 on an old Win95 SR2 computer at my next-door neighbor's house and it works.
what version of AVG Pro were you using, streetwolf?
I use AVG Free 7.5 and it didn't find anything wrong with it. AND I have the latest virus definition files for AVG Free installed. weird :scratch:
Last edited:
which version of AVG Free, wk357mag? version 7.1 or 7.5
I even installed AVG anti-spyware free edition (latest version & latest build) and it too found nothing wrong with the sbsdtools15beta.exe file.
note to diverdan and streetwolf: try downloading the sbsdtools15beta.exe file using Firefox or Seamonkey web browser instead of IE. do not use any third party download managers to get the file.
note to diverdan and streetwolf: try downloading the sbsdtools15beta.exe file using Firefox or Seamonkey web browser instead of IE. do not use any third party download managers to get the file.
Last edited:
md usa spybot fan
Spybot Advisor Team [Retired]
Last edited:
I have the 7.5 Free edition, which updates daily, so it had the latest files onboard at that time.
Hi all,
Randy ( rdsok ) Moderator from the AVG Free forum here...
I'd thought I'd clarify some issues concerning the AVG Pro detection that was mentioned. AVG Pro AntiVirus also detects adware and other potentially unwanted programs... AVG Free only detects standard ( if there is such a term today ) virus's, trojans and worms but not the others that Pro can detect. You should also note that Pro detected ( falsely in this case ) this as a Potentially Unwanted Program... not as a virus and there is a big difference as many here already know.
This is an important distinction that users really need to pay attention to with any protection program or they may be getting rid of a utility that they knowingly download and use for good reasons... a lot of good utils are detected by AV and AS programs just to alert the user to their presence and not to indicate that the program is malware of some sort. Commonly detected programs include network scanners, password retrieval utils and many others as well. So the point is... pay attention to what your software is really telling you about the items it is detecting and don't just blindly delete everything listed or you may loose something you don't want lost.
PS... just for good measure... I've tested with the AVG Free 7.1x and 7.5x as well as AVG Pro 7.5 versions against this and it still comes up as clean.. :bigthumb:
Randy ( rdsok ) Moderator from the AVG Free forum here...
I'd thought I'd clarify some issues concerning the AVG Pro detection that was mentioned. AVG Pro AntiVirus also detects adware and other potentially unwanted programs... AVG Free only detects standard ( if there is such a term today ) virus's, trojans and worms but not the others that Pro can detect. You should also note that Pro detected ( falsely in this case ) this as a Potentially Unwanted Program... not as a virus and there is a big difference as many here already know.
This is an important distinction that users really need to pay attention to with any protection program or they may be getting rid of a utility that they knowingly download and use for good reasons... a lot of good utils are detected by AV and AS programs just to alert the user to their presence and not to indicate that the program is malware of some sort. Commonly detected programs include network scanners, password retrieval utils and many others as well. So the point is... pay attention to what your software is really telling you about the items it is detecting and don't just blindly delete everything listed or you may loose something you don't want lost.
PS... just for good measure... I've tested with the AVG Free 7.1x and 7.5x as well as AVG Pro 7.5 versions against this and it still comes up as clean.. :bigthumb:
you bring up some really great points about avg pro vs. avg free and also anti-virus/anti-spyware programs.
great job on the quick response and modification of the definitions file. that's why i use avg pro. plus it gives me a warm and fuzzy feeling. :bighug:
Your welcome... but I don't work for Grisoft, but they do respond very quickly to issues like these.. The moderators on the AVG Free forum are all just AVG Free users that have voluteered their time to help the other users.
I installed this tools on Vista Rc1 Build 5600. Even though Teatimer and Sdhelper were all on, it still showed this:
If I attempt to click turn on, it will just launch Spybot S&d and the status will still remain turn off.
Also, the text in Vista security centre shows like that:
The text is missing an &.
I don't know if these problems are fixed in later builds of vista but they sure are a problem in RC1.
Shouldn't be a problem in RC2 (5744), I don't have a VM of RC1 any more to test it there (edit: wait, or maybe it still is, see below).
Btw: Spybot-S&D has absolutely no way of influencing Windows Defender, so that bug won't come from us.
The thing about the amp (&) is that Windows can use this characters as a sign that the next caption is a shortcut letter, thus the & would not be displayed, but the following letter underlined. In those cases, one has to use a double amp (&&) to tell it to display the actual letter. The problem here is something you can see in the other screenshot: in one place Windows is interpreting it as a shortcut, in the other as a letter. We can provide only one name - so it's a bug in WSC
Btw: Spybot-S&D has absolutely no way of influencing Windows Defender, so that bug won't come from us.
The thing about the amp (&) is that Windows can use this characters as a sign that the next caption is a shortcut letter, thus the & would not be displayed, but the following letter underlined. In those cases, one has to use a double amp (&&) to tell it to display the actual letter. The problem here is something you can see in the other screenshot: in one place Windows is interpreting it as a shortcut, in the other as a letter. We can provide only one name - so it's a bug in WSC
- Did you leave the checkboxes at the end of the setup on (Service Installation & Run service)?
- Could you check if the SDWinSec service is running?
(Start) > Control Panel > Administrative Tools > Computer Management > Services and Applications > Services > SBSD Security Center Service - I'm going to improve some of the updating for a second beta
<snip>
[/url]?
- Did you leave the checkboxes at the end of the setup on (Service Installation & Run service)?
- Could you check if the SDWinSec service is running?
(Start) > Control Panel > Administrative Tools > Computer Management > Services and Applications > Services > SBSD Security Center Service- I'm going to improve some of the updating for a second beta
1. Yes, I check both boxes at the end of the setup.
2. Yep, is turned on.
---------------------------------------------------------------------
Ones I installed it, Security centre started detecting that spybot is on.
When I turned off teatimer through the windows taskbar, it takes a while(10sec) before security centre realized that spybot is off.
Then, I attempted to turn it on through the security centre, it works like a charm, teatimer was instantly turn on and shown in the taskbar.
But one thing to note that if when turning off/on teatimer through WSC, it dosen't affect the settings located at Spybot-->Advance mode-->Tools-->Resident.
Cheers.
Last edited:
Ok, Microsoft apologizes for not finding the & bug in testing, won't even be ready for SP1, so we'll probably change the "&" to "and" to workaround their bug :laugh:
Regarding the settings: hmmm yes, that's right. Right now it's just a silly starter. Good point
Regarding the settings: hmmm yes, that's right. Right now it's just a silly starter. Good point
before this update ihave message box issues now i can see all text inside and all button well placed but, i have new issues based on teatimer advices
One reg modify box pop and ask me confirmation about the change of my home page (like before was www.google.com now is www.google.com\ the only change is "\") i push on allow after choose remember my decision.
teatimer start spamming message box (like a colum from the sistray to the top of desktop) taking about white list and my decision that allow modify of registry.
I am at work (windows 2000 professional edition)cannot do screeshot, the only way to shut up this colum of messages (same text in all boxes) is to close teatimer.exe process from taskmanager.
I like spybot i hope to see a fix:bigthumb:
One reg modify box pop and ask me confirmation about the change of my home page (like before was www.google.com now is www.google.com\ the only change is "\") i push on allow after choose remember my decision.
teatimer start spamming message box (like a colum from the sistray to the top of desktop) taking about white list and my decision that allow modify of registry.
I am at work (windows 2000 professional edition)cannot do screeshot, the only way to shut up this colum of messages (same text in all boxes) is to close teatimer.exe process from taskmanager.
I like spybot i hope to see a fix:bigthumb:
Last edited:
Could you take a look at C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\ ?
There should be a folder Snapshots (old TeaTimer) and Snapshots2 there. If you remove the second one, he'll redetect all current settings. Or maybe even better: remove the Excludes\RegKeyWhite.sbs file. Then, please try again.
There should be a folder Snapshots (old TeaTimer) and Snapshots2 there. If you remove the second one, he'll redetect all current settings. Or maybe even better: remove the Excludes\RegKeyWhite.sbs file. Then, please try again.