On one computer:

WHO says: expanded memory: inactive

There is EMS 4096 filled in properties/memory,

AREV is called with /x /m4096 switches

(checked with DOSCMDLINE() routine:))

Why the expanded memory is not active?

Thank you for advices.

With Win98 you must employ an EMM program, like EMM386.EXE, otherwise expanded memory will not be available to you.

See these links or search the site for EMM386

http://www.revelation.com/Discuss.nsf/f12696d31000b22a8525652b00831bb2/FF0C82CBAD7890BB85256CF50062117D?OpenDocument

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q98/7/68.ASP&NoWebContent=1

Regards

The Sprezzatura Group

World Leaders in all things RevSoft

Thank you for answer.

Unfortunately there have been "device=c:\windows\emm386.exe" in config.sys already.

(And the properties-memory allows me to set EMS 4096)

When I was unable to config EMS on some other machines, the properties-memory EMS "COMBOBOX" was not configurable (until free "communication address was found") so I hope EMS works well during *.bat invocation. There is probably problem later.

Any other toughts?

Have you tried:

device=c:\windows\emm386.exe RAM

in config.sys? Also, you need to make sure that

device=c:\windows\himem.sys

is loaded in your config.sys file prior to the EMM386.EXE line. If adding the "RAM" parameter causes an error, try

device=c:\windows\emm386.exe RAM M5

instead. This sets the base page-frame address, and has always worked for me. It might generate an error message about the page-frame being swapped out, but this is generally an ignorable error as long as Windows boots correctly.

You can always open a command prompt and execute MEM /C to check the memory settings. At the end of the listing, you should see two lines similar to the following:

Total Expanded (EMS)                 67,108,864    (64M)

Free Expanded (EMS)                  16,777,216    (16M)

HTH,

msorrel@greyhound.com

Greyhound Lines, Inc.

Hippo, point your Windows shortcut to AREV.EXE first of all, then adjust XMS to 4096, and save. Then once your memory settings are fixed, try returning the shortcut to run your bat file.

Steve

Thanks Matt,

I will try to add:

mem /c

pause

into arev invocation *.bat. (I am not in the office now.)

There was himem.sys in the config.sys already (I just didn't tell it).

I don't thing there is problem with EMS on the computer, but in cooperation of AREV with it.

Does anyone have problem with inactive EMS in AREV while EMS set in shortcut memory properties (and called with /x /m4096 switches).

Thanks, I will try it, either (even I didn't understand why it can help).

I have tried:

device=c:\windows\himem.sys

device=c:\windows\emm386.exe RAM

no error message (even during boot:))

device=c:\windows\emm386.exe RAM M5

You can always open a command prompt and execute MEM /C to check the memory settings. At the end of the listing, you should see two lines similar to the following:

Total Expanded (EMS) 67,108,864 (64M)

Free Expanded (EMS) 16,777,216 (16M)

I have added mem /c and pause rows to AREV invocating *.bat and

seen (translated)

Total Expanded (EMS) … (4MMB)

Free Expanded (EMS) … (4MMB)

Biggest free block in high memory 0B.

(Dos is resident in himem area)

The himem status is probably key to the problem. Do you agree?

Hi can I improve the situation? Thanks for answers.

The problem disappiers, but I don't know why/how.

I've checked WHO in another application run on the same machine and EMS was active. The only difference was SET AREV= row in the *.bat starting the problematic one. I removed the line … EMS active, I've added the line … EMS "remains" active. I didn't check EMS status before, therefore this maynot be the cure.

MEM /C still reports highest block 0.

I hope EMS will be active in future. Thanks

Hippo,

The AREV= indicates that it is using a custom ini file. The settings in this file can affect Indexing, Caching, Video, Rollout (suspend) files etc.

Obviously, there must be a difference between the standard AREVC.ini and the ini that this WS is using. Find the difference and you may find your problem.

HTH,

John

Surprising thing is that after returning

SET AREV=

back. Everything is OK.

Unfortunately I didn't check the status just before removing the

SET AREV=

row. Therefore I cannot say that 1.removing + 2.adding the row solved the problem.

Fortunately problem is solved now:)

View this thread on the forum...