CLIPPER LOCKS

CLIPPER LOCKS

[Anderson Pereira Ataides]

Sorry, but I am still having problems with locks.

I followed the steps:

1. $cd /usr/local/src
2. $tar -xzvf dosemu-1.1.3.tgz
3. cd dosemu-1.1.3
4. tar -xzvf ../patchset-1.1.3.4.tgz
5. sh tmp/do_patch
6. cp ../dosemu-freedos-bin.tgz .
7. make
8. ./install_systemwide -i /usr/local/dosemu -fd dosemu-freedos-bin.tgz
9. dosemu

My version of samba is: 2.2.5

After all installed and running, I opened a file (using DBU) in this Linux 
workstation, then I went to a Windows 98 and tried to open the same DBF file 
and id opened. It could not open since DBU opens file exclusive.

So did I do anything wrong?

Anderson Pereira Ataides

Re: CLIPPER LOCKS

[Oscar A. Valdez]

It could be the FreeDOS kernel you are using.

When you start Dosemu, you should see a line that says

"FreeDOS kernel version 1.x.x (Build yyyy)..."

What version and build number are you running?

Oscar

El lun, 07-10-2002 a las 10:35, Anderson Pereira Ataides escribió:
> Sorry, but I am still having problems with locks.
> 
> I followed the steps:
> 
> 1. $cd /usr/local/src
> 2. $tar -xzvf dosemu-1.1.3.tgz
> 3. cd dosemu-1.1.3
> 4. tar -xzvf ../patchset-1.1.3.4.tgz
> 5. sh tmp/do_patch
> 6. cp ../dosemu-freedos-bin.tgz .
> 7. make
> 8. ./install_systemwide -i /usr/local/dosemu -fd dosemu-freedos-bin.tgz
> 9. dosemu
> 
> My version of samba is: 2.2.5
> 
> After all installed and running, I opened a file (using DBU) in this Linux 
> workstation, then I went to a Windows 98 and tried to open the same DBF file 
> and id opened. It could not open since DBU opens file exclusive.
> 
> So did I do anything wrong?
> 
> Anderson Pereira Ataides
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 


-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: CLIPPER LOCKS

[Oscar A. Valdez]

I had similar problems when I started using dosemu/FreeDOS. I was
advised by Bart Oldeman to use kernel 2026a because prior versions
didn't handle locking for networked drives. By now, I think 2026b is
out.

So you would have to download the kernel from
http://sourceforge.net/project/showfiles.php?group_id=5109, extract, and
simply copy it over your existing kernel.sys.

I hope this helps.

Oscar

El lun, 07-10-2002 a las 10:56, Anderson Pereira Ataides escribió:
> I tried with FreeDOS 1.1.24c Build (2024c) and DOS part of MS-Windows 98
> 
> Anderson Pereira Ataides
> 
> 
> Em Seg 07 Out 2002 13:49, Oscar A. Valdez escreveu:
> > It could be the FreeDOS kernel you are using.
> >
> > When you start Dosemu, you should see a line that says
> >
> > "FreeDOS kernel version 1.x.x (Build yyyy)..."
> >
> > What version and build number are you running?
> >
> > Oscar
> >
> > El lun, 07-10-2002 a las 10:35, Anderson Pereira Ataides escribió:
> > > Sorry, but I am still having problems with locks.
> > >
> > > I followed the steps:
> > >
> > > 1. $cd /usr/local/src
> > > 2. $tar -xzvf dosemu-1.1.3.tgz
> > > 3. cd dosemu-1.1.3
> > > 4. tar -xzvf ../patchset-1.1.3.4.tgz
> > > 5. sh tmp/do_patch
> > > 6. cp ../dosemu-freedos-bin.tgz .
> > > 7. make
> > > 8. ./install_systemwide -i /usr/local/dosemu -fd dosemu-freedos-bin.tgz
> > > 9. dosemu
> > >
> > > My version of samba is: 2.2.5
> > >
> > > After all installed and running, I opened a file (using DBU) in this
> > > Linux workstation, then I went to a Windows 98 and tried to open the same
> > > DBF file and id opened. It could not open since DBU opens file exclusive.
> > >
> > > So did I do anything wrong?
> > >
> > > Anderson Pereira Ataides
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Oscar A. Valdez
Gerente de Finanzas y Administración
Plastipak, S.A. de C.V.

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

CLIPPER LOCKS

[Anderson Pereira Ataides]

Hi,

I've got an application develop using Clipper 5.01 and I'm having trouble 
with locks.

When I lock a file (or record) in one workstation using Windows another 
workstation can not open the same file, that's ok. But when I lock a file in 
the same workstation, my Linux + Dosemu does not see that file is locked and 
open it anyway. The same problem occurs between two Linux+Dosemu Workstations.

This problem does not happen when two dosemu sessions are opened in the same 
workstation. In this case, file locked in first session can not be read by 
the second session.

Because of this problem, my application is loosing data, because of 
concurrent updates to a locked file.

How can I solve this problem? Is it a dosemu bug?

I'm using dosemu 1.1.2.

Anderson Pereira Ataides

RE: CLIPPER LOCKS

[Matthew Nuzum]

I had a similar problem with 0.98.  I was using MS Dos 6.2.  I fixed it
by going to the newest version of Samba.  This may or may not be your
solution, here are my details:

DOS program was hosted on Linux Server.  People accessing the
application through a Windows computer (via a Samba share) had serious
locking/not locking issues.

I think my problem was due to Samba 2.0 and going to the (then) new 2.2
fixed it.

Matthew Nuzum
newz@cyberdude.com
www.bearfruit.org

> -----Original Message-----
> From: linux-msdos-owner@vger.kernel.org [mailto:linux-msdos-
> owner@vger.kernel.org] On Behalf Of Anderson Pereira Ataides
> Sent: Friday, June 14, 2002 11:21 AM
> To: linux-msdos@vger.kernel.org
> Subject: CLIPPER LOCKS
> 
> Hi,
> 
> I've got an application develop using Clipper 5.01 and I'm having
trouble
> with locks.
> 
> When I lock a file (or record) in one workstation using Windows
another
> workstation can not open the same file, that's ok. But when I lock a
file
> in
> the same workstation, my Linux + Dosemu does not see that file is
locked
> and
> open it anyway. The same problem occurs between two Linux+Dosemu
> Workstations.
> 
> This problem does not happen when two dosemu sessions are opened in
the
> same
> workstation. In this case, file locked in first session can not be
read by
> the second session.
> 
> Because of this problem, my application is loosing data, because of
> concurrent updates to a locked file.
> 
> How can I solve this problem? Is it a dosemu bug?
> 
> I'm using dosemu 1.1.2.
> 
> Anderson Pereira Ataides
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos"
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: CLIPPER LOCKS

[Anderson Pereira Ataides]

I am already using samba 2.2.

Also I think problem is not with samba because as I told before, it still 
happens between two Linux workstations connected via NFS not samba.

Anderson Pereira Ataides

Em Sexta 14 Junho 2002 12:33, you wrote:
> I had a similar problem with 0.98.  I was using MS Dos 6.2.  I fixed it
> by going to the newest version of Samba.  This may or may not be your
> solution, here are my details:
>
> DOS program was hosted on Linux Server.  People accessing the
> application through a Windows computer (via a Samba share) had serious
> locking/not locking issues.
>
> I think my problem was due to Samba 2.0 and going to the (then) new 2.2
> fixed it.
>
> Matthew Nuzum
> newz@cyberdude.com
> www.bearfruit.org
>
> > -----Original Message-----
> > From: linux-msdos-owner@vger.kernel.org [mailto:linux-msdos-
> > owner@vger.kernel.org] On Behalf Of Anderson Pereira Ataides
> > Sent: Friday, June 14, 2002 11:21 AM
> > To: linux-msdos@vger.kernel.org
> > Subject: CLIPPER LOCKS
> >
> > Hi,
> >
> > I've got an application develop using Clipper 5.01 and I'm having
>
> trouble
>
> > with locks.
> >
> > When I lock a file (or record) in one workstation using Windows
>
> another
>
> > workstation can not open the same file, that's ok. But when I lock a
>
> file
>
> > in
> > the same workstation, my Linux + Dosemu does not see that file is
>
> locked
>
> > and
> > open it anyway. The same problem occurs between two Linux+Dosemu
> > Workstations.
> >
> > This problem does not happen when two dosemu sessions are opened in
>
> the
>
> > same
> > workstation. In this case, file locked in first session can not be
>
> read by
>
> > the second session.
> >
> > Because of this problem, my application is loosing data, because of
> > concurrent updates to a locked file.
> >
> > How can I solve this problem? Is it a dosemu bug?
> >
> > I'm using dosemu 1.1.2.
> >
> > Anderson Pereira Ataides
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-msdos"
>
> in
>
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: CLIPPER LOCKS

[Sergey Suleymanov]

>>>>> Anderson Pereira Ataides writes:

 Anderson> Hi, I've got an application develop using Clipper 5.01 and
 Anderson> I'm having trouble with locks.

 Anderson> How can I solve this problem? Is it a dosemu bug?

        Can you try this fix?

diff -rubN dosemu-1.1.3/src/dosext/mfs/mfs.c dosemu-1.1.3.my2/src/dosext/mfs/mfs.c
--- dosemu-1.1.3/src/dosext/mfs/mfs.c	Tue Apr 23 15:16:39 2002
+++ dosemu-1.1.3.my2/src/dosext/mfs/mfs.c	Mon May  6 10:18:53 2002
@@ -3795,6 +3866,7 @@
 		ret = fcntl (fd,F_SETLK,&larg);
 		Debug0((dbg_fd, "lock fd=%x rc=%x type=%x whence=%x start=%lx, len=%lx\n",
 			fd, ret, larg.l_type, larg.l_whence, larg.l_start,larg.l_len));
+		if (ret == -1) SETWORD(&(state->eax), ACCESS_DENIED);
 		return ret != -1 ? TRUE : FALSE;
 	}
     break;

-- 
  Sergey Suleymanov