Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!apple!mips!pacbell.com!pacbell!att!mcdchg!laidbak!obdient!vpnet!cak
From: cak@vpnet.chi.il.us (Cindi Knox)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: DOS Batch Programming
Keywords: DOS Batch DELETE
Message-ID: <268abc49-d6.10comp.sys.ibm.pc.programmer-1@vpnet.chi.il.us>
Date: 29 Jun 90 05:55:04 GMT
References: <1990Jun24.043414.24256@caen.engin.umich.edu> <3868@optilink.UUCP>
Lines: 27


the reason ^Break won't work when you 

y|del *.*

is that break checking is normally done only on console calls: i.e. screen
writes and keyboard reads. So the command y (which doesn't exist) opens
a pipe to del's input, the input ends, del is not satisfied and waits in
a loop of calls to DISK I/O! No break checking here. To get DOS to do
more break checking (at the penalty of some processing speed... nothing
drastic) put 

BREAK = ON

in your config.sys or type

BREAK ON

This gives you break checking within ALL DOS function calls. This still
doesn't help if you're stuck in a non-function calling loop though it WILL
fix the hang/can't break problem in y|del *.*

             I doubt any of these opinions are those of my employer.
                   I don't agree with ANYTHING they say.

Cindi Knox          | You've got a lot of living to do without life.
                    | 
cak@vpnet.chi.il.us | ``Little Miss S.'' by  Edie Brickell and New Bohemians.