------------------------------------------------------------------------------
User Guide for setup4K6                                               7-Oct-99
------------------------------------------------------------------------------

This package is for the K6-2 (model 8+, CXT core) and K6-III CPUs.
It's purpose is to optimally setup the CPU for those that have
upgraded their CPU but kept their old motherboard, and where the
motherboard can't itself do the K6 setup.

If you have a K6 or K6-2 model 7 or prior, this program won't do
anything for you, nor is is usually needed since if you have a
K6 you probably at least have a motherboard that supports the
original K6 and early K6-2 CPUs.

9-Oct-99: Added code to flush caches and TLB.

------------------------------------------------------------------------------
Results
------------------------------------------------------------------------------

If your motherboard doesn't setup the K6-2/K6-III optimally, you can expect
about 30% better performance after using this package.  Write allocate gives
about 100% better memory write performance (ie, twice as fast), and write-
combine gives about 100% better memory-to-video-buffer write performance
(ie, writing to the video buffer from main memory, esp. useful in games).


------------------------------------------------------------------------------
Installation
------------------------------------------------------------------------------

This package comes with two parts: the device driver, which does all the CPU
configuration, and a the EXE, which tells you how to call the device driver.


------------------------------------------------------------------------------
setup4k6.exe
------------------------------------------------------------------------------

 setup4K6 1.0   Copyright (C)2000 Cornel Huth   http://40th.com/

 Use: [C:\]setup4K6 <[mb=n] [vfb=x vmb=n]>

         mb=n  n=mb of main memory (eg, mb=128)
        vfb=x  x=address of video frame buffer (eg, E1000000)
        vmb=n  n=mb of video memory (eg, vmb=4)

            setup4K6 mb=128 vfb=E1000000 vmb=4
        or, setup4K6 mb=128
        or, setup4K6 vfb=E1000000 vmb=4

 vfb should be available from your video card setup program.
 Matrox, for example, has it in the MGA Settings->Information, Board mapping

  - This is for the K6-2 (CXT core, model 8+) and K6-III only
  - vfb=/vmb=, if used, must both be specified

Use setup4k6.exe to find out what arguments are needed for the
basedev=wacker.sys line, for both the write-allocate and write-combine
switches.

You specify the write-allocate data by using mb=.  For example, if you have
128 MB of main memory, use -mb=128 on the wacker.sys line.

You specify the write-combine data by using both vfb= and vmb=.  For example,
if you have a Matrox:

 OS/2 System folder -> System Setup -> MGA Settings -> Information

Next to Board Mapping is E1000000 (in my case).  This is used for the vfb=
switch for wacker.sys.  In the same panel you see On-board memory, 4MB (in
my case).  This is used for the vmb= switch.  Both the Video Frame Buffer
(vfb=) and the Video MB (vmb=) are needed if you want to setup a write-
combine buffer.


------------------------------------------------------------------------------
wacker.sys
------------------------------------------------------------------------------

Use wacker.sys in your OS/2 config.sys file.  It is a base driver, and is
loaded very early in the boot process.  If there is an error in booting with
this driver see the [HELP] section below.  Install wacker.sys in the root
directory of the boot drive (just copy it there).

Using the information from setup4k6.exe, add wacker.sys to your config.sys
file.  In my case, I use:

   BASEDEV=WACKER.SYS -whcr:08010000 -wcr0:E101FF82                 -v

This is for 128 MB of main memory (mb=128), with my video frame buffer at
E1000000 (vfb=E1000000) and 4MB of video memory (vmb=4).  This line is what
setup4k6.exe gave.  Once you add this line, reboot.  All is well in Mudville.


------------------------------------------------------------------------------
HELP
------------------------------------------------------------------------------

This is unsupported software.  If you can use it, great.  If not, well, you
should and if you can't, then don't use it any more.

If, after you put basedev=wacker.sys... in config.sys and you can no longer
boot OS/2 (unlikely), do the following:

Reboot.  At the white blob in the upper-left, immediately press Alt-F1.
At the menu, select Command line.  This gets you your original config.sys
that was made when you last installed OS/2.  If you have never done this,
do so now, just to check it out.  You can use the tedit.exe texit editor
to change config.sys (either delete the wacker.sys line or REM it out).
Type Exit when you're done.  It reboots.  Next start your regular config.sys
is used, the one with wacker.sys now removed (or REMed out).

If you are already using Wacker.sys for something else, you need to keep
using it as you are, and just add a new entry for this (so you have to
wacker.sys lines).  Wacker is not memory resident; it does not install.


