Our locking problem has not been resolved. I was wondering if we had any other options? The locking problem is not affecting the entire company but a selected few. The few users that are having this problem remain constant. We have no clue what the problem could stem from. All we do know is that it needs to be fixed and soon. So any help that anyone can give will be of much appreciation.

Have you verified that the tsr is loading on these workstations?

    If so, have you added the /p and /s:3 parameters to the tsr       command line?

Is the revparam file established?

Are there any other Dos-based products running at the same time?

Have you unchecked the 'always suspend' feature on the shortcut properties?

In the config.sys, did you set files=200?

Are you using Novell Client 32? If so, what version?

The parameters have been set in the tsr file and the revparam file exists. We are using Client 32 but I don't know what version. Please explain concerning Client 32. The config.sys file has been set. We are using WordPerfect 5.1 for DOS so there is another DOS application running. The always suspend is also unchecked. I think that that covered everything.

Older versions of Client 32 (say, earlier than mid 1997) have been known to cause Arev to lock. This has been fixed in later releases of Novell Client 32.

Also, what parameters–if any– do you have on the LH.NLM and the LHIPXSER?

The current version of the client32 is 2.2.0.0

John Revelation

The only parameter that we are using is the /m: parameter that controls the minutes.

LuCristi Goynes-Lee,

The locking problem is not affecting the entire company but a selected few.

Are the affected users all running the WP/DOS program? If they avoid running it (for testing purposes) does the problem remain?

Cameron Purdy

Revelation Software

View this thread on the forum...