From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Egli" Subject: Re: SegFault Date: Tue, 25 Jun 2002 19:02:22 -0600 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <00cc01c21cad$22704c20$4600000a@FlagShip> References: <005301c21c84$bc9f1c00$4600000a@FlagShip> <3D18E115.9B5981C1@microsoft.com> <005701c21cac$55a19280$4600000a@FlagShip> Mime-Version: 1.0 Content-Transfer-Encoding: 7BIT Return-path: List-Id: Content-Type: text/plain; charset="us-ascii" Cc: linux-msdos@vger.kernel.org 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" To: Cc: 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" > To: "Dan Egli" > 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 : 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 >