ms spyware beta

Toggle sidebar Toggle sidebar
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

marvellous programme. but spybot regularly finds something called DSO, which
alters five registry keys, which the spyware beta never notifies me about.
anyone know why not?

after being infected i cleaned out windows/system32/drivers/etc/hosts to
leave only local host 127.0.0.1 and then made the file read only and that
hasn' been touched since.

however i think autoexec.nt has been corrupted, any advice on restoration?
 
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

muffin from mars wrote:
> marvellous programme. but spybot regularly finds something called
> DSO, which alters five registry keys, which the spyware beta never
> notifies me about. anyone know why not?
>
> after being infected i cleaned out windows/system32/drivers/etc/hosts
> to leave only local host 127.0.0.1 and then made the file read only
> and that hasn' been touched since.
>
> however i think autoexec.nt has been corrupted, any advice on
> restoration?

False Positive. Known issue with Spybot Search and Destroy. Google search
will bring that fact up.

--
<- Shenan ->
--
The information is provided "as is", it is suggested you research for
yourself before you take any advice - you are the one ultimately
responsible for your actions/problems/solutions. Know what you are
getting into before you jump in with both feet.
 
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

One of the points where Microsoft AntiSpyware is better...no false positive
for DSO.
Do you have all the latest Windows XP Critical Updates?
Do you also have the latest version of SpyBot with latest updates?

Also, further questions should be directed to the Microsoft Antispyware
newsgroups:
http://communities.microsoft.com/newsgroups/default.asp?ICP=spyware&sLCID=us

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
In memory of our dear friend, MVP Alex Nichol
http://www.dts-l.org


"muffin from mars" <muffinfrommars@discussions.microsoft.com> wrote in
message news:25DB2D7F-87C1-4F42-976D-F568361DA351@microsoft.com...
> marvellous programme. but spybot regularly finds something called DSO,
> which
> alters five registry keys, which the spyware beta never notifies me about.
> anyone know why not?
>
> after being infected i cleaned out windows/system32/drivers/etc/hosts to
> leave only local host 127.0.0.1 and then made the file read only and that
> hasn' been touched since.
>
> however i think autoexec.nt has been corrupted, any advice on restoration?
 
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

Because it's not a problem. SpyBot is giving you a false positive.


--
Regards,

Richard Urban

aka Crusty (-: Old B@stard 🙂

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!


"muffin from mars" <muffinfrommars@discussions.microsoft.com> wrote in
message news:25DB2D7F-87C1-4F42-976D-F568361DA351@microsoft.com...
> marvellous programme. but spybot regularly finds something called DSO,
> which
> alters five registry keys, which the spyware beta never notifies me about.
> anyone know why not?
>
> after being infected i cleaned out windows/system32/drivers/etc/hosts to
> leave only local host 127.0.0.1 and then made the file read only and that
> hasn' been touched since.
>
> however i think autoexec.nt has been corrupted, any advice on restoration?
 
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

In news:25DB2D7F-87C1-4F42-976D-F568361DA351@microsoft.com,
muffin from mars <muffinfrommars@discussions.microsoft.com> had this to say:

My reply is at the bottom of your sent message:

> marvellous programme. but spybot regularly finds something called
> DSO, which alters five registry keys, which the spyware beta never
> notifies me about. anyone know why not?
>
> after being infected i cleaned out windows/system32/drivers/etc/hosts
> to leave only local host 127.0.0.1 and then made the file read only
> and that hasn' been touched since.
>
> however i think autoexec.nt has been corrupted, any advice on
> restoration?

For your autexec.nt perhaps:

Error message when you start a DOS or 16 bit Program:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

For the rest, as told, use the beta newsgroups.

Galen
--
Signature changed for a moment of silence.
Rest well Alex and we'll see you on the other side.
 
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

As others have stated, SpyBot reports a false positive for DSO. You can set
SpyBot to ignore DSO in it's advanced mode settings.

--
Curt,
'The way is open to those who would see'


"muffin from mars" <muffinfrommars@discussions.microsoft.com> wrote in
message news:25DB2D7F-87C1-4F42-976D-F568361DA351@microsoft.com...
> marvellous programme. but spybot regularly finds something called DSO,
> which
> alters five registry keys, which the spyware beta never notifies me about.
> anyone know why not?
>
> after being infected i cleaned out windows/system32/drivers/etc/hosts to
> leave only local host 127.0.0.1 and then made the file read only and that
> hasn' been touched since.
>
> however i think autoexec.nt has been corrupted, any advice on restoration?
 
Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

"muffin from mars" wrote:

> marvellous programme. but spybot regularly finds something called DSO, which
> alters five registry keys, which the spyware beta never notifies me about.
> anyone know why not?
>
> after being infected i cleaned out windows/system32/drivers/etc/hosts to
> leave only local host 127.0.0.1 and then made the file read only and that
> hasn' been touched since.
>
> however i think autoexec.nt has been corrupted, any advice on restoration?


thanks for adive
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom