🚀 go-pugleaf

This is the second posting - I didn't see any replies the first time :-(

I'm trying to write a Windows 3 application which needs to interface to a
DOS TSR which communicates via an interrupt. Everything works fine in real
mode, but I get UAEs and reboots in both standard and 386 enhanced mode.

The code segment that's causing the trouble:

	union	REGS	InRegs;
	union	REGS	OutRegs;
	struct	SREGS	SegRegs;
	HANDLE		hBuffer;
	LPSTR		lpBuffer;

	InRegs.h.ah = 11;
	InRegs.h.al = 1;
	InRegs.x.dx = FP_OFF(lpBuffer);

	hBuffer = GlobalAlloc(GHND,512L);
	lpBuffer = GlobalLock(hBuffer);
	InRegs.x.di = FP_OFF(lpBuffer);
	SegRegs.es = FP_SEG(lpBuffer);

	int86x(0x7f,&InRegs,&OutRegs,&SegRegs);

I've done a lot of RTFM-ing, but to no avail (at least, the problem isn't
solved). I didn't write the TSR, so it's difficult to get changes done
there (I don't have the source).

My suspicions are that lpBuffer above is a 'selector' (whatever that is)
rather than a true, _far address, and when the TSR (assembler) uses the
ES:DI register pair, some sort of protect trap takes place.

Any ideas on how to solve this? Do I need to spend $500 on the DDK and write
a special device driver? Please help - any comments would be appreciated;
if you did respond via a posting last time, please respond again. My upstream
site lost some news just about the "right" time :-(.

Thanks in advance!

-- 
Dave Lockwood          dave@mgc.uucp                 G4CLI@GB7DCC._199.GBR.EU
Head of Technology           ...!uunet!mcsun!ukc!mgc!dave
----MG Computer Systems Ltd, PO Box 50, Doncaster, DN4 5AW +44-302-738770----