Novell 32 Client for W95 unable to write to OV file (AREV Specific)
At 01 APR 1998 01:28:00AM Bill Barker wrote:
Running AREV 3.1 under W95 with Novell Intranetware 32 client I appear to be having the following problem:
if the OV part of the AREV file is zero length (o Bytes) I get an FS write error!
If the OV part of the file already has data in it - then I have no problems. Only if the OV pary is empty and AREV tries to add arecord to it.
Removal of the Novell Intranetware 32 Client fixes the problem…
Anybody else having this problem?
At 01 APR 1998 06:51AM Egbert Poell wrote:
At the moment I can't figure out what is happening.
We are using the Intranetware client 32 version 2.2 without problems on AREV 3.12, Windows 95 and a Novell 3.11 server using the NLM 1.10
Which version of the Intranetware client 32 are you using?
Best regards,
Egbert Poell
Mecomp Automatisering
At 01 APR 1998 08:19PM Bill Barker wrote:
The 'problem' environment is-
Novell 4.1 server
Win95 running IntraNetware Client 2.2.1
AREV 3.1 with NPP 1.5
Problem appears whenever AREV attempts to write to an empty (0 bytes) OV file!
For example - whenever a LHVerify is run and AREV creates the SYSLHVerify and SYSLHGroup files. The moment it tries to write to the OV pertion of either of these files during the verification process we get an FSMsg indicating that it cannot write to the REVxxxxx.OV file!
I was able to reproduce this problem by creating a new empty file and running a basic program that writes records to it in a loop. Again - as sson as the ARev decides to write the record to the OV file we get the same error message.
Note : the problem only occurs on network drives, - not local C: drive!
Also - if the OV already has data in it - then there is no problem writing to it!
Removal of the Novell client and replacment with the standard Win95 MS client for Novell fixes the problem!
At 02 APR 1998 02:37PM Aaron Kaplan wrote:
There is a patch, ZBYTEFIX or something like that, it's short for Zero Byte Fix. You might have this loaded. That could cause the problem.
It could be that the files do not have owners.
What happens if you delete the 0 byte OV files?
At 03 APR 1998 10:23AM Egbert Poell wrote:
This might not be the solution for your problem but why do you use the NPP instead of the NLM.
Revelation Software advises to use the NLM in a Novell\Win95 environment.
Best regards,
Egbert Poell
Mecomp Automatisering