From:	Corinne Merry <bmerry AT iafrica DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	DJGPP, DOSEmu and IPX
Date:	Sun, 17 Jan 1999 18:09:31 +0200
Organization:	UUNET Internet Africa
Lines:	36
Message-ID:	<36A20B3B.D8AB5558@iafrica.com>
NNTP-Posting-Host:	196-31-84-143.iafrica.com
Mime-Version:	1.0
X-Trace:	nnrp01.iafrica.com 916589276 1782 196.31.84.143 (17 Jan 1999 16:07:56 GMT)
X-Complaints-To:	abuse AT iafrica DOT com
NNTP-Posting-Date:	17 Jan 1999 16:07:56 GMT
X-Mailer:	Mozilla 4.5 [en] (Win98; I)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi

I'm having some trouble writing an IPX driver in DJGPP 2.01. It seems to
work ok in Real DOS, but under DOSEmu it reports that IPX is not present
even though it is definitely enabled in dosemu.conf.

I have the following code chunk:

int IPXInitialise() {
  __dpmi_regs r;

  r.x.ax = 0x7a00;
  __dpmi_int(0x2f, &r);
  if (r.h.al) return 1;
  return 0;
}

According to Ralf Brown's interrupt list, INT 2F/AX=7A00 should return
0xff in AL if IPX is installed, 0x00 otherwise. Under DOSEmu, debugging
(with RHIDE) reveals that none of the registers in r are changed by the
__dpmi_int call (I didn't check exactly, but I didn't see any change and
AX definitely didn't change). However, if in debug (as in Windows 95,
from the authors of edlin and debug) I assemble two lines to call this
interrupt with AX=7a00 and trace it, then AL is set to 0xff (all of this
is under DOSEmu). So it seems that it is a combination of DJGPP and
either DOSEmu itself or its IPX implementation. Does anyone know what is
causing this / how to work around this? I find DOSEmu a much nicer
environment for programming than Real DOS because I can have
documentation on the other terminals and I can nuke programs that crash.

Please reply by email. My phone calls aren't free so I can't check
newsgroups regularly :-(

Thanks in advance
Bruce

- Raw text -