Hello Frederic , Sorry to bother you about this if you would please read this link whenever you have some free time:-> http://www.wilderssecurity.com/showthread.php?t=70591 And the person who started the thread,his name is tinker,and just brought up a good question(reason Tinker would not buy LnS because of this problem which he claims Look"n"Stop is effected also?."that he read somewhere about this Trojan and LnS is unable to stop it"said Tinker",but he never got back to me on that link. (Quote by tinker)"LnS coz some site claimed bugs in it's version due to no protection from trojan with firewlal bypassing technology that uses api hooking / and injecthig RAT [trojan] dll to trusted app memory space".End Quote)Please read the link to get a better understanding if you like. Can you please tell me more about this Trojan and why it can't stop it,if Tinker is correct?Is it a Windows flaw?Or is it a general problem with most firewalls on the market today?Or would a Real-Time Trojan protector,registry Watcher for dill's stop this dill?,or Can LnS do it all by itself with it's on dill checking on Xp LnS users only? Thank you Frederic for your time.