Signaling dosemu application to kill itself from Linux
Hello.
Quoted 3 lines · [email protected] wrote:
Quoted 2 lines
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.
Quoted 3 lines
Quoted 2 lines
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.
Quoted 2 lines
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.
Quoted 2 lines
So the PIT is goin crazy after about 3weeks of
running???
Looks like that. I can't try myself to tell for sure though.
Quoted 2 lines
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.
Quoted 3 lines
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.
Quoted 7 lines · On Fri, 08 Apr 2005 07:55:46 +0400 Stas Sergeev <[email protected]> wrote:
Hello.
Quoted 1 line · [email protected] wrote:
Quoted 1 line
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!
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
if you need an LPT too, then that's
a problem.
I knew that wasnt emulated from some posts.
Quoted 2 lines
Quoted 2 lines
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.
Quoted 5 lines
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!
Quoted 5 lines
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
/ __|\\// __|| \ __ __ / [email protected] \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers