NT Lazy Write (AREV Specific)
At 18 MAR 1998 05:32:04PM Russell Causey @ Lifescan, Inc. wrote:
When I installed the NLM and began allowing Win95 workstations access to AREV I was warned to never ever allow access to one with 'DriveWriteBehindCaching' enabled. The reason being that it would surely cause GFE's. It's been almost a year and we haven't had any problems. Not one GFE!
Now I have users demanding that they be allowed access from NT 4.0 Workstation. NT uses a similar technique called Lazy Write. I'm assuming that this should also be disabled. I have two questions?
How do you disable Lazy Write?
Is it really necessary to disable it?
Thanks,
Russ
At 19 MAR 1998 11:25AM Aaron Kaplan wrote:
Probably. What you want to avoid is the workstation caching server information. However you need to do this is what has to be done. The trick is to make sure that if the file changes size or hashes, you have correct information. If you write back with old frame data, you'll cause a GFE.
apk@sprezzatura.com
At 20 MAR 1998 02:15PM Russell Causey @ Lifescan Inc. wrote:
According to the NT expert I need to use Regedit to put a Dword value of 00000000 in both HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanworkstation\Parameters.
This came with warnings of dire consequences should you blow the regedit, and also that it slows down your network.