AREV and Win2000 (AREV Specific)
At 01 NOV 2000 11:33:20PM Michael Watson wrote:
AREV 3.12
I have an arev application that I wish to run under MS Windows 2000.
I have 2 issues:
1) I often get "out of string space" error messages when running my arev application. In the past I have found that these problems occur when expanded memory is not active. When I type WHO from TCL I find that expanded memory is NOT ACTIVE so … How do I activate expanded memory in MS Windows 2000 (I have already tried adjusting the memory settings on my desktop shortcut without any luck).
2) I am unable to use my mouse within my arev application. How do I go about enabling the mouse for a DOS session within MS Windows 2000.
Thanks,
Michael
At 02 NOV 2000 04:04AM Barry Stevens wrote:
1) Do you have /XM4096 in the AREV.EXE command line
You are setting EMS to 4096 in the Memory Tab of the ShortCut properties.!Barry
At 02 NOV 2000 08:16AM Joe Doscher wrote:
Michael;
Use file find to locate the CONFIG.NT file. Edit it and make sure there are lines as follows:
dos=high, umb
device=%SystemRoot%\system32\himem.sys
Hope this helps
At 03 NOV 2000 02:10AM Michael Watson wrote:
I have already checked that …. any other ideas????
At 03 NOV 2000 02:11AM Michael Watson wrote:
Yes (This is our standard command to start up AREV)
Yes
Any other ideas
At 08 JAN 2001 05:15PM Irma Harris wrote:
I had the same issue. I found that I had to adjust the properties of the _default.pif (C:\WINNT). I change the memory setting of this pif to expanded 4096 with no extended memory. This worked fine for the local version of the application. Thought I was home free but when I tried to execute the network version of the application I would get a line break.
I found an obscure tech note that said that if you execute any programs, utilties, etc. in dos, including "mem" it will utilize the expended memory resources available and will not reallocate the mem.
Long story short is 1. I re-installed Windows 2000 Prof. 2. Modified the _default.pif before I did any thing at the command line.
Both the local software version and the network version utilize
expanded memory correctly now. Hope this helps.