Am Mittwoch, 23. Oktober 2002 18:15 schrieb Bart Oldeman:
> On Wed, 23 Oct 2002, Jan Kandziora wrote:
> > Tracing the program's system calls with "dosemu -Da" showed me it tries
> > to detect an EMM by opening the 'files' EMMXXXX0, EMMQXXX0, $MMXXXX0,
> > QMMXXXX0, EMMXXXQ0 and QEMM386$. See the trace snippet below.
> >
> > INT21 (0) at 12bb:7ff7: AX=3d00, BX=0000, CX=ffef, DX=100a, DS=1b5d,
> > ES=f800 INT21: open file "EMMXXXX0"
>
> I solved this issue only recently in dosemu-1.1.3.3 and later. EMMXXXX0 is
> the name of the device, however previous dosemu's did not recognize it as
> a device name.
> In earlier versions you could quickly hack around the issue by adding
> EMMXXX0 to the list of reserved names ("CON", "AUX" etc) in
> src/dosext/mfs/mangle.c. The newest DOSEMU's walk the DOS device driver
> chain to find out which names correspond to devices which is a better way
> to do this IMHO.
I was using 1.0.2. However, I have tried it with MS-DOS instead of FreeDOS a
few minutes ago and "copy EMMXXXX0 con:" actually worked instead of giving an
error message "Cannot copy 'C:\CON\EMMXXXX0' to itself".
I looked at the trace output while running the accounting software and it
also worked.
*** But, bad luck, the program now wants to use the VCPI functions :(
The program's 'tech documentation' says, it also works with XMS or DPMI, so I
will use that instead. Does the "ems.sys" have to be loaded in these cases?
If yes, I will be in trouble.
Anyway, this #/&��(* piece of software seems to be good for testing DOSEMU's
features ;)
Thanks
Jan
-
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
