Path: utzoo!utgpu!watmath!clyde!att!ucbvax!hplabs!hp-pcd!hpcvlx!everett
From: everett@hpcvlx.HP.COM (Everett Kaser)
Newsgroups: comp.sys.ibm.pc
Subject: COMMAND.COM INT 2E
Message-ID: <101000022@hpcvlx.HP.COM>
Date: 10 Nov 88 17:44:52 GMT
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 16

Recently, there have been a few posts discussing the INT 2E entry point into
COMMAND.COM, for executing commands.  Rather coincidentally, I've been
working on a program that makes use of this entry.  However, I've encountered
a "gotcha" with it.  If the command that is being executed is a .BAT file,
and during the execution of it, the user presses ^C,  the execution of the
.BAT file terminates, but the next time you try to execute a command via
INT 2E, the batch file resumes where it left off.  When the batch file
finishes, then the new command is executed.  I tried saving the ^C interrupt
vector (INT 23), setting it to the saved ^C vector from my PSP (offset 0eh),
calling INT 2E, then restoring the ^C vector.  That didn't make any noticeable
difference.

Any thoughts, anyone?

Everett Kaser
!hplabs!hp-pcd!everett