From: tonyb@thekrnl.sysdev.org
To: linux-msdos@vger.kernel.org
Subject: Re: Signaling dosemu application to kill itself from Linux
Date: Sat, 9 Apr 2005 16:32:25 -0800 [thread overview]
Message-ID: <20050409163225.641f1276.tonyb@sysdev.org> (raw)
In-Reply-To: <425600C2.7020908@aknet.ru>
On Fri, 08 Apr 2005 07:55:46 +0400
Stas Sergeev <stsp@aknet.ru> wrote:
> Hello.
>
> tonyb@thekrnl.sysdev.org wrote:
> >> Why are you using the direct access
> No, client couldn't request you
> to use the direct access instead
> of an emulated one,
I guess my client has a TSR that installs
its own services for the COM1/2 IRQs and then
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!
>
> >> if you need an LPT too, then that's
> >> a problem.
I knew that wasnt emulated from some posts.
> > but will test as non-root,
> > anyway. Problem is that I believe we already did...
No, we hadnt, they were all members of group root.
So, I had to do a lot of changes to the embedded
linux, It assumed only root access, so had to fix
the permisions in /dev and change many scripts and
permissions...
But when I was able to fire it up, the screen during
dosemu kill was NO LONGER HANGING Linux. And the restarts
occurred fine. This might have also solved the PIT emulation
going crazy, but wont know for 3 or 4 weeks. The idea was
to reset dosemu every week, to avoid the problem.
> Now looking into your report at SF,
> you claim that you use int1a/ah=2, so
> probably my guess about a PIT doesn't
> apply, as the timemode patch affects
> the int1a/ah=2 too.
We are not using INT 1A, I just asked if
I could use that to reset the dosemu clock
back to the correct Linux clock when I detect
that it goes bad. I would add code to the TSR
instead of having to do a dosemu kill and restart!
> If you are using FreeDOS, you can try
> using MS-DOS instead. There are the
> reports where the time gets wrong with
> FreeDOS but not with MS/PC-DOS, which
> I haven't looked up yet.
I was using MSDOS 5.0
Thank you mucho,
for your help and discussion.
Great tech support.
TonyB
--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers
next prev parent reply other threads:[~2005-04-10 0:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 3:55 Signaling dosemu application to kill itself from Linux Stas Sergeev
2005-04-10 0:32 ` tonyb [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-10 8:40 Stas Sergeev
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=20050409163225.641f1276.tonyb@sysdev.org \
--to=tonyb@thekrnl.sysdev.org \
--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