Article View: alt.msdos.programmer
Article #552Re: Propagating Device Driver error status into C runtime errno
From: Edward John Kalenda
Date: Wed, 22 Aug 1990 02:39
Date: Wed, 22 Aug 1990 02:39
16 lines
1190 bytes
1190 bytes
You also need to set bit 8 (DONE) in addition to bit 15 (ERROR) and the low nibble with the driver error code. Of the 16 codes available you must pick one that fits your error best. MS-DOS generates it's errors based on what you give it and what it thinks you mean. You must restore all registers to their original state. My experience has been that even the flags must be restored. Some versions of MS-DOS seem to be more sensative to the flags than others. Looking in the Encyclodedia, I find that you MUST restore the flags (wish I'd seen that when I wrote my first driver). If this, and the other postings, don't seem to help, e-mail your source and I'll see if I can see the problem. Ed ekalenda@cup.portal.com
Technical Details
Message-ID:
<33073@cup.portal.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!portal!cup.portal.com!ekalendaReferences:
<163@matrix.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!portal!cup.portal.com!ekalenda From: ekalenda@cup.portal.com (Edward John Kalenda) Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer Subject: Re: Propagating Device Driver error status into C runtime errno Message-ID: <33073@cup.portal.com> Date: 22 Aug 90 02:39:08 GMT References: <163@matrix.UUCP> Distribution: na Organization: The Portal System (TM) Lines: 16