From: "Dan Egli" <dan@shortcircuit.dyndns.org>
Cc: linux-msdos@vger.kernel.org
Subject: Re: SegFault
Date: Tue, 25 Jun 2002 19:02:22 -0600 [thread overview]
Message-ID: <00cc01c21cad$22704c20$4600000a@FlagShip> (raw)
In-Reply-To: 005701c21cac$55a19280$4600000a@FlagShip
One more thing that could be of value is the config.sys file, so it is
pasted below:
DEVICE=C:\DRDOS\SETVER.EXE
SHELL=C:\COMMAND.COM C:\ /E:512 /P
BREAK=ON
BUFFERS=30
LASTDRIVE=Z
HISTORY=ON,512,ON
COUNTRY=1,,C:\DRDOS\COUNTRY.SYS
DOS=HIGH,UMB
FILES=100
----- Original Message -----
From: "Dan Egli" <dan@shortcircuit.dyndns.org>
To: <bonz@misty.apana.org.au>
Cc: <linux-msdos@vger.kernel.org>
Sent: Tuesday, June 25, 2002 6:56 PM
Subject: Re: SegFault
> Sorry! I was rushed and I forgot some things!
>
> I'm CCing the list on this..
>
> Distribution: RedHat 7.3
> DosEMU Ver (as reported by RPM) 1.1.1-3
> DOS ver: Caldera Dr-Dos 7.03
> Program: FastEcho 1.46 (I'd not be surprised if no one has heard of it).
> EMS/XMS/DPMI define: 8192KB
> CPU defined: 80586
> PCI: On
>
> Anything else that would be of value? I'll name it off if requested.
> ----- Original Message -----
> From: "Bonz" <lemmings@microsoft.com>
> To: "Dan Egli" <dan@shortcircuit.dyndns.org>
> Sent: Tuesday, June 25, 2002 3:31 PM
> Subject: Re: SegFault
>
>
> > Dan Egli wrote:
> > >
> > > I thought everything was working grand, when all of a sudden, I
noticed
> that
> > > DosEMU was crashing when I ran a certain program. This program starts
> up,
> > > looks fine for a while, then all of a sudden, DosEMU dies. The error
is
> > > listed below (I tried to extract it from the program header on the
> screen so
> > > if something is missing, sorry)
> > >
> > > ERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=00000000 while
> in
> > > vm86 (DOS)
> > > Program=sigsegv.c, Line=190
> > > EIP: 0000:0000000c ESP: 2890:0000072c VFLAGS(b): 00000 00000010
> 00010010
> > > EAX: 00000006 EBX: 276b0007 ECX: 00000002 EDX: 0000200d VFLAGS(h):
> 00000212
> > > ESI: 00000007 EDI: 0000075f EBP: 00000000 DS: 1c58 ES: 0000 FS: 0000
GS:
> > > 0000
> > > FLAGS: AF IF RF VM VIF IOPL: 06)
> > > STACK: 00 20 07 00 00 00 00 00 00 00 -> 00 00 00 00 00 00 00 00 00 00
> > > B0\x0f : aa 03 c6 20 97 0d 20 00 00 f0 -> c6 20 97 0d 29 02 70 00 50 00
> > > = 62097 0000:000c mov [bx+si],97
> > >
> > > Anyone know how I could fix this?
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-msdos"
> in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > That's not very helpful.
> >
> > If you are expecting a response from the list supply at the very least,
> > the distribution you are using, for instance debian woody
> > the version of dosemu you are running, for instance 1.0.2.1
> > the actual operating system you are using, for instance DR Open-DOS
> > 7.02,
> > the program that caused the error, for instance master of magic 2.3
> >
> > It is quite possible that different dos versions might work under dosemu
> > with the software you are trying to run.
> > By supplying this information people can try other versions of dos &
> > determine the exact cause of the problem & possibly even suggest a
> > solution like (freedos does not support blah-blah & will cause dosemu to
> > segfault, try opendos 6.3 or higher instead)
> >
> > When you report a problem with your car to a mechanic over the phone, do
> > you withhold the model & year of your car & expect him to provide you
> > with a quote to fix the problem?
> >
> > Other things that may help define the problem would be certain
> > configuration parameters like the amount of ems, etc you have
> > configured, especially if the program you are trying to use creates a
> > lot of memory pages.
> > I suggest you relook at the problem & then ask yourself If I was helping
> > me to fix this what would I need to know?
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2002-06-26 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 20:13 SegFault Dan Egli
[not found] ` <3D18E115.9B5981C1@microsoft.com>
2002-06-26 0:56 ` SegFault Dan Egli
2002-06-26 1:02 ` Dan Egli [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 1:56 SegFault Stas Sergeev
2002-06-26 3:11 ` SegFault Dan Egli
2002-06-26 3:14 ` SegFault Dan Egli
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='00cc01c21cad$22704c20$4600000a@FlagShip' \
--to=dan@shortcircuit.dyndns.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