Bug in the latest version

DISCUSSION Stas Sergeev 4 participants 9 messages Oct 27, 2002 – Oct 28, 2002

lore

Share & tools

lore

Stas Sergeev

author

2002-10-27 20:30 UTC #0 lore raw

Hello.

Quoted 6 lines · Lars BjÛrndal

After starting dosemu:
c:\wp51\wp
exit wp
c:\wp51\wp
Then, Dosemu exits with an error message.
What can we do with this problem?

What can we do to reproduce this problem,
that is the question...
Btw, wp.exe is exepack'ed. To my memory
exepack was a constant source of troubles
("Packed file corrupt" and the like things).
I would suspect it also here.
Does it help if you unpack wp.exe before
starting?

-
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

Hartmut Figge

2002-10-27 20:53 UTC #1 lore raw

[Stas Sergeev]:

Quoted 3 lines

Btw, wp.exe is exepack'ed. To my memory
exepack was a constant source of troubles
("Packed file corrupt" and the like things).

That reminds me of old days, when some programms refused to work. Looking in the folder, in which ancient batch files resides, shows e.g. push.bat, which contains the line 'loadfix push'.
That cured the problem with the 'corrupte file' and was the only way, to use that game. Full name was pushover, IIRC.

Perhaps 'wp' could be tested with 'loadfix'.

Signature · 1 line

hafi

Lars Bjørndal

2002-10-27 21:08 UTC #2 lore raw

How do I unpack the wp.exe-file?

I've tried "loadfix c:\wp51\wp.exe". Doing this command two times, results in the same error.

Quoted 23 lines · Hartmut Figge

[Stas Sergeev]:
Quoted 3 lines
Btw, wp.exe is exepack'ed. To my memory
exepack was a constant source of troubles
("Packed file corrupt" and the like things).
That reminds me of old days, when some programms refused to work. Looking in the folder, in which ancient batch files resides, shows e.g. push.bat, which contains the line 'loadfix push'.
That cured the problem with the 'corrupte file' and was the only way, to use that game. Full name was pushover, IIRC.
Perhaps 'wp' could be tested with 'loadfix'.
cu
Signature · 6 lines
hafi

-
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

Signature · 7 lines

Lars Bjørndal <[email protected]>
Storetveitåsen 15, 5067 Bergen.
Tlf.: 55 28 87 55  Mobil: 958 37 537  Telefaks: 55 28 40 67
-
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

Bart Oldeman

2002-10-28 05:43 UTC #3 lore raw

Quoted 1 line · Lars Bjørndal

How do I unpack the wp.exe-file?

try this:
http://www.mirror.ac.uk/sites/ftp.simtel.net/pub/simtelnet/msdos/execomp/unp411.zip

I don't completely understand the log so I couldn't reply anything useful so far. The last lines of your log look like this:

INT21 (0) at c000:1508: AX=3300, BX=0001, CX=0000, DX=0001, DS=c000, ES=c000 int 0x21, ax=0x3300
DO_VM86, cs=0133:109e ss=c000:00f4 f=00033002
ax=3300 bx=0001 ss=c000 sp=00f4 bp=0000

           cx=0000 dx=0001 ds=c000 cs=0133 ip=109e
           si=13fb di=0162 es=c000 flg=00033002
RET_VM86, cs=c000:c009 ss=c000:00ee f=000b3217 ret=0x1
ax=8f11 bx=bf06 ss=c000 sp=00ee bp=0000
           cx=2352 dx=0001 ds=09e8 cs=c000 ip=c009
           si=e451 di=8208 es=c000 flg=000b3217
PIC:   0  32 00000000 fffafff9 00000000 Activate ++ dos time to 176073668
DO_VM86,  cs=c000:c00a ss=c000:00ee f=000b3217
ax=8f11 bx=bf06 ss=c000 sp=00ee bp=0000
           cx=2352 dx=0001 ds=09e8 cs=c000 ip=c00a
           si=e451 di=8208 es=c000 flg=000b3217

SIGILL while in vm86()
ERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=00000000 while in vm86 (DOS)

Program=sigsegv.c, Line=202
EIP: c000:0000c3cf ESP: c000:000018e2 VFLAGS(b): 00000 00110010 00000110
EAX: 00006f04 EBX: 0000a0aa ECX: 0000f16a EDX: 00000000 VFLAGS(h):
00003206
ESI: 00008f79 EDI: 00008208 EBP: 0000e0e2 DS: 09e8 ES: 372a FS: 0000 GS:
0000
FLAGS: PF IF RF VM VIF IOPL: 3

essentially the PIC is the last thing handled before the crash and Stas knows the PIC better than I do. What looks suspicious (though maybe it might be completely logical to the DOSEMU PIC experts) is that
a) the DOS time is the same as in the previous PIC call.
b) IP is increased by 1 (c000:0009->c000:000a) for no apparent reason.

Namely, the PIC call before the one above does this:

RET_VM86, cs=fdc8:6c52 ss=0133:0916 f=000b3286 ret=0x2f02 ax=111b bx=03c0 ss=0133 sp=0916 bp=0444

           cx=0000 dx=3601 ds=0133 cs=fdc8 ip=6c52
           si=00b0 di=00b0 es=036a flg=000b3286

Do INT0x2f: Using caller_function()
INT2F at fdc8:6c52: AX=111b, BX=03c0, CX=0000, DX=3601, DS=0133, ES=036a
MFS: Entering dos_fs_redirect, FN=1B
.. bunch of MFS stuff

PIC:   0  32 00000000 fffafff9 00000000 pic_itime[1]= 176096631
PIC:   0  32 00000000 fffafff9 00000000 pic_sys_time set to 176073668
PIC:   0  32 00000000 fffafff9 00000000 Activate ++ dos time to 176073668

DO_VM86, cs=fdc8:6c52 ss=0133:0916 f=000b3287

Bart

-
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

Lars Bjørndal

2002-10-28 21:43 UTC #4 lore raw

Thank you! Now, wp.exe works perfect!
Lars

Quoted 64 lines · Bart Oldeman

Quoted 1 line · Lars Bjørndal
How do I unpack the wp.exe-file?
try this:
http://www.mirror.ac.uk/sites/ftp.simtel.net/pub/simtelnet/msdos/execomp/unp411.zip
I don't completely understand the log so I couldn't reply anything useful so far. The last lines of your log look like this:
INT21 (0) at c000:1508: AX=3300, BX=0001, CX=0000, DX=0001, DS=c000, ES=c000 int 0x21, ax=0x3300
DO_VM86, cs=0133:109e ss=c000:00f4 f=00033002
ax=3300 bx=0001 ss=c000 sp=00f4 bp=0000
           cx=0000 dx=0001 ds=c000 cs=0133 ip=109e
           si=13fb di=0162 es=c000 flg=00033002
RET_VM86, cs=c000:c009 ss=c000:00ee f=000b3217 ret=0x1
ax=8f11 bx=bf06 ss=c000 sp=00ee bp=0000
           cx=2352 dx=0001 ds=09e8 cs=c000 ip=c009
           si=e451 di=8208 es=c000 flg=000b3217
PIC:   0  32 00000000 fffafff9 00000000 Activate ++ dos time to 176073668
DO_VM86,  cs=c000:c00a ss=c000:00ee f=000b3217
ax=8f11 bx=bf06 ss=c000 sp=00ee bp=0000
           cx=2352 dx=0001 ds=09e8 cs=c000 ip=c00a
           si=e451 di=8208 es=c000 flg=000b3217
SIGILL while in vm86()
ERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=00000000 while in vm86 (DOS)
Program=sigsegv.c, Line=202
EIP: c000:0000c3cf ESP: c000:000018e2 VFLAGS(b): 00000 00110010 00000110
EAX: 00006f04 EBX: 0000a0aa ECX: 0000f16a EDX: 00000000 VFLAGS(h):
00003206
ESI: 00008f79 EDI: 00008208 EBP: 0000e0e2 DS: 09e8 ES: 372a FS: 0000 GS:
0000
FLAGS: PF IF RF VM VIF IOPL: 3
essentially the PIC is the last thing handled before the crash and Stas knows the PIC better than I do. What looks suspicious (though maybe it might be completely logical to the DOSEMU PIC experts) is that
a) the DOS time is the same as in the previous PIC call.
b) IP is increased by 1 (c000:0009->c000:000a) for no apparent reason.
Namely, the PIC call before the one above does this:
RET_VM86, cs=fdc8:6c52 ss=0133:0916 f=000b3286 ret=0x2f02 ax=111b bx=03c0 ss=0133 sp=0916 bp=0444
           cx=0000 dx=3601 ds=0133 cs=fdc8 ip=6c52
           si=00b0 di=00b0 es=036a flg=000b3286
Do INT0x2f: Using caller_function()
INT2F at fdc8:6c52: AX=111b, BX=03c0, CX=0000, DX=3601, DS=0133, ES=036a
MFS: Entering dos_fs_redirect, FN=1B
.. bunch of MFS stuff
PIC:   0  32 00000000 fffafff9 00000000 pic_itime[1]= 176096631
PIC:   0  32 00000000 fffafff9 00000000 pic_sys_time set to 176073668
PIC:   0  32 00000000 fffafff9 00000000 Activate ++ dos time to 176073668
DO_VM86, cs=fdc8:6c52 ss=0133:0916 f=000b3287
Bart
-
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

Signature · 7 lines

Lars Bjørndal <[email protected]>
Storetveitåsen 15, 5067 Bergen.
Tlf.: 55 28 87 55  Mobil: 958 37 537  Telefaks: 55 28 40 67
-
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

Lars Bjørndal

2002-10-27 21:16 UTC #5 lore raw

In reply to Hartmut Figge

I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line "largest executable program size" 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think?
Lars

Signature · 7 lines

Lars Bjørndal <[email protected]>
Storetveitåsen 15, 5067 Bergen.
Tlf.: 55 28 87 55  Mobil: 958 37 537  Telefaks: 55 28 40 67
-
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

Bart Oldeman

2002-10-28 05:32 UTC #6 lore raw

Quoted 3 lines · Lars Bjørndal

I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line "largest executable program size" 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think?

I don't know. Depending on the DOS (Free or not), try mem /f or mem /d and compare the two to find out where the difference is.

Bart

-
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

Lars Bjørndal

2002-10-28 21:41 UTC #7 lore raw

Quoted 6 lines · Bart Oldeman

Quoted 3 lines · Lars Bjørndal
I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line "largest executable program size" 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think?

This problem was caused by that thing that 1.1.3.5 will not use the autoexec.emu. I've replaced it with autoexec.bat now, and then it's ok. Why will not .emu work?

My config.emu's last lines is:

SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p

install=c:\subst.exe i: c:\
install=c:\lredir.exe c: linux\fs/dos

Witn dosemu-1.0.1, it is the autoexec.emu on the new drive c: that is executed.

Lars

Signature · 7 lines

Lars Bjørndal <[email protected]>
Storetveitåsen 15, 5067 Bergen.
Tlf.: 55 28 87 55  Mobil: 958 37 537  Telefaks: 55 28 40 67
-
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

Bart Oldeman

2002-10-28 23:38 UTC #8 lore raw

Quoted 14 lines · Lars Bjørndal

Quoted 6 lines · Bart Oldeman
Quoted 3 lines · Lars Bjørndal
I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line "largest executable program size" 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think?
This problem was caused by that thing that 1.1.3.5 will not use the autoexec.emu. I've replaced it with autoexec.bat now, and then it's ok. Why will not .emu work?
My config.emu's last lines is:

Quoted 7 lines

SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p
install=c:\subst.exe i: c:\
install=c:\lredir.exe c: linux\fs/dos
Witn dosemu-1.0.1, it is the autoexec.emu on the new drive c: that is executed.

Well you can use
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p /k C:\AUTOEMU.BAT and use AUTOEMU.BAT instead of AUTOEXEC.BAT.

The problem with $_emubat, is that while it seems to work using some OS'es, some COMMAND.COM's and some types of AUTOEXEC.BAT it is really a hack and can be confusing. All kinds of weird things were possible such as:

* command.com simply crashing DOSEMU (this is what the FreeDOS command.com did)
* command.com executing autoexec.emu for the first half and autoexec.bat for the second half if the number of estimated "fakes" was not correct.
* you doing "type autoexec.bat" and getting the contents of autoexec.emu.
* potentially deleting or renaming the wrong file.

$_emusys is a hack too, but it's more predictable what the DOS does (only one fake is needed) and it cannot be worked around so easily (only using bootmenu's and keystrokes or a separate boot directory).

BTW if /K doesn't work you can use isemu.com in autoexec.bat:

isemu
if errorlevel 1 goto native_dos
call autoemu.bat
exit
:native_dos

Bart

-
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