Dec 132017
 
Power Kit II version 1.20.
File PKII-120.ZIP from The Programmer’s Corner in
Category Utilities for DOS and Windows Machines
Power Kit II version 1.20.
File Name File Size Zip Size Zip Type
ANSI.DOC 26988 9739 deflated
ANSI.MNU 1716 1025 deflated
ANSI.MOD 6591 5173 deflated
INSTAL.COM 902 635 deflated
INSTALL.BAT 484 273 deflated
KEYBOARD.MNU 904 524 deflated
KYBD.BUF 1350 1057 deflated
KYBD.DOC 2904 1282 deflated
LOAD.COM 793 680 deflated
MACROS.MNU 611 342 deflated
MENU.DOC 4572 2225 deflated
MENU.MOD 2194 1510 deflated
MODEM.MNU 1415 835 deflated
MODES.MNU 905 483 deflated
NEWHOTKY.COM 556 488 deflated
NEWHOTKY.DOC 347 223 deflated
PKII.DOC 33853 11752 deflated
PKII.MOD 6658 4643 deflated
POWERKIT.MNU 1857 1097 deflated
PRINTER.MNU 1984 1049 deflated
QWIK-REF.DOC 5492 2316 deflated
README.1ST 6726 3044 deflated
UNLOAD.COM 473 414 deflated
UPDATE.LST 3055 1452 deflated

Download File PKII-120.ZIP Here

Contents of the README.1ST file


POWERKIT II INSTALLATION (preceded by a short commercial break)

Welcome to the "modular" world of POWERKIT II, where you never again need have
more stuff taking up valuable space in your machine than what you are actually
using. Nor, must you purchase more than you require, just to have the one or
two special items that interest you. Modules do even more than that for you.
They are much smaller than their "TSR" and "device driver" cousins (they can be
half the size, but perform the same task -- BETTER), and because they are all
controlled from a central "switchboard", they don't get in each other's way.

Modules are a new form of memory-resident program. They achieve their parsi-
monious use of memory by; attaching themselves to COMMAND.COM, thus doing away
with the extras MS-DOS insists on affixing to programs under its direct control
(like a PSP and an Environment); modules have direct access to dozens of useful
routines in ANSI.MOD (why must EVERY program reinvent the wheel?); modules
don't need any code to determine whether they should pop up or not, they simply
tell ANSI.MOD (itself a module, of course) what their "hot" key is, and
ANSI.MOD "wakes" them when it's time (this also helps to keep modules from
stepping on each other's toes).

There are so many things POWERKIT II can do for you, that at first, you'll need
all the help you can get. Later, after you have learned the commands, you can
delete MANY thousand bytes of what the, about to be described, INSTALL
procedure loads.

TO INSTALL POWERKIT II, assuming you are reading this AFTER you have de-arced
the POWERKIT II files:

For a system WITHOUT a hard disk, type:
INSTALL A: <-- be sure to type that colon

For a system WITH a hard disk, type:
INSTALL C: <-- be sure to type that colon

In rare instances, hard disk systems don't boot from drive C:, so type:
INSTALL X: <-- the colon is VERY important
Replace that "X" with the drive from which your system boots

ALSO, make sure you are in the directory in which you de-arced the POWERKIT II
package, when you type "INSTALL ... ".

YES, that's all there is to it!

Well, not quite. If you have a "floppy only" system, place the POWERKIT II
disk on drive "B", and your "bootup" disk on drive "A". Your bootup disk is
the one with DOS, and all the system files on it; the one you shove into drive
"A" when you turn the machine on. With a single floppy system, this will en-
tail some disk swapping. Also, you may have to delete some of the boot disk's
files, because the INSTALL program writes some POWERKIT II files to it. You
may decide to create a brand new "boot" disk (just put a blank diskette into
drive B, your old boot disk in drive A, then type "FORMAT /S").

KYBD.BUF IS OPTIONAL:

INSTALL inserts a the line:

DEVICE=KYBD.BUF

Page 2

at the top of your CONFIG.SYS file. KYBD.BUF is an extended keystroke buffer
(to let you type up to 255 keystrokes into the buffer, before they are drawn
out, and used). Because of this buffer, KYBD.BUF MUST reside within the first
65k bytes of memory. KYBD.BUF also opens a "view-port" into that buffer, to
let you see what you are typing. If that's not enough, KYBD.BUF saves several
interrupt vectors, and contains code to perform a fast warm boot. For the warm
boot to perform properly, The DEVICE=KYBD.BUF line should be placed ahead of
anything in CONFIG.SYS that taps into "important" interrupts.

If you don't want these features, you can remove that line from CONFIG.SYS,
without affecting the rest of the POWERKIT II system.

ENVIRONMENTAL WOES:

You may be unlucky enough to have a full "environment". The POWERKIT II
system requires 14 bytes of that "environment", so if you see an "Out of
environment space" message whiz by when AUTOEXEC.BAT is trying to load
POWERKIT II modules, you have some HARD work to do. If your DOS version is
3.0, or above, you must include the following line in your CONFIG.SYS file:

SHELL=X:\COMMAND.COM /P/E:xxx

In DOS 3.0 or 3.1, those "little x's" are the number of bytes you want your
"environment"'s size to be, DIVIDED BY 16 (yes, I know that doesn't make any
sense, but "that's the way it is"). In DOS 3.2, or above, they represent the
actual number of bytes to reserve for the "environment". 500 bytes is usually
enough.

If you are still using a DOS in the 2's, you will need to call the POWERKIT II
support BBS, and download a program that patches your COMMAND.COM, to increase
the "environment".

The "environment" is just an area of memory where "strings", like "COMSPEC=",
or "PKD=C", are kept.

MANUAL INSTALLATION:

If you're like me, and don't cotton to some program messing around with your
CONFIG.SYS and AUTOEXEC.BAT files on your hard disk, you can hand-load the
POWERKIT II package thusly:

Create a directory "\PKII" right off the root directory on your bootup disk (or
diskette). Move the files ending in *.MOD, *.MNU, as well as KYBD.BUF,
LOAD.COM, and UNLOAD.COM, into this directory.

Add the line:

DEVICE=X:\PKII\KYBD.BUF ("X" is your boot drive)

somewhere near the TOP of your CONFIG.SYS file.

In your AUTOEXEC.BAT file:

Add "X:\PKII;" to your "PATH=" statement (replace the "X" with your boot drive)

Below the "PATH=" statement, add these lines to AUTOEXEC.BAT (and replace "X"
with your boot drive letter):

Page 3

SET PKD=X
LOAD X;\PKII\ANSI.MOD <-- (ANSI.MOD MUST BE MENTIONED FIRST)
LOAD X:\PKII\PKII.MOD
LOAD X:\PKII\MENU.MOD POWERKIT.MNU

If you have questions, contact the POWERKIT II support BBS at:

(303) 377-6725,

or call (303) 595-4218

If you're leery of "INSTALL"ing POWERKIT II on your hard disk before testing
the package, create a floppy "boot" disk, and "INSTALL" POWERKIT II on the
floppy disk FIRST. If everything goes well, then INSTALL it on your hard disk.

Thanks for your patient attention. The price for this POWERKIT II starter
kit is $19.95 (a $5 upgrade fee for POWERKIT owners registered before December
22, 1988). Test it thoroughly, but please don't linger too long before send-
ing your check (U.S. funds only, please).

John H. Brooks

DO YOU DREAM OF A WHITE CHRISTMAS WHEN ANSI.MOD UPDATES YOUR SCREEN?

If you do, you have an old, slow, SNOW producing CGA (Color Graphics Adaptor).
Call the POWERKIT II support BBS to download a "no-snow" version of ANSI.MOD.
It'll be slower (than the "regular" ANSI.MOD), but in "raw" mode, your screen
updates will be noticeably faster than you're used to now.




 December 13, 2017  Add comments

Leave a Reply