[[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]]


==== RevG Record Locking on Windows 2000 (AREV Specific) ====
=== At 13 MAR 2001 03:15:02PM Gary Kammeraad wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
One of our customers just purchased a Windows 2000 workstation, which is attached to their Novel 5 server. The network driver in RevG is for Novell. On the Windows 2000 machine itself, two copies of Rev in separate DOS windows do record locking against each other, but they do NOT do record locking against other workstations on the rest of the network.



Any help would be appreciated!

Thanks,

Gary
</QUOTE>
----

=== At 13 MAR 2001 04:08PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>Here's a listing of available network drivers for RevG.

+---------------------------------------+

¦Choose a network.                      ¦

¦                                       ¦

¦  1.  NO NETWORK.                      ¦

¦  2.  3COM ETHERSHARE 2.4 NETWORK.     ¦

¦  3.  3COM 3+ NETWORK.                 ¦

¦  4.  AT&T STARLAN NETWORK.            ¦

¦  5.  GENERIC DOS 3.1 NETWORK.         ¦

¦  6.  BANYAN NETWORK.                  ¦

¦  7.  HP OFFICESHARE NETWORK.          ¦

¦  8.  IBM PC NETWORK.                  ¦

¦  9.  MULTI-DOS NETWORK.               ¦

¦ 10.  NESTAR NETWORK.                  ¦

¦ 11.  NOVELL NETWORK.                  ¦

¦ 12.  NOVELL ADVANCED NETWARE.         ¦

¦ 13.  TAPESTRY NETWORK.                ¦

¦ 14.  IBM TOKEN RING NETWORK.          ¦

¦                                       ¦

¦Enter a number (1 - 14)                ¦

¦Or for no change press RETURN.         ¦

+---------------------------------------¦

¦ Current driver:                       ¦

¦      NO NETWORK.                      ¦

+---------------------------------------+



The one you need to use is #12, Novell Advanced Netware.  This is at least Netware/286, Netware/386 compatible.  The Novell Netware driver is for versions of Novell that shipped sometime in the mid to early 1980s.



[url=http://www.sprezzatura.com" ]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]







</QUOTE>

----

=== At 13 MAR 2001 04:39PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>Late afterthought - you'll probably need to enable the Bindery BIND (old style calls) in the Windows Novell Client as well as NDS - so use BIND/NDS as the client type if your client supports it. The locking scheme in use by REVG is Netware's logical locking, supported by int 21h function D0-D4h. At a pinch you could try enabling byte range locking (DOS 3.1 compatible) but the performance is much slower. Also check for the presence of @STATION on the workstation - use WHO from TCL.



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>

----

=== At 13 MAR 2001 05:21PM Don Miller - C3 Inc. wrote:  ===

<QUOTE>I'm not sure that Netware 5.x's support of Bindary mode will work without Netware's Client32 3.30.0.  I'm pretty sure that the Byte-Range driver will work but at a performance disadvantage; however, REV-G is still a pretty quick animal.  Watch out for ROS files that are not setup as .LNK files since network locking only works on .LNK files.



Don Miller

C3 Inc.

</QUOTE>

----

=== At 13 MAR 2001 06:26PM Gary Kammeraad wrote:  ===

<QUOTE>Thanks for the info - I'll try this out at the customer site on Thursday.

</QUOTE>


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