Xref: utzoo comp.binaries.ibm.pc:115 comp.sys.ibm.pc:9603
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!mandrill!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.binaries.ibm.pc,comp.sys.ibm.pc
Subject: Re: PC Aquarium program
Summary: Are you sure it is a *write* to disk?
Message-ID: <850@neoucom.UUCP>
Date: 15 Dec 87 15:15:46 GMT
References: <1070@sjuvax.UUCP> <19637@amdahl.amdahl.com>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 19


<<<Aquarium tries to write to disk upon exit>>

Are you sure?  I'll bet that it is rloading the overlay portion of
COMMAND.COM when it exits.  If you run a big program that uses all
available memory, COMMAND.COM unloads itself.  Note that eventhough
you always are allocated the entire free memory pool when you run a
program, COMMAND.COM only reloads when the memory it is residing in
was actually used.

Here's a way to test.  Boot from a floppy.  Run aquarium from a
different floppy that does not have COMMAND.COM on it.  When
aquarium exits, see if the system prompts "INSERT DISK WITH
COMMAND.COM".

Naturally, one possibility is that the aquarium *is* a trojan.
The only way to be sure is to whip out DEBUG and pick it apart.

--Bill