Uninstall old spybot before download 1.3?

Topic

New Reply

I want to install the new version of Spybot 1.3 Will this download over my current version (1.2) or should I uninstall version 1.2 first and then download the new version. Thanks in advance.

Reply | Quote

Replies

Hi Jeff,
I’ve recently installed S&D 1.3 and it appears to overwrite the previous version with no problems.

Reply | Quote

Hi Jeff,
I’ve recently installed S&D 1.3 and it appears to overwrite the previous version with no problems.

Reply | Quote

I’ve always been one to remove an older version before installing a new one, but it’s personal preference. I just feel better that way.

Reply | Quote

I uninstalled it. I do that as general practice when I moved to new software versions.

Reply | Quote

I uninstalled it. I do that as general practice when I moved to new software versions.

Reply | Quote

You can install 1.3 over the old version but as others have said, it’s a good practice to uninstall the old first.
I think the exception might be if you wanted to retain custom settings and configurations.

Reply | Quote

That’s a good point, but sometimes the settings and configurations are significantly different in the new version and will require some changes anyway. That depends, of course, on how comprehensive the new version of the software is. It’s always advisable to check out what changes have been made. Often, they’re relatively minor, but sometimes not.

Reply | Quote

That’s a good point, but sometimes the settings and configurations are significantly different in the new version and will require some changes anyway. That depends, of course, on how comprehensive the new version of the software is. It’s always advisable to check out what changes have been made. Often, they’re relatively minor, but sometimes not.

Reply | Quote

You can install 1.3 over the old version but as others have said, it’s a good practice to uninstall the old first.
I think the exception might be if you wanted to retain custom settings and configurations.

Reply | Quote

I’ve done both on various machines (i.e. uninstalled v1.2 first, and also installed 1.3 on top of 1.2) – no apparent problems with either!

The only thing I found is that once you’ve installed it without “Tea Timer” you don’t appear to be able to add TeaTimer later without another install. (TeaTimer seems to be a “startup locations monitor”, much like Mike Lin’s StartupMonitor, which I’ve used very happily for ages. About all I can say about it so far is that the TeaTimer service seems to use about 4% CPU on my very ancient 133 MHz NT4 box!)

John

Reply | Quote

To start/stop “Tea Timer”

1/ Run Spybot S&D in advanced mode
2/ Select Tools in left pane & then select Resident

Reply | Quote

To start/stop “Tea Timer”

1/ Run Spybot S&D in advanced mode
2/ Select Tools in left pane & then select Resident

Reply | Quote

Thanks, Tony, but I’m not sure what question you’re answering!

Are you saying that if I hadn’t selected Tea Timer at installation time, I can subsequently start it using the method you give, without having to install Spybot again?

John

Reply | Quote

When I installed Spybot I did not select “Tea Timer”. I subsequently started “Tea Timer” using this method without re-installing Spybot.

Reply | Quote

Tony

Thanks!

Shows again that I have no idea what I’m talking about!

John

Reply | Quote

Tony

Thanks!

Shows again that I have no idea what I’m talking about!

John

Reply | Quote

When I installed Spybot I did not select “Tea Timer”. I subsequently started “Tea Timer” using this method without re-installing Spybot.

Reply | Quote

Thanks, Tony, but I’m not sure what question you’re answering!

Are you saying that if I hadn’t selected Tea Timer at installation time, I can subsequently start it using the method you give, without having to install Spybot again?

John

Reply | Quote

Hi John & Tony:
I had no idea what “Tea Timer” was until I saw your posts. Actually, I still don’t know what it is. The only reference was that it protects “overall system settings”. Any idea what that is?
Thanks,

Reply | Quote

Phil

Look at the stuff in brackets in post 373837! I reveal all (well, some!)…

John

Reply | Quote

I saw that, John. But the description in Spybot seems to imply more. So, in other words, it prevents new applications from adding themselves to your startup registry keys unless you deliberately allow it? I haven’t used any startup monitors before…just msconfig to uncheck whatever I didn’t want to run.

Reply | Quote

Phil,
See the post John mentioned for a link to Mike Lin’s startup Monitor. I’ve used it for quite a while. I like being able to stop things from getting into my startup rather than figure out later that I don’t want it to start. Seems like everybody wants to ‘phone home’ these days to check for updates. I’d rather delude myself into thinking I’m in control.

Joe

--Joe

Reply | Quote

---

I’d rather delude myself into thinking I’m in control.

---

LOL! Perhaps the most profound & telling statement I’ve read, regarding computers, for a long time.

Alan

Reply | Quote

---

I’d rather delude myself into thinking I’m in control.

---

LOL! Perhaps the most profound & telling statement I’ve read, regarding computers, for a long time.

Alan

Reply | Quote

Phil,
See the post John mentioned for a link to Mike Lin’s startup Monitor. I’ve used it for quite a while. I like being able to stop things from getting into my startup rather than figure out later that I don’t want it to start. Seems like everybody wants to ‘phone home’ these days to check for updates. I’d rather delude myself into thinking I’m in control.

Joe

--Joe

Reply | Quote

Phil

Joe has explained it like it is! And it’s not just the RUN-type registry keys, but in Startup folders and the like. Basically, everywhere, scure and obscure, that something can run from at startup time!

John

Reply | Quote

Thanks to both of you. I cringe at the thought of installing yet another utility (time is so short ), but this does seem like a good one.

Reply | Quote

Thanks to both of you. I cringe at the thought of installing yet another utility (time is so short ), but this does seem like a good one.

Reply | Quote

Phil

Joe has explained it like it is! And it’s not just the RUN-type registry keys, but in Startup folders and the like. Basically, everywhere, scure and obscure, that something can run from at startup time!

John

Reply | Quote

I saw that, John. But the description in Spybot seems to imply more. So, in other words, it prevents new applications from adding themselves to your startup registry keys unless you deliberately allow it? I haven’t used any startup monitors before…just msconfig to uncheck whatever I didn’t want to run.

Reply | Quote

Phil

Look at the stuff in brackets in post 373837! I reveal all (well, some!)…

John

Reply | Quote

Phil

I posted the following in the Spybot S&D forum:

Has anyone done a comparison of the locations checked (registry values, startup folders, etc) by both Tea Timer and Mike Lin’s Startup Monitor?

On my ancient 133 MHz NT4 box, the resource usage of Tea Timer is orders of magnitude higher than for Startup Monitor.
Since the last reboot Task Manager shows:
Tea Timer: CPU time 9749 seconds (nearly 2

Reply | Quote

Yep! Think I’ll avoid Tea Timer. Thanks,

Reply | Quote

Yep! Think I’ll avoid Tea Timer. Thanks,

Reply | Quote

John,
Thanks for the comparison. I’ll definitely avoid Tea Timer until there is more information about it and/or something is done to reduce the overhead involved.

Joe

--Joe

Reply | Quote

John,
Thanks for the comparison. I’ll definitely avoid Tea Timer until there is more information about it and/or something is done to reduce the overhead involved.

Joe

--Joe

Reply | Quote

Phil

I posted the following in the Spybot S&D forum:

Has anyone done a comparison of the locations checked (registry values, startup folders, etc) by both Tea Timer and Mike Lin’s Startup Monitor?

On my ancient 133 MHz NT4 box, the resource usage of Tea Timer is orders of magnitude higher than for Startup Monitor.
Since the last reboot Task Manager shows:
Tea Timer: CPU time 9749 seconds (nearly 2

Reply | Quote

Hi John & Tony:
I had no idea what “Tea Timer” was until I saw your posts. Actually, I still don’t know what it is. The only reference was that it protects “overall system settings”. Any idea what that is?
Thanks,

Reply | Quote

I’ve done both on various machines (i.e. uninstalled v1.2 first, and also installed 1.3 on top of 1.2) – no apparent problems with either!

The only thing I found is that once you’ve installed it without “Tea Timer” you don’t appear to be able to add TeaTimer later without another install. (TeaTimer seems to be a “startup locations monitor”, much like Mike Lin’s StartupMonitor, which I’ve used very happily for ages. About all I can say about it so far is that the TeaTimer service seems to use about 4% CPU on my very ancient 133 MHz NT4 box!)

John

Reply | Quote