[[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]]
==== Nlm client 1.5a Driver - Slow response (AREV Specific) ====
=== At 16 OCT 2004 01:45:14AM Jim Leong wrote: ===
{{tag>"AREV Specific"}}
A client of mine was running Arev 2.11 on Novell 4.2 and the NLM 1.5. I found the Arev index searches rather slow althought they had recently upgraded to a new server and have a modest size database. It was taking Arev 20 seconds to load on a XP machine and 5 seconds on a Windows 98 workstation. I then decided to upgrade them to 2.12. Once the installed was completed I receive an message that the IPX Network driver did not exist. I then changed the driver to Advance Netware 2.0 Drv 2.12. Arev loaded up in 2 seconds on the XP machine. A certain reports that took amost 2 minutes to run was finishing in 10 seconds, mainly due to the increase speed in searching the indexes. The client was thrilled! But once I installed the IPX/Advance Netware 2.1 Drv 1.5a it when back to slow or slower. What would have caused this?
I have since gone back to Advance Netware 2.0 Drv. 2.12. Would this cause any problems?
----
=== At 16 OCT 2004 05:42PM Warren Auyong wrote: ===
Which Novell client are you using on the XP system? Novell Client32 v4.83 SP2 seems to give good results and is the version I would recommend trying / using.
----
=== At 18 OCT 2004 12:30PM Jim Leong wrote: ===
They have 3 similar machines running XP
1) V4.92 SP2 - Fast (5 sec to load Arev)
2) V4.92 SP2 - Slow (30 secs to load Arev)
3) V.4.92 No SP - Fast (5 secs to load Arev)
and Terminal Server running on 2000, using V4.92 SP2, also slow.
Doesn't make sense why that one machine is running fast on V.92 SP2. As far as I can tell, there setup are identical.
----
=== At 18 OCT 2004 01:39PM Warren Auyong wrote: ===
Well, that's the great mystery. 99% of the time the configurations work properly on different XP and 2K boxes and 1% you need to individually tweak the settings.
Check the autoexec.nt and config.nt files for any differences. I don't think XP comes with a Novell driver but there could also be leftover entries from Microsoft's Novell driver that's caused grief in the past.
How are you starting Arev? Through a BAT file or PIF file?
When a BAT file setup runs slow usually this method works:
Create a PIF to the AREV.EXE with a custom AUTOEXEC.REV file (set in Properties - Program - Advanced). The AUTOEXEC.REV should load: LHIPXTSR /P. Copy the existing AUTOEXEC.NT as a starting point.
Adding LHIPXTSR /P to the batchfile setting on the PIF properties rarely works, but you can try that instead of a custom autoexec. You might try creating a PIF for the LHIPXTSR beforehand. I've only gotten this method to work once on Win2K and never on XP.
----
=== At 18 OCT 2004 09:22PM Jim Leong wrote: ===
Got It. Now I can Load Arev in 2 seconds from the terminal server running Novell Client 4.92 Service Pak 2
The rem the following 2 lines in the Autoexec.nt and it did the trick.
REM Install network redirector
rem lh %SystemRoot%\system32\nw16
rem lh %SystemRoot%\system32\vwipxspx
Thanks for your help & suggestions.
----
=== At 19 OCT 2004 08:37AM Hippo wrote: ===
Thanks ... at least startup is much faster
... I suppose everyone knows ... if you want to configure .pif to
.bat, you start with pointing to .exe, do the configuration and at the end point to .bat.
----
=== At 19 OCT 2004 05:40PM Warren Auyong wrote: ===
Glad you were able to solve the problem. I'm going to try the v4.92 sp2 client and see if I can get good speed results too :)
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=1C5B52BE5098743685256F2F001F9B7C|View this thread on the forum...]]