🚀 go-pugleaf

Hi!

I have written a critical error handler in MS C 5.1. It is a simple handler,
designed to catch interrupts on interrup no 24h (I think - sorry I'm working
from memory and not in my office). All it does is catches the error, prints
on a diagnostic, sets a flag and returns. The flag is examined in other
parts of the program.

It works with no problems for errors where the floppy drive door is left
open etc., but I can still generate this message:

Printer error !
Abort, Retry?

My question is where does the message come from, I'm catching all the errors
from the critical error handler, where is this one coming from ?

I'm using a IBM clone 386, MS-DOS 3.2, Pheonix bios, Epsom dot-matrix
printer that is connected to the machine, but not switched on for the
purpose of testing. There is no printer driver installed either.

Can anybody help !! I've been through Ralf Browns interrupt listing for the
PC and can't find any mention of it. I'm stumped.

Thanks in advance.

--
|Michael A. Green.              |JANET:  mike@uk.ac.keele.cs                |
|Department of Computer Science |BITNET: mike%cs.kl.ac.uk@ukacrl            |
|University of Keele, Keele,    |ARPANET:mike%cs.kl.ac.uk@nsfnet-relay.ac.uk|
|Staffordshire. ST5 5BG.   U.K. |VOICE:  +44 782 621111  ex. 3357/3347      |