🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.msdos.programmer
Article #987

Intercepting DOS messages...

#987
From: Brad S. Choate
Date: Wed, 26 Aug 1992 23:00
17 lines
1147 bytes
I'm needing some information/code samples on how to intercept any one of
the DOS error messages (i.e. "Bad command or file name").  Is there some
vector I can hook to for catching these things?  Or would I have to
physically change the system files to print my own messages?

 Suggestions/help anyone?
Please e-mail to   choate@acs.harding.edu

Thanks!
I'll post a summary.
--
 Disclaimer: "I really don't care."

 |) |) /\ |\  | Brad S. Choate                      | 1314 E. Market, Apt. 6
 |) |\ || |/  |                                     | Searcy, AR  72143
 --------_--  | choate@acs.harding.edu              | (501) 279-2584
  <||()/\|[   | V.P., Software Extensions, Inc.
Technical Details
Message-ID: <1992Aug26.180005.610@ualr.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!engr.uark.edu!mbox.ualr.edu!acs.harding.edu!CHOATE

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!engr.uark.edu!mbox.ualr.edu!acs.harding.edu!CHOATE
Newsgroups: comp.os.msdos.programmer
Subject: Intercepting DOS messages...
Message-ID: <1992Aug26.180005.610@ualr.edu>
From: choate@acs.harding.edu (Brad S. Choate)
Date: 26 Aug 92 18:00:04 -0500
Reply-To: choate@acs.harding.edu
Organization: Harding University
Nntp-Posting-Host: acs.harding.edu
Lines: 17