home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
utility
/
dos5gbag.zip
/
DOS5.ZIP
/
DOS5QE.TXT
< prev
next >
Wrap
Text File
|
1991-06-18
|
7KB
|
210 lines
This document details my experiences installing MS-DOS v5.0 and
configuring to use QEMM 5.11 with it. It took me the better part
of the last week to get it all straight. Including are my results,
reflections, and speculations along with input from the message
traffic over the last week in the MSDOS (Microsoft DOS 5) and
PCVENB SS 1 (Quarterdeck) CIS forums.
Environment: Everex OEM 386/20 with AMI bios, 9 Mb ram, 80 Mb hard
drive.
Objective: a) To maximize DOS ram (conventional memory, tpa).
b) To load residents into high DOS ram (upper memory area).
c) To have some expanded ram available for DOS applications.
d) A suitable environment for Windows 3.00/3.00a.
(The following file examples are reduced to the essentials.)
1) Starting Point: Compaq DOS 3.31 w/QEMM 5.11
CONFIG.SYS
device=c:\qemm\qemm386.sys extmem=1024 exclude=a000-bfff ram=c800-dfff rom
device=c:\qemm\loadhi.sys /r:1 c:\windows\ramdrive.sys 1024 512 256 /e
device=c:\qemm\loadhi.sys /r:1 c:\bin\vansi.sys
stacks=0,0
buffers=1
files=10
break=on
lastdrive=f
shell=c:\command.com /e:384 /p
AUTOEXEC.BAT
@echo off
set comspec=C:\COMMAND.COM
path C:\BIN;C:\DOS;C:\WORD5;C:\WINDOWS;C:\WINWORD;C:\WS;F:\; (cont.)
D:\C600\BINB;D:\C600\BIN
c:\qemm\loadhi /r:1 c:\qemm\buffers=30
c:\qemm\loadhi /r:1 c:\qemm\files +20
c:\qemm\loadhi /r:1 c:\bin\mouse
c:\qemm\loadhi ... etc.
set include=D:\C600\INCLUDE
set ... etc.
prompt $P$G
echo on
Available Memory
DOS ram 606352
High DOS ram 96K
Notes
a) qemm386.sys
- put aside 1024K for ram disk
- keep qemm out of video area
- limit high DOS ram area (ems page frame will be at E000)
- map video rom and bios to fast ram
b) autoexec.bat
- load residents before 'set' statements to minimize environment
size of each loaded resident
2) Mid Point: MS-DOS 5.0
CONFIG.SYS
device=c:\dos\setver.exe
device=c:\dos\himem.sys
device=c:\dos\emm386.exe 3072 m9 ram
dos=high,umb
devicehigh=c:\dos\ramdrive.sys 1024 512 256 /e
devicehigh=c:\bin\vansi.sys
buffers=30,8
files=30
break=on
lastdrive=f
shell=c:\command.com /e:384 /p
AUTOEXEC.BAT
@echo off
set comspec=C:\COMMAND.COM
path C:\DOS;C:\BIN;C:\WORD5;C:\WINDOWS;C:\WINWORD;C:\WS;F:\; (cont.)
D:\C600\BINB;D:\C600\BIN
loadhigh c:\bin\mouse
loadhigh ... etc.
set dircmd=/L/W/O:N/P
set include=D:\C600\INCLUDE
set ... etc.
prompt $P$G
echo on
Available Memory
DOS ram 623328
High DOS ram 96K
Notes
a) emm386.exe
- set aside 3Mb expanded memory (this is optional)
- force ems page frame buffer to E000 (m9)
[The AMI bios uses areas of the E000-EFFF address space for
initialization and fools emm386.exe into thinking that this area is
unavailable costing 64K of high DOS ram. (386MAX has a similar
problem costing 12K of this space.) An include statement
(i=E000-EFFF) added to the ems386.exe command line will reclaim
this space. The 'm9' statement accomplishes the same thing and by
forcing the page frame buffer to E000 makes the upper memory buffer
area a contiguous 96K.]
- enable ems and high DOS ram (ram)
- use 'noems' rather than 'ram' if you don't want ems but want to
use high DOS ram
- [Note that some people are advocating using both 'ram' and 'noems'
to allocate the page frame buffer area but to allocate no ems memory.
The theory is to make the page frame buffer available for running DOS
applications which use EMS under WIN 3.0 and to avoid filling the upper
memory buffer area with residents thus using up the area necessary for
the 64K page frame buffer. (This possibility of this situation occurring
was not a problem before DOS 5.0). Have seen no Microsoft comment on
this and don't know if it is an acceptable or even necessary practice;
however, it does make sense.]
b) dos=high,umb
- load dos into HMA and enable high DOS ram (upper memory buffers)
3) End Point: MS-DOS 5.0 w/QEMM 5.11
CONFIG.SYS
device=c:\dos\setver.exe
device=c:\qemm\qemm386.sys extmem=1024 exclude=a000-bfff (cont.)
ram=c800-dfff rom nohma
device=c:\qemm\loadhi.sys /r:1 c:\dos\ramdrive.sys 1024 512 256 /e
device=c:\qemm\loadhi.sys /r:1 c:\bin\vansi.sys
dos=high
stacks=0,0
buffers=30,8
files=10
break=on
lastdrive=f
shell=c:\command.com /e:384 /p
AUTOEXEC.BAT
@echo off
set comspec=C:\COMMAND.COM
path C:\DOS;C:\BIN;C:\WORD5;C:\WINDOWS;C:\WINWORD;C:\WS;F:\; (cont.)
D:\C600\BINB;D:\C600\BIN
c:\qemm\loadhi /r:1 c:\qemm\files +20
c:\qemm\loadhi /r:1 c:\bin\mouse
c:\qemm\loadhi ... etc.
set dircmd=/L/W/O:N/P
set include=D:\C600\INCLUDE
set ... etc.
prompt $P$G
echo on
Available Memory
DOS ram 633168
High DOS ram 96K
Notes
1) qemm386
- WIN 3.00a would not run until the 'nohma' statement was inserted
telling QEMM to consider the HMA area already allocated.
- I normally don't use DesqView. If you use DesqView, omit the
'nohma' statement and do not load DOS high (omit 'dos=high statement).
- With DOS 5.0, the QEMM buffers.com utility does not work and is
not necessary.
General Notes
1) In all of the above examples, ALL residents are loaded into high
DOS ram. 96K is adequate for most purposes. For the adventuresome,
QEMM386 and 396MAX are capable of ferreting out additional high DOS
ram. Use this option with care. QEMM's analysis feature is useful
for determining which additional memory areas are really available.
2) The advantages of using QEMM with DOS 5.0 are obvious.
- Additional DOS ram and additional high DOS ram can be squeezed out.
- Management of extended and expanded memory is more flexible and
more transparent to the user.
- Manifest and the other analysis tools are better than the DOS MEM
utility.
2) Use FASTOPEN and SMARTDRV.SYS if you wish. Map them into high DOS
ram. Read the DOS 5.0 manual (pp. 302-305) on the merits of each.
3) QEMM 5.12 and 5.13 should work as above.
4) Note patches for QEMM 5.11 in PCVENB DL 1 - WIN30A.PAT, RALLOC.PAT and
FUNC24.PAT. I had to make the WIN30A patch to run WIN 3.00a in standard
mode with QEMM 5.11. I have not had the need for the other patches. Also
note that there is an updated version of WINHIRAM.VXD in PCVENB DL 1. QD
Tech Support said that this file is the same as that shipped with QEMM
5.11; however, it does differ from the WINHIRAM.VXD that I received with
QEMM 5.11.
5) Manifest 1.0 does not work with DOS 5.0. Version 1.01 is required.
6) Notes on upgrading to QEMM 5.13 (which includes Manifest 1.01)
(513233.TXT) and DesqView 2.34 (DVDOS5.TXT) are available in PCVENB DL 1.
7) Thank you, Microsoft, for MS-DOS 5.0!
Disclaimer - The above suggestions are mine and carry no approval or
concurrence from either Microsoft or Quarterdeck Office Systems.
17 June, 1990 Jim Byram
71715,1124