Hi CHRIS!
Answering a message from CHRIS THURTELL to RICK COLLINS:
 CT>  -=> Quoting Rick Collins to John Kismul <=-
 CT>  Fuk you're nice dude.
Oh, what kind of friendly speaking while just entering a thread.....
 RC>> How many times and how many ways do you have to be told that
 RC>> "reading" a disk and "writing" to a disk will _not_ cause an
 RC>> infection?  How many times will you have to be told that, to get
 RC>> infected, you have to _execute_ the software that causes the
 RC>> infection?
 RC>> Not reading an infected disk.  Not writing to a disk with an infected
 RC>> boot sector.
 CT> Looks like you don't know everything. Wot happens if the virus is in  
 CT> memory and you read a disk? 
First of all: seems there are some more people out there who don't know 
evrything. As far as I know, Rick is one of last in the echo who needs 
instructions about the difference between "reading or writing an infected 
disk" and "reading or writing an infected disk *while a virus is active in 
memory*". 
BTW: Ricks statement "How many times [..] do you have to be told ..." exactly 
pointed out to the tremendeous number of mails (not only written by Rick) 
trying John to explain *that* difference.
 CT> i have seen a virus LOOK for *.exe *.com  
 CT> when a disk is read to infect. 
Maybe you'll be surprised but - you're not the _only_ one ;-).
 CT> Its not hard to code. Virus's can
 CT> spawn to other executables and run from there.
I know. Especially if a virus-scanner doesn't check his own integrity before 
starting up cleaning.
Greetings from Wiesmoor (Germany)
Klaus
--- FleetStreet 1.18+
---------------