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' EMM0, EMMQXXX0, $MM0,
> > QMM0, EMMXXXQ0 and QEMM386$. See the tr
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' EMM0, EMMQXXX0, $MM0, QMM0,
> EMMXXXQ0 and QEMM386$. See the trace snippet below.
> INT21 (0) at 12bb:7ff7: AX=3d00, BX=, C
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"
Hello.
Peter Forst wrote:
can someone explain me about the following error-message
Dosemu somehow happened to execute an
invalid code, which caused a GPF in vm86().
The dosemu craches while starting an application from our, via
novell/ipx mapped network drive.
Does this happen when starting a
Hi out there,
can someone explain me about the following error-message when I start the dosemu with
the log-option (-o logfile) ?
The dosemu craches while starting an application from our, via novell/ipx mapped
network
drive.
I've tried it with the dosemu 1.0.2 - 1.1.3-4 with same result (also 0
