Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!bu-cs!bucsb.bu.edu!madd
From: madd@bucsb.bu.edu.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo troubles (color vs. monochrome)
Message-ID: <742@bucsb.bu.edu.UUCP>
Date: Sun, 15-Feb-87 12:50:58 EST
Article-I.D.: bucsb.742
Posted: Sun Feb 15 12:50:58 1987
Date-Received: Mon, 16-Feb-87 03:41:10 EST
References: <163@arcsun.UUCP>
Reply-To: madd@bucsb.bu.edu.UUCP (Jim "Jack" Frost)
Organization: ODO (Organization for the Disorganization of Organization)
Lines: 28
Keywords: are they incompatible?

In article <163@arcsun.UUCP> rob@arcsun.UUCP (Rob Aitken) writes:
>Why is it that when I compile a program on an AT with a color monitor
>then try to run it on another AT with a monochrome monitor the program
>doesn't work? The reverse case also does not work.

Very simple.  There are three compiler modes that you could set when you
install the Turbo programs (with TINST).  They are:

	* Color
	* Monochrome
	* Default

If you use multiple boards in the same machine, you might need to set
color or monochrome mode to suit.  For most uses, however, you want
default mode.  This means that Turbo checks to see what type you are
using and then uses that one.  This should fix your problem.

Note that changing the diplay page from 0 causes turbo to become confused.
This is almost never a problem.

>Rob Aitken

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
                   - Jim Frost * The Madd Hacker -
UUCP:  ..!harvard!bu-cs!bucsb!madd | ARPANET: madd@bucsb.bu.edu
CSNET: madd%bucsb@bu-cs            | BITNET:  cscc71c@bostonu
-------------------------------+---+------------------------------------
"Oh beer, oh beer." -- Me      |      [=(BEER) <- Bud the Beer (cheers!)