Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Blinker 5.10 Online Reference - <b> the blinker error handler</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 The Blinker error handler
------------------------------------------------------------------------------
 The Blinker error handler is a small routine called by the kernel in the
 event of a runtime error, or the expiration of a demonstration limit, in a
 DOS or DOS extended program.
 Blinker automatically links the appropriate error handler into DOS and DOS
 extended programs, and unless you modify it, there is no reason to
 explicitly link it into your program.

 The default behaviour of the error handler is to display the Blinker error
 number for the error which has occurred, with a descriptive message
 detailing the type of error. Following display of the error message, the
 overlay manager will terminate the program, and return to DOS.
 The code of the Blinker error handler is included in the BASIC, C, Pascal,
 and CA-Clipper subdirectories of the Blinker directory, should you wish to
 make modifications for your own purposes.

 Modifying the error handler

 The error handler may be modified to suit your individual requirements.
 However, care should be taken in handling Blinker errors 1201, (cannot find
 overlay file) and 1202 (error reading overlay file), as you will not be able
 to make any overlaid function calls in these particular cases.

 Once you have modified and recompiled the error handler, it should be
 specified in the link script as a FILE in the root section. For reliable
 operation, the Blinker error handler should not be overlaid, since an error
 which prevents the overlay manager from loading overlays will prevent the
 loading of the error handler, and the reporting of the error condition.

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson