From: "J. Solomon Kostelnik" <roz@one.net>
To: DOSEMU List <linux-msdos@vger.kernel.org>
Subject: Re: MFS: possible bad behaviour of the function exists
Date: 14 Dec 2002 11:40:33 -0500 [thread overview]
Message-ID: <1039884034.2207.6.camel@jsk.one.net> (raw)
In-Reply-To: <20021214133836.GA1585@ens-lyon.fr>
On Sat, 2002-12-14 at 08:38, Emmanuel Jeandel wrote:
> However, if i execute :
> PROMPT>E:
> PROMPT>bar
> bar.exe is not found (it is found by "dir", by "type", but i can neither
> execute it nor modify it with an editor)
I get this same problem in 1.1.3.7 with all experimental patches
applied. I have my C: linked to a real Linux directory,
/var/lib/dosemu/C -- if I try to edit (DOS' edit) anything in the root
directory it says "Edit was unable to access the file 'C:\'", even
though I typed "edit config.sys" in C:\ (it actually does the same thing
in any directory). It also ends up deleting the file I was trying to
open. However, ezedit works fine.
I also get some very strange behavior if I try to save a file. If I
attempt to save to a filename that does not exist, it will ask me if I
want to replace the existing file! If I say yes, it'll give me an error
that it wasn't able to write it, but I still end up with a new filename
named something like "ALCGDCEO." Very odd.
Any ideas?
Solomon
next prev parent reply other threads:[~2002-12-14 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 13:38 MFS: possible bad behaviour of the function exists Emmanuel Jeandel
2002-12-14 16:40 ` J. Solomon Kostelnik [this message]
2002-12-14 21:25 ` Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-12-15 1:50 Stas Sergeev
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=1039884034.2207.6.camel@jsk.one.net \
--to=roz@one.net \
--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