Windows 2000 Pro will not run Arev 3.12 (AREV Specific)
At 20 SEP 2000 11:34:31AM Jason wrote:
I have recently upgraded a Windows NT Workstation to Windows 2000 Pro and surprise surprise, it will no longer run any Arev programs.
The Arev NLM is running on a NetWare 4.2 server, with the latest service pack. I am loading the lhipxtsr at the command prompt. When I attempt to run the Arev program, I receive the following message:
'RTP27' Line 1 B12 File has not been opened. (Repeated many times)
'RTP27' Line 1 B114 Maximum number of variables exceded.
Any suggestions besides uninstalling Windows 2000?
At 20 SEP 2000 05:11PM WinWin/Revelation Technical Support wrote:
Jason-
Have you enabled Expanded memory on the machine?
Does the Icon for Arev use 4096 of Expanded memory, but no Extended?
In your Config.NT, do you have a setting for files=200, buffers=30?
These could all help.
Mike Ruane
At 22 SEP 2000 09:27AM Jason wrote:
Mike,
I believe that I do have the Expanded memory enabled. The icon and Config.nt are set as you recommended. Unfortunately, nothing is working yet. Any other suggestions?
Jason
At 24 SEP 2000 11:07PM Lon LeMaster wrote:
Jason
The answer is a follows:
1. Uninstall Novell's client 32
2. Install Microsofts Client for Novell
3. Uninstall Microsofts Client for Novell
4. Install Novell's client 32
The Microsoft client apparently leaves some necessay DLL's lying around that the Novell Client needs. (So I was told)
It will run - the logon's are very very slow but once in the application most things work ok. However complex or large selects are much slower (3x to 4x slower)
I have a PIII 650 and its just acceptable
At 25 SEP 2000 10:35AM Jason Crooks wrote:
Thanks for your help Lon,
That did work for the connection and yes the logon is very, very slow, but it does connect and seems to run fine after.
Cheers
At 26 JAN 2001 10:05PM jf goulet wrote:
Ok… guys…
hmmm… thanks to Microsoft "again" and a great tools like Novell Zenworks, I was able to find what was not removed after uninstalling the "Microsoft Client for Netware". It's not a DLL… no registry key's… just 2 lines… 2 lines that were left at the end of the C:\WINNT\SYSTEM32\AUTOEXEC.NT file.
lh %SystemRoot%\system32\nw16
lh %SystemRoot%\system32\vwipxspx
Important :
They must be added before the lines :
%SystemRoot%\system32\vipx.exe
%SystemRoot%\system32\vlmsup.exe
(thoses are from the Novell Client)
From what i'ved tested, I don't even need to specify IPX as the preferred protocol.
It's not fast… but it works!
At 26 JAN 2001 10:05PM TheJoker wrote:
Ok… guys…
hmmm… thanks to Microsoft "again" and a great tools like Novell Zenworks, I was able to find what was not removed after uninstalling the "Microsoft Client for Netware". It's not a DLL… no registry key's… just 2 lines… 2 lines that were left at the end of the C:\WINNT\SYSTEM32\AUTOEXEC.NT file.
lh %SystemRoot%\system32\nw16
lh %SystemRoot%\system32\vwipxspx
Important :
They must be added before the lines :
%SystemRoot%\system32\vipx.exe
%SystemRoot%\system32\vlmsup.exe
(thoses are from the Novell Client)
From what i'ved tested, I don't even need to specify IPX as the preferred protocol.
It's not fast… but it works!