![]() |
![]() |
Articles / TULARC / Security / Computer Viruses / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
61 Under OS/2 2.0+, could a virus infected DOS session infect another DOS session? |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
|
|
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
This article is from the Computer Viruses FAQ, by Nick FitzGerald n.fitzgerald@csc.canterbury.ac.nz with numerous contributions by others.
Each DOS program is run in a separate Virtual DOS Machine (their memory
spaces are kept separate by OS/2). However, any DOS program has almost
complete access to the files and disks, so infection can occur if the
virus infects files; any other DOS session that executes a program
infected by a virus that makes itself memory resident would itself
become infected.
Also, bear in mind that generally all DOS sessions share the same copy
of the command interpreter. Hence if *it* becomes infected, the virus
will be active in *all* DOS sessions.
 
Continue to:
security, computer viruses, software, vendors, protection, infection, bomb, trojan, anti-virus, commercial, removal, false positive, BIOS, diagnostic
![]() |
|
|