Re: Problems detecting the EMM

Re: Problems detecting the EMM

[Jan Kandziora]

Am Mittwoch, 23. Oktober 2002 20:59 schrieb Bart Oldeman:
> On Wed, 23 Oct 2002, Jan Kandziora wrote:
> > 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.
>
> Can you type "truename EMMXXXX0" in both DOSes? Which FreeDOS kernel are
> you using, and which command.com?
>
FreeDOS:
C:\>truename EMMXXXX0
C:/EMMXXXX0 

C:\>ver
FreeCom version 0.83 Beta 32 [Dec 03 2001]

I used the "command.com" from the latest FreeDOS "base1" install disk from 
their server.
The "comcom.com" which came with DOSEMU and all the tools based on 
"generic.com" make my dosemu go into an endless loop or simply quit. They 
work on a friend's computer without problems and I haven't investigated in 
this further yet.

MS-DOS:
C:\>truename EMMXXXX0
C:/EMMXXXX0 

C:\>ver
MS-DOS Version 6.22


> > 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?
>
> No. ems.sys is only necessary for EMS. For XMS and DPMI you only need to
> adjust dosemu.conf. VCPI can never be provided by DOSEMU, because VCPI
> needs ring 0 access and ring 0 is (Linux) kernel space.
>
Ok.

By the way, that program gives me a headache. It even breaks with MS-DOS under 
vmware. With another error, of course.

	Jan

Re: Problems detecting the EMM

[Stas Sergeev]

Hello.

Jan Kandziora wrote:
> The "comcom.com" which came with DOSEMU and all the tools based on 
> "generic.com" make my dosemu go into an endless loop or simply quit. 
> They work on a friend's computer without problems and I haven't investigated 
> in this further yet.
You are not the first who observed that so
this worth an investigations.
Please contribute to that bug report
http://sourceforge.net/tracker/index.php?func=detail&aid=605551&group_id=49784&atid=457447
if you are going to hunt this bug because
there is already some usefull info about it.

Re: Problems detecting the EMM

[Jan Kandziora]

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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Problems detecting the EMM

[Jan Kandziora]

Hi,

I have problems with an accounting software for a hotel.
It refuses to run under DOSEMU but fails reporting a missing EMM. I have 
loaded "ems.sys" within "config.sys", and xms, ems, and dpmi memory settings 
in "dosemu.conf" seem ok to me.

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"
int 0x21, ax=0x3d00
INT2F at 003e:ac43: AX=1123, BX=0003, CX=6a99, DX=100a, DS=1b5d, ES=0139
MFS: Entering dos_fs_redirect, FN=23
MFS: selecting drive fn=23 sda_cds=0x1fbaf
MFS: FNX=EMMXXXX0
MFS: dos_fs: build_ufs_path for DOS path 'EMMXXXX0'
MFS: MFS: dos_gen: ufs '/root/dosemu/drives/d/', path 'EMMXXXX0', l=22
MFS: dos_gen: path_to_ufs 'emmxxxx0'
MFS: dos_fs: build_ufs_path result is '/root/dosemu/drives/d/emmxxxx0'
MFS: no drive selected fn=23
MFS: Finished dos_fs_redirect
int 0x2f, ax=0x1123
INT2F at 003e:6ae5: AX=1116, BX=6a99, CX=0000, DX=1000, DS=0139, ES=0139
MFS: Entering dos_fs_redirect, FN=16
MFS: selecting drive fn=16 sda_cds=0xfcb8
MFS: selected drive 3: /root/dosemu/drives/d/
MFS: (mode = 0x0000)
MFS: (sft_open_mode = 0x0000)
MFS: Open existing file D:\HOTEL2\EMMXXXX0
MFS: dos_fs: build_ufs_path for DOS path 'D:\HOTEL2\EMMXXXX0'
MFS: MFS: dos_gen: ufs '/root/dosemu/drives/d/', path '\HOTEL2\EMMXXXX0', l=22
MFS: dos_gen: path_to_ufs '/hotel2/emmxxxx0'
MFS: dos_fs: build_ufs_path result is '/root/dosemu/drives/d/hotel2/emmxxxx0'
MFS: find_file(/root/dosemu/drives/d/hotel2/emmxxxx0)
MFS: find file /root/dosemu/drives/d/hotel2/emmxxxx0
MFS: scan_dir(/root/dosemu/drives/d/hotel2,emmxxxx0)
MFS: scan_dir gave emmxxxx0 FALSE
MFS: find_file(): no match: /root/dosemu/drives/d/hotel2/emmxxxx0
MFS: find_file gave /root/dosemu/drives/d/hotel2/emmxxxx0 0
MFS: open failed: '/root/dosemu/drives/d/hotel2/emmxxxx0'
MFS: Finished dos_fs_redirect
INT21 (0) at 12bb:7ff7: AX=3d00, BX=0000, CX=ffef, DX=1013, DS=1b5d, ES=f800
INT21: open file "EMMQXXX0"
int 0x21, ax=0x3d00

etc. etc.

Discovering that I checked how the DOSEMU "ems.sys" calls himself: It would 
respond to " EMS", but not on anything of the above :(

My question now: Is it possible to change the name the "ems.sys" driver 
reports?

Any help appreciated

	Jan

Re: Problems detecting the EMM

[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.

Bart