Ken Hrynchuk wrote the following to Charles Jennings, and I quote (in part):

 AZ>> 1) Make sure the [x] Close  on Exit option is checked (Program tab
 AZ>> of the Pif's Properties dialogue)
 KH>  
 AZ>> 2) Make sure the last line of the Batch file reads:
 KH>  
 AZ>> Exit

   Yep.  I tried those but they don't work for me.  On my Win95
system it acts just like the PAUSE command except it only accepts
Ctrl-C.

   Sometimes on non closing bats a CLS is enough to close it.  But
on this one, no Ctrl-C no go.

 KH> It's an intermittent quirk, that I wish I could prevent. It almost 
 KH> looks like Windows thinks that COMMAND.COM has gone resident, at 
 KH> times (?). 

    Well, since I found the work-around I haven't done much
investigating.  Isn't COMMAND.COM resident anytime you are in a
batch file?

 CJ>> kpush 3 CR 3
 KH>  
 CJ>>    I like kpush because it is not a TSR.  You will find it in
 CJ>> HORST32.ZIP available at http://home.mnet-online.de/horst.muc.
 KH>  
 KH> Well, why didn't I think of that (actually I did, but dismissed the
 KH> idea, because I didn't think a DOS key-pusher would work)!
 KH>  
 KH> Thanks, Charles; I'll grab the above. It would be nice if we didn't 
 KH> have to resort to such tactics, though.

   Yep, that would be nice.  That is my biggest complaint about
windows.  You never know what in the hell it is doing.  A little
disconcerting for an ole DOS guy ;-).

   As it sounds like the same problem I assume it will work for you
also.

    Good luck, 
      Charles

... *SYSTEM ERROR* - Place sacrifice at keyboard to continue.
--- Via Silver Xpress V4.5/P [Reg]