Xref:	news2.mv.net comp.os.msdos.djgpp:3460
From:	fnunez AT cs DOT uct DOT ac DOT za (Fabian Nunez)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: dxegen questions
Date:	5 May 1996 07:06:24 GMT
Organization:	University of Cape Town
Lines:	27
Message-ID:	<4mhk1g$8c3@groa.uct.ac.za>
References:	<318872e1 DOT 110404129 AT news DOT webstar DOT net> <318b9699 DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host:	unagi.cs.uct.ac.za
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In <318b9699 DOT sandmann AT clio DOT rice DOT edu> Charles Sandmann <sandmann AT clio DOT rice DOT edu> writes:

>> i stumbled across the example for dxegen. apparently, it is for
>> generating loadable modules (like a dll) but i can't find any
>> documentation about it... where should i look?

>src/dxe/dxegen.doc is the only thing I ever wrote about it - and I
>never enhanced the docs or put them into the info format, sorry.
>I really wrote it for loadable graphics device drivers and emu387
>support, neither which needed I/O, with a goal to have the tiniest
>footprint possible.

I tried to write a loadable VESA 2 module using a DXE and all I got was
segmentation violations.  The code worked fine if statically linked, so
my guess is that DXE's have problems talking to the __dpmi and _go32_dpmi
functions, same as with printf, etc. Any ideas for a workaround, or have I
found a bug? (BTW, I looked at the old '94 version of DLL's for DJGPP V1,
and it allowed for sharing variables and functions with the main executable -
why was this removed from DXE's? it seems like a good idea to me)

Thanks
Fabian
--
Fabian Nunez, Bachelor of Computer Science, University of Cape Town
email:fnunez AT cs DOT uct DOT ac DOT za   web:http//www.cs.uct.ac.za/~fnunez
----------------------------------------------------------------             
"k3wl aRe th3 lAmErz, 4 thEy sh4ll RulE!" - from the ElitE Bible 

- Raw text -