🚀 go-pugleaf

DOS 3.2 hangs with a "fatal system error" or something like that, when
it gets enough control-C or any other interrupts. (I posted an extract
from an article in PC WEEK (april) about this before)   The problem is
that 3.2 will no longer recognize more than a certain number of 
interrupts without specifically being told to. I believe (if I recall
correctly) that the default value is 9, or something equally absurd. 
This is a particularly nasty design error, since it will only cause your
system to crash when you're doing something **interesting** and fun.
There is a crufto fix IBM proposed. I forget the exact syntax, but there
is another of those semi-documented parts in the dos manual that tells
you you can set the number of interrupts yourself in your config.sys 
file. Try grubbing through the manual or tech ref, or better, get hold
of the PC WEEK article. 
	I'm sorry I've forgotten the facts on this, but I hope this has
shed some light. I was so disgusted by the whole thing I degenerated my
system to 3.1 again. Only IBM would think they could get away with such
a stupid blunder. (anyone else would be out of business) Not only does 
3.2 blow up every so often, but as far as I can tell it offers a whole
mess of services that are only useful to networked ATs (someone please
flame me if I'm wrong) :-)  and the new version is slower and more RAM
hogging than 3.1 (which was more RAM hogging that ..., etc...)  Unless
you plan to hook nifty toys to your AT it might be a good idea to sit
back and wait for the next version...   *sigh*... 

-- 

*All opinions expressed aren't even mine, let alone those of Gould, Inc.*