Dear dosemu person,
Below is a note that I recently sent to H. Lermen, but from which I've
received no reply. It explains what my situation is, and about the crashes.
The block of error codes immediately below is something I obtained today
while running dosemu and the same DOS application in foreground. Have you
any thoughts as to what is happening, or what I can do to help track down
the bug?
Thanks for your help.
ERROR: unexpected CPU exception 0x06 errorcode: 0x00000000 while in vm86
(DOS)
Program=sigsegv.c, Line=250
EIP: fff1:00003051 ESP: c04a:000017d2 VFLAGS(b):
00000 00111000 10000111
EAX: 000036fe EBX: 00000000 ECX: 00000000 EDX: 00000117
VFLAGS(h): 00003887
ESI: 000017e7 EDI: 00000002 EBP: 00001868 DS: c04a ES: 9000 FS:
0000 GS: 0000
FLAGS: CF PF SF IF OF RF VM IOPL: 3
STACK: 51 1f 00 01 00 00 00 37 3c
10 -> 4f 1e 26 fa 16 32 23 19 00 90
OPS : 00 db 8e 03 2d 02 00 19 00 af -> 8e 08 6c
06 00 1a 00 e1 8e 70
8e08 fff1:3051 mov cs,[bx+si]
~ Gary
/---------------------------------------------------------------------------
\
| Gary Trachier / U. S. Army Cold Regions Research & Engineering Laboratory
|
| Internet: [EMAIL PROTECTED]
|
| CorpsMail: [EMAIL PROTECTED]
|
| Telephone: voice (603) 646-4303 fax (603) 646-4720
|
| USnail: (.^.) USA CRREL / 72 Lyme Road / Hanover, NH USA / 03755-1290
|
\--------A--U--A------------------------------------------------------------
/
> ----------
> From: Trachier, Gary M ERDC
> Sent: Donnerstag, 9. Dezember 1999 10:34
> To: 'Hans Lermen'
> Subject: RE: DOSemu in background
>
> Hans,
>
> Thank you very much for your help last September. I was able to make
> dosemu run as I needed in background. It is running a DOS program that
> collects data from remote dataloggers. The program uses 2 serial ports.
> There is however still a nagging question. I find that some times I start
> dosemu and it runs fine for several weeks (at least). Other times I start
> it and it runs only a few hours, or a few days, then crashes. The symptom
> when it goes kaput is use all of the CPU time. For example, I started it
> about 4 weeks ago, and today using ps I got the following information.
>
> 16 hanish> ps -C dos -f
> UID PID PPID C STIME TTY TIME CMD
> trachier 5692 1 0 Nov18 ? 00:01:21 dos -I video{none}
> keystroke "cd pc208\rtelcom master.scr\r"
>
> It had used only 1:21 of CPU time during 4 weeks. I started a system
> backup this morning that uses tar to copy files to a Jaz disk. A few
> minutes later I got the following information.
>
> 16 hanish> ps -C dos -f
> UID PID PPID C STIME TTY TIME CMD
> trachier 5692 1 0 Nov18 ? 00:05:17 dos -I video{none}
> keystroke "cd pc208\rtelcom master.scr\r"
>
> As you can see, it is starting to use more CPU time. Often dosemu will
> crash and continue to use all of the CPU time. It will continue to use
> many hours until I kill the process. One day I ran it in foreground and
> when it crashed, I got the following information.
> ---------------------------------------------------
> .
> .
> .
> 110F
> 110F
> 110F
> 24F
> C
> Y99 D0288 T10:04:28 C1301
> *E
> !R
> 0000 0187 0054
> 0000 0179 0052
> !T
> Next time for "testcell" is 10/15/99 10:15:00
>
> Waiting for:
> - next wake up time (10/15/99 10:07:00)
> - PC203 on/off switch to be turned on
> - modem ring signal to become active
> - a ctrl-C or Esc to be pressed
>
> Next time for "reno1d" is 10/16/99 01:00:00
> Next time for "reno2d" is 10/16/99 01:30:00
>
> Calling Station "eallen"
>
> IO_attach() -out of memory
>
> Memory allocation error
> Cannot start COMMAND, exiting
> �|+�*�6��|*�.��|d@�*�%����*�-��|> *���DC:\COMMAND.COM{ �sF&�d<
> t`F.�s.f�u^&;Lhr
> 6ws&;T�r.&;Lw(r:&;Tcw �2&;Lh|^^s&;T�|>&;L^
> |-&;Tc^@��} =`u{.}s�fs :�{ �|:�&�d`�S{H=![r7Ph}c �*&�+lh+h+&h+l�+
> �+2��+|`�h
> Xs�`. I=!�* X&��h�m=ZX& s%ds&�s�h&}s &�h ^�^�+3`�^"d&�^ �} �#d}s"d &�c
> 3`�#d�^
>
> -------------------------------------------------------
>
> The upper part is normal output from the DOS program. It then appears to
> crash because of a memory error. It appears that when the system has a
> very light load that everything is fine. If dosemu must compete for
> resources (memory?) then it makes trouble.
>
> Have you any thoughts as to what the problem is? Let me know if you have
> any questions. Thank you very much.
>
> ~ Gary
>
>
> /-------------------------------------------------------------------------
> --\
> | Gary Trachier / U. S. Army Cold Regions Research & Engineering
> Laboratory |
> | Internet: [EMAIL PROTECTED]
> |
> | CorpsMail: [EMAIL PROTECTED]
> |
> | Telephone: voice (603) 646-4303 fax (603) 646-4720
> |
> | USnail: (.^.) USA CRREL / 72 Lyme Road / Hanover, NH USA / 03755-1290
> |
> \--------A--U--A----------------------------------------------------------
> --/
>
>
> ----------
> From: Hans Lermen
> Reply To: Hans Lermen
> Sent: Freitag, 24. September 1999 8:05
> To: Trachier, Gary M CRL
> Cc: [EMAIL PROTECTED]
> Subject: RE: DOSemu in background
>
> On Fri, 24 Sep 1999, Trachier, Gary M CRL wrote:
>
> > That is unfortunate news,
>
> No reason to give up with this issue ;-)
>
> There are some limited ways to run DOSEMU in the background.
> However, STDIN can't be feed in via a pipe, you need the 'keystroke'
> feature to 'type-in' some few commands (rest has to be DOSish).
> Look at ./doc/README.txt chapter "Running a DOS-application directly from
> Unix shell" and especially "Running DOSEMU within a cron job".
>
> The below script would run DOSEMU, start an application 'myapp' and then
> exit. The (DOSish) output goes into the file '/tmp/outfile' :
>
> #! /bin/bash
> export TERM=dumb
> exec dos </dev/null 2>/dev/null >/tmp/outfile \
> -I 'video{none} keystroke "myapp\rexitemu\r"'"
>
> ... and this script very well should run in the background ;-)
>
> Hans
> <[EMAIL PROTECTED]>
>
>
>
