🚀 go-pugleaf

In article <661@ucbcad.BERKELEY.EDU> chapman@pavepaws.UUCP (Brent Chapman) writes:
>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?
>
>
>Thanks!
>
>Brent
>
>--
>
>Brent Chapman
>chapman@pavepaws.berkeley.edu
>ucbvax!pavepaws!chapman
>
>TANSTAAFL!  (There Ain't No Such Thing As A Free Lunch!)

In one of the computer centers here there is an HP-VECTRA
running DOS 3.0 (plus HP Compatibility 1.0) and in DOS it will completely
lock up, as you described, if you hit ^C or CTRL-BREAK.
Sorry, I don't know why.  By the way, if you are running KERMIT
or some other program, you can ^C all you want, no problem.  Its
only in DOS that it screws up...  Actually I am surprised since
usually HP stuff that I've used has been pretty good.  Not
having ^C is a real pain, though.

-- 
Dan Green    ARPA:    hsgj%vax2.ccs.cornell.edu@cu-arpa.cs.cornell.edu
~~~~~~~~~    BITNET:  hsgj@cornella
             UUCP:    {decvax,ihnp4,allegra}!cornell!batcomputer!hsgj