Win95 and NT locking problem 
Author Message
 Win95 and NT locking problem

Hi

I am experiencing problems connecting NT 4 workstation (SP4) with win95
computers.  I appears to be a locking problem.  I was experiencing lock
Time Outs.  Since I have done the changes below it appears to have
gotten worse rather than better.

NT4 computer is where all the data is stored and the win95 computers (4
of them) contain the forms.

win95  Changes:

(a) Added this key
Key: KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VREDIR
Value added : DiscardCacheOnOpen (binary value)
Data : 01
(b) vredir.vxd version 4.00.1116 installed on each
(c) Disabled (1) new file lock and sharing semantic (2) write behind
caching
(d) BDE local share set to TRUE

Changes to NT workstation 4:
Key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

Added Value : EnableOplocks   (dword)         Data : 0
Added Value : CacheOpenLimit (dword)        Data : 0
Added Value : EnableOpLockForceClose (dword)    Data : 1

Key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters

Added Value : UseOpportunisticLocking   (dword)         Data : 0
BDE : Local share is set to true

Is EnableOplocks the correct case?
Is EnableOpLockForceClose (dword) a dword type?

The Pdoxusers.net file appears to be working ok because if I look at the
current user list all five computers are listed.

When a locking problem occurs I noticed by looking at the NT under
server used files that

                    For        locks
Register4    write           1       D:\...\Pdoxusrs.lck
Register3    write           0       D:\...\Pdoxusrs.lck

Other than that there were no other duplicated files
Does the D:\...\    cause a problem?

The shared name on the NT is "Data Area" - does the space cause a
problem?
The ... above represents "Network Files" - does the space cause a
problem?

How do I solve my locking problem?

TIA
Ronald



Sun, 14 Oct 2001 03:00:00 GMT
 Win95 and NT locking problem

Hi

Is case in the registry important?

Would making all computers win95 fix my problem ?
or
if I moved my data tables and the paradox net file on a win95 machine fix it for me?

What else can I do - I have tried everying that I can find and it has not gotten any
better?

TIA

Ronald Singh



Tue, 30 Oct 2001 03:00:00 GMT
 Win95 and NT locking problem
Ronald:

Quote:
>Is case in the registry important?

Yes, from everything I know or have read, it's very important.

It sounds like your network is peer-to-peer.  Does your problem go
away if you take the NT machine out of the loop?  Also, ensure that
"local share = true" is set within the BDE for each machine.

HTH.

Bob



Thu, 01 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem

Quote:

> It sounds like your network is peer-to-peer.  Does your problem go
> away if you take the NT machine out of the loop?  Also, ensure that
> "local share = true" is set within the BDE for each machine.

> HTH.

> Bob

Hi Bob

What I have is a 4 win95 "cash registers" accessing data on  the NT4
workstation SP4 which is also used as a cash register.

If 1 win95 register is working and all other computers are not using the
same paradox  tables then access to the data on the NT computer works
well.  If the computers are not sharing files ONE win95 computer will
work without problems when using data on the NT.  If we add other
computers to share these tables then the locking occurs.  However, if
the other computers are using paradox and not using the same tables then
there tends not to be any locking.  Locking appears to occur only when
paradox is sharing files.

Because any of the win95 computers can access the data on the NT (one at
a time without sharing) and windows has never GPF or lost the mouse or
keyboard - I think the network is ok.

The locking problem also occurs with different combinations of machines
- so i don't think that it is a hardware problem.

The paradox *.net and *.lck files are always open when the timeout
occurs - other than that it is various datatbase files that have been
used that are shown as open.  This can be seen on the NT computer. How
can you determine which file is actually causing the timeout lock

Could my locking problem be caused by coding - I do not place any locks
on the system, Paradox does it all for me.

Local Share is set to true.
My drives are all mapped the same except the drive letter.
CacheOpenLimit has been updated to the correct value of CachedOpenLimit
EnableOpLockForceClose has the case corrected to EnableOplockForceClose

When the NT computer is running as a cash register if a lock occurs and
I use NT to close the other resources the lock is immediately freed and
the NT computer can progress as normal.

What can I do to try to solve this problem - I think I have tried
everything that I have seen on the newgroup?

Are my registry values correct and in the correct spots?

Should I try to temporarily take the NT computer off the network (ie not
switch it on) and move my data files onto an win95 machine and see if
that corrects the sharing problem?

All tables have been verified with chimneysweep 3.0
scandisk and defragments have been done on the win95 computers

This problem is wearing me down - what am i doing wrong. Please help!

TIA
Ronald Singh



Fri, 02 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem
Hi

I tried not using the NT computer eg I had 4 win95 computers networked.  I
transferred the data files (tables)  from the NT to a win95 computer.

When I ran the "cash register" I experienced a locking problem.

However, I thing that I discovered is that I think the locking problem is
caused by the BDE.  When a lockup occurs the user name is dropped from the
user list.  Before the lockup the computer is seen by paradox (it is a
listed user) then after the lockup paradox does not see the user even though
the paradox screen is still open.  What could be causing this?

I think if I can determine what is causing the users to drop off the
"paradox network" then I think that I will solve my problem.

Could I have set something incorrectly in the BDE configuration?

TIA
Ronald Singh



Sat, 03 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem
Ronald:

What are the versions of Pdox and BDE that you're using?

Bob



Sun, 04 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem

Quote:

> Ronald:

> What are the versions of Pdox and BDE that you're using?

> Bob

I am using paradox 8 and runtime 8.  I have not applied the service
pack.
I have just upgraded to BDE 5.01 on all computers to see if this would
fix my problem but it did not

Ronald Singh



Sun, 04 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem
As you suggest, "try to temporarily take the NT computer off the
network (ie not switch it on) and move my data files onto an win95
machine and see if that corrects the sharing problem?" If so, try
bringing the NT back.

Other than that, it sounds like you're using the NT as just another
workstation; I suspect that if you upgraded it to a Server system
things would go better, but I can't say for 100% sure.
--
Mike Irwin
[Volunteer CTech Sysop, not a Corel employee
Please post enquiries and responses to the Corel newsgroups
(cnews.corel.ca).]



Wed, 07 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem
I agree that moving from NT Workstation to NT Server is probably
required.  Workstation has a "10 user" limit, but it it really a 10
connection limit & you can end up with multiple connections from another
PC depending upon what you are doing.  It is real easy to run out of
resources in this way.


Fri, 09 Nov 2001 03:00:00 GMT
 Win95 and NT locking problem

Quote:

> As you suggest, "try to temporarily take the NT computer off the
> network (ie not switch it on) and move my data files onto an win95
> machine and see if that corrects the sharing problem?" If so, try
> bringing the NT back.

I have now tries this and the system became even more unstable.  With
the win95 computer (using paradox) connected to another win95 computer
(not using paradox) but had the data tables on it the system needed to
be rebooted a lot (sometimes after a few sales on the computer).

One win95 with paradox running sharing data on the NT (paradox not
running ) would only lock up if another paradox user came on - if no
other paradox user came onto the system then this configuration was
stable and would not crash.

Could my problem be coding -  if so what should I be looking for.

Quote:

> Other than that, it sounds like you're using the NT as just another
> workstation; I suspect that if you upgraded it to a Server system
> things would go better, but I can't say for 100% sure.
> --

Do I need to buy NT Server or can I tweak NT workstation to act like a
server?

TIA
Ronald Singh



Sun, 11 Nov 2001 03:00:00 GMT
 
 [ 10 post ] 

 Relevant Pages 

1. Locking Btrieve with NT, not with Win95?

2. Help!!! Multiuser locking problems for Win95

3. Paradox locking problem with Win95 ??

4. Problems connecting a Win95 client to NT/SQLserver7 through ODBC

5. ODBC Problems under Win95/NT using Visual FoxPro

6. Oracle, NT and Win95 Comms Problem

7. Miracle Y2K problem among Oracle, NT, and Win95

8. Data Connection lost problem?/Win95 to NT Server

9. Chinese Win95 and English Win95 Problem

10. Lock problem for databases on NT : no solution ?

11. Sybase 11 on NT : problems with locking......

12. Locking problems on SQL Server for NT


 
Powered by phpBB® Forum Software