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

 Overview of GPFs
------------------------------------------------------------------------------
 General protection faults (also known as general protection exceptions,
 GPEs, or general protection violations) occur in protected mode when the
 program code currently executing attempts to perform an invalid operation,
 access an invalid segment or access beyond the end of a valid segment. This
 section describes how to determine the exact cause of a GPF.

 It should be emphasised that these errors ARE NOT extender or linker errors,
 they are errors in the protected mode program, and the Blinker extender
 error handler is simply reporting as much information as it can in the GPF
 dump. In addition, the program code which was running when the GPF occurred
 is not necessarily the code responsible for the error, since GPFs can result
 from bad information being passed to good code.

 As a result, before providing technical support for a GPF, we require all
 the results of analysing, isolating and reproducing the GPF as described in
 the following section. Technical support for a GPF CANNOT and WILL NOT be
 provided on the basis of just the GPF dump, it requires ALL the information
 listed in the section below entitled `Reporting a GPF to technical support'.

 GPF dumps are written to standard output, so by default they are displayed
 on the screen. The GPF dump can be redirected to a file by using standard
 redirection on the program command line, e.g.

 TEST > TEST.GPF

 or, to keep a cumulative file of all the GPFs,

 TEST >> TEST.GPF