From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: How-to disable irq4 serial ints
Date: Fri, 10 Jun 2005 23:45:45 +0400 [thread overview]
Message-ID: <42A9EDE9.3010506@aknet.ru> (raw)
Hello.
Hufnus wrote:
> I am afraid that is not exactly true! It is related
> to dosemu not being 100% DOS compatible, when handling these
> programs of ours. Because they have been un-crashable for the
> 20 years that they have been shipped to customers on vanilla
> Dos 3.2 - 6.2
This still doesn't mean your progs
are bug-free. Dosemu is not 100%
compatible mostly in the area of
the hardware timings. For example,
you program may assume that after
it unmasks the IRQ on PIC, it can
still execute a bunch of instructions
before the interrupt is received,
but under dosemu the interrupt can
happen immediately because it doesn't
properly emulate the delays of the
hardware. So you can be interrupted
immediately after you did the "out"
instruction that unmasks an IRQ.
This may be called a bug in dosemu,
but the properly written programs
should not rely on such a things
(fortunately most of them do not).
> The hole issue started when we discovered that: after about 20 or
> 30 days of continuous running the dosemu clock date/time would get
> corrupted.
This really sounds like a bug in
dosemu, but unfortunately most people
do not have a resources for running
such a long tests. And since fixing
this will fix also another problem of
yours, it would be nice if you track
this one down on dosemu side:)
next reply other threads:[~2005-06-10 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 19:45 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-10 15:38 How-to disable irq4 serial ints Stas Sergeev
2005-06-10 19:13 ` Hufnus
2005-06-10 3:49 Hufnus
2005-06-10 5:08 ` Hufnus
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=42A9EDE9.3010506@aknet.ru \
--to=stsp@aknet.ru \
--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