Chapter 4 (b1) - The [MemMakerData] Section.  

The [MemMakerData] section is the first section in the MEMMAKER.STS file. It contains information 
about the current state of the optimization process and your computer’s memory configuration. The 
following is an example of a [MemMakerData] section:
  
[MemmakerData]
State=     DONE 2283
AvailConvMemoryBefore=481696
AvailUpperMemoryBefore=66448
UsedUpperMemoryBefore=59504
WindowsUpperMemoryBefore=0
EMSUpperMemoryBefore=0
AltSysFiles=False
WindowsXlat=False
CustomMode=True
AutoexecBatCheckSum=28495 
ConfigSysCheckSum=40673 
SystemIniCheckSum=0     
WindowsLocation=E:\WIN
  
The following sections explain each field in the [MemMakerData] section.

State
The State field describes the current state of the optimization process. This field is always the first in 
the MEMMAKER.STS file. The State field uses the following syntax:

State=     CurrentState SessionID
The CurrentState variable indicates the current state of the MemMaker optimization process. For a list 
of possible CurrentState values, see the following tables.
The SessionID is a unique number generated by MemMaker and later used as a startup parameter. 
MemMaker uses the SessionId number to verify that the correct file is being accessed.
The following table lists values for the CurrentState variable that indicate normal processing.
  
Value	Current state of optimization process

SR1	MemMaker is about to restart your computer in order to measure the size in memory of each 
device driver and memory-resident program.

SR2	Your computer has restarted, and MemMaker is about to begin the sizing process (measuring 
the size of each memory-rsesident driver or program). State SR2 indicates that the highscan option for 
EMM386 is enabled. It can be entered only from state SR1.

SR3	MemMaker is about to begin the sizing process with the highscan option for EMM386 disabled. 
State SR3 can be entered from state SR1 if you chose Custom Setup and then disabled the highscan
option for EMM386 by answering No to the question “Scan upper memory aggressively?” State SR3 
can also be entered from state SR2 if you restart your computer while in state SR2 and then disable the 
highscan option.

SR4	The CHKSTATE.SYS device driver has loaded with state SR3.  This state indicates starting of 
sizing (with highscan disabled).

FR1	MemMaker has determined the optimum memory configuration, but has not yet made 
modifications to the CONFIG.SYS and AUTOEXEC.BAT files.  The user cannot reenter the sizing 
process (states SR1 through SR4) once state FR1 is reached.

FR2	The computer has restarted, and the CHKSTATE.SYS device driver has loaded and determined 
that the previous state was FR1.  Drivers and memory-resident programs are being loaded into their new 
locations in upper memory.

  
Value	Current state of optimization process

DONE	The optimization process has successfully completed.

UNDO/state	MemMaker has previously undone the changes it made. The /state parameter 
indicates  the state MemMaker was in before you chose to undo changes.
The CurrentState variable can also indicate that an error condition has occurred. The following table 
lists CurrentState values that indicate an error condition.
  
Value	Current state of optimization process

ESR1	MemMaker restarted your computer successfully at least twice, but the sizing process was not 
completed. MemMaker enters state ESR1 if the CHKSTATE.SYS device driver loads during state SR2 
and you then choose to undo all changes.

ESR2	MemMaker restarted your computer successfully at least twice, but the sizing process did not 
complete successfully even though the highscan option for EMM386 was disabled. MemMaker enters 
state ESR2 if the CHKSTATE.SYS device driver was loaded during state SR4 and you then choose to 
undo all changes.

EFR1	Your computer was restarted while in state FR2, before MemMaker was started for the final 
time.  State EFR1 indicates that a device driver or memory-resident program did not start properly, or 
that some other problem occurred that prevented MemMaker from starting.

BADID	The State field in the MEMMAKER.STS file contains an invalid SessionID value.  
MemMaker automatically undoes all changes when it encounters state BADID.

AvailConvMemoryBefore
Shows how much conventional memory was free before you started MemMaker. 

AvailUpperMemoryBefore
Shows how much upper memory was available before you started MemMaker.

UsedUpperMemoryBefore
Shows how much upper memory was in use before you started MemMaker. 

WindowsUpperMemoryBefore
Shows how much upper memory was reserved for use by Windows before you started MemMaker. 

EMSUpperMemoryBefore
Shows how much expanded memory was available before you started MemMaker. 

AltSysFiles
Indicates whether there are extra copies of system files (CONFIG.SYS and AUTOEXEC.BAT) on the
 drive that contains the MEMMAKER.STS file. If  this field is set to True and you choose to undo the 
changes made by MemMaker, MemMaker copies the original AUTOEXEC.BAT and CONFIG.SYS files 
to both the startup drive and the drive that contains the MEMMAKER.STS file.

WindowsXlat
Indicates whether or not MemMaker will reserve upper memory for Windows to use for translation 
buffers. If set to True, MemMaker reserves upper memory for Windows translation buffers.

ConfigChksum
A number that MemMaker uses to determine whether the CONFIG.SYS file has changed.

AutoexecChksum
A number that MemMaker uses to determine whether the AUTOEXEC.BAT file has changed.

SysIniChksum
A number that MemMaker uses to determine whether the Windows SYSTEM.INI file has changed.

SysIniLoc
Indicates the location of the Windows 3.0 SYSTEM.INI file, if the file was modified. 

 