Click above to get retro games delivered to your door ever month!

 Internal and external overlays
------------------------------------------------------------------------------
 There are two methods of storing overlays in a program: internally and
 externally. By default Blinker will create an internal overlay, storing the
 overlays within the .EXE file to create one large .EXE file.

 Alternatively, all the overlays can be put into one or more separate overlay
 files, which are external to the .EXE and have a default extension of .OVL.
 These external overlays are created by using one or more SECTION INTO
 commands, with each external overlay file requiring its own file handle at
 run time. This feature is generally used to simplify distribution since it
 allows the developer to deliver the executable part of a program on several
 diskettes.

 Fortunately, the Blinker user does not have to manage the organization of
 these overlays; it is all handled at runtime by the overlay manager. The
 overlay manager is automatically linked into a program containing overlays.
 To set up an overlaid program for Blinker, the developer need only specify
 what is to be overlaid and whether the code is in an object module or a
 library.