Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!hao!hplabs!hpda!hpisoa2!hpitg!drivax!alexande@drivax
From: alexande@drivax
Newsgroups: net.micro.pc
Subject: Re: MS DOS crashes on random keyboar
Message-ID: <473@drivax>
Date: Tue, 29-Apr-86 22:06:00 EDT
Article-I.D.: drivax.473
Posted: Tue Apr 29 22:06:00 1986
Date-Received: Wed, 14-May-86 20:16:28 EDT
Lines: 31

Subject: Re: MS DOS crashes on random keyboard in

In article <23900016@siemens.UUCP> jrv@siemens.UUCP writes:
>One very frustrating way to hang the system is to accidently request
>a screen dump or logging of output to the printer when there is no
>printer connected to the system. Control or Alt print-screen will do
>this. One way to prevent stop the ystem form hanging is to map the print
>screen interrupt, interrupt 5, to a do nothing routine or a routine 
>which will test for presence of the printer before continuing.

If you have a printer port but no printer, use a paper clip
to connect pins 11 and 23 on the port.  This connects the BUSY* input
to ground, so attempts to use the printer will not hang the system.
I did this after my toddler son banged on the PrtSc key a few too
many times.  Here's how the port looks (* indicates the pins that
should be connected):

      13			 1
	o o * o o o o o o o o o o 
	 o o * o o o o o o o o o
       25			14

--
#include "disclaimer.h"
#include "quote.h"
-- Mark Alexander   {ihnp4,mot,ucscc,ucbvax!hplabs!amdahl} !drivax!alexande
-- 
--
#include "disclaimer.h"
#include "quote.h"
-- Mark Alexander   {ihnp4,mot,ucscc,ucbvax!hplabs!amdahl} !drivax!alexande