Xref: utzoo comp.lang.c:12581 comp.sys.ibm.pc:19094
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: PC DOS "Bad command or file name" interrupt wanted
Summary: no such thing
Message-ID: <3941@bsu-cs.UUCP>
Date: 14 Sep 88 03:16:37 GMT
References: <1988Sep12.202413.23423@gpu.utcs.toronto.edu>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Followup-To: comp.sys.ibm.pc
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 15

In article <1988Sep12.202413.23423@gpu.utcs.toronto.edu> sarathy@gpu.utcs.UUCP
(Rajiv Sarathy) writes:
>I want DOS to jump to my memory-resident-program instead of printing
>"Bad command or file name" whenever appropriate.

Nitpicking:  You can't make MS-DOS jump.

Answer:  The "Bad command..." error message comes from the MS-DOS
command interpreter which lies in the file "command.com".  I greatly
doubt that you can make "command.com" transfer control to a
memory-resident program when it sees an invalid command.

Follow-ups to to comp.sys.ibm.pc, please.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi