Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 31 JUL 2002 04:26:09PM Donald Bakke wrote:

We support an OI16 application with many deployed network installations. At present the majority of these networked systems are running the NT Service 1.5 with the corresponding 1.5 All Networks Driver. We are going to deploy a new copy of this application to the end users, however, we've had to upgrade our copy of the application to the All Networks Driver to 2.1 in order to develop against our 2.1 Service.

Since it appears the the 2.1 client replaces the 1.5 client (i.e. LH2.DLL), will there be a problem if end users are running the 2.1 client against a 1.5 service?

Thanks,

dbakke@srpcs.com

SRP Computer Solutions, Inc.


At 31 JUL 2002 04:30PM Pat McNerthney wrote:

Yes there is a problem, it doesn't work.

Sorry,

Pat


At 01 AUG 2002 12:39AM Donald Bakke wrote:

Pat,

Thanks for the *definitive* response. At least I know where I stand! ;-)

Can you tell me, then, what is the best way to downgrade the client to v1.5? Is it as simple as restoring the LH2.DLL or are there internal components as well?

dbakke@srpcs.com

SRP Computer Solutions, Inc.


At 01 AUG 2002 12:50AM Pat McNerthney wrote:

Don,

The easiest way to switch between the two is to just copy RCLNT15.DLL to RCLCLNT.DLL for the 1.5 driver, and to copy RCLNT21.DLL to RCLCNLT.DLL for the 2.1 driver.  LH2.DLL should be the LH.DLL for both.

Pat


At 01 AUG 2002 09:19AM Donald Bakke wrote:

LH2.DLL should be the LH.DLL for both.

Really? Doesn't LH2.DLL contain the driver name that NETDRV.EXE uses to display in its list? This is what first caused me to think that the two drivers can't co-exist in the same system (at least in OI16, it appears that OI32 uses two different DLLs for the 1.5 and the 2.1 client.)

dbakke@srpcs.com

SRP Computer Solutions, Inc.


At 01 AUG 2002 12:47PM Pat McNerthney wrote:

If NETDRV detects the LH2.DLL as the LH.DLL, it then used RCLCLNT.DLL to determine the network driver name.

Pat


At 10 DEC 2002 01:53PM John Bouley wrote:

Pat,

I'm confused… I took a look at a system with just the 1.5 driver installed and they did not have rclcnlt.dll. They did have rclnpcli.dll.

Also, I am trying to diagnose a problem with a customer who has the 2.1 driver installed but can not activate. When chosen we get a message "System Error" "File is already in use" "Abort, Retry, Ignore". Only a reboot cures this.

I tried copying the LH2.dll to the lh.dll but now OI locks up when we try to run it. If I look for Rclcnlt.dll it is nowhere to be found.

Thanks,

John Bouley


At 10 DEC 2002 02:21PM Pat McNerthney wrote:

John,

I am confused too!
In reviewing this thread, it appears to me that I was always talking about the 32 bit product, not realizing Don was talking about the 16 bit product.
In OI16, the standard 2.1 driver consists of LH2.DLL (which, when renamed to LH.DLL becomes the "installed" driver).  This LH2.DLL then uses APILH2.DLL, which contains the new RCL code and does not require an additional dll.

Pat


At 11 DEC 2002 09:28AM John Bouley wrote:

Thanks Pat for the clarification.

Maybe you could help with the problem my customer is having…

We tried to change the network driver to "All networks 2.1" but receive the following error:

"System Error" "File is already in use" "Abort, Retry, Ignore"

I did copy/rename lh2.dll to lh.dll and netdrv did show "All networks 2.1". I then tried to run OI and it locked upon entry of the password.

This particular client is using Arev on an NT server using the 1.5 service. The OI app is on a W2k server using the 2.1 service. Is it possible that the 2.1 client is getting confused and trying to make a connection to the 1.5 service??

Thanks,

John


At 11 DEC 2002 11:41AM Pat McNerthney wrote:

John,

Create a file called LH2.LOG in the OI root directory.  OI will then log every LH driver request to this file.  Post the result here if it is not clear what the problem is by viewing this log file.  (Don't forget to delete this log file when you are done, it really slows everything down!)

Pat


At 13 DEC 2002 10:00AM John Bouley wrote:

Excellent Pat,

We found out that the last entry in the LH2.log file that occured when OI locked was:

"OP G:\REVSOFT\OINSIGHT.DEV\REVMEDIA"

That got me thinking… Since the customer does not have a G: drive I had them temporarily map the G: drive to OI. This allowed us in, however, in a Runtime there is no way to update the database image!

So, I had them edit the .dbt file with wordpad and replace all of the g: with z:. After deleting the G: mapping OI loaded without problems!!!

I don't know if this breaks the licensing agreement but should'nt you be able to change what files are attached even in a runtime?

Thanks,

John Bouley

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/14689d23849169ab85256c070070422c.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1