Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Hufnus <tonyb@thekrnl.sysdev.org>
To: linux-msdos@vger.kernel.org
Cc: Gordon Morris <gmorris@toyecorp.com>
Subject: Re: How-to disable irq4 serial ints
Date: Fri, 10 Jun 2005 11:13:51 -0800	[thread overview]
Message-ID: <20050610111351.26ea2d8d.tonyb@sysdev.org> (raw)
In-Reply-To: <42A9B402.4080201@aknet.ru>

On Fri, 10 Jun 2005 19:38:42 +0400
Stas Sergeev <stsp@aknet.ru> wrote:

> Hufnus wrote:
> > Problem is, if the serial device on /dev/ttyS0 is receiving
> > data and generating ints, this serial servicing tsr crashes
> > during its init.
> So finally you did what I suggested,
> and located the broken DOS program
> instead of presuming the bugs in dosemu?

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

I dont see a fault with Dosemu handling of serial, execept when
we mix it with this Quick Basic/asm Serial I/O TSR combination!

It only crashes Dosemu on a Dosemu restart, if the serial device is
left ON, sending I/O at 1200 baud.

It does not crash when Dosemu starts or when the asm Serial I/O TSR
installs. It crashes on the initial requests between the Quick Basic
Gui trying to start getting serial data events.

Its a hard debug, but we are slowly narrowing THE WHAT is happening,
so it can be resolved, whatever it is...

But it is related to Dosemu 1.2.0 -> 1.3.2, with MsDos 5.0 files,
with our 2 programs, not getting along when Dosemu starts while
serial events are takin place.

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. So we started restarting Dosemu about once every 10 days
to get around the corruption.

It is still NOT clear what is at fault,
but it works with real DOS, but that is a
different environment.

Thanks
TonyB

> > Basically I was wondering, if masking the PIC with a 0x04 by
> > doing I/O to port 0x21 would work in dosemu emulation or if there
> > is a better way to do this?
> This *of course* works under dosemu.
> But this may be irrelevant. Because
> unless I am seriously mistaken, the
> DOS doesn't unmask the serial port
> IRQs by default. So if this is the
> problem, you have to search further
> and locate another broken program of
> yours that unmasks the IRQ and forgets
> to mask it back before exit.
> 
> -
> 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
> 


--
  __      __  _     I N C.               http://www.sysdev.org
/ __|\\// __||  \  __   __          /         tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers


  reply	other threads:[~2005-06-10 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 15:38 How-to disable irq4 serial ints Stas Sergeev
2005-06-10 19:13 ` Hufnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-10 19:45 Stas Sergeev
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=20050610111351.26ea2d8d.tonyb@sysdev.org \
    --to=tonyb@thekrnl.sysdev.org \
    --cc=gmorris@toyecorp.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