Beruflich Dokumente
Kultur Dokumente
�����������������http://www.mdgx.com/������������������
��������������������
MS-DOS 7.xx/8.00 + Windows 95/98/ME Memory Management Guidelines
����������������������������������������������������������������
Take control of your Windows 9x/ME machine at DOS level!
��������������������������������������������������������
... And Boost Your DOS Memory to the MAX!
�����������������������������������������
___________________________________________________________________
| ALWAYS BACKUP ALL YOUR OPERATING SYSTEM DRIVES TO A SAFE LOCATION |
| BEFORE ATTEMPTING TO MAKE ANY SYSTEM CHANGES ! |
| http://www.mdgx.com/secrets.htm#BKP |
�������������������������������������������������������������������
WARNING: Take EXTREME CAUTION when modifying your System/Startup settings!
Faulty changes may result in crashes/lockups/permanent data loss, or
might lead to having you REINSTALL your Operating System(s)!
YOU are the ONLY one responsible for ANY changes YOU make!
ALWAYS HAVE YOUR MOST RECENT SYSTEM BACKUP READY!
FYI: Other web pages guidelines linked here do not necessarily reflect the
opinion of the author of these files.
MEMORY.TXT Contents:
Intro
BASIC *ESSENTIAL* MEMORY TIPS
Windows DOS Box Tips
My CONFIG.SYS + AUTOEXEC.BAT Step by Step:
I. My CONFIG.SYS Lines Explained
II. My AUTOEXEC.BAT Lines Explained
Killer Replacements
Notes + Wrap-Up
Reference: Memory Management Terms + System Files @ Wikipedia
http://www.mdgx.com/mem7.htm#WKL
______________________________________________________________________________
������������������������������������������������������������������������������
Intro
After all Windows 95/98/ME is a MIXED (read "partially enabled") 32-bit AND
16-bit [for backward compatibility with MS-DOS (DOS16 and DOS32) and older
16-bit Windows/WfWG 3.xx (Win16) programs] Graphical User Interface (GUI)
protected mode virtual environment [... sorry, Operating System :)], which
still depends on the good ol' MS-DOS 7.xx TSR modules (IO.SYS + COMMAND.COM),
MS-DOS mode memory manager (HIMEM.SYS) and compatibility (legacy) drivers
(IFSHLP.SYS) to load on top of the plain DOS command line based layer!
The good news is Microsoft released Windows XP
(eXPerience)/2003/Vista/2008/7/8/8.1/2012, true 32-bit/64-bit multitasking,
multithreading and Symmetrical MultiProcessing (SMP) graphical OSes, which do
away once for all with the "ancient" 16-bit MS-DOS command line.
NOTE: Unfortunately Microsoft removed 16-bit application support from all
Windows 64-bit (x64) OSes. ;-(
But the bad news is these advanced OSes do NOT support native/real/true/pure
MS-DOS mode, necessary for some old DOS based programs/games that require
exclusive access to memory/video/audio/network hardware resources, and most of
which are still memory "hungry", especially the ones that canNOT run from a
DOS session/box/window inside Windows.
Therefore master your CONFIG.SYS:
http://www.mdgx.com/mem7.htm#7
+ AUTOEXEC.BAT command lines:
http://www.mdgx.com/mem7.htm#A7
and your MSDOS.SYS: see "COMPLETE MSDOS.SYS REFERENCE" in MYTIPS95.TXT
(included):
http://www.mdgx.com/msdos.htm
+ SYSTEM.INI parameters: see "SYSTEM.INI TWEAKS" in MYTIPS95.TXT (included):
http://www.mdgx.com/lastweek.htm#SYSINI
to BOOT into your system the way YOU want!
Solutions [free(ware)]:
- DOSBox:
http://www.mdgx.com/dos.htm#BOX
- ScummVM:
http://www.scummvm.org/
- "95/98/ME SETUP + MEMORY MANAGERS":
http://www.mdgx.com/newtip20.htm#9SMM
- "WINDOWS DOS BOX TIPS":
http://www.mdgx.com/newtip23.htm#WDBT
- "PLAY DOS GAMES WITH SOUND BLASTER LIVE!":
http://www.mdgx.com/newtip18.htm#DGSBL
- UMBPCI.SYS:
http://www.mdgx.com/umb.htm
- DOS Tools:
http://www.mdgx.com/dos.htm
- Virtualization Software:
http://www.mdgx.com/xptoy.htm#VPC
TIP: A good thing is that you can successfully use the Win9x/ME MS-DOS mode
memory managers releases (HIMEM.SYS + EMM386.EXE) in your MS-DOS 6.xx
CONFIG.SYS, ONLY IF you are using the dual-boot feature in Win9x/ME AND have
kept your old MS-DOS 6.xx + Windows/WfWG 3.1x.
IMPORTANT:
To learn how to ACTIVATE and USE the native/real/true/pure MS-DOS mode in:
* Windows 95/OSR2/98: read these topics from MYTIPS95.TXT (included):
- "2 DOS OR NOT 2 DOS":
http://www.mdgx.com/last3.htm#DOS2DOS
- "MS-DOS PROMPT":
http://www.mdgx.com/lastweek.htm#MSDOSPROMPT
- "DOS NOW!":
http://www.mdgx.com/newtip1.htm#DOS
- "RETURN TO DOS".
* Windows ME: see "A MUST for ALL Windows ME users running DOS based programs
+ games:" at the bottom of the "Windows DOS Box Tips" chapter further below:
http://www.mdgx.com/newtip23.htm#WDBT
1. Add/modify the EMM386.EXE (or your 3rd party expanded memory manager) line
in your CONFIG.SYS to provide UMBs (Upper Memory Blocks), access to UMA (Upper
Memory Area) and expanded memory (EMS) provided by the EMM386.EXE "RAM" and
"HIGHSCAN" parameters.
Contrary to what you may have read/heard, expanded memory is STILL needed by
certain (older) DOS applications and games that canNOT be executed from a DOS
box/session/window INSIDE the Windows GUI, and DOES NOT slow down your
computer's performance. What DOES slow down is the mere presence in memory of
ANY upper/extended/expanded memory manager loaded from CONFIG.SYS, EVEN IF
expanded memory is NOT enabled.
There are 2 exceptions though (see further below for details):
- Microsoft's HIMEM.SYS = provides ONLY extended RAM, NOT upper NOR expanded,
and does NOT slow down your CPU.
- Uwe Sieber's UMBPCI.SYS (HIMEM.SYS extender) = provides ONLY upper RAM, NOT
extended NOR expanded, but leaves the CPU in "real mode", which is MUCH
faster than ANY "virtual mode" memory manager.
Such programs NEED to run from native/real/true/pure MS-DOS mode, OUTSIDE
Windows.
Here is a list of DOS programs that use Expanded Memory Specifications (EMS):
* Applications:
- Autodesk CAD
- Borland: dBASE, Paradox, Quattro Pro + Turbo C
- Computer Associates Clipper
- Geoworks
- Liberation Enterprises Intellicom
- Lotus: 1-2-3 2.x/3.x, Agenda, Magellan + Symphony
- Microsoft FoxPro
- Mustang Wildcat BBS
- Novell Word Perfect
- SPC Harvard Graphics
- Symantec: DESQview + Q&A
* Games:
- id: Spear of Destiny + Wolfenstein 3D
- Lucas Arts: X-Wing, TIE Fighter + Super Star Wars
- Microprose Civilization
- Origin: Strike Commander, Ultima Underworld + Wing Commander
- Spectrum HoloByte Falcon
- Three-Sixty: Patriot + V for Victory
* Network Software:
- 3Com TCPIP 2.x
- DEC DecNet
- FTP PC/TCP 2/3
- Microsoft LanMan 2.x
- Novell: EMSNETX + VLM
* Utilities + TSRs:
- Microsoft MSCDEX.EXE CD-ROM Extensions TSR
- Lineo (Caldera) DR-DOS NWCDEX.EXE CD-ROM Extensions TSR
- Creative Labs Sound Blaster AWE32/AWE64/Live! series Audio Tools/TSRs
- HyperWare HyperDisk
- IIT XtraDrive
- Novell Btrieve
- PC-Kwik
- Stac Electronics Stacker
- Symantec: FastBack, NDOS, NCACHE, Norton PC Tools + QRAM
- Vertisoft DoubleDisk
Therefore if you are still running ANY DOS programs/games that use expanded
memory, I suggest to enable it in your CONFIG.SYS.
Some of these DOS programs/games can function even without EMS, but certain
features will be disabled and/or conventional memory usage will increase if
EMS not enabled.
See REGIONS.TXT + EMM386.TXT (both included) for detailed MS-DOS Upper Memory
Management, Upper Memory Regions Mapping + Expanded Memory Management and
Troubleshooting, TO MASTER THE WAY DEVICES, DRIVERS + TSRs LOAD FROM YOUR
CONFIG.SYS + AUTOEXEC.BAT.
FYI:
- MSKB: General Tutorial on Various Forms of Memory:
http://support.microsoft.com/kb/37242
- MSKB: Overview of Memory Management Functionality in MS-DOS:
http://support.microsoft.com/kb/95555
- MSKB: Win95: Managing Memory in MS-DOS Mode:
http://support.microsoft.com/kb/151718
- MSKB: How to Increase Conventional Memory for MS-DOS Based Programs:
http://support.microsoft.com/kb/134399
- MSKB: Running Both Extended and Expanded Memory on Your Computer:
http://support.microsoft.com/kb/96766
- MSKB: EMM386.EXE Slows Down System Performance:
http://support.microsoft.com/kb/74152
- MS TechNet: Windows 98 Startup Process:
http://www.microsoft.com/technet/archive/win98/reskit/part1/wrkc05.mspx
- MS TechNet: MS-DOS 6 Memory Management:
http://www.microsoft.com/technet/archive/msdos/05_memry.mspx
- MSKB: Requirements to Boot Previous Operating System:
http://support.microsoft.com/kb/121963
- MS TechNet: Working with Startup files:
http://www.microsoft.com/technet/archive/msdos/03_confg.mspx
- MSKB: EMM386 Troubleshooting and Technical Information:
http://support.microsoft.com/kb/78557
- MAXIMIZING DOS CONVENTIONAL MEMORY WITH DOS 5/6/7 + Win95:
http://winmac.mvps.org/doswin.html
- Optimizing Windows 95/98 startup for DOS programs:
http://winmac.mvps.org/win95dos.html
- Running MS-DOS programs under Windows 9x:
http://wb1.150m.com/DOSPgms/DOSPgms2.html
- Running MS-DOS games:
http://faqs.cs.uu.nl/na-dir/windows/win95/faq/part12.html
- DOS Tweaks + Tuneup tips:
http://web.archive.org/web/20070604053121/http://www.devedia.com/dosghost/dos/twks_
w31.htm
- FreeDOS memory management FAQ:
http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/memfaq.txt
- Configuring your MS-DOS properly:
http://www.cubic.org/docs/configuring.htm
- DOS memory managment:
http://www.robvanderwoude.com/dosmem.php
- Lineo (Caldera) DR-DOS 7.03 EMM386.EXE v3.27 (free trial) enhanced memory
manager CONFIG.SYS line (applies to ALL EMM386 releases starting with 3.00):
DEVICE=C:\DRDOS\EMM386.EXE USE=C800-EFFF USE=B000-B7FF AUTO DMA=256 HANDLES=128
QUIET
Get DR-DOS 7.03 Operating System [6 MB, free trial]:
http://ftp.uni-bayreuth.de/pc/caldera/DR-DOS.703/dr703.exe
FYI:
- For more info on HIMEM.SYS + EMM386.EXE parameters read the HIMEM.SYS and
EMM386.EXE topics in MSDOSDRV.TXT (using Notepad), found in your Windows 9x/ME
folder, or go to:
http://support.microsoft.com/kb/234868
- For more info using your 3rd party memory manager with Windows 9x/ME read
"95/98/ME SETUP + MEMORY MANAGERS" in MYTIPS95.TXT (included):
http://www.mdgx.com/newtip20.htm#9SMM
- For more info on optimizing your Windows 9x/ME + MS-DOS 7.xx/8.00 memory
resources see this Microsoft page:
http://www.microsoft.com/technet/archive/win98/reskit/part5/wrkc26.mspx
FYI:
"Some of my old DOS games would not run from their CDs using NWCDEX.EXE in
native MS-DOS. But if I load SHSUCDX.COM (or MSCDEX.EXE) right before I start
a game, even though NWCDEX is still in memory and a new drive letter is
assigned to my CD-ROM, the games will work. I'm using SHSUCDX because it can
be unloaded, and I can restart Windows without having to reboot.
I created a batch file to load SHSUCDX before the game starts and then unload
it after the game exits."
[Thank you Edward!]
5. Load the LARGER devices/drivers/TSRs FIRST, and the SMALLER LAST in your
AUTOEXEC.BAT + CONFIG.SYS. Some trial-and-error is necessary to establish your
optimal configuration, depending on your own custom "combo".
7. ONLY IF you do NOT use ANY native MS-DOS mode programs or games:
A. You can safely delete your AUTOEXEC.BAT + CONFIG.SYS files, but BACK THEM
UP FIRST!
IMPORTANT:
It is recommended to keep a stripped down AUTOEXEC.BAT (or CONFIG.SYS) though,
to include your custom PATH line, because Windows 95/98 canNOT "see" the
location of some of your installed programs/drivers, or canNOT function
properly otherwise. :(
Furthermore, there is a wide variety of hardware and software that during
installation add the lines below to your existing AUTOEXEC.BAT, or create a
new one if not present, and this applies to ALL Windows 95/98 systems (default
setup folders used in these examples):
- Creative Labs Sound Blaster Live! PCI (ALL "flavors") install legacy support
(SB16 FM emulation) for real mode DOS games/apps:
FYI:
SBEINIT.COM requires Microsoft EMM386.EXE with expanded memory (EMS) enabled
(the "RAM" switch) in CONFIG.SYS!
See "PLAY DOS GAMES WITH SOUND BLASTER LIVE!" in MYTIPS95.TXT (included) for
complete details:
http://www.mdgx.com/newtip18.htm#DGSBL
- Creative Labs Sound Blaster AWE64/AWE64 Gold ISA PnP install legacy support
(SB AWE64 Audio + MIDI synthesis) for real mode DOS games/apps:
SET CTCM=C:\WINDOWS
C:\WINDOWS\CTCM.EXE
SET SOUND=C:\SB16
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET MIDI=SYNTH:1 MAP:E MODE:0
C:\SB16\AWEUTIL.COM /S
C:\SB16\MIXERSET.EXE /P /Q
C:\SB16\DIAGNOSE.EXE /S /W=C:\WINDOWS
- Creative Labs Sound Blaster AWE32/Vibra 16 ISA PnP install legacy support
(SB AWE32 Audio + MIDI synthesis) for real mode DOS games/apps:
C:\PROGRA~1\MONSTE~1\F3INIT.EXE C:\PROGRA~1\MONSTE~1\F3DOS.BDI
- Aureal3D Vortex 2.0 (A3D 2.0) based PCI sound cards install legacy support
(SB Pro compatible Aureal FM emulation) for real mode DOS games/apps:
LH C:\WINDOWS\AU30DOS.COM
SET QTJava=C:\WINDOWS\SYSTEM\QTJava.zip
SET CLASSPATH=%QTJava%;
SET CLASSPATH=C:\PROGRA~1\PHOTOD~1.1\ADOBEC~1
SET
PATH=C:\;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\WINDOWS\SYSTEM;C:\BAT;C:\MAX;C:\AWE64;C:\
ZIP;C:\3D;C:\QEMM;
Also make sure to add a semicolon (;) at the end of EACH directory, and AFTER
the LAST PATH entry (see example above), so the OS can "read" the entire path
properly.
B. Use a well tuned MSDOS.SYS file to decrease Win95/98 boot loading time as
much as possible: SCANDISK.EXE will not check your drives/partitions for
errors in case OSR2/Win98 shut down improperly (AutoScan=0), the Startup Menu
will not be displayed (BootMenu=0), the bootup Logo will not show (Logo=0),
the Win9x GUI will load automatically (BootGUI=1) with no pause (BootDelay=0),
Win95/OSR2 is automatically selected as current OS (BootWin=1), Normal boot
option is selected as default (BootMenuDefault=1) without any delay
(BootMenuDelay=0), and you are not using an older MS-DOS version
(BootMulti=0). Example:
[Options]
AutoScan=0
BootDelay=0
BootGUI=1
BootMenu=0
BootMenuDefault=1
BootMenuDelay=0
BootMulti=0
BootWin=1
Logo=0
Also online:
http://www.mdgx.com/newtip23.htm#WDBT
All these tips aim to MAXimize the performance and reliability of DOS based
programs/games started from a Windows DOS box. This allows compatible native
DOS applications to execute from within the Windows protected mode GUI
environment in a confined (isolated) DOS box/session/window, by emulating a
DOS Virtual Machine (VM).
But keep in mind that unfortunately not all software originally written for
real DOS mode can run this way. :( Some require strict conventional, upper,
extended and/or expanded memory specs, and/or exclusive access to hardware
resources, like full screen VGA/SVGA/XVGA resolution, real time
audio/sound/music FM/wavetable/MIDI etc. Such programs/games need
native/real/true/pure MS-DOS mode, and eventually large amounts of usable RAM
to run properly: see all other topics in this file to learn how to customize
your system for providing MAXimum free memory in native MS-DOS.
It is also important to realize that certain older (EGA or even VGA, but
probably not some SVGA) DOS based apps/games may run OK from a Windows DOS
session, but usually slower than from native MS-DOS mode. :(
To avoid DOS box errors/lockups, sometimes the only way is to disable certain
program/game features, like: enhanced audio stereo/effects, SVGA/VESA video
modes (i.e. revert to 640x480 or even lower screen resolutions if available)
etc. You decide if the tradeoffs are worth giving up native MS-DOS mode.
CAUTION:
Windows 95/98/ME OSes support a maximum of 64 DOS boxes/sessions/windows open
at the same time:
http://www.geocities.com/budallen98_98/fatalexp.html#Fatal%20Exception%20Error
%20Using
FYI:
- DOSBox CPU, Video, Sound + Network DOS emulator allows to install + play old
DOS games on Windows PCs (free GPL):
http://www.mdgx.com/dos.htm#BOX
- ScummVM scripting/re-encoding tool + hardware emulator allows playing old
DOS games from within all Windows 32-bit + 64-bit OSes (free GPL):
http://www.scummvm.org/
More info:
http://en.wikipedia.org/wiki/ScummVM
- See "95/98/ME SETUP + MEMORY MANAGERS" in MYTIPS95.TXT (included):
http://www.mdgx.com/newtip20.htm#9SMM
- See "PLAY DOS GAMES WITH SOUND BLASTER LIVE!" in MYTIPS95.TXT (included):
http://www.mdgx.com/newtip18.htm#DGSBL
- Some of these DOS tools might help [free(ware)]:
http://www.mdgx.com/dos.htm
- MS-DOS Mode Configuration Wizard Customization Tool (DOSWZCFG.EXE) for
Windows 9x/ME, part of Microsoft Kernel Toys for Windows 95/OSR1/OSR2 [57 KB,
free, unsupported]:
http://web.archive.org/web/20070320222146/http://download.microsoft.com/download/c/
1/a/c1a2a8d9-e2e0-4b94-8e47-61583e71b837/W95KRNLTOYS.EXE
configures OS boot files: AUTOEXEC.BAT, CONFIG.SYS + MSDOS.SYS.
But let's see what you CAN do to speed up your DOS programs running from DOS
boxes and make sure they perform as error-free as possible: [good luck! :)]
- Turn off "Warn if still active": right-click on your MS-DOS PIF shortcut ->
Properties -> Misc tab -> uncheck the box to get rid of that annoying nagging
dialog window.
- Turn off "Fast ROM emulation": right-click on your MS-DOS PIF shortcut ->
Properties -> Screen tab -> uncheck the box.
This is necessary for (especially older, without hardware VESA support) video
controllers that do NOT emulate their VESA/VBE BIOS video modes properly into
Windows 32-bit protected mode drivers (VXDs).
If you own such a "crippled" video card, make sure to load a dedicated
VESA/VBE 2.0/3.0 driver/TSR (eventually from AUTOEXEC.BAT) PRIOR to starting
Windows GUI.
Most manufacturers/vendors of old VGA cards provide compliant VESA/VBE drivers
bundled with the hardware, also available for download (usually free of
charge) at their web/ftp sites.
See "SPEED-UP + BENCHMARK TOOLS" in SOFTWARE.TXT (included) for examples of
VESA/VBE drivers + tweaking tools:
http://www.mdgx.com/speed.htm#VGA
- Assign a fixed amount for each type of RAM to the PIF shortcuts, according
to your particular application's vendor guidelines: right-click on your MS-DOS
PIF shortcut -> Properties -> Memory tab -> here are 4 different kinds of
memory: "Conventional memory", "Expanded (EMS) memory", "Extended (XMS)
memory" and "MS-DOS protected-mode (DPMI) memory" -> scroll to the desired
"Total" value (NOT "Auto"!) for each of them -> click OK or hit Enter.
Turn on "Protected" mode: right-click on your MS-DOS PIF shortcut ->
Properties -> Memory tab -> look under "Conventional memory" -> check the box.
Certain DPMI games may crash Windows if this setting is NOT enabled!
ALL Windows "Total" defaults are set to "Auto", which may attract annoying
hard disk swapping and/or program/game slowdown/stutter.
It is recommended to enable ONLY the required memory type(s) and disable ALL
other(s) to achieve MAXimum performance.
Games known to need specific amounts of RAM for optimal operation:
* 3D Realms Duke Nukem 3D:
- EMS = None.
- XMS = 8192 KB (8 MB).
- DPMI = 8192 KB (8 MB).
* Activision MechWarrior 2:
- EMS = None.
- XMS = 8192 KB (8 MB).
* Bullfrog Magic Carpet + Magic Carpet II:
- EMS = None.
- XMS = 16384 KB (16 MB).
- DPMI = 16384 KB (16 MB).
* id Doom + Doom II:
- EMS = None.
- XMS = None.
- DPMI = 4096 KB (4 MB).
* id Quake:
- EMS = None.
- XMS = None.
- DPMI = 8192 KB (8 MB).
* Interplay Descent + Descent II:
- EMS = None.
- XMS = None.
- DPMI = 4096 KB (4 MB).
* Access Links 386:
- DPMI = 4096 KB (4 MB).
* Lucas Arts X-Wing + TIE Fighter:
- EMS = 4096 KB (4 MB).
- XMS = None.
* Lucas Arts Rebel Assault + Rebel Assault II:
- EMS = None.
- XMS = 8192 KB (8 MB).
- DPMI = 8192 KB (8 MB).
* Microprose Civilization:
- EMS = 4096 KB (4 MB).
- XMS = None.
* Trilobyte The 11th Hour:
- EMS = None.
- XMS = 16384 KB (16 MB).
- DPMI = 16384 KB (16 MB).
* Trilobyte The 7th Guest:
- EMS = None.
- XMS = 4096 KB (4 MB).
- Install/turn on your sound card DOS (i.e. Sound Blaster FM) emulation mode
(if any) in Windows 9x/ME, if your DOS programs/games require audio.
See "PLAY DOS GAMES WITH SOUND BLASTER LIVE!" in MYTIPS95.TXT (included) for
details:
http://www.mdgx.com/newtip18.htm#DGSBL
- DOS software that require Virtual Control Program Interface (VCPI) services
MUST be run ONLY from native MS-DOS mode with an expanded memory manager (like
MS EMM386.EXE loaded from CONFIG.SYS), because VCPI relies on the EMM386.EXE
EMS/XMS sharing scheme, even if expanded (EMS) memory is turned off by the
EMM386.EXE "NOEMS" switch.
Unfortunately Windows 95/98/ME do NOT supply VCPI support for DOS apps!
Origin Strike Commander needs VCPI (implicitly native MS-DOS mode) to start.
In such cases it is necessary to turn on "Single DOS mode" in your MS-DOS PIF
shortcut.
See "EXIT TO DOS" in TIPS95.TXT (included) for details:
http://www.mdgx.com/newtip10.htm#EXIT2DOS
Note that Microsoft REMOVED this feature from Windows ME!
See "MS-DOS PROMPT" in MYTIPS95.TXT (included) for details:
http://www.mdgx.com/lastweek.htm#MSDOSPROMPT
[386enh]
EMMExclude=B800-D3FF,F000-FFFF,A000-AFFF
EMMSize=0
NoEMMDriver=on
MUST keep the EMMExclude= line (but make sure it does NOT exclude the ENTIRE
UMA) because your video controller probably requires to use its own
properietary area(s) for proper operation. Example: the EMMExclude= line above
is OK. Then add this (similar) line (example):
EMMInclude=B000-B7FF,D400-EFFF
Available upper memory areas (UMAs) are displayed by running MSD [MicroSoft
Diagnostics tool = see MSD9X.TXT (included) for details] ONLY from native
MS-DOS: press M at main screen and scroll down to see black color coded
contiguous UMAs between addresses B000 - B7FF and D400 - EFFF (hex). These are
just examples, they may be different on your computer. Then add them on the
EMMInclude= line separated by commas (if more than 1).
Let Windows 9x/ME provide its own EMS management in DOS sessions: make sure it
is enabled: right-click on your MS-DOS PIF shortcut -> Properties -> Memory
tab -> "Expanded (EMS) memory" area should be Enabled.
See "BASIC *ESSENTIAL* MEMORY TIPS" further above for a list of DOS software
that needs EMS to operate.
A MUST for ALL Windows ME users running DOS based programs + games:
Microsoft REMOVED COMPLETELY the access to native/real/true/pure MS-DOS mode
from Windows Millennium Edition (ME), a.k.a. MS-DOS 8.00. :(
But you CAN get it back by applying the Unofficial WinME DOS Patch:
http://www.mdgx.com/dos.htm#ME
which modifies COMMAND.COM + IO.SYS (from C:\Windows\Command\EBD) +
REGENV32.EXE (from C:\Windows\System) to allow Windows ME to boot to native
MS-DOS and use DOS mode startup files (AUTOEXEC.BAT + CONFIG.SYS), Windows
95/98 style, to be able to use your (old) MS-DOS based apps/games that do NOT
work from within a Windows DOS session/box, and tweak your CUSTOM AUTOEXEC.BAT
+ CONFIG.SYS files to free MAXimum conventional DOS memory. :)
More info:
http://web.archive.org/web/20080501082722/http://thestarman.pcministry.com/DOS/DOSi
nWIN.html
______________________________________________________________________________
/TESTMEM:OFF loads HIMEM.SYS without taking a few extra seconds to test all
your system's extended memory [more RAM you have, longer the delay :)]. Most
modern Pentium class (and newer) computer BIOSes test the entire installed
memory at bootup anyway, making this HIMEM.SYS function obsolete.
See this MSKB troubleshooting article:
http://support.microsoft.com/kb/109845
/Q (QUIET) prevents the display of HIMEM.SYS loading status during bootup.
UNDOCUMENTED: See "HIMEM.SYS HIDDEN PARAMETERS" in SECRETS.TXT (included) for
details:
http://www.mdgx.com/secrets.htm#HIMEM
NOTE: HIMEM.SYS and EMM386.EXE (or similar 3rd party) memory managers MUST be
loaded in CONFIG.SYS with the DEVICE command, before ANY OTHER DEVICE,
DEVICEHIGH, INSTALL, INSTALLHIGH, SHELL or SET lines! The CONFIG.SYS: DEVICE,
DEVICEHIGH, INSTALL, INSTALLHIGH, and the AUTOEXEC.BAT LOADHIGH (LH for short)
commands are internal MS-DOS commands built into the OS (IO.SYS and
COMMAND.COM).
These are my "generic" EMM386 lines (examples) which provide expanded memory,
and accommodate almost ANY system with a standard:
DEVICE=C:\WINDOWS\EMM386.EXE X=EC00-ED00
The other method (which may work better on some systems) is to include the
regions above and below the grayed ROM area (using same example above):
DEVICE=C:\WINDOWS\EMM386.EXE X=C000-CFFF
DEVICE=C:\WINDOWS\EMM386.EXE X=D000-DFFF
DEVICE=C:\WINDOWS\EMM386.EXE X=F000-FFFF
DEVICE=C:\WINDOWS\EMM386.EXE X=C000-DFFF
DEVICE=C:\WINDOWS\EMM386.EXE X=F000-FFFF X=C000-CFFF
The "M3" switch loads EMM386's page frame at the C800 upper memory address
(hex). On my system this leaves maximum contiguous Upper Memory Blocks (UMBs)
available for loading devices/drivers/TSRs "high".
You can also "tell" EMM386 to load its page frame at a particular upper
memory address by using the FRAME= switch (example):
DEVICE=C:\WINDOWS\EMM386.EXE FRAME=C800
Better, by forcing EMM386 to provide expanded memory without a page frame,
you can free a little extra low/upper RAM, but ONLY IF your DOS apps/games
run properly this way (example):
DEVICE=C:\WINDOWS\EMM386.EXE FRAME=NONE
I tested this with Microprose's Civilization and Lucas Arts' X-Wing, but
other (older) DOS programs may refuse to start WITHOUT a page frame, in
which case you need to enable it.
TIP: Try to avoid the aggressive "HIGHSCAN" switch on your EMM386.EXE line!
It can be dangerous to your "health", as it may hang your machine at bootup!
Use the "RAM" and customized "I=xxxx-yyyy" switches instead, which do the
same job searching the Upper Memory Area (UMA) for unused UMBs (Upper Memory
Blocks).
The "D=256" switch allows for buffered I/O (In/Out) Direct Memory Access
(DMA), in KiloBytes (allowed: 16 - 256). Default is 32, which is NOT enough
in most cases, i.e. if you are using a sound card for DOS based programs.
Buffered DMA is required for ALL floppy/disk/IDE and ISA/PCI I/O operations.
The "A=64" switch specifies how many fast alternate register sets (for
multitasking) are allocated to EMM386 (allowed: 0 - 254). Default is 7.
Every alternate register set adds about 200 Bytes to EMM386's memory size.
The "H=128" switch specifies how many handles EMM386 can use (allowed:
2 - 255). Default is 64.
CAUTION:
Avoid using the EMM386.EXE "ALTBOOT" switch IF using ANY
SCSI/(U)DMA/ATAPI/(E)IDE/RAID add-in/3rd party/proprietary controllers! The
ROM addresses used by these adapters may CONFLICT with the memory address
used by the "ALTernative BOOT" routine, causing LOCKUPS!
FYI:
DOS based apps/games using VCPI (Virtual Control Program Interface) services
(i.e. Strike Commander) do NOT work from a Windows DOS box, because Windows
3.1x/95/98/ME DOS VM (Virtual Machine) does NOT provide VCPI support.
If you get an error message like:
"PROGRAM.EXE cannot communicate with the EMS Memory Manager"
you need to run such programs from native/real/true/pure MS-DOS mode
OUTSIDE Windows, with an EMS memory manager (like EMM386.EXE, QEMM386.SYS,
RM386.EXE etc) with VCPI enabled, loaded from your CONFIG.SYS.
TIP:
If EMM386.EXE loads from a CONFIG.SYS DEVICE line, ALL these parameters:
I=xxxx-yyyy, X=xxxx-yyyy, NOEMS, Mx, Pnnnn and FRAME take precedence over
these Windows 3.1x/95/98/ME SYSTEM.INI settings under the [386enh] section:
EMMInclude=xxxx-yyyy, EMMExclude=xxxx-yyyy and EMMPageFrame=xxxx.
To enable these EMS settings in Windows you need to remove these switches
from your CONFIG.SYS EMM386.EXE line, or REMark with a semicolon (;) the
entire EMM386.EXE DEVICE line, and then reboot.
See "SYSTEM.INI TWEAKS" in MYTIPS95.TXT (included) for more details:
http://www.mdgx.com/lastweek.htm#SYSINI
You can fiddle with the "/L:1", "/L:2", "/L:3" etc... switches to determine
your own best upper memory loading configuration. This example:
DEVICEHIGH /L:1=C:\WINDOWS\COMMAND\ANSI.SYS
loads the ANSI.SYS DOS CONsole driver in Upper Memory Area (UMA) region 1
(located on my system between B000 and B7FF hex addresses). You can use any
ANSI driver that supports extended keys (F1-F12) remapping.
I recommend Daniel Kegel's NANSI.SYS v4.0d MS-DOS ANSI CONsole driver
accelerator: fastest and most versatile replacement for Microsoft ANSI.SYS,
with built-in support for key reassignment [63 KB, free GPL]:
http://ericauer.cosmodata.virtuaserver.com.br/soft/by-others/nansi40d.zip
More info:
http://www.kegel.com/nansi/
NANSI.SYS (faster) takes only 3.2 KB of upper DOS memory IF loaded with
"DEVICEHIGH" in CONFIG.SYS, compared with Microsoft ANSI.SYS (slower) which
occupies 4.2 KB of RAM.
To find out what you can do with an ANSI driver loaded, see "F1-F12
Remapping = MS-DOS Mode + ANSI Driver" in DOSTIPS.TXT (included).
This means that my MS-DOS mode MOUSE.COM driver loads in the 2nd upper
memory region, located between C800 and EFFF (hex addresses) on my system
(the upper memory regions are delimited by the extended/expanded memory
managers (EMM386.EXE), respectively the I=xxxx-yyyy and E=xxxx-yyyy
switches, when using the Microsoft HIMEM.SYS and EMM386.EXE "combo").
Example of EMM386.EXE line, to enable two upper memory regions in the Upper
Memory Area (UMA):
In this case:
- the first upper memory area is called region 1, located at the B000-B7FF
hex addresses, enabled by the "I=B000-B7FF" EMM386.EXE switch above, and
- the second upper memory area is called region 2, located at the C800-EFFF
hex addresses, enabled by the "I=C800-EFFF" EMM386.EXE switch above.
These 2 upper memory regions are available for loading devices/drivers/TSRs
"high", using the CONFIG.SYS "DEVICEHIGH" and the AUTOEXEC.BAT "LOADHIGH"
(abbreviated to "LH") commands.
A MUST:
THE EMM386.EXE LINE MUST FOLLOW THE HIMEM.SYS LINE IN CONFIG.SYS!
ALL other "DEVICE", "DEVICEHIGH", "INSTALL" and "INSTALLHIGH" lines MUST
follow the HIMEM.SYS and EMM386.EXE commands in CONFIG.SYS!
I gave up on using the limited MS-DOS MemMaker utility (or the similar QEMM's
Optimize or NetRoom's Customiz tools for that matter) to gain more
conventional memory, in favor of manually tweaking my startup files. ;)
I modified the memory manager lines/parameters in CONFIG.SYS (and changed the
order of loadind devices/drivers in CONFIG.SYS + AUTOEXEC.BAT), BUT ONLY
AFTER reading ALL related documentation for each of the 5 memory managers I
have used: MicroSoft's HIMEM.SYS + EMM386.EXE, Quarterdeck's QEMM386.SYS,
Helix's NetRoom RM386.EXE, Lineo DR-DOS' EMM386.EXE, and Uwe Sieber's
UMBPCI.SYS, and then experimenting with all possible configurations (more
devices you load, more combinations you have to try).
This is a time consuming job, but rewarding, because I managed to make ALL
my DOS and Windows programs work with these final configurations found in my
startup files: CONFIG.SYS + AUTOEXEC.BAT (included):
http://www.mdgx.com/mem7.htm
Rewarding, because I have now 625 KB of free conventional memory, and enough
upper memory for Windows, with expanded memory enabled, in MS-DOS mode
(outside Windows), to run ANY DOS hungry program/game without EVER running
out of low DOS memory [that was an old obsession for any DOS user :)], or EVER
needing to reboot again, or using "custom setups" for different program
requirements.
SWITCHES=/F skips the 2 second delay before processing the startup files
(CONFIG.SYS + AUTOEXEC.BAT) during bootup, valid for MS-DOS
6.xx and Windows 9x/ME (a.k.a. MS-DOS 7.xx/8.00). This command
MUST be loaded from CONFIG.SYS as the FIRST line.
SWITCHES=/E:288 use this switch ONLY in Win95/98's CONFIG.SYS. Moves ONLY 288
Bytes of Extended BIOS (EBIOS) to the conventional memory
area. Valid values for /E: = 48 - 1024.
You may gain up to 1 KB of conventional RAM by using this
switch. In order to adapt the /E: switch to your system, a
little try-and-error is necessary. Increase the /E: value
starting with 64, in 16 Bytes increments at a time, and reboot
each time, until you get your best free low RAM result,
displayed by running "MEM /C/P" from native MS-DOS prompt,
outside Win95/98 GUI.
You can also use the plain /E parameter without any numbers for better
compatibility:
SWITCHES=/E /F
Use them both on the SAME line (you can have ONLY one SWITCHES line in your
CONFIG.SYS). Their order doesn't matter. Example:
SWITCHES=/E:288 /F
DOS=HIGH,UMB loads the DOS kernel high and provides UMBs (Upper Memory
Blocks) for loading DOS devices/drivers/TSRs in UMA (Upper
Memory Area).
Windows 9x/ME has added another useful switch: AUTO (or NOAUTO) to the "DOS="
line in CONFIG.SYS:
DOS=HIGH,UMB,NOAUTO
or:
DOS=HIGH,UMB,AUTO
or (multiple "DOS=" lines allowed):
DOS=HIGH
DOS=UMB
DOS=NOAUTO
DOS=AUTO
Win95/98/ME OS can move the FILES, STACKS, LASTDRIVE + FCBS to the upper
memory area (UMA), the 384 KB RAM region above the 640K low memory barrier.
The BUFFERS are moved to the High Memory Area (HMA), the first 64 KB of RAM
above the 1st MegaByte. These features are implemented in the Win9x OS and can
be achieved by adding these lines to the beginning of CONFIG.SYS.
The values below are ONLY my own examples, and you should change them to suit
your OWN needs:
DOS=HIGH,UMB,NOAUTO
BUFFERSHIGH=10,0
FILESHIGH=60
LASTDRIVEHIGH=H
FCBSHIGH=1,0
STACKSHIGH=0,0
Or go with the "conservative" version: [let the OS do the work for you :)]
DOS=HIGH,UMB,[AUTO]
BUFFERS=11,0
FILES=60
LASTDRIVE=H
FCBS=1,0
STACKS=0,0
The "AUTO" switch is not necessary [it's the default :)]. By using "AUTO" you
may free 256 - 512 Bytes of low memory opposite to using "DOS=NOAUTO" and the
"HIGH" switch added to each of the lines above: BUFFERS, STACKS, FILES, FCBS +
LASTDRIVE.
FCBS=x,y short for File Control BlockS [obsolete]. Use 1,0 (1 for x and
0 for y) to preserve memory (minimum allowed). Higher values
are needed only by older DOS programs. It is very probable
that you'll never need more than that. If the FCBS line is
absent from CONFIG.SYS, MS-DOS loads the default value of 4,0.
Newer programs use the "FILES" setting instead (see below).
Valid values for x = 1 - 255.
FILES=n where "n" MUST be at least 40 to have your Windows and CPU
intensive DOS apps/games "behave" properly (open multiple
files at the same time). If this line is not specified, the
default "FILES" are set to 30 (Win95/OSR2) or 60 (Win98/ME) at
bootup. Set "FILES" to at least 60 - 80 in your CONFIG.SYS to
play safe! Valid values for n = 8 - 255.
ADD-ON:
If using any DOS apps/games in DOS sessions within Windows, you can increase
the number of files available to programs running in DOS boxes by adding this
line under the [386enh] section of your SYSTEM.INI file, located in your
Windows directory:
PerVMFiles=60
See "SYSTEM.INI TWEAKS" in MYTIPS95.TXT (included) for more details:
http://www.mdgx.com/lastweek.htm#SYSINI
Edit SYSTEM.INI with EDIT.COM in DOS or Notepad/Sysedit in Windows.
FYI:
- MSKB: All Windows 9x/ME [a.k.a. MS-DOS 7.xx/8.00] documented CONFIG.SYS
commands + parameters:
http://support.microsoft.com/kb/234853
- Use Notepad to read the CONFIG.TXT file in your Win9x/ME folder.
- MS-Dos7 Commands:
http://www.lagmonster.org/docs/DOS7/
Generic CONFIG.SYS line for your CD-ROM, CD-R(W), DVD-ROM, DVD-R(W), DVD-RAM
MS-DOS mode device driver:
DEVICEHIGH=C:\path\YOUR_CDROM_DRIVER.SYS /D:YOUR_CDROM_NAME
DEVICEHIGH=C:\path\ASPIDOS.SYS
and/or:
DEVICEHIGH=C:\path\ASPIHLP.SYS
and:
DEVICEHIGH=C:\path\ASPICD.SYS /D:MYCDROM
Note that all Windows 98/98 SE/ME releases can create bootable floppy
diskettes with CD/DVD support.
See "CD-ROM DRIVERS 4 DOS" in MYTIPS95.TXT (included) for more details on
CD/DVD DOS mode drivers and (in)compatibilities:
http://www.mdgx.com/newtip1.htm#CDROM4
See "FREE WinDOwS CD/DVD Drivers + Tools" in SOFTWARE.TXT (included) for
download links:
http://www.mdgx.com/drv.htm#CDR
You also NEED to load MSCDEX.EXE in your AUTOEXEC.BAT, for your CD/DVD drive
to be recognized by the system in native/real/true/pure MS-DOS mode.
Typical MSCDEX line:
NOTE: The CD-ROM drive name specified with the /D:XXXXXXXX switch on your
MSCDEX line may NOT exceed 11 characters (case insensitive), and you canNOT
use spaces or special/punctuation symbols!
The command line below loads Windows 3.1x/9x/ME 32-bit (Fast) Disk access
legacy support device driver (IFSHLP.SYS = Installable File System Helper),
MANDATORY for ALL Windows releases beginning with 3.0 (except NT, 2000, XP
and 2003), to enable compatibility with the underlying MS-DOS FAT system:
DEVICEHIGH /L:1=C:\WINDOWS\IFSHLP.SYS
You could use any other 3rd party (retail) memory manager on the market:
Symantec (Quarterdeck) QEMM 9.00/8.0x, McAfee (Helix) NetRoom 3.0x, Lineo
(Caldera) DR-DOS 7.0x, IBM (Qualitas) 386MAX 8.0x etc, with similar (or even
BETTER) results, but you are likely to provide LESS compatibility for your
DOS/Windows programs, than by using Microsoft's own (already included with
your OS) HIMEM + EMM386 "combo", especially if using some of the advanced
memory management tools provided by these pay-for utilities.
Try NOT to use ANY special 3rd party memory management features (i.e.
QEMM's "Stealth", or NetRoom's "VidCloak"/"SysCloak") that move the Video
ROM and/or the Extended ROM BIOS to upper/extended memory or above the 1st
Meg! Windows is not very "happy" about these "moves"! Certain DOS programs
are also "allergic" to these advanced "features" and your machine may lockup
unexpectedly!
I also urge you to use the MS-DOS internal "DEVICEHIGH" (in your CONFIG.SYS)
and "LOADHIGH" ("LH" for short in your AUTOEXEC.BAT) commands to load
devices, drivers and TSRs high, instead of the 3rd party memory managers'
external upper memory "loaders" (like QEMM's "LOADHI" or NetRoom's "XLOAD"),
to provide BETTER compatibility. Some of these "loaders" may interfere with
certain programs proper operation, thus leading to system crashes!
provided you have a copy of COMMAND.COM in your boot drive's root folder
(C:\ is default).
See "2 DOS OR NOT 2 DOS" in MYTIPS95.TXT (included) for more details:
http://www.mdgx.com/last3.htm#DOS2DOS
You can have the COMMAND.COM file anywhere on your local drives/partitions,
just mention its path on the SHELL= line in your CONFIG.SYS. Example:
But BEWARE that certain (older) DOS programs expect to find the command
interpreter (COMMAND.COM) in C:\ root [default location], and may FAIL to work
properly if they don't!
If you don't specify an /E: switch value of 1024 or smaller, Win95/98 will set
it to 2048 by default, which is usually larger than needed by most, and that
will take a LOT of your valuable upper (and in some cases conventional) memory
space.
FYI:
You rarely need a SHELL environment size larger than 1024, and that may happen
only if using many and/or long SET <variable> environment lines in your BATch,
AUTOEXEC.BAT and/or CONFIG.SYS files. In such cases COMMAND.COM will display
this error message:
"Out of environment space"
and then abort.
How to fix "Out of environment space" errors:
- Windows 95/98:
http://support.microsoft.com/kb/230205
- Windows ME:
http://support.microsoft.com/kb/261825
If the SHELL line is NOT present in your CONFIG.SYS, Windows 95/98 loads its
GUI (Graphical User Interface) automatically after processing the CONFIG.SYS
+ AUTOEXEC.BAT files at bootup, and sets a default evironment size of 2048,
even if the line "BootGUI=0" is present in your MSDOS.SYS file under the
[Options] section.
The purpose of starting Win95/98 on demand (and NOT automatically right
after processing the startup files) is if you'd like to have a custom
Win9x startup, by starting Windows let's say from a DOS batch file, or from
AUTOEXEC.BAT (by adding WIN as the last line), after you eventually "play"
in native MS-DOS [SVGA DOS games anyone? :)], or/and if you use the dual-boot
feature implemented into the Win95/98 OS to boot into MS-DOS 6.xx.
* To load devices/drivers high, you can also use the CONFIG.SYS specific
INSTALLHIGH command, available ONLY in MS-DOS 6.xx and Windows 95/98/ME.
INSTALLHIGH is needed ONLY IF you have ANY drivers/TSRs that:
- have problems loading from AUTOEXEC.BAT (eventually using the LOADHIGH
command),
- or need to load earlier (or before other drivers/TSRs) in the boot sequence.
Example of such CONFIG.SYS line:
INSTALLHIGH=C:\MOUSE\MOUSE.COM <YOUR_MOUSE_DRIVER_PARAMETERS>
* Lines you might need in your AUTOEXEC.BAT, valid for both Windows 9x
[a.k.a. MS-DOS 7.xx] and MS-DOS 6.xx + Windows/WfWG 3.1x:
NOTE: Always use the most recent MSCDEX.EXE release: the newest is 2.25,
included with MS-DOS 7.xx/8.00 [a.k.a. Windows 9x/ME], very similar with the
not so old version 2.23, bundled with MS-DOS 6.xx.
SMARTDRV 2048 16 A+ C+ D /N
I presumed that A is your 3.5 inch floppy drive, C is your hard drive, and D
your CD/DVD drive. Change/add drive letters if different on your system.
Load Smartdrv ONLY AFTER the MSCDEX line, if you want your CD/DVD drive to be
cached in true MS-DOS mode!
Run:
SMARTDRV /?
from any DOS prompt to see all available Smartdrv parameters, and to learn
how to adapt it to your system.
A MUST: For more details on how to tailor the SMARTDRV line to your needs and
to master its little known parameters (/B:xxxxx and /E:xxxxx), see
"OUTSMART SMARTDRIVE" in MYTIPS95.TXT (included):
http://www.mdgx.com/newtip2.htm#OUTSMART
NOTE: If you run ANY DOS programs/games OUTSIDE Win95/98 (i.e. in "Command
prompt mode"), Smartdrv IS A MUST, customized to cache ALL read and write
disk operations on ALL your drives!
SMARTDRV 2048 16 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 hard disk (drive C) reads and writes, including the floppy
(drive A) and the cd-rom (drive D).
WARNING:
Use the "N" switch with CAUTION: this allows returning to the command prompt
BEFORE ALL data is written back to disk from SMARTDRV's memory buffer (the
cache does NOT flush), which may generate data loss if the computer shuts off
unexpectedly!
FYI: If you don't use ANY DOS mode programs/games, DO NOT load Smartdrv,
because if properly configured Win9x/ME loads its own 32-bit disk cache!
Smartdrv only takes extra memory.
But if you find that besides having enough room in memory (preferably in
upper) to spare, Windows loads faster (as it does on my PC, since I'm
starting Windows from a huge DOS batch file) with Smartdrv loaded, then
ENABLE it in your AUTOEXEC.BAT.
My Windows startup batch file (W9X.BAT) is included here. You can view its
contents with Notepad.
SET MOUSE=C:\MOUSE
is required to read the MOUSE.INI parameters upon loading, by the majority of
DOS mouse drivers out there, by most DOS programs, and by most Windows
3.xx/9x virtual mouse drivers, too.
Use:
LOADHIGH=C:\MOUSE\MOUSE <YOUR_MOUSE_DRIVER_PARAMETERS>
to load your DOS mode mouse driver from AUTOEXEC.BAT. You need it with Win9x
ONLY IF you run ANY DOS programs/games that use a mouse OUTSIDE the Windows
GUI, in native MS-DOS (using the "Command prompt mode only" option from the
Startup Menu). This allows your DOS mouse driver to load the custom settings
from the MOUSE.INI initialization file located in the directory specified by
the "SET MOUSE=" line (C:\MOUSE in this case).
Change the DOS mouse driver's directory if different and adapt its parameters
to your own mouse driver/hardware specifications.
If you never use DOS programs outside Windows in real MS-DOS mode, remove
these lines pointing to your DOS mouse driver from your AUTOEXEC.BAT (or
CONFIG.SYS in some cases, if you use any MOUSE.SYS devices instead).
Example of .SYS mouse driver loaded from CONFIG.SYS:
DEVICEHIGH=C:\MOUSE\MOUSE.SYS <YOUR_MOUSE_DRIVER_PARAMETERS>
LogiTech Mouse drivers require this SET line (example) to point to the
location of MOUSEDRV.INI (LogiTech mouse initialization file):
SET LMOUSE=C:\MOUSE
instead of the default "SET MOUSE=" line. Add it to your AUTOEXEC.BAT if you
use LogiTech mouse drivers.
SET MSINPUT=C:\MOUSE
Killer Replacements
DOS text mode video BIOS accelerator ZENO174.EXE v1.74 = DOS text mode
= NOT provided! video BIOS accelerator (public
domain): 1 KB of upper DOS mem.
Fast!
IMPORTANT:
*READ* each program's provided documentation *FIRST* for proper usage!
... And here are my CONFIG.SYS + AUTOEXEC.BAT lines (ONLY AS EXAMPLES!) for
all devices, drivers + TSRs listed above, tested and used successfully ONLY on
my PCs (see "BASIC *ESSENTIAL* MEMORY TIPS" further above), using MY OWN
CUSTOM system SETTINGS: directory NAMES, CPU, ROM BIOS, Video BIOS,
motherboard chipset, hard disk controller BIOS etc.
CAUTION:
You NEED to adapt them to YOUR OWN system to make them work PROPERLY, and
BEWARE that some MAY NOT work with YOUR particular hardware/software/OS
"combo":
- XMSDSK.EXE v1.9i creates here a 40 MB RAM disk (F) in extended (XMS) memory
(loads itself high if UMA is available) in CONFIG.SYS:
INSTALL=C:\MAX\XMSDSK.EXE 40960 F: /T /Y
or in AUTOEXEC.BAT:
C:\MAX\XMSDSK.EXE 40960 F: /T /Y
You MUST load XMSDSK.EXE BEFORE your CD-ROM Extensions driver (MSCDEX.EXE,
SHSUCDX.COM, NWCDEX.EXE etc) in CONFIG.SYS or AUTOEXEC.BAT to avoid CD/DVD
drive letters SHIFTING!
See "BROWSER CACHE IN MEMORY" in REGISTRY.TXT (included) for more details:
http://www.mdgx.com/newtip12.htm#CACHRAM
XMSDSK.EXE [74 KB, freeware]:
http://www.uwe-sieber.de/files/xmsdsk.zip
XMS/EMS RAMdisk v1.9i with installer/uninstaller for Windows 9x/ME [114 KB,
freeware]:
http://www.mdgx.com/files/RAMDRIVE.EXE
- HYPERKEY.EXE v4.70 (loads itself high with the "XS" switch if UMA enabled)
in CONFIG.SYS:
INSTALL=C:\MAX\HYPERKEY.EXE XS A:+ C:1 C:- CR:- D:300 H:127 KW:- L:1 P:30 R:30 W:+
OK:- OX:+
or in AUTOEXEC.BAT:
C:\MAX\HYPERKEY.EXE XS A:+ C:1 C:- CR:- D:300 H:127 KW:- L:1 P:30 R:30 W:+ OK:- OX:
+
in combination with Microsoft MODE.COM (uses NO memory) in AUTOEXEC.BAT:
MODE.COM CON: RATE=32 DELAY=1
for FASTEST keyboard response in ALL DOS modes.
HYPERKEY.EXE [15 KB, no nag shareware]:
http://www.mdgx.com/files/HYPRKEY.ZIP
Notes + Wrap-Up
* In case not using a really old computer (486DX or even older) there is a
good chance you won't need SETVER.EXE loaded from your CONFIG.SYS.
ONLY IF you determined you do NOT need SETVER.EXE: you're NOT using ANY older
IBM or ANY other 3rd party ESDI/IDE/ATA hard disk drivers, older 3rd party
disk compression tools (other than Microsoft DblSpace/DrvSpace), or ANY older
DOS Network drivers, delete (BUT BACKUP FIRST!) the SETVER.EXE file from your
Windows folder (C:\WINDOWS is default location), and REMark with a semicolon
(;) this CONFIG.SYS line (example):
; DEVICE=C:\WINDOWS\SETVER.EXE
If you'll need it later on, you can always extract the file SETVER.EXE from
your Windows 9x Setup CD-ROM (drive D used below) or floppies (usually drive
A) to your Windows folder, by running (example):
- Win95/OSR1/OSR2 CD-ROM:
EXTRACT D:\WIN95\WIN95_09.CAB %winbootdir%\SETVER.EXE
- Win98/98 SP1/98 SE CD-ROM:
EXTRACT D:\WIN98\WIN98_42.CAB %winbootdir%\SETVER.EXE
and then reenable its CONFIG.SYS line, by removing the preceding semicolon
(example):
DEVICE=C:\WINDOWS\SETVER.EXE
These operations must be performed from native/real/true/pure MS-DOS mode
outside Windows GUI.
More info @ MS TechNet:
http://technet.microsoft.com/library/bb490782.aspx
[SafeList]
cacheclk.exe ; Helix Cloaked Disk Cache
Text after the semicolon (;) is ignored and used for comments.
IOS.INI is a text file located in your Win9x/ME folder, you can edit with
Notepad in Windows or EDIT.COM in DOS.
See "IOS.INI TWEAKS" in MYTIPS95.TXT (included) for details!
Get Helix Multimedia Cloaking [200 KB, last release, discontinued!]:
http://www.mdgx.com/files/CDX.ZIP
* I primarily use Cute Mouse v2.1 16-bit Mouse Driver for DOS, which works
with all Microsoft, LogiTech, Mouse Systems and compatible serial + PS/2
mice/trackballs [50 KB, free GPL]:
http://cutemouse.sourceforge.net/
mostly for speed, as this is the FASTEST DOS mouse driver available!
CTMOUSE.EXE uses only 3.3 KB of upper DOS RAM (upper memory manager required
in CONFIG.SYS).
The AUTOEXEC.BAT LOADHIGH command (LH for short) is not needed, because
CTMOUSE loads itself "high". Example:
C:\MAX\CTMOUSE.EXE /R44
* I also use LogiTech/Helix MouseWare Cloaked Mouse Driver for DOS, which
works with most LogiTech, Microsoft and compatible serial + PS/2
mice/trackballs [free]:
- MOUSE.EXE v8.50 [200 KB]:
http://www.mdgx.com/files/CDX.ZIP
also part of LogiTech MouseWare v9.73 [4.96 MB]:
http://www.logitech.com/pub/techsupport/mouse/mw9731enu.exe
- CLOAKING.EXE v1.02 [200 KB]:
http://www.mdgx.com/files/CDX.ZIP
MOUSE.EXE uses 1 KB of upper DOS RAM and 54 KB of extended RAM ONLY IF
CLOAKING.EXE loads FIRST with LOADHIGH in AUTOEXEC.BAT (upper memory manager
required in CONFIG.SYS). Example:
LOADHIGH=C:\HELIX\CLOAKING.EXE
LOADHIGH=C:\MAX\MOUSE.EXE AHIGH S04
WARNING: MOUSE.EXE may generate conflicts/errors with certain Windows
3.1x/9x/ME setups!
IMPORTANT:
For details about using your 3rd party memory manager with MS-DOS 5/6/7/8 + MS
Windows 3.xx/9x/ME *READ* the provided documentation: HIMEM, UMBPCI, HIRAM,
EMM386, QEMM, RM386, 386MAX, BlueMax, CEMM etc!
See "95/98/ME SETUP + MEMORY MANAGERS" in MYTIPS95.TXT (included) for details:
http://www.mdgx.com/newtip20.htm#9SMM
FYI: With all TSRs/devices/drivers loaded in upper memory you may be able to
"squeeze" a MAXimum of 625-629 KB FREE conventional memory in native MS-DOS
mode outside Windows, without using ANY 3rd party memory management special
features. You'll NEVER need more than 620 KB of free "low" RAM to run ANY DOS
program/game created in the past few years anyway. ;)
Have fun.
______________________________________________________________________________