Re: Signaling dosemu application to kill itself from Linux

[Stas Sergeev <stsp@aknet.ru>]

Hello.

tonyb@thekrnl.sysdev.org wrote:
>> Why are you using the direct access
>> to the serial ports?
> Client requested it!
No, client couldn't request you
to use the direct access instead
of an emulated one, cause that's
silly. Emulated access works nearly
as fast in the CVS code, there is
no reason for using the direct access,
at least not before you made sure
the emulated access doesn't work
for you properly.

>> if you need an LPT too, then that's
>> a problem.
> Client requirement also
Client couldn't request you to enable
the direct access to an LPT either.
The problem here is that dosemu still
doesn't support an emulated access to
the LPT ports, so you had no choice.
This is something to change in the future.

> but will test as non-root,
> anyway.  Problem is that I believe we already did...
And that didn't fix the rebootes? Sorry,
I have troubles beleiving into this.

> So the PIT is goin crazy after about 3weeks of
> running???
Looks like that. I can't try myself
to tell for sure though.

> If that is so, then why is the Linux
> time correct
We are talking about dosemu here, and
of course I mean the PIT emulation of
dosemu only.

> while the dosemu one goes BAD,
> since with the timemode patch, dosemu is reading
> the linux time directly???
Because the timemode patch affects
only an RTC, and not PIT. Unfortunately
I think such an approach is not possible
for PIT at all.

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.
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.