Under XP a 16bit program needs EMM

[Guest]

It appears that XP dos does not support EMM.
The config.nt presents a command line example as to how the
EMM command should be executed but it doesn't work.

The EMM command is not in the supported command list.
The expanded memory drop down in the properties page has no
effect.

Any suggestion?

 

[R.E Fernandez]

see:
http://spaces.msn.com/reinaldoefernandezspain/blog/cns!F7B99A385052C90!415.entry

--
saludos cordiales..!
regards....!
REFernandez
http://spaces.msn.com/reinaldoefernandezspain/?mkt=en-us
http://spaces.msn.com/members/reinaldoefernandez/
http://eduardofernandez.bitacoras.com/
http://spaces.msn.com/reinaldoefernandezspain/?mkt=en-us

 

[Guest]

The program requires atleast 2700k of expanded memory. No were can I find
instructions as to how to define expanded memory under XP. Setting the
drop downs in the properties page of a MS-DOS .pif doesn't work. After
executing the pif I get a dos window, I execute the mem command in the
dos window and only XMS and conventional mem are available.

Its beginning to look like Microsoft has dropped this feature but didn't
remove
it from the properties page.

 

[John John]

Try using a shorcut to the program with command.com in the target line,
then you should be able to edit the memory settings in the memory tab in
the shortcut properties. Create the shortcut as you usually do but the
location of the item would look something like this:

command /c c:\ProgramFolder\DosProg.exe

Can't say for sure that it's going to work but it's easy enough to try
and no harm done if it doesn't work.

John

 

[Guest]

Configuring the ms-dos shortcut is not the problem. The problem is that
EMM does not exist any more under XP in any form.

There doesn't seem to be any docs to thatfact nor can anyone tell confirm
its gone. If it is why does the memory tab display it?

 

[Robert Gault]

Configuring the ms-dos shortcut is not the problem. The problem is that
EMM does not exist any more under XP in any form.

There doesn't seem to be any docs to thatfact nor can anyone tell confirm
its gone. If it is why does the memory tab display it?

<snip>

Are you sure about your facts? Have you read the file
C:\WINDOWS\System32\Config.nt

"
REM EMM = [A=AltRegSets] [B=BaseSegment] [RAM]
REM
REM AltRegSets
REM specifies the total Alternative Mapping Register Sets you
REM want the system to support. 1 <= AltRegSets <= 255. The
REM default value is 8.
REM BaseSegment
REM specifies the starting segment address in the Dos conventional
REM memory you want the system to allocate for EMM page frames.
REM The value must be given in Hexdecimal.
REM 0x1000 <= BaseSegment <= 0x4000. The value is rounded down to
REM 16KB boundary. The default value is 0x4000
REM RAM
REM specifies that the system should only allocate 64Kb address
REM space from the Upper Memory Block(UMB) area for EMM page frames
REM and leave the rests(if available) to be used by DOS to support
REM loadhigh and devicehigh commands. The system, by default, would
REM allocate all possible and available UMB for page frames.
REM
REM The EMM size is determined by pif file(either the one associated
REM with your application or _default.pif). If the size from PIF file
REM is zero, EMM will be disabled and the EMM line will be ignored.
"

 

[Guest]

Ya, I'm sure, give it a try yourself. Oh when the dos window opens
execute the mem command you'll see con & xms memory but no
emm memory

Placing the emm command in the config in any configuration generates an
error message that the emm command contains invalid parameters or syntax
errors

examples:
emm = A=1, B=0x4000, 3072

or without the comma
emm = A=1 B=0x4000 3072

Searching XP help for the emm command is no help because the emm is
not in the XP Sub-System. I checked this by search the XP help for echoconfig.

Take a look if your not sure..

Configuring the ms-dos shortcut is not the problem. The problem is that
EMM does not exist any more under XP in any form.

There doesn't seem to be any docs to thatfact nor can anyone tell confirm
its gone. If it is why does the memory tab display it?

<snip>

Are you sure about your facts? Have you read the file
C:\WINDOWS\System32\Config.nt

"
REM EMM = [A=AltRegSets] [B=BaseSegment] [RAM]
REM
REM AltRegSets
REM specifies the total Alternative Mapping Register Sets you
REM want the system to support. 1 <= AltRegSets <= 255. The
REM default value is 8.
REM BaseSegment
REM specifies the starting segment address in the Dos conventional
REM memory you want the system to allocate for EMM page frames.
REM The value must be given in Hexdecimal.
REM 0x1000 <= BaseSegment <= 0x4000. The value is rounded down to
REM 16KB boundary. The default value is 0x4000
REM RAM
REM specifies that the system should only allocate 64Kb address
REM space from the Upper Memory Block(UMB) area for EMM page frames
REM and leave the rests(if available) to be used by DOS to support
REM loadhigh and devicehigh commands. The system, by default, would
REM allocate all possible and available UMB for page frames.
REM
REM The EMM size is determined by pif file(either the one associated
REM with your application or _default.pif). If the size from PIF file
REM is zero, EMM will be disabled and the EMM line will be ignored.
"