msn payg and spyware detection

[terry]

has anybody got a fix for this: msn payg(freeweb service)
has updated its software if you intend to pay for just
the cost of the call this is the software you need BUT
when you come to "connect" after you install it spyware
detects koko trojan in ::c:/program files/msn.exe AND if
you click "IGNORE" the spyware stops theapplication AND
deletes the msn installation files the quwestion is
WHY?? any msn microsoft software should be 100 spyware
free yes? so why does its own software detect flaws/
spyware in its own software?? this is as interesting as
it gets
if you want to try it goto msn payg page install software
then try to connect anybody on dial up must be pulling
their hair out at this i know i would be

 

[Bill Sanderson]

There may be very few users of MSN here. Have you used the feedback options
within MSN to report this?

Do you have a URL for where to find this--I've never heard of the service
you are talking about.

 

[terry]

-----Original Message-----
There may be very few users of MSN here. Have you used the feedback options
within MSN to report this?

Do you have a URL for where to find this--I've never heard of the service
you are talking about.

--



sure bill, msn payg is the "old msn freeweb" service

where you only pay for te cost of the local call 1p off
peak 4p all other times it coes under "narrowband/dial up
access" through a modem the link is here
:http://join.msn.com/?pgmarket=en-gb&page=misc/narrowband
and it is specifically aimed at users who dont want a
monthly contract and who dont use the internet frequently

 

[Bill Sanderson]

Thanks--I'd never seen this--there's nothing similar available in the United
States.

This looks like something I may be able to test, when I get some time, which
won't be before Thursday or Friday, I think.

If I am able to test it and can replicate in some fashion your experience,
I'll make sure that it is brought to the attention of the development team.

It'd help if you could re-post your message, including the URL that you sent
me, in the appcompat group--that one is also relevant. I don't know the
details about how the Microsoft monitoring of these groups works, but having
the issue in that group may help get it fixed.

--