1. A method of testing, in a computer network, potential malware, the method comprising the steps of: establishing at least one Virtual Machine on a first computer coupled to the computer network and operating suspected malware on the at least one Virtual Machine; coupling, at least one second computer to the computer network and the first computer such that image display data from the at least one Virtual Machine on the first computer is transmitted from the first computer to the at least one second computer for image display on the second computer; observing in the image display data from the at least one Virtual Machine on the first computer, from at least one second computer coupled to the computer network and the first computer, source code variables identifying attempts by the suspected malware operating on the at least one Virtual Machine to change Memory and Bridge configuration settings of the at least one Virtual Machine on the first computer to observe how the suspected malware hops memory to attempt access to a hard drive of a host operating system; and locking down flexible memory and partition space of RAM of the at least one Virtual Machine; to ensure that no shared memory or hard drive is accessed by the suspected malware running on the at least one Virtual Machine; wherein the step of locking down flexible memory and partition space of RAM of the at least one Virtual Machine comprises the steps of: modifying how the host operating system handles memory by lowering a sys control config file to ‘zero’ by setting the variable “vm.swappiness=zero” to instruct the host operating system not to swap processes out of RAM to hard disk; and setting a variable Vm.overcommit_memory=1 to disallow the host operating system from overcommitting memory that it currently has installed, as a backup to the process swap to keep the host operating system from swapping from RAM to disk and therefore potentially writing viruses to disk.