Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 15 SEP 2000 07:25:54AM Dave Berkovsky wrote:

How one turns on the expanded memory on NT workstation.

I am not sure of a syntax in config.nt

Thanks in Advance

Dave Berkovsky


At 15 SEP 2000 10:24AM Warren wrote:

Look at [u][size=2]this MSFT kb article[/size][/u] for some pointers.

Basically you need to create a PIF on your desktop (find your AREV.EXE in explorer right click on it create shortcut - drag shortcut/PIF to desktop). Right click on the PIF you created and adjust properties - total conventional mem set to 640, expanded mem to 4096, no extended mem, run in background, idle sensitivity to 80-100%.


At 15 SEP 2000 01:05PM dale walker wrote:

The syntax (sin tax?) that I use is:

d\arev\arev.exe /x/m4096

where d is the drive letter.

Dale


At 15 SEP 2000 04:47PM Warren wrote:

This will only work if expand memory is enabled in the pif or in your _default.pif


At 18 SEP 2000 01:25PM d berkovsky wrote:

Hi Warren,

That is my problem. I am not sure how to enable expanded memory

under Windows NT. Can you explain how it can be done.

Thanks.

Dave


At 19 SEP 2000 05:30PM Warren wrote:

See my previous message in this thread.


At 20 SEP 2000 01:08PM Dave B. wrote:

Warren,

I did it chage in c:\winnt\_default.pif, but still expanded memory is not enabled.

Do you have any ideas why it is not working ?

—————————–7d05d141e0228–


At 20 SEP 2000 02:35PM Warren wrote:

Is himem.sys in your CONFIG.NT (Windows\System32 directory)?

Have any EMM statements been entered in the same?

The _default.pif should be placed in the Windows or system32 folder. You also need to create a specific pif for AREV and make the necessary settings there also.

_default.pif applies mainly to the command prompt window.


At 21 SEP 2000 10:30AM Dave B. wrote:

WArren,

Here is my config.nt

What I do not know is the syntax for EMM command.

I appreciate your help greatly.

REM EMM

REM You can use EMM command line to configure EMM(Expanded Memory Manager).

REM The syntax is:

REM

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.

REM

SET ALOPTIONS=BIGDISK

SET PCPLUS=S:\PCPLUS

dos=high, umb

device=%SystemRoot%\system32\himem.sys

files=20


At 22 SEP 2000 06:22PM Warren wrote:

Looks okay to me.

Let's review:

You created a pif that points to AREV.EXE, the command line is AREV.EXE username /x /m4096 working directory is where AREV.EXE is located, memory settings conventional=640, expanded (EMS)=4096, extended (XMS)=none, DPMI=auto. Correct?

What happens if you set initial environment to 256 or 512K vs auto?


At 04 OCT 2000 08:30AM Paul Boughton wrote:

Looks to me like you have enabled Himem, but not EMM. You will need a line to call EMM. I am not familar enough with the options to make a suggestion.

Look on Microsoft's MSKB for some explaination of the EMM command under Win NT.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/8d80e5e8797c61de8525695b003ecbd7.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1