Hey Chris, and All, Chris Maunder wrote: This was posted last week (So that means I can point at you and go 'ha ha!'. Doh! :) "Where is the emoticons for smacking forehead?" Chris Maunder wrote: What's your new job? And is it still hot and sandy over there? is it ever HOT!!!, I tell you man last night it was 47 c, yes that was last NIGHT. I thought I would see more sand storms, but I guess you need a wind current for that :). I work in a medical city,My job is raising the awarness of networking and e-security amongst the medical and IT staff. Nothing, I did not learn at :rose: Dundas :cool: :rose: I will be making other presentations on e-security in other hospitals July . Chris Maunder wrote: I think the reason the infection risk is low is because the virus affects IE5.5 but the VS.NET install will upgrade IE to 6.0 Nimda is like a swiss army knife, it spread in several ways; client to client via email (this needs vulnerable with "Automatic Execution of Embedded MIME Types" problem.) client to client via open network shares , web server to client via browsing of compromised web sites , from client to web server via scanning for the back doors left behind by the "Code Red II" I am wondering if there is a way to get that genie out of the lamp. How would this be triggered if it is possible? cheers G. W. Alfadhly It is Illogical to define an inventor by his invention