Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!seismo!lll-crg!styx!nike!ucbcad!pavepaws!chapman
From: chapman@pavepaws.berkeley.edu (Brent Chapman)
Newsgroups: net.micro.pc
Subject: Help!  PC-DOS 3.2 hangs following ^C interrupts
Message-ID: <661@ucbcad.BERKELEY.EDU>
Date: Mon, 16-Jun-86 18:42:01 EDT
Article-I.D.: ucbcad.661
Posted: Mon Jun 16 18:42:01 1986
Date-Received: Wed, 18-Jun-86 03:42:14 EDT
Sender: news@ucbcad.BERKELEY.EDU
Reply-To: chapman@pavepaws.UUCP (Brent Chapman)
Organization: UNIXversity of California, Berkeley
Lines: 26

I upgraded to PC-DOS 3.2 about a week ago.  I'm having a major problem,
however.  If I stop a program with a ^C, everything appears fine, but
there is about a 75% chance that sometime during the execution of
the next two or three commands, the whole system will simply hang.  No
garbage, no error messages, no beeps, no NOTHING.  Just dead.  It has to
be power-cycled to restart it.  That is a pain, even on an AT.  I won't
even THINK about installing it on our PC while it's doing that.

I need some help.  Has anyone else encountered this?  Are there any fixes?
I've already reallocated 'STACKS' in my config.sys, but that doesn't seem
to have any effect.  I know there was some discussion on this a month or
so ago, but I went on vacation just as things were getting warmed up, and
the articles had all expired by the time I got back.


Thanks!

Brent

--

Brent Chapman
chapman@pavepaws.berkeley.edu
ucbvax!pavepaws!chapman

TANSTAAFL!  (There Ain't No Such Thing As A Free Lunch!)