About MrGPF
 A .GPF Map file scanner for MrDebug
──────────────────────────────────────────────────────────────────────────────

 MrGPF is a Map file Scanner which has been designed to work specifically
 with output from MrDebug. Of course, MrDebug doesn't have to be linked in to
 an application to use MrGPF. MrGPF will also work with screen output from
 either Blinker or Causeway.

 When used with Exospace, MrGPF will only work correctly if you are using
 VCPI or XMS, without a DPMI interface. Because Exospace does not have a DPMI
 simulator incorrect results may arise.

 When used with MrDebug, it is probably a good idea to understand what
 MrDebug does when an application linked with MrDebug falls over with a GPF.

 MrDebug intercepts the GPF and captures the details of the GPF and
 immediately logs the GPF details to a file <EXE name> + ".GPF" (just in case
 something unexpected happens, like a second GPF!)

 MrGPF saves the current screen and searches the current directory for any
 .GP? files. MrDebug will collect these and sort them into ascending order
 based on the date and time stamps of the files.

 MrGPF will then display the information pertaining to each of the GPFs to
 the screen with the oldest first and the most recent GPF last, followed by
 the screen GPF.

 This means that the most recent GPF's will always be at the bottom of the
 list

 When MrGPF is called, MrGPF scans the MrGPF.DAT file to see if the segment
 and/or the function are know already. If they are then an explanation can be
 read from the .DAT file. You can add your own GPF information to the .DAT
 file. See the section on Adding to MrGPF.DAT file.