public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Samek <webmaster@tony.cz>
To: Linux-MSDOS Mailing list <linux-msdos@vger.kernel.org>
Subject: Re: dosemu-1.1.3.3 for testing
Date: 19 Sep 2002 13:37:45 +0200	[thread overview]
Message-ID: <1032435466.1759.4.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0209141833180.3456-100000@enm-bo-lt.enm.bris.ac.uk>

Neither 1.1.3.3 nor 1.1.3.4 don't solves the locking problems with
clipper apps. The behaviour is the same as before.

Michal Samek

On Ne, 2002-09-15 at 00:58, Bart Oldeman wrote:
> Hi,
> 
> a new prerelease is available at http://www.dosemu.org/testing
> This includes the keyboard fixes, the 30 minutes in DOS EDIT problem, the
> hlist fix (255 times "dir" gave problems), various other MFS (for
> lredir'ed drives) changes, some DPMI PIC fixes and some of part of the
> work to get non-suid-root IPX working.
> 
> I also included Per's get PID and PPID patch and Clarence's patch to show
> the current program in the xdos title bar if you run comcom.com.
> 
> See the Changelog (in the patch) for other things and more details.
> 
> It would be good to get some feedback from people who need locking (for
> Clipper, FoxPro and friends) as I changed the file locking scheme to be
> more like what DOS expects and also added a patch from Sergey.
> 
> Especially if it is worse than before please tell me.
> 
> If you still have problems with locking try the patch from Sergey and see
> if it makes a difference. It should not go in until we understand the bit
> fiddling however.
> 
> Bart
> 
> diff -ur dosemu-1.1.3.3/src/dosext/mfs/mfs.c dosemu-1.1.3.3.bart/src/dosext/mfs/mfs.c
> --- dosemu-1.1.3.3/src/dosext/mfs/mfs.c	Sun Aug 18 18:45:42 2002
> +++ dosemu-1.1.3.3.bart/src/dosext/mfs/mfs.c	Sat Sep 14 18:32:38 2002
> @@ -3864,8 +3864,12 @@
>  			the top two bits are set. Shift the top ones by two bits. This
>  			still allows OLE2 apps to operate, but should stop lockd from
>  			dieing */
> +#if 0
>  		if ((larg.l_start & mask) != 0)
>  			larg.l_start = (larg.l_start & ~mask) | ((larg.l_start & mask) >> 2);
> +#else
> +		larg.l_start &= 0x7fffffff;
> +#endif
> 
>  		ret = fcntl (fd,F_SETLK,&larg);
>  		Debug0((dbg_fd, "lock fd=%x rc=%x type=%x whence=%x start=%lx, len=%lx\n",
> 
> 
> -
> 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



      parent reply	other threads:[~2002-09-19 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-14 22:58 dosemu-1.1.3.3 for testing Bart Oldeman
2002-09-16  8:26 ` Grigory Batalov
2002-09-16 14:34   ` Bart Oldeman
2002-09-19 11:37 ` Michal Samek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1032435466.1759.4.camel@localhost.localdomain \
    --to=webmaster@tony.cz \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox