Arev 3.11 and Winframe 1.7 (AREV Specific)
At 04 JUN 1998 02:30:09AM Darren Wylie wrote:
I have setup a Winframe server that runs Arev 3.11 - the speed is great but every so often when a user is trying to save data arev either hangs or goes to the debugger and reports RTP57 Line1 ERRMSGB114
Does anyone know the solution to this problem?
At 09 JUN 1998 03:32PM Robert Popoff wrote:
You may want to see how much Expanded Memory you have available. Press the key and type WHO. See first if your Expanded Memory is available and if so, how much
At 11 JUN 1998 09:04PM Darren Wylie wrote:
Here is the Expanded memory information for arev - using the WHO command:
Available memory=288204
Descriptors used=1845
Expanded Memory=Active
Expanded Memory Information
Expanded Memory Statistics
EM used= 270,336
EM Allocated= 524,288
Memory Region Segment Address
16K EM window = C800 (800K)
64K Overflow Buffer 1 = 18FF (100K)
64K Overflow Buffer 2 = 28FF (164K)
Does this look right?
At 13 JUN 1998 03:44PM Aaron Kaplan wrote:
That's real low.
My EMS sits at 4,194,304. Make sure you're allocating EMS to the session and starting ARev with the /X M4096 command line options.
akaplan@sprezzatura.com
At 15 JUN 1998 01:13AM Darren Wylie wrote:
Thanks for that advice Aaron Kaplan
I will try that and see how it goes
Do you use a pif to allocate the EMS?
At 15 JUN 1998 01:43AM Darren Wylie wrote:
Unfortuantly that didn't work
I still get this message:
'RTP57' Line 1. ERRMSGB114
ERRMSGD4 1 RTP17
'RTP37' Line 1. ERRMSGB114
ERRMSGD4 1 CATALYST
I use a pif to call a batch file
In the pif I have set EMS Required to: 4096Kb
and EMS Limit to 4096Kb
Here is the batch file:
@echo off
arevfix.com
net use r: \\nt_sydney\arev /y
set arev=r:\arevnoin.ini
r:
arev.exe dw /X M4096
At 19 JUN 1998 09:15AM Aaron Kaplan wrote:
In the batch file, try adding MEM ] MEM.TXT so we can see the actual memory available before loading the ARev session.
akaplan@sprezzatura.com