Problem with 2021 vDos

[steve]

Hi Jos,

I am experiencing a problem with the new version. I have copied the CONFIG.TXT and AUTOEXEC.TXT from 2019 version but my program causes an Unhandled Exception 0D under the 29/05/2021 version (works perfectly under 2019).

(I have had to REM out the WINDOW setting for the time being.)

CONFIG.TXT:
<QUOTE>
REM C:\VDOS-21\CONFIG.TXT

REM WINDOW = 18,1100:0

MOUSE = ON

LPT1 = SEL:"\\SIGMADELTA-PC\HP" RAW
LPT2 = SEL:"\\SIGMADELTA-PC\HP" RAW
LPT3 = SEL:"\\SIGMADELTA-PC\HP" RAW
<UNQUOTE>

AUTOEXEC.TXT:
<QUOTE>
REM C:\VDOS-21\AUTOEXEC.BAT

REM ---------------------- 11-JUL-21

USE D: D:\
USE E: E:\
USE F: F:\
USE O: O:\
USE P: P:\
USE S: E:\DRIVE-S
USE L: E:\DRIVE-L
USE U: E:\DRIVE-U

E:
CD OPS

CLS

O:\OPS-EXES\OPS-516J SVR-1
<UNQUOTE>

Any ideas what is happening.

Regards,
Steve.

ScreenShot.bmp (267.49 KB)
.

[steve]

Looks very similar to the problem I experienced with the original 2019 version (see thread dated May 7, 2019 at 2:44pm)

[Jos]

LOL, it’s indeed the same issue as once before.

The offending instruction is again MOV SS:[DI],AL.

The DataEase program relies on this 0D exception to be generated with MOV ES:[DI],AL and DI out of bounds.

vDos however checks for this condition as the segment prefix is already processed. With a change to that code, vDos again incorrectly assumes the segment prefix was ES:.
I always had the remark to this DataEase related testing that it should be moved to another location, at processing the ES: prefix. I’ll do that and send you a corrected vDos this weekend.

Jos