Here's two possible reasons, Charlie...

1) On the server, recently turned it ON after having it off all these years. Often done by the uninitiated, until they learn better (at least that's what my net admin told me years ago when I argued to have it on and I agreed a little later that she was right).

2) On the client, recently upgraded to HDs that have a cache on their controllers, which of course is defaulted to ON.

cheers

>Hi James,
>We just went through something similar. A program had run fine for many years and all of a sudden, lockups and sluggish performance. Network Admin set file caching off on the Novell server and everything is back to normal. He suggested to turn off file caching on the Novell Client's properties too--and we are, but the server change seems to have done the trick. Why now after all these years, I have no idea.
>
>>Thanks Jim,
>>
>>I will give that a try and let you know.
>>
>>:-)
>>
>>>Well, if that is the case, try DISABLING the write-caching on the HD(s) where it is running.
>>>
>>>That reportedly made a difference for one soul here.
>>>
>>>good luck
>>>
>>>
>>>>Thanks for the input, unfortunately that is looking like my only option.
>>>>
>>>>Thank you!
>>>>
>>>>;-)
>>>>
>>>>>Radical, but we format the hard drive on the rogue machine and re-install Windows