Programmer 7500/MAX_PROGRAMMERS.iso/PROGRAMS/UTILS/MEMORIA/PKII_127.ZIP/README.1ST

Text File | 1989-06-14 | 7.5 KB | 173 lines

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 upon affixing to programs under its direct con-
trol (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?); mod-
ules 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
do away with MANY thousand bytes of what the, about to be described, INSTALL
procedure loads.

TO INSTALL POWERKIT II:

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:
Replace that "X" with the drive from which your system boots

ALSO, make sure you are in the directory into which you extraced 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 taken
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.  Also (as an option for Tandy 1000 users)
KYBD.BUF can save 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 (except KEYB??.SYS, see below).

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".  512 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 me on the POWERKIT II support BBS:

[phone], or call me at [phone]

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 have a SNOW producing CGA (a Color Graphics Adaptor that comes with some
IBM machines, and a few clones), call me or the POWERKIT II support BBS to
obtain "no-snow" versions of ANSI.MOD and KYBD.BUF.

USERS OF 101/102 KEY "ENHANCED" KEYBOARDS NOT SUPPORTED BY YOUR BIOS:

European (and American) users of "enhanced" keyboards who must load KEYB.COM
(DOS 3.3), or KEYB??.COM (DOS 3.2 and below), in order for your keyboards to
work properly -- you must run FIXKEYB.COM.  FIXKEYB.COM converts the above
mentioned "COM" files into "SYS" files, which can be loaded by CONFIG.SYS
(where they BELONGED in the first place).  To use FIXKEYB.COM, type:

fixkeyb [path] KEYB??.COM or KEYB.COM

FIXKEYB.COM will create a file KEYB??.SYS or KEYB.SYS.  The "??" stands for the
keyboard driver that is specific to your type of "enhanced" keyboard, and can
be FR, GR, IT, SP, UK, and US (among several others).

After the "SYS" file has been created, put the following line in CONFIG.SYS:

DEVICE= [path] KEYB??.SYS or
DEVICE= [path] KEYB.SYS ??

The above line must appear BEFORE the line:

DEVICE=C:\PKII\KYBD.BUF ...

The "??" stands for the same thing it did earlier.  In the second version, the
space between "SYS" and the "??" is REQUIRED.