Path: utzoo!utgpu!attcan!uunet!husc6!rutgers!gatech!linus!mbunix!jcmorris
From: jcmorris@mitre-bedford.ARPA (Joseph C. Morris)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: FILECRC -- File comparison Programs Part 1 of 2
Message-ID: <38472@linus.UUCP>
Date: 11 Aug 88 13:21:48 GMT
References: <3606@bsu-cs.UUCP>
Sender: news@linus.UUCP
Reply-To: jcmorris@mbunix (Morris)
Organization: The MITRE Corporation, McLean, VA.
Lines: 20

In article <3606@bsu-cs.UUCP> ncsugn!emigh@mcnc.mcnc.org (Ted H. Emigh) writes:
>
>     FILECRC is a program to help detect when files have been
>corrupted.  FILECRC creates a list of all the files on the
[mucho deleted including the uuencoded binary]

There's something in this code (possibly from T-Pascal routines) which is
clobbering the display.  Running on either an old PC-1 with an IBM ega or
an AT with a Vega board, I get a green screen with severe sync problems.  On
a PS2/50 I get a low-contrast black on gray; on a Compaq 386 I get normal
operation.  On all but the Compaq the program exhibits uncivilized behavior
by leaving the screen in mode 7; for some reason on the Compaq it properly
leaves the screen as it found it in mode 3.

The garbaged screen made me immediately suspect a trojan, but it is instead
apparently just an interface problem.  The program is one I need, but I
also need to be able to run it without losing the screen.  Any suggestions?

(BTW: once the program finishes, the screen can be restored to normal operation
by blindly issuing the MODE CO80 command and hoping it's in the search path.)