Category : Utilities for DOS and Windows Machines
Archive   : BREAK.ZIP
Filename : BRK.DOC

Output of file : BRK.DOC contained in archive : BREAK.ZIP
CTRL-BRK Control Programs - Version 1.0

Copyright 1985 by

Solid Systems
20 Dinwiddie Place
Newport News, VA. 23602

Neither Solid Systems, nor Everett C. Johnson, nor the SYSOP of any public BBS,
nor any other person handling or distributing this program free of charge makes
any warranty as to the fitness of these programs or this documentation for any
purpose. The user of these programs accepts total responsibility for their use
and for any results of using them.

Any person is free to copy and or distribute these programs and documentation
as long as no fee is charged for doing so.

--- +++ ---

The programs BRK.DRV and BRK.COM provide the user with the ability to decide if
and when keyboard break is operative, or ignored. (For the purposes of this
document, "keyboard break" is defined to be the abnormat termination of a
process by pressing either the Ctrl-Break or the Ctrl-C key combinations.) The
user can cause the system to boot with keyboard break disabled thus preventing
his AUTOEXEC.BAT file from being interupted.

BRK.DRV is a device driver which creates a character oriented device by the
name CTRL-BRK. (Other character oriented devices are LPT1, COM1, CON, etc.)
This device driver is installed by placing the line DEVICE=BRK.DRV in a file
named CONFIG.SYS in the root directory of the disk drive from which you will be
booting your system. The same directory must contain the file BRK.DRV. It is
suggested that DEVICE=BRK.DRV be one of the first lines in your CONFIG.SYS
file. The system will then come up with keyboard break disabled. This means
that the system will totally ignore the Ctrl-Break and Ctrl-C key combinations.

A device named CTRL-BRK will then exist. Any attempt to read from this device
(such as TYPE CTRL-BRK, or COPY CTRL-BRK CON) will cause DOS to display a Read
Failure diagnostic. If you write to this device (COPY CON CTRL-BRK) all
characters written will be ignored except for 'N'and 'n' which will cause
keyboard break to be enabled, and 'F' and 'f' which will cause keyboard break
to be disabled. Thus writing 'ON' or 'OFF' to the device CTRL-BRK will do what
you think they would do.

Writing to the device is a convenient way to turn keyboard break on and off
from within a program, but not too easy to use from the keyboard or from a
batch file. That is why the program BRK.COM is provided. If the device driver
has been installed, entering BRK ON will enable keyboard break BRK OFF will
disenable keyboard break. If the device driver has not been installed, or
nothing follows the BRK, an error message will be issued.

More simply Put:

1. Place the line DEVICE=BRK.DRV in a file named CONFIG.SYS (along with
whatever else you may already have in that file.)

2. Place the files CONFIG.SYS and BRK.DRV in the root directory of the disk
from which you will boot your system. The system will come up in a such a
way that it ignores keyboard break.

3. After the system boots, you can use the program BRK.COM to turn keyboard
break on or off (enable or disable it) by entering BRK ON or BRK OFF. You
may use upper or lower case letters.

LIMITATION: Using the t option of PKLOAD (Part of PROKEY 4.0) will cause
Ctrl-C to be detected by DOS at all times. Other resident
programs may have the save effect.

Sorry the documentation is not more complete, or more clearly written, but this
is all the time I had to spend on a free "product" which I wrote because a user
on Gene Plantz's BBS (312 882-4227) wanted this capability. I hope you find
these programs useful.

Everett C. Johnson

  3 Responses to “Category : Utilities for DOS and Windows Machines
Archive   : BREAK.ZIP
Filename : BRK.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: