Hesitation after upgrading from NT 1.5 to 2.1 driver (Networking Products)
At 06 JUN 2006 10:34:22PM dave w bennett wrote:
60 users, 2003 Windows Server, full rights including the System user.
At 07 JUN 2006 01:38PM Bob Carten wrote:
I'm not sure if this applies to 2.1, or just 3.x, but when you attach a subdirectory the driver will look for a revparam file by searching up the path from the location of your files.
Is there a revparam file in the openinsight subdirectory?
If your data is in subdirectories thar are not under the Oi directory, do these subdirectories also have revparam files?
HTH
Bob
At 19 JUL 2006 02:33AM dave w bennett wrote:
Each sub-folder under arev has the same revparam file.
At 20 JUL 2006 05:17AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
I don't know if you have checked these, the thread seems to begin in the middle of a conversation :)
For the Client and the server make sure that the CONFIG.SYS/NT file has the files=200 entry.
A large number of protocols can degrade the service. Remove any unused protocols and ensure that the one selected for the 2.1 service is first in the list of protocols.
Sometimes one utilises the LH2.log and/or the LH2srvc.log files to troubleshoot during the installation of the service. Make sure that there are no incidences of these files anywhere. Even check the client for LH2.log files.
World leaders in all things RevSoft
At 16 OCT 2006 01:00PM dave w bennett wrote:
config.nt was set to 200 on the server and a complete search of the network found no other files.
We downgraded to 1.5 and it removed the hesitation.
This also corrected hesitations at another account.
Dave