LC.YRS@forsythe.stanford.edu (Richard Stanton) (02/06/90)
As a followup to my previous posting, it looks like 4DOS will not let you ^C out of AUTOEXEC.BAT. It works OK in most batch files, but when I have tried to get out of AUTOEXEC, the ^C appears on the screen, the current command is interrupted, but it just goes on to the next, rather than asking if I want to terminate batch job (y/n). Anyway, these all seem pretty minor gripes about a program that has a huge amount going for it. Richard Stanton
meyer@suna5.cs.uiuc.edu (02/09/90)
>As a followup to my previous posting, it looks like 4DOS will not >let you ^C out of AUTOEXEC.BAT. It works OK in most batch files, >but when I have tried to get out of AUTOEXEC, the ^C appears on the >screen, the current command is interrupted, but it just goes on to >the next, rather than asking if I want to terminate batch job (y/n). This is not just a 4dos problem. I also have had it happen in DOS - what I think is happening is that whatever program is interrupted by ^C clears the break when exiting. I usually have to press ^C several times in order to catch the batch file and not an executing program. (I'm using DOS 3.3) _____ Don Meyer internet: dlmeyer@uiuc.edu quote du jour: "If, indeed, there exists Artificial Intelligence, then there must also exist Artificial Stupidity" - ???
austin@bucsf.bu.edu (Austin H. Ziegler, III) (02/09/90)
>>>>> On 8 Feb 90 17:39:59 GMT, meyer@suna5.cs.uiuc.edu said: [^C doesn't exit AUTOEXEC.BAT in 4DOS...] meyer> This is not just a 4dos problem. I also have had it happen in DOS - meyer> what I think is happening is that whatever program is interrupted by meyer> ^C clears the break when exiting. I usually have to press ^C meyer> several times in order to catch the batch file and not an executing meyer> program. (I'm using DOS 3.3) Check your CONFIG.SYS file for a line that says BREAK = OFF, and that should tell you weather you can break *.BAT easily. Because BREAK is OFF, MS-DOS will not allow you to interrupt disk i/o operations, which is primarily what a batch file is. This isn't guaranteed correct, it just seems right. -- +--------------------------------------------------------------------------+ | The surgeon general of the United States of America has determined that | | reading USENET turns your brain to jelly, leaving nothing to claim or to | | disclaim. +--------------------------------------------------------------+ +-----------+ Austin Ziegler austin@bucsf.bu.edu or austin@buengf.bu.edu | | 700 Commonwealth Box 2094, Boston, Massachusetts 02215 BUENG '93 | +--------------------------------------------------------------------------+
meyer@suna5.cs.uiuc.edu (02/10/90)
> Check your CONFIG.SYS file for a line that says BREAK = OFF, and >that should tell you weather you can break *.BAT easily. Because BREAK is >OFF, MS-DOS will not allow you to interrupt disk i/o operations, which is >primarily what a batch file is. There is no "BREAK=OFF" line in my config.sys. However, the default value for BREAK when not specified is OFF. Maybe this is the problem with 4DOS as well? _____ Don Meyer Internet: dlmeyer@uiuc.edu disclaimer: How could UIUC policy possibly agree with me? I'm too sane. quote du jour: "If, indeed, there exists Artificial Intelligence, then there must also exist Artificial Stupidity"