Hello all,

I have a client with a system (created by another group) which has suddenly developed some of the weirdest errors I have seen in my 10 years with Arev.

The client workstations are Windows 3.1, running on a Novell 4.11 network using Novell Windows network drivers.

The application is running on Arev 2.03 with Novell network driver, and has been running without any significant problems for years.

In the last 2 days, however, the client has experienced 3 separate cases of phantom FS105 (Operating system access error, unable to read file) on the !INDEXING and MENUS files.

The !INDEXING error are reported after the user has been in the system for a while and the background indexing function is kicking-in.

I have checked all the Novell settings that I'm aware of, the files are all shareable-read/write. Expanded memory is not enabled or used, the available memory is a little low but no string space messages have been encountered. I have tested the network locking functions and they are correct.

I'm stumped! And would appreciate any help/suggestions.

Sean

Was anything changed just prior to these errors? Files restored? Virus scanner added?

Check to make sure files have an owner also.

Warren,

The workstations do have a virus scanner loaded, but I don't know off-hand what the settings are (or whether REV*.* are excluded). I am pursuing the possible scanner/Arev collission issue with their IT group (thanks for prompting that thought…)

I did check the ownership of the files and they are all owned by a user (there is no disk space limitation in effect for users).

Thanks

Sean

I'll be TRANSACTION TRACKING is on - on the server; turn it off.

A MAJOR fix is to remove the network cache from REVBOOT.

With EVERYONE off, MAKE A BACKUP OF REVBOOT!, then from TCL,

EDIT DOS REVBOOT (enter)

do a CTRL-F (Find) for 20 and replace it EXACTLY with 00 (double zero). Save Revboot. Set to R/O, SH

In Win3.1, check your VCACHE setting (if they're not there, and they probably aren't) search the MS troubleshooting database for 'VCACHE' and '3.1'. It's Good to limit VCACHE!

I'd appreciate a note if any of the above fixes your problem.

Oh, yes, again, make SURE that ALL workstations use the same drive letter and path to get to AREV. I'd also make the SORT and ROLLOUT path/files to a local drive. I also create a local directory and create a LISTS file and SYSTEMP file there; you'll like the speed increase.

Larry tardis@earthlink.net

http://members.tripod.com/rehabsw

]EDIT DOS REVBOOT (enter)

]do a CTRL-F (Find) for 20 and replace it EXACTLY with 00 (double ]zero). Save Revboot.

Doing this on my system would change RTP20 to RTP00. I don't think that's what you had in mind.

View this thread on the forum...