RK> #1, Writing to executing executables is simple and is in fact done 
 RK>     quite often by shareware and some comercial applications.

You can not write to a running exe/dll (hence,  can not write to any vital
os/2 element).

 RK> #2, Protected mode means nothing to the virus programmer.

Explain -- protected mode prevents the virus from writing outside of its
memory space;  to say it means nothing is quite a claim.

 RK> #3, Even a DOS based program can read/write to HPFS drives under OS/2
 RK>     just as they do in DOS. NO VIRUS uses BIOS/DOS 
 RK> calls for reads and     writes. Such operations are 
 RK> performed at the port level which, as you
 RK>     apparently aren't aware, bypasses the operating system entirely.

buzzzt.  Wrong.  Just try running a dos program that goes after the disk
controller ports -- they are all virtualized and will deny all writes. A
native OS/2 device driver could do it,  but this would mean a very visible
"device=virus.sys" being added to your config.sys & a reboot.

 RK> #4, The OS/2 scanners that are available, DO NOT detect several virusi.
 RK>     One that I can demonstrate readily is the 
 RK> Frankenstien virus which I     have on a floppy. Not 
 RK> only do the OS/2 scanners not see it, but the DOS

But can this virus do any damage when run in a VDM?   I don't think so...


--- Maximus/2 2.01