Path: utzoo!attcan!uunet!husc6!mailrus!cornell!batcomputer!itsgw!rpi!pawl17.pawl.rpi.edu!fargo
From: fargo@pawl.rpi.edu (Ethan M. Young)
Newsgroups: comp.lang.pascal
Subject: Re: What's going on?
Message-ID: <274@rpi.edu>
Date: 23 Jan 89 04:21:51 GMT
References: <1822@maccs.McMaster.CA>
Sender: usenet@rpi.edu
Distribution: na
Organization: Rensselaer Polytechnic Institute, Troy, NY
Lines: 16

[In reference to article about direct and indirect screen writes in the same
 program.]

I'm not sure about TP5.0, but I know that TP4.0, when compiling programs,
compiles your program to use all screen writes.  So, using indirect screen
writes is impossible in TP4.0 unless you have the line "USES crt;" at the top
of your program, and then add the line "DirectVideo := FALSE" somewhere in
your initialization code.  Also-as a small aside-normally using BIOS calls and
direct hardware modification in the same program may cause odd quirks.  I
suggest that you either use all direct screen writes, all BIOS calls, or
find a way to use one or the other (based on asking the user, looking at
equipment, etc.) but not both.

Thank you and happy hunting!     Internet: fargo@pawl.rpi.edu                       ____    [> SB <]                       fargo@{paraguay|uruguay}.acm.rpi.edo
   /__      -=>??<=-          Bitnet (??): usergac0@rpitsmts.bitnet
  /   ARGO : 3000 years of regression from the year 4990