[[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]]


==== Win 2000 / XP w/ NW 4.11 (AREV Specific) ====
=== At 23 OCT 2001 01:00:16PM Tony Hake wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
I am attempting to get a Win2K and WinXP workstation to work with AREV (on a NW4.11 server) and despite my best efforts, it isn't working.  While the program does run, it is extraordinarily slow.  I've read all of the messages in the group about these issues but can't seem to get it to work right.



Here are my config files:



AUTOEXEC.NT

@echo off



REM Install CD ROM extensions

lh %SystemRoot%\system32\mscdexnt.exe



REM Install network redirector (load before dosx.exe)

lh %SystemRoot%\system32\redir

lh %SystemRoot%\system32\nw16

lh %SystemRoot%\system32\vwipxspx



REM Install DPMI support

lh %SystemRoot%\system32\dosx



%SystemRoot%\system32\vipx.exe

%SystemRoot%\system32\vlmsup.exe





CONFIG.NT

dos=high, umb

device=%SystemRoot%\system32\himem.sys

device=%SystemRoot%\system32\emm386.exe 4096 ram

FILES=200



I am running the program from a batch file (hdwc.bat) that says this:

;@ECHO OFF

K:

SET AREV=\AREV\COLOR_US.INI

CD\AREV

CLS

LHIPXTSR.EXE

AREV HDWMGR.COLOR/E/X/M4096

LHIPXTSR /U

CD\





The memory properties for the shortcut to hdwc.bat are set for auto everything EXCEPT for EMS which is set to 4096.  Per another message in the forum, I have deselected "always suspend" and adjusted idel sensitivity to 80%.



PLEASE HELP!  Thank you!



Tony
</QUOTE>
----

=== At 23 OCT 2001 02:04PM Tony Hake wrote:  ===

<QUOTE>Just one addendum...  I am using Client 32 v4.8 on Win2K and NLM v1.5.



Thanks again!

</QUOTE>

----

=== At 24 OCT 2001 04:39PM Dan Reese wrote:  ===

<QUOTE>You are right, this combination is slow beyond belief.  I have discussed this with Revelation and they are pursuing a fix of some type.  You might call them and ask about its status.



Personally, I believe that the culprit may be vwipxspx, which is a Microsoft implementation of ipx.  The 4.8 client in Windows NT does not require this program in autoexec.nt, but the 4.8 client in Windows 2000 does.  

</QUOTE>


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