When Borland BGI drivers are made into object modules
(using BGIOBJ) and linked into a program, they write into their
own code area. The CS for this code does not match that of any
code segments in the .MAP file, so BOUNDS-CHECKER does not display
any module or procedure name.
Get the length of this module from the .MAP file, and
add an entry to the exception file similar to the following:
ACCESS _EGAVGA_driver len 1820H
_EGAVGA_driver len 1820H
In this example," _EGAVGA_driver" is the symbolic name of the
BGI driver linked in, and its length was 1820H. The entry allows it
to write into its own space.