EMS & Windows 2000 SP3 (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|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]]


==== EMS & Windows 2000 SP3 (AREV Specific) ====
=== At 13 MAR 2003 01:48:34PM Tom Moffett wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
I can not obtain any EMS (Expanded Memory) from my

new workstation running Windows 2000 Pro installed with

Service Pack 3. Other workstations running with Service Pack 2

are working find.

I found several discussions of this problem on the net, but

no one has come up with a solution. There does not 

appear to be any hotfix yet that addresses this.



Any Ideas?
</QUOTE>
----

=== At 13 MAR 2003 03:00PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>Tom,



It must be pertinent to your hardware somehow - I have been running SP3 for some weeks now and it supports expanded memory fine. Try rebuilding your shortcut direct to AREV.EXE, configure for Expanded memory and see if that works. Even if you usually run a batch file, try run the arev.exe directly from the shortcut for starters.



http://www.state-of-the-art.com.au/sp3.jpg



Steve



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>

----

=== At 13 MAR 2003 04:35PM Janice Preston wrote:  ===

<QUOTE>Are you configuring the expanded memory in the _default.pif?

Unfortunately, we have found that many of the new computers will not allow you to utilize EMS.  It is not related to the OS necessarily.

The ironic thing is, you can have two identical machines, same manufacturer same everything, one will use EMS and the other will not.



Janice

</QUOTE>

----

=== At 13 MAR 2003 05:16PM Daniel Rebich wrote:  ===

<QUOTE>Steve,



I'm guessing that information in the .jpg you attached is inherited by AREV from the PC and not something that you can turn on/off somewhere in the application.  Thanks



Of course, if it can be turned on in the application please let me know where.



Daniel Rebich

</QUOTE>

----

=== At 13 MAR 2003 05:25PM Tom Moffett wrote:  ===

<QUOTE>Thank You Janice & Spezzatura Group for your quick response.

We have tried setting up the Shortcut (pif) both directly to the

exe and to a batch file. The short cuts are specific to the Arev

exe, I am not sure what you mean by the _default pif.

The fact that it might be hardware related is scary for not only

us, but all our clients that are upgrading hardware.

We have a very large base of Arev clients.

This computer contains the new Asus A7N8X AMD motherboard using

Corsair PC2700 CAS2 memory. Could it possile be a BIOS problem?

</QUOTE>

----

=== At 14 MAR 2003 04:05AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>Tom, check for devices (such as network cards or video adaptors) that operate in the region between A000:0000 and F000:0000 segments - these are possible culprits. Also, some video driver adjustments may be required (lower resolution, disable RAM/video caching in BIOS etc)



I've heard of this being a drama on Dell and Compaqs (use the search feature in this forum on those Brand names) but don't know in your case.



Another trick is to remove all pifs from the AREV.EXE path ahead of setting up your shortcut.



Another is to set up the shortcut to the exe then revert the same shortcut to the batch file instead, *after* configuring memory etc.



You may need the lines



dos=high, umb

device=%SystemRoot%\system32\himem.sys

files=40



at the bottom of your \winnt\system32\config.nt file



You might also opt for files=200 if this is advantageous to performance.



Steve



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>

----

=== At 19 MAR 2003 09:00PM C Mansutti wrote:  ===

<QUOTE>I have a site with 6 Dell PCs all running XP, the older ones provide EMS, the latest two (2.5G) PCs won't.



I've tried many of the things Steve has covered and am working on doing the remainder. I don't hold up much hope though.



Found this problem - incurable - with certain Acer (Asus) PCs as well. Had to return them to the vendor. 



My experience has been - Lots of time spent on the problem with no solution other than return of product. We are now becoming very selective with our hardware.



If anybody has some good news/solutions, I'd be happy to hear it.



Claude 

</QUOTE>

----

=== At 20 MAR 2003 06:09AM Hippo wrote:  ===

<QUOTE>We had simillar problem (all page frames occupied by BIOS).

Fortunately disabling some features (booting from USB) solved the problem.

</QUOTE>

----

=== At 20 MAR 2003 07:18AM Joe Doscher wrote:  ===

<QUOTE>Tom,



Sounds like you have tried everything in everybodies bag of tricks.  One I did not see that worked on a WinBook running ME was this:

make sure the HIMEN.sys is available and in your config.nt( this was already in another responce ). Then make sure the EMM386 or an other mem mgr. is available and in your config.nt.  EMM386 has an M switch "/M" with several settings.  With the WinBook "ME" I kept trying each "M" swich option and cold rebooted each time and one worked.

I don't if you tried this yet but???

Hope it helps



Joe Doscher

Rev. Tech. Support

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=F76F45225992B9BA85256CE80061D4CD|View this thread on the  forum...]]