Universal Driver 4.5, Arev Runtime 3.1, Non-network Dev (Networking Products) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[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]]


==== Universal Driver 4.5, Arev Runtime 3.1, Non-network Dev (Networking Products) ====
=== At 09 APR 2009 10:45:13AM Chris Snell wrote: ===
 
{{tag>"Networking Products"}}
 
<QUOTE>
We need to migrate our ARev app from Novell to MS servers and have purchased the Universal Driver 4.5 to replace our NLM. However, I have read of table backward compatibility problems with the Win 2000 network driver, but I don't understand the conditions/impact.

We have an ARev 3.1 runtime which has had a network bump so it seems to be working with the UD 4.5 fine. However, our development environment has never had a network bump so it cannot use the Universal Driver, or any other for that matter.



Will we experience table backward compatibility problems trying to use the UD4.5 runtime and non-network-aware environments together? In the past we have just been careful not to alter data tables in the development environment to avoid GFE's.
</QUOTE>
----

=== At 09 APR 2009 10:24PM Richard Bright wrote:  ===

<QUOTE>Chris,



It would seem that if you shifted data / code from your development system to your AREV runtime system, all should be OK.  However if a table is created in the runtime / 4.5 environment, it wont be readable in the development system as is.  This is because a) UD 4+ creates a different LH header layout - not readable by earlier LH implimentations, but the UD4.5 driver is backward compatable in its reading of LH.

Why dont you just run the OIv4.5 client-side install on the development system - thus bringing it up to the latest driver set. You can run as many arev or OI systems as you like on the server with the UD4.5 service.  If you are not running the Arev system on the server supporting the UD4.5 then set the Revparam to ServerOnly=0.

</QUOTE>

----

=== At 13 APR 2009 08:46AM Chris Snell wrote:  ===

<QUOTE>Thanks Richard. I think we can work around the table issue for data, but what about indexes? If we create an index in runtime on UD4.5 will this index also be incompatible with the non-network development environment? Since ARev indexes are contained in ARev tables I am guessing they are also not backward compatible? That would be much more problematic.



I have tried installing the UD4.5 into the runtime environment. Even when selected I get no network vendor type, no station id, and no indication of locks in the UD4.5 manager. I was assuming this is because there is no network bump (Lanpack) on our development version.

</QUOTE>

----

=== At 13 APR 2009 09:47AM Chris Snell wrote:  ===

<QUOTE>Oops. I meant I have installed the UD4.5 into the development version, and have no station id etc. Our runtime is working fine with UD4.5.

</QUOTE>

----

=== At 14 APR 2009 02:28PM Jared Bratu wrote:  ===

<QUOTE>I think you are on the right track. Installing the Universal Driver client into the development environment should allow you to work on tables in either networked or standalone.

Since your development environment is single user it might be missing a REVPARAM file. If this were the case it would not utilize the linear hash service. Do you have a REVPARAM file in the development system?

</QUOTE>

----

=== At 14 APR 2009 04:24PM Richard Bright wrote:  ===

<QUOTE>



Unless you are running humungus files - I believe you will be OK; that is to say Arev 3.12 / OI should be OK if same network driver - UD4.5 installed.  RevSoft I'm sure will confirm;  I have one client that has for last year been running combo OI + Arev /Development and runtime with UD; they are not free of issues BUT the issues are not necessarilly associated with this topic.







Check the install DOC.  You need to Install THEN select the driver.  I suspect the driver has not been selected.  Also as Jared says, check for the REVPARAM file that should be in root of Arev (or OI).  The UD4.5 creats a standard REVPARAM file and should copy it to the right spot; if not copy from the \Revsoft\Universal driver\ location  to the Arev (or OI) root.



Richard Bright

</QUOTE>

----

=== At 15 APR 2009 02:00PM Chris Snell wrote:  ===

<QUOTE>The universal driver is installed in the development environment, I have selected "Universal" as the network type using the Lanpack user, and the REVPARAM file is:

ServerOnly=1

ServerName=hunvm02

TcpIpPort=777



"Who" still reports no network vendor/type and no station id. This is true no matter what network type I select: Universal, IPX/Advanced Netware, or Microsoft LAN Manager.

</QUOTE>

----

=== At 15 APR 2009 04:36PM Jared Bratu wrote:  ===

<QUOTE>The settings and revparam file appear correct but there is something wrong. Your purchase of the UD includes 30 days of installation support. This might be best resolved by contacting your reseller. Perhaps they can do a remote support session to look at your system and see what is missing or mis-configured.

</QUOTE>

----

=== At 17 APR 2009 09:10PM Warren Auyong wrote:  ===

<QUOTE>How many maximum users does "Who" show?



If it's only one then then it has never had a user "bump" disk applied to it and thus will not support networking.

</QUOTE>

----

=== At 20 APR 2009 08:39AM Chris Snell wrote:  ===

<QUOTE>Who shows 1.

Thanks for the info Warren, that kind of confirms what I had thought about our development environment.

I have now found that our un-bumped development cannot properly attach files that are shared with the UD4.5-installed runtime. I think the two versions lock files in a mutually incompatible manner. I will see if there is any way of restoring one of our now-unused network bump disks so I can bump development. Seems like the only way out.

</QUOTE>

----

=== At 20 APR 2009 02:21PM Jared Bratu wrote:  ===

<QUOTE>Bump disks that were previously used cannot be transferred to another system and cannot be re-applied. Bump disks are unusable after the first use.

</QUOTE>


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