Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Signaling dosemu application to kill itself from Linux
Date: Sun, 10 Apr 2005 12:40:44 +0400	[thread overview]
Message-ID: <4258E68C.1050303@aknet.ru> (raw)

Hello.

tonyb@thekrnl.sysdev.org wrote:
> handles the I/O to 378h and 3f8h.  Since
> he was not using INT 14h, I didnt realize
> that your dosemu abstraction (emulation)
> would filter both port and IRQ I/O!
Thats actually a common problem here.
People assume that something doesn't
work without even trying it (even after
they were suggested to try), and the
serial ports is a most frequent casuality
of such a self-delusion.

> But when I was able to fire it up, the screen during
> dosemu kill was NO LONGER HANGING Linux. And the restarts
> occurred fine.
Good that is now works. But it would
be nice to understand where the problem
was, so that we can fix it. Your config
looks mostly safe, but there are still
those dangerous things like the hardware
ram and irqpassing (and I really think
that the hardware_ram thing was not
tested here for about something like 5
years or more, so it can easily be broken).
It would be nice if you try the things
as root again, but with the fresh dosemu.conf,
the one with everything is commented out,
and see whether it still hurts the linux
box or not. If it works without the
lookups/rebootes, then you can easily
locate an option of dosemu.conf that
made the problem for you. And it should
be the latest CVS code of dosemu to
make the testing more valueable.

> This might have also solved the PIT emulation
> going crazy, but wont know for 3 or 4 weeks.
This is very unlikely, but keep us
informed.

> The idea was
> to reset dosemu every week, to avoid the problem.
Quite pity that such a hacks are
still needed. Apparently dosemu was
never tested for such a long uptimes.

>> >> if you need an LPT too, then that's
>> >> a problem.
> I knew that wasnt emulated from some posts.
So how at the end you got the LPTs to
work without a root? To the best of
my knowledge, it is not possible right
now, unless you implemented the missing
emulation yourself. (I don't mean the
printing-only mode, which is how the
LPT emulation is implemented right now)

> We are not using INT 1A
OK, then please refresh my memory on
what you actually use and I'll take
another look at that code.

> I would add code to the TSR
> instead of having to do a dosemu kill and restart!
Yes, that should work.


             reply	other threads:[~2005-04-10  8:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  8:40 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-08  3:55 Signaling dosemu application to kill itself from Linux Stas Sergeev
2005-04-10  0:32 ` tonyb
2005-04-07 17:59 Stas Sergeev
2005-04-07 17:50 Stas Sergeev
2005-04-08  2:14 ` tonyb
2005-04-07  3:45 Stas Sergeev
2005-04-07  9:07 ` Andrew Brooks
2005-04-07 16:23   ` tonyb
2005-04-07 17:25     ` Gene Heskett
2005-04-07 16:06 ` Gene Heskett
2005-04-07 16:35   ` Andrew Brooks
2005-04-07  3:38 Stas Sergeev
2005-04-07  6:12 ` tonyb
2005-04-06 16:06 Stas Sergeev
2005-04-06 22:16 ` tonyb
2005-04-07  0:47   ` Gene Heskett
2005-04-06  7:14 tonyb

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=4258E68C.1050303@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