From: "Vasil Daskalov" <vbdasc@ekom2002.com>
To: linux-msdos@vger.kernel.org
Subject: Opening a file for exclusive access in DOSEMU
Date: Fri, 30 Jan 2004 19:37:53 +0200 [thread overview]
Message-ID: <001c01c3e757$ce2d9290$036511ac@comp3> (raw)
Hi all,
I'm trying to run a Clipper database program in network mode in DOSEMU. The
program opens some files for exclusive access, assuming that no other
program can open them. This assumption holds true under MSDOS 6.22, Windows
2000 and other network environments. However, two instances of this program,
running in two instances of DOSEMU on one Linux machine, can open these
files simultaneously, ruining the program logic. The machine runs Debian
Linux 3.0, kernel version 2.2.20. The DOSEMU is the latest version, 1.2, the
DOS is MS DOS 6.22. The database files are located on the DOSEMU drive C: ,
which is a linux directory, with a symlink " ~/.dosemu/drives/c " pointing
to it. I tried moving the files to a lredir-ed drive with no success. Tried
to run SHARE.EXE in AUTOEXEC.BAT - again no success. This problem is
apparently not Clipper-related, because it can be easily reproduced with two
instances of a simple QBASIC program, which opens a file in the following
fashion:
OPEN "FILE.TMP" FOR BINARY ACCESS READ WRITE LOCK READ WRITE AS #1
Then the two instances easily open the file simultaneously, which shouldn't
be possible.
Besides, DOSEMU gives me the following message:
SHAREing doesn't work on drive C: (probably NFS volume?)
This is probably related to the problem. I wonder, why SHAREing doesn't
work? I'm sure I don't have any NFS volumes in my system. Any suggestions?
TIA,
Vassil Daskalov
next reply other threads:[~2004-01-30 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 17:37 Vasil Daskalov [this message]
2004-01-30 20:25 ` Opening a file for exclusive access in DOSEMU Bart Oldeman
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='001c01c3e757$ce2d9290$036511ac@comp3' \
--to=vbdasc@ekom2002.com \
--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