Hi again.
Ok, so now I'm getting a problem where I wasn't having one before.
Aside from the config.sys not being acted upon (apparently), this
one is an exception occuring within a running dosemu session with a
dos app that I've been using for ages and have had no issue.
Brief history: been running this one using an hdimage-based configuration.
After a successful hdimage-based bootup, would do a subst i: c:, and
then an lredir c: linux\fs\dosc, and then would run this app.
The app is a simple inventory program. All of this was fine, and then
I started using dosemu 1.1.99.1 and .2, and transitioned over from
using hdimage to booting straight off my DOS partition by setting
$_hdimage = /dosc/dos (and have also now tried setting it to /dosc;
that didn't change the exception). I've also just installed dosemu 1.2.0,
and that didn't change or fix the exception. Same result.
Current: I boot xdosemu, no issues. Whether I boot with /dosc/dos and
then do a re-redirection of C: to /dosc, or whether I just start in
/dosc with no re-redirection, the rest of this is the same.
I cd into the directory the program is installed in:
cd ppm
then invoke it:
ppm
I get a nice window with the thing running. I then immediately exit using
the program's exit function, and DOS tells me it can't find command.com,
and asks me to specify its correct location. No issue - had been doing
this last night and earlier today, and all was fine.
Then all of a sudden, when I do that, I get the crash. Didn't change
anything on the underlying system - am using linux-2.6.1-mm4, and have
been.
The exception:
ERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=000b88c2 while in vm86 (DOS)
Program=sigsegv.c, Line=162
EIP: 0000:0000992b ESP: 0000:00004608 VFLAGS(b): 00000 01110000 10000011
EAX: 5803a103 EBX: 00008e0b ECX: 0000415e EDX: 0044ffff VFLAGS(h): 00007083
ESI: 00000050 EDI: 00000b00 EBP: 0000b17f DS: 0000 ES: 0005 FS: 0000 GS: 0000
FLAGS: CF SF IF NT RF VM IOPL: 3
STACK: 00 00 00 00 00 26 04 a1 01 26 -> 04 00 00 00 00 01 eb 05 43 3a
OPS : 00 9e e1 00 99 02 00 9e e1 00 -> 63 d7 d8 e1 00 89 97 01 7c 00
63d7 0000:992b arpl di,dx
Aborted
and I have a 39 MEGABYTE boot log from just these few operations (I have
+a turned on for debug)
My config.sys is now empty, and my autoexec.bat simply sets a path.
Any help greatly appreciated. I'd be happy to send along whatever files
anyone wants, including the app that I'm running.
thx,
jbh
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
