             My MS-DOS 6.xx/Windows 3.1x Memory Management Tips


                                  Intro



These are my own memory management tips on how to squeeze a few more KB (Kilo
Bytes) of free low (conventional) memory (RAM) for your DOS programs/games
(under MS-DOS 6.xx and Windows 3.1x) and on how to optimize your CONFIG.SYS
and/or AUTOEXEC.BAT (MS-DOS 6.xx versions) to make all this happen:


I included here my own MS-DOS 6.22 startup files: AUTOEXEC.BAT and CONFIG.SYS.
You can read these files by opening them in Windows with Notepad, or in
MS-DOS mode with EDIT.COM (the MS-DOS default ASCII text editor).
I use MS-DOS 6.22's HIMEM.SYS and EMM386.EXE memory managers in CONFIG.SYS.
My CONFIG.SYS also uses QEMM version 8.01 and NetRoom version 3.04 updated,
third party 386 enhanced memory managers, and if you read MSD62.TXT and
MEM62.TXT, you'll see how much conventional RAM I've gained by using each one
of them.
The file MSD62.TXT was created by running MSD.EXE from the MS-DOS Command
Prompt line (outside Windows):
MSD /P C:\path\MSD62.TXT

NOTE: All CONFIG.SYS and AUTOEXEC.BAT command lines in these examples are
      customized to my system, and you'll need to follow the guidelines in
      this text file, and then edit your OWN startup files (ONLY after you've
      made BACKUP copies) to adapt them to your own system configuration !


                   MY CONFIG.SYS AND AUTOEXEC.BAT EXPLAINED


Bellow are my MS-DOS 6.22 CONFIG.SYS and AUTOEXEC.BAT command lines explained
(most of these tips are ALSO VALID for my DOS7/Win95's startup files, if not
specified otherwise):


                         My CONFIG.SYS lines explained


My HIMEM.SYS command line in CONFIG.SYS:

DEVICE=C:\DOS\HIMEM.SYS /NUMHANDLES=128 /TESTMEM:OFF

For more info on "himem.sys" parameters, run:
HELP HIMEM.SYS
from a DOS prompt (MS-DOS 6.xx users).
/NUMHANDLES=128 represents the maximum number of extended memory block
handles (has no influence in Windows).
/TESTMEM:OFF loads HIMEM.SYS without taking an extra few miliseconds to test
all your system's extended memory. Most of the newer system BIOS-es do this
at bootup time anyway.

NOTE: For detailed info on HIMEM.SYS and EMM386.EXE parameters run:
      HELP HIMEM.SYS
      from a DOS prompt, and then run:
      HELP EMM386.EXE

NOTE: the HIMEM.SYS and EMM386.EXE memory managers MUST be loaded in
      CONFIG.SYS with the "DEVICE" command, before ANY OTHER DEVICE, INSTALL,
      DEVICEHIGH, INSTALLHIGH or/and SHELL commands !
      The CONFIG.SYS commands DEVICE, DEVICEHIGH, INSTALL, INSTALLHIGH, and
      the AUTOEXEC.BAT commands LOAD, and LOADHIGH (LH for short) are internal
      MS-DOS commands, built into the OS (MS-DOS 6.00 and above).

My EMM386.EXE command line in CONFIG.SYS:

DEVICE=C:\DOS\EMM386.EXE X=C000-C7FF I=EE00-EFFF I=E000-ECFF I=B000-B7FF M3
A=64 H=128 D=256 RAM AUTO ALTBOOT NOTR

The following is my "model" EMM386 line (acomodates almost all systems with a
standard MS-DOS 6.xx setup):

DEVICE=C:\DOS\EMM386.EXE X=C000-C7FF I=B000-B7FF D=256 RAM AUTO ALTBOOT

Change the path to EMM386.EXE if other than C:\DOS on your system.

Including and excluding addresses in upper memory (the "I" and "X" switches)
depends on your system CMOS, ROM, Option ROM, and Video BIOS configuration and
video card upper ROM memory addresses and can be tricky. Use these switches
with EXTREME CAUTION (if not properly set, your machine may lockup, or worse,
you may loose data!). You can see how these regions of upper memory are set on
your system, by running MSD.EXE at the DOS prompt, and pressing M (for the
memory screen).
To visualize the upper ROM regions (color coded in grey) occupied by
ROM/VGA/Video, CMOS and Extended BIOS memory hardware configuration you can
click "Utilities" on MSD's menu bar and then click "Memory Browser".
Then write down the hex addresses occupied by your upper ROM memory, and
exclude them, using as many as necessary X= switches on your EMM386.EXE line
in CONFIG.SYS (edit Config.sys with Notepad in Windows, or EDIT.COM in DOS).
EXAMPLE: Let's say that your "Option ROM" (one of the greyed areas in upper
memory, in your MSD memory screen) exists at EC00-ED00. You will need to add
an X= parameter to the EMM386.EXE line to exclude those addresses from your
extended memory manager upper memory map:
DEVICE=C:\DOS\EMM386.EXE X=EC00-ED00

A classical method to make more upper memory available to drivers/devices is
to add these 2 switches:

X=C000-C7FF I=B000-B7FF

to the EMM386.EXE line. C000-C7FF is usually reserved for the video ROM BIOS,
and B000-B7FF region is only used for text on black and white (monochrome)
monitors, so it's safe to add them to your EMM386 line.
For Windows 3.1x Enhanced mode to take advantage of the unused monochrome
region, include the line:

device=c:\dos\monoumb.386

into the [386enh] section of your SYSTEM.INI file, located in your Windows
3.1x directory. The file MONOUMB.386 comes with MS-DOS 6.xx, and is usually
installed by MS-DOS setup, in your \DOS directory (default).
Check out your upper memory configuration with MSD.EXE (comes with MS-DOS
5.0 and up). Run:
MSD
from a DOS prompt (AFTER YOU EXIT Windows 3.1x). Then press M to bring up the
memory screen.

The "M3" switch loads EMM386's page frame to the C800 upper memory address
(hex). On my system this gives maximum contiguous Upper Memory Blocks (UMBs)
used for loading drivers/TSRs "high".
The switch "NOTR" is not documented (prevents EMM386 from detecting a Token
Ring Network Adapter, which detection may hang some machines). "NOTR" is NOT
enabled by default (you need to add it to EMM386.EXE's line yourself!).
Try to avoid the "HIGHSCAN" switch on the EMM386.EXE line! It may be dangerous
to your health (it may hang your machine on bootup!). The "RAM" switch does
the same job on searching the Upper Memory Area (UMA) for unused UMB-s (Upper
Memory Blocks).

To load: FILES, BUFFERS, FCBS, STACKS and LASTDRIVE high in CONFIG.SYS (MS-DOS
6.xx users ONLY), I recommend the excellent DOSMAX version 2.1 utility found
at keyword "DOS" for AOL-ers, at "Memory utilities" (or type DOSMAX when you
bring up the File Search screen, after signing up on AOL. Click the magnifier
glass sitting on top of a floppy disk icon, on the AOL menu bar). Download
the archive DOSMAX21.ZIP. Using the DosMax utilities can save you an extra
16-48KB of low memory! This is the DOSMAX line in my config.sys:

DEVICE=C:\MAX\DOSMAX.EXE M1 N+ P- R- U02 U08 U09 U0A U0B U0C U0D U0E U70 U72 U73 U74 U76 U77

* NOTE 1: to understand how to use DosMax/ShellMax/EnviMax, READ the
          documentation files that come with the DosMax package.
* NOTE 2: DO NOT USE DOSMAX/SHELLMAX/ENVIMAX WITH WINDOWS 95 OS !

DosMax loads itself high, no need for a "DEVICEHIGH" command.

It is useful to load drivers/devices/TSRs with the "DEVICEHIGH" command, to
gain more low (conventional) memory (RAM). Use MEMMAKER to gain more memory.
(MS-DOS 6.00 and up users only!). Or change the order of loading drivers in
config.sys and autoexec.bat until you're satisfied with the amount of
conventional memory reported by the "MEM /C /P" command. You can fiddle with
the "/L:1", "/L:2", "/L:3", etc. switches to determine your own best high
memory loading configuration. Example:

DEVICEHIGH /L:3 C:\DOS\ANSI.SYS

to load the ANSI.SYS driver in Upper Memory (UMA)--region 3 (located on my
system between hex addresses EE00 and EFFF).

NOTE: READ REGIONS.TXT (Courtesy of Mr. Dale F. Ogden and included here)
      FOR PRECIOUS INFO ON MS-DOS UPPER MEMORY MANAGEMENT AND UPPER MEMORY
      REGIONS MAPPING, IF YOU WANT TO MASTER YOURSELF THE WAY DEVICES,
      DRIVERS AND TSR-S LOAD IN YOUR CONFIG.SYS AND AUTOEXEC.BAT.

The order of loading the devices/drivers/TSRs is of utmost importance
(bigger first, smaller last). Same principles apply to loading TSRs high in
AUTOEXEC.BAT, using "LOADHIGH" ("LH" for short). Example:

LH /L:2 C:\MOUSE\MOUSE

This means that my MS-DOS mode Mouse.com Driver loads in the 2nd upper
memory region, located between C800 and ECFF (addresses in hex), on my
system.

NOTE: THE EMM386.EXE LINE MUST FOLLOW THE HIMEM.SYS LINE IN CONFIG.SYS!
      All THE DEVICE/DEVICEHIGH commands in CONFIG.SYS MUST follow the
      HIMEM.SYS and EMM386.EXE lines!

MEMORY TIP: I gave up on using MS-DOS's MemMaker (or QEMM's Optimize, or
            NetRoom's Customiz) utility, to gain more conventional memory.
            I modified the memory manager lines/parameters in CONFIG.SYS
            myself (and changed the order of loadind devices/drivers in
            CONFIG.SYS and AUTOEXEC.BAT manually), only after reading all
            the documentation related to each of the 3 memory managers I
            used (HIMEM.SYS + EMM386.EXE, QEMM386.SYS, and RM386.EXE), and
            experimenting with many different configurations.
            It is a time consuming job, but rewarding, after I made all
            DOS and Windows programs work with the final configuration
            found in my startup files (CONFIG.SYS and AUTOEXEC.BAT in this
            archive). Rewarding, because I have now 625KB of free
            conventional memory, with expanded memory enabled, in MS-DOS
            mode (outside Windows).

SWITCHES=/F - skips the 2 second delay before processing the startup files
	      after bootup.

DOS=HIGH,UMB - loads the DOS kernel high and provides UMBs (upper memory
               blocks) for loading devices/drivers/TSRs in UMA (upper memory
               area).

FILES=n - where 'n' MUST be at least 40 to run MS Windows 3.x and CPU
	  intensive DOS applications/games. Set files to at least 50 in your
          config.sys to play safe!

FCBS=1,0 - not to take extra memory. Higher values are needed only by older
	   DOS programs (very probable that you'll never need more than that)
	   If you don't specify a value for FCBS, MS-DOS loads the default
	   value of 4. Newer programs use the "FILES" setting instead.

BUFFERS=10,0 - if you use ANY hard disk cache utility (SMARTDRV.EXE is
	       strongly recomended if you run Windows 3.1x with 32bit
	       access enabled and DOS programs that access your hard disk
	       frequently). Try to avoid 3rd party disk caches that may
	       crash your computer, especially if you run 32bit disk access
	       in Windows.
	       The first number here (10) is the number of disk buffers.
	       Its value must be between 1-99. Default is 30 (if not
               mentioned) and occupies too much memory (30 or more buffers
               are considered excesive, and cannot fit entirely into the HMA
               anyway).
	       The second number here (0) is the number of buffers in the
	       secondary buffer cache. Its value must be between 0-8.
	       Default is 0 (no secondary cache buffers).
	       Secondary cache buffers are needed ONLY if your hard disk
	       (a SCSI disk) is not recognized or cached by SmartDrive.
               Use Smartdrv with Win31 (add a SMARTDRV line in your MS-DOS
               6.xx AUTOEXEC.BAT), if you use any DOS programs/games that
               require frequent files access (huge files/directories).
               Doing so, it won't interfere with the Win31 disk operations.

STACKS=n,m - where 'n' can be: 8-64 and 'm' can be: 32-512. If you are
	     running older programs that rely on DOS stacks, set STACKS to
	     at least 12,128 (default is STACKS=9,256, set by DOS if you don't
             mention a STACKS= line in config.sys!). Newer DOS programs and
             Windows 3.1x/95 do not use DOS stacks! Set STACKS=0,0 in your
             config.sys to save RAM, if your DOS programs don't need any
             (your older DOS software specifications should tell you if you
             should increase the STACKS!).

LASTDRIVE=n - where 'n' is the letter following your last drive on your system
              (counting all your floppy, hard, CD-ROM, removable, dblspace,
              drvspace, Stacker, or other compressed drives, network drives,
              and RAM virtual drives, if you installed any). You can specify
              any letter from A to Z. Default is the letter following the last
              drive on your system (including floppy, CD-ROM, tape, external,
              RAM and compressed drives) if not mentioned. If you are not
              using a Network Card connection, or/and a RAM disk, you don't
              need to specify this switch in CONFIG.SYS.

DEVICEHIGH /L:1 C:\path\CD_ROM.SYS /D:MYCDROM - your CD_ROM device driver.
You also need to load MSCDEX.EXE in your AUTOEXEC.BAT, for your CD-ROM drive
to be recognized by the system!
Typical mscdex line:

LH C:\path\MSCDEX /D:MYCDROM /M:24 /E

with EMM386 configured to provide expanded memory (EMM386's "RAM" switch) to
load the buffers in expanded memory ("/M:24") with the  "/E" switch.
"/D:MYCDROM" is the cd-rom drive's "name" and MUST be the same as the one on
your cd-rom device driver line in config.sys!

DEVICEHIGH /L:1 C:\WINDOWS\IFSHLP.SYS - MS Windows 32 bit access support driver

DEVICEHIGH /L:1 C:\DOS\ANSI.SYS - or any other ANSI driver found on AOL, that
supports extended keys (F1-F12) remapping (READ chapter II further bellow
on how to remap your extended keys: F1 to F12 in DOS).

The MS-DOS 6.xx version of SHELL= line in CONFIG.SYS:

SHELL=C:\MAX\SHELLMAX.COM /N+ /P- /R- /S- C:\COMMAND.COM C:\ /E:512 /P /F

ShellMax is part of DosMax 2.1 package and loads COMMAND.COM shell high!

NOTE: USE SHELLMAX ONLY WITH MS-DOS 6.xx (NOT with Win95)!

NOTES: You can use any other third party memory manager on the market:
QEMM 8.00, NetRoom 3.0, 386MAX 8.00 with similar (or better) results.
Using DosMax (MS-DOS 6.xx only) with these memory managers may conflict with
their own "DosUp/DosHigh" features! I recomend to disable those "dosup/doshigh"
features and use DosMax's.
Also if you use any 3rd party memory managers, I recommend to NOT enable the
moving of Video/ROM BIOS to high/extended memory (like QEMM's "Stealth" or
NetRoom's "VidCloak" and "SysCloak" features!).
Also try to use MS-DOS's internal (any version above 5.00) "DEVICEHIGH" (in
your config.sys) and "LOADHIGH" ("LH" for short in your autoexec.bat) commands
to load devices/drivers/TSR-s high, instead of your third party memory
managers' external high/upper memory "loaders" (like QEMM's "LOADHI", or
NetRoom's "XLOAD") for better compatibility reasons. Some of these loaders may
interfere with certain DOS programs proper operation, and may lead to system
crashes!


* To load devices/drivers high, you can also use the INSTALLHIGH command
ONLY in your CONFIG.SYS (MS-DOS 6.xx users). INSTALLHIGH is needed only if you
have, for example, a big driver that you want to load before the smaller ones
that load in your AUTOEXEC.BAT (using LH command). Example:
INSTALLHIGH C:\MOUSE\MOUSE.COM <parameters>
A disadvantage to using this command, is that you can't specify an upper
memory region (by using the /L:x switches, as you can use with DEVICEHIGH
and LH). Therefore, that particular driver will load into the largest
contiguous upper memory area.


                          My AUTOEXEC.BAT lines explained


* Lines you might need in your AUTOEXEC.BAT (MS-DOS 6.xx and up users):

LH C:\DOS\MSCDEX /D:MYCDROM /M:24 /E

The cd-rom drive's name (/D:MYCDROM in this example) HAS TO BE EXACTLY THE
SAME as the one specified on your CONFIG.SYS cd-rom driver line (read the
config.sys cd-rom driver topic above);
/M:24 - gives MSCDEX 24 buffers to handle cd-rom cache (if you don't specify
this switch, the default is 8);
/E - loads MSCDEX's buffers into expanded memory, provided you have a line
for EMM386.EXE in your config.sys (example of EMM386 line to provide expanded
memory):

DEVICE=C:\DOS\EMM386.EXE X=C000-C7FF I=B000-B7FF D=256 RAM AUTO ALTBOOT

NOTE: Always use the latest version of MSCDEX.EXE (the newest is 2.23, the
      one included with MS-DOS 6.22).

MSCDEX.EXE takes 23KB of conventional memory if loaded without the LH command
and 2KB per buffer unit above 4 (if loaded in upper memory). Use the /E
parameter with MSCDEX to load its buffers in extended memory.

Example of Smartdrv command line in AUTOEXEC.BAT:

C:\DOS\SMARTDRV 2048 A+ C+ D /N

I presumed that A is your 3.5 inch floppy drive, C is your hard drive, and D
your CD-ROM drive. Change the drive letters if different on your system.
Load Smartdrv AFTER the MSCDEX line, if you want your CD-ROM drive to be
cached in DOS mode!
Run SMARTDRV /? at DOS prompt to see all Smartdrv related parameters, and to
understand how to adapt Smartdrv to your system.

NOTE: If you run any DOS programs/games OUTSIDE Windows, Smartdrv IS A MUST
      (customized to cache ALL read and write disk operations on ALL your
      drives)!

You can decrease Smartdrv's size to a minimum of 64KB (Microsoft recomends
128KB), if you want Smartdrv to cache your drives in DOS mode, and not to
perform caching in Windows:
SMARTDRV 2048 64 A+ C+ D /N
The first number represents Smartdrv's size in DOS mode, and the second number
represents Smartdrv's size in Windows (in this example Smartdrv is set to
cache all drives' reads and writes).

NOTE: If you don't use any DOS mode programs/games, DO NOT load Smartdrv!
      It only takes extra memory space.
      But if you find that besides having enough room in memory (preferably in
      upper) to spare, Windows loads faster (as it does on my system, since
      I'm loading Win31 from a big DOS batch file) with Smartdrv loaded, then
      enable it in your AUTOEXEC.BAT.
      W31.BAT, my Win31 startup batch file is included here. Open it with
      Notepad.

SET MOUSE=C:\MOUSE
LH C:\MOUSE\MOUSE <parameters>

to load your DOS mode mouse driver. You only need a DOS mouse driver in
Windows, if you run any DOS programs/games that use a mouse.
Change the DOS mouse driver's directory if different and adapt the parameters
to your own mouse driver specifications.


                               Wrap-up/Notes


* My MS-DOS 6.22 CONFIG.SYS and AUTOEXEC.BAT files, with EVERYTHING loaded
high, give me 625KB of free low (conventional) memory and 2KB of free upper
memory (with MS-DOS's own HIMEM.SYS and EMM386.EXE memory managers).
This IS ENOUGH to run ANY memory hungry DOS program/game in MS-DOS mode.
ALWAYS make sure to alocate ALL your computer's memory as expanded or
extended memory with your expanded memory manager (use EMM386's "RAM" switch
to provide expanded memory combined with "AUTO", OR use "NOEMS" to provide
ONLY extended memory).
NOTE: DO NOT USE "NOEMS" IF YOUR DOS PROGRAMS/GAMES NEED EXPANDED MEMORY!

* If you don't use any DOS communications software, or if you're not
connected to a network, DO NOT LOAD SHARE.EXE in your MS-DOS 6.xx
autoexec.bat!
Remove the:
C:\DOS\SHARE.EXE
line from autoexec.bat.
Instead use Win31's file-sharing/locking program called "vshare.386".
Add up this line to the [386enh] section of your SYSTEM.INI:
device=vshare.386
and make sure the file VSHARE.386 is located in your \WINDOWS\SYSTEM
directory!
There are DOS applications need a sharing-violation message. Turn it on in
SYSTEM.INI, [386Enh] section, by adding this line:
EnableSharingPopups=TRUE
Windows 95 has its own 32bit (VXD) driver for loading VShare, that loads at
boot time in extended memory:
device=*vshare
this being the line in your Win95's SYSTEM.INI file (no need to load a DOS
driver in autoexec.bat).

* There is a good probability that if you're using a relatively new computer
(386DX/33 and up) and not using a network (or an old ESDI hard disk, or an
old hard disk compression utility), you won't need SETVER.EXE loaded in your
config.sys.
If you determined that you don't need SETVER.EXE loaded (you're not using
any older IBM or third party ESDI/IDE hard disk drivers, or old disk
compressors, or older DOS network drivers), delete the file SETVER.EXE from
the \DOS directory (default) and remove the:
DEVICE=C:\DOS\SETVER.EXE
line from your config.sys.
If you'll need it later on, you can expand the file SETVER.EXE
again and copy it to your hard disk from your OS install disks.

* If you run DOS mode TSRs/drivers/devices loaded high in your CONFIG.SYS
and AUTOEXEC.BAT files (loaded with "DEVICEHIGH" and "LH" by EMM386.EXE),
and have a memory configuration (on bootup, before launching Windows) of
less than 16KB of free upper RAM (the first 384KB of memory above the 640KB
boundary), make sure to remove the following line, or better remark it with
a semicolon (;), or change its numeric value to "0", in the [386enh] section
of your SYSTEM.INI file, located typicaly in C:\WINDOWS:
LocalLoadHigh=0
If this line has a value of "1", you won't be able to start Windows with
less than 16KB of free upper memory on some systems (depending on your video
card's ROM upper memory address location)!
This applies to Windows 3.1x, 386 enhanced mode only.

* Other helpful lines to add to the [386enh] section of SYSTEM.INI (Windows
3.1x and Windows for Workgroups 3.1x):
MaxBPs=768  => maximum number of break points used by Win31's virtual
               memory manager;
EMMExclude=A000-FFFF  => not to allow Windows to search for unused RAM
                         in the upper memory area (UMA): safer on some
                         systems, especially using third party adapter
                         cards, or 3rd party memory managers;
DualDisplay=on  => to make use of the B000-B7FF upper memory area on VGA
                   monitors, if not using a secondary display;
DMABufferSize=64  => to let your 16bit sound card have enough room to play
                     music (MID, RMI, MOD) files (16bit DMA channel HI-FI
                     stereo buffer);
PageBuffers=32  => for faster hard disk buffered read and write operations;
SyncTime=on  => MUST have this line if:  TrapTimerPorts=off;
TrapTimerPorts=off  => might help running time sensitive programs/games
                       better (that rely on the computer's timer) in Win31;
InitPS2MouseAtExit=off  => saves a few miliseconds upon exiting Win31 (not
                           looking for a PS/2 style mouse on exit);
UniqueDOSPSP=TRUE  => to start every DOS application at a unique address in
                      memory (especially if using some networks);
IRQ9Global=on  => use this line if your system hangs when reading from your
                  floppy drive(s);
COMBoostTime=1  => decrease character download time with high speed
                   communication software (increase it if you are loosing
                   characters during modem high speed transfers);
COM2Buffer=1024  => your fast modem 16550AxN UART port (at least 9600bps);
COM2FIFO=1  => if your modem is hooked to COM2 with a 16550AxN UART;
VGAMonoText=off  => to allow Win31 to use the B000-B7FF area if not used
                    by other hardware devices/applications;
32BitDiskAccess=on => turn on 32 bit disk access in Windows 3.1x/WfWG 3.1x;
FileSysChange=off  => not to update file changes in DOS mode (speeds things
                      up in DOS sessions and in File Manager).

Some of these parameters can be loaded at Windows startup, as command
line parameters. To see which ones suit you, run:
WIN /?
at the DOS prompt (outside Windows).

NOTE 1: If you don't know what these lines do, YOU MUST READ MS-DOS and
        Windows help and documentation files and manuals BEFORE altering
        your configuration files and beware that if you type in the wrong
        things you can damage the data on your hard disk and / or have
        unexpected machine hangups !!!
        Win31 afficionados may want to purchase Microsoft's "Windows 3.1"
        or "Windows for WorkGroups 3.11 Resource Kit" for more info on
        tweaking Win31 startup files (they sell for 19 bucks or less).

NOTE 2: ALWAYS BACKUP YOUR DOS / WINDOWS STARTUP FILES BEFORE MAKING ANY
        MODIFICATIONS !!!

* MS-DOS 6.xx STARTUP FILES (default location in C:\ root):
AUTOEXEC.BAT
CONFIG.SYS
* WINDOWS 3.1x STARTUP FILES (located in your Win31 directory, \WINDOWS
is default):
SYSTEM.INI
WIN.INI



Trademarks:

- MS DOS 5.00,
- MS-DOS 6.00,
- MS-DOS 6.20,
- MS-DOS 6.21,
- MS-DOS 6.22,
- MS-DOS 7.00,
- MS Windows 3.00,
- MS Windows 3.10,
- MS Windows for WorkGroups 3.10,
- MS Windows for WorkGroups 3.11,
- MS Windows 95 and
- MS Plus! for Windows 95
  are trademarks of Microsoft (COMERCIAL programs);
- DosMax 2.1 is trademark of Phillip B. Gardner (SHAREWARE);
- NetRoom 3.x is trademark of Helix Software (COMERCIAL);
- QEMM 8.0x is trademark of QuarterDeck Systems (COMERCIAL).



One Final Note:

I uploaded all these hints/tips/tricks in the hope that people like you and
me will find useful to have "shortcut" keys to their favorite programs and
plenty of low free RAM to run any "nasty" (read "memory hungry") DOS
program or game on the planet!
Hope you'll find something useful in here. Enjoy!
If you have any comments/ideas/questions/sugestions etc... send me a
"wire" at:
AXCEL216@aol.com

Regards and best of luck!