XP Problem

N

Nick Swart

Hi

We have a 16 bit DOS based application. It accesses data
through the network. The database is dBase III. For years
it worked perfectly under any Windows OS. However with
WinXP we are encountering file locking problems. Some of
our earlier problems we were able to fix, but the file
locking one we have been unable to resolve..

The following happens when we open the files in Shared
mode:
The first user is OK
As soon as another user opens a file exclusively, with
another user on the system, and busy accessing any file in
the database, the file they are trying to access is found
locked and remains locked after the operation in
completed.
Interrogating the network with Computer Manager on the
Win2000 server, you can see the file is in use by the user
that locked it exclusively, although the user is not using
the file, and has in fact closed the file.
To make the file available again to everyone after it
becomes locked, the needs to close the applications, then
everyone else can continue working. This is an
intermittent file locking and there is no pattern to the
problem.

I have been to http://support.microsoft.com/ and from the
articles that I've read, referenced below, my
understanding is that it is an Opportunistic Locking
issue. I have changed registry settings, as shown below,
but the only difference it makes, is access is either
faster, or slower, but the problem persists.

I have updated WinXP to SP1a.

Is there something I'm missing or is it a problem with
WinXP?

Article I'm referencing to is 812937
http://support.microsoft.com/default.aspx?scid=kb;en-
us;812937



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nServer\Parameters]

"autodisconnect" = dword:ffffffff
"CachedOpenLimit" = dword:00000000
"EnableOpLockForceClose" = dword:00000001
"EnableOpLocks" = dword:00000000
"SharingViolationDelay" = dword:00000000
"SharingViolationRetries" = dword:00000000


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nWorkstation\Parameters]

"UseOpportunisticLocking" = dword:00000000
"UtilizeNtCaching" = dword:00000000
"UseUnlockBehind" = dword:00000001
"UseLockReadUnlock" = dword:00000000


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSm
B\Parameters]

"OplocksDisabled" = dword:00000000
 
S

Steven Liu [MSFT]

Hi Nick,

This problem may be resolved by applying a supported fix which is now
available from Microsoft. To resolve this problem immediately, contact
Microsoft Product Support Services to obtain the 812937 fix. For a complete
list of Microsoft Product Support Services phone numbers and information
about support costs, please go to the following address on the World Wide
Web:

http://support.microsoft.com/directory/overview.asp

NOTE: If you contact Microsoft to obtain this fix, a fee may be charged.
This fee is refundable if it is determined that you require only the
requested fix. However, this fee is non-refundable if you request
additional technical support.

Thanks for using Microsoft News Group!

Sincerely,

Steven Liu

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top