From: John Charlton <j.d.charlton@ieee.org>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: file lock() and share.exe
Date: Sun, 21 Sep 2003 12:10:38 -0400 [thread overview]
Message-ID: <200309211210.38416.j.d.charlton@ieee.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0309210113420.7297-100000@enm-bo-lt.localdomain>
On Saturday 20 September 2003 20:14, Bart Oldeman wrote:
> On Sat, 20 Sep 2003, John Charlton wrote:
> > void chkkbd(void)
> > {
> > int ch;
> > char str[80];
> >
> > fprintf(stderr, "Hit enter to continue, s to stop, q to quit
> > immediately...");
> > fgets(str, 80, stdin);
> > fputs(str, stderr);
> > ch = str[0];
> > if (ch == 's' || ch == 'S') {
> > bStop = TRUE;
> > }
> > if (ch == 'q' || ch == 'Q') {
> > bQuit = TRUE;
> > }
> > }
> >
> > It is a pretty basic function. I did use getchar() at first, with the
> > same result. This function works as intended with kernel 1.1.26a (2026a)
> > or in linux. With kernel 2031 it behaves as described above and if you
> > rerun the same program it crashes the dosemu session.
> >
> > Is there an earlier kernel I can use to solve the share/lock issue and
> > not introduce this stdin problem?
>
> your problem looks like it might have been fixed in the upcoming kernel
> 2032. Please try and test http://freedos.sourceforge.net/kernel/kernel.zip
>
> Bart
Yes the stdin problem is corrected in the 2032 kernel.sys. Thank you.
--John
prev parent reply other threads:[~2003-09-21 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 1:43 file lock() and share.exe John Charlton
2003-09-12 10:21 ` Bart Oldeman
2003-09-12 13:42 ` John Charlton
2003-09-20 22:51 ` John Charlton
2003-09-21 0:14 ` Bart Oldeman
2003-09-21 16:10 ` John Charlton [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=200309211210.38416.j.d.charlton@ieee.org \
--to=j.d.charlton@ieee.org \
--cc=bartoldeman@users.sourceforge.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