Win 2000 on Novell (AREV Specific)
At 10 MAY 2001 02:38:21PM Janice Preston wrote:
User has a Windows 2000 workstation on a Novell 4.11 network, running
Arev 3.111. No NLM. The workstation is logging on to the network drive
where AREV is installed, the program works fine except they get a warning that No network drive can be found, either the drive is local or no network drive is configured. This occurs when they log in to the program. They can suspend out from the AREV program and see the network drive with no problem, the program works but of course will not lock properly. They have Novell client (The latest for Win2000)
which will not allow them to set the frame type, it reverts back to
auto when they try.
If anyone has any suggestions I would appreciate it. Thank you
Janice
At 10 MAY 2001 05:57PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
You would be best to run the Revelation Software LH NLM with Novell 5.0
What version does your netware client show?
World Leaders in all things RevSoft
At 11 MAY 2001 08:56AM Janice Preston wrote:
As I said in the main letter, they do not have the NLM, and they have Novell 4.11. Any other suggestions appreciated.
Thanks
Janice
At 11 MAY 2001 11:07AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
ARev returns that error when the drive letter does not respond as being a network drive. This determination is based on the DOS Int21h call which asks the system to return a status flag indicating whether the drive is local or remote. This call is specified in the DOS 3.1 networking protocol as defined by Microsoft.
Since others do not appear to have this problem, Win2000 in and off itself would seem to honour this message.
Novell tends to shell most of these functions, including most of COMMAND.COM's functionality, which was one of the functions of NETX. It assumed all drives were Novell drives, and if not, passed control back to the regular DOS kernel. Anyway, enough with the history lesson.
Frame type is not important except with the NLM. On pure Novell, as long as the client can see the drive, it will respond to the semaphore lock that the drivers use.
Basically, then, the problem is that current incarnation of NETX is not answering the question of whether this is a network drive or a local drive correctly.
Novell's clients have tended to be really flaky of late, especially when dealing with semaphore locks, which not too many applications use any longer.
Going back to history lessons, it used to be that to gain locking you had to log into the network using 'private' mode, which meant that each DOS session had it's own login and server connection. Otherwise, ARev would not recognize the drive as networked and treat it as local.
On Novell 4.11 you also have the problems of bindery verses Netware Directory Services (NDS) which handle the locks differently.
You also have the problem where Microsoft intercepts the sempahore lock and assumes you really want a logical semaphore lock and replaces the call for you.
Try reverting to a previous version of the client as ARev/Novell problems seem to alternate on Netware client versions.
On another note, we'd strongly recommend the NLM. Very strongly.
World Leaders in all things RevSoft