Category : Tutorials + Patches
Archive   : STAC0694.ZIP
Filename : 2201.TXT

 
Output of file : 2201.TXT contained in archive : STAC0694.ZIP
___________________________________________________________________________
STACKER NOTE STACKER NOTE
Title: Stacker and Windows Enhanced Mode.
STAC FAX Index #2201 - 6/29/92
___________________________________________________________________________

Background.

Stacker is fully compatible with the 386 Enhanced mode of Windows.
However, some fine tuning is required to ensure optimum performance.
This note will assist in the configuration of Windows 3.0 and 3.1 in a
Stacker environment.

I. Using the Stacker XT/8 Coprocessor

If you are using the Stacker XT/8 coprocessor on a 386
and plan to run Windows in 386 Enhanced Mode, you'll
need to add an EMMExclude statement to the SYSTEM.INI
file in your Windows directory. Syntax:

EMMExclude=

For example, if your XT/8 coprocessor base address is
cc00, in the SYSTEM.INI file, add the following
statement under the heading [386Enh]:

EMMExclude=cc00-cfff

The following table lists the seven possible memory
ranges, based on the base address of the XT/8
coprocessor card:

Base Address to Exclude

------------ ------------------
c400 c400-c7ff
c800 c800-cbff
cc00 cc00-cfff
d000 d000-d3ff
d400 d400-d7ff
d800 d800-dbff
dc00 dc00-dfff

Note: The Stacker AT/16 card uses an exclusive I/O address so
it requires no special treatment.

II. Temporary Windows swap files

If you are using a temporary Windows swap file, you can
place the swap file on an uncompressed portion of your disk
to reduce fragmentation of your Stacker drive. Windows
3.1 is Stacker aware and will not give you the option of
placing it on the Stacker drive. With Windows 3.0,
specify the swap file location by adding the following
line to the SYSTEM.INI file, located in your Windows
directory, under the heading [386Enh]:

PagingDrive=

where is an uncompressed drive with more
than 2 MB of available disk space. If the drive does
not have this amount available, Windows will not operate
properly. If your uncompressed drive has less than 2 MB
of available disk space, you can use SDEFRAG /G to make
more uncompressed space available.

For example, if drive C was your only drive before
Stacker, installing Stacker creates drive D, which then
becomes the uncompressed portion of your disk. Use the
following PagingDrive parameter.

PagingDrive=D:

NOTE: If you built your Stacker drive by building an
empty Stacker drive, or if you have manually
removed the SSWAP command, then your uncompressed
drive may have a different letter.

III. Permanent Windows swap files

If you decide to use a permanent swap file (which must
be on an uncompressed drive) after you've already
created your Stacker drives, you may discover that you
don't have enough room. You can make more uncompressed
space available by using SDEFRAG /G.

If Windows still reports that there is not enough disk space,
even though it appears there is plenty, it may not be
contiguous. In this case you'll have to unhide the Stacker
drive's STACVOL file and run a disk optimizer such as Norton
Speedisk or PCTOOLS Compress to make the space contiguous.
Use the following procedure:

1. Make sure your disk optimization program exists on
the uncompressed drive or floppy. Then, restart your
system from a clean boot diskette. (No Stacker device
driver).

2. Insert your Stacker diskette and type:

a:\SATTRIB -R -S -H c:\STACVOL.DSK

where c: is the Stacker host drive letter.

3. Next, run the disk optimizer on the drive you wish to
host the permanent swap file.

4. Finally, rehide the STACVOL file with:

a:\SATTRIB +R +S +H c:\STACVOL.DSK

5. Reboot the machine from the hard disk. You are now
ready to create the permanent swap file.
___________________________________________________________________________
Copyright 1992, STAC Electronics



  3 Responses to “Category : Tutorials + Patches
Archive   : STAC0694.ZIP
Filename : 2201.TXT

  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: http://www.os2museum.com/wp/mtswslnk/