Table of Contents
Advertisement
Application Size Considerations
DOS applications often include an entire support infrastructure with them (aside from DOS
and BIOS calls, and various APIs supplied by TSRs). The need to include graphics support
code within DOS applications results in large, sophisticated, graphical DOS programs. This
often means that multiple applications carry multiple copies of such code. Some DOS
development systems allow applications to share code, but that is the exception. Where
possible, make use of shared code to save memory.
Matching Software Requirements to the Hardware
Available
In this chapter, we've discussed issues specifically related to ROM disk, RAM disk, and
applications. How does all of this information fit together?
There are a number of ways to configure your application based on the amount of Flash and
RAM as detailed below.
The configuration is set up as follows:
t
0.5 MB, 2.5 MB, or 4.5 MB Flash
t
2 or 4 MB RAM
t
DOS, TSRs, application(s), and constant data are stored in ROM Disk.
t
PDT 3400 boots from ROM Disk.
To meet additional software and data storage needs:
t
Use Stacker to compress the ROM Disk and extend program and constant data
storage
t
Add additional Flash (up to 4.5 MB) to meet program and constant data storage
needs
t
Use Stacker to compress the RAM Disk
t
Use EMSALLOC.SYS to reapportion the amount of RAM memory used for DOS
and as EMS memory used for RAM disk storage. Refer to the description of
EMSALLOC.SYS in the section Symbol-Provided Drivers in Chapter 5 for more
information on reapportioning RAM memory.
Terminal Configuration Issues
4-3
Advertisement
Table of Contents
