Xref: news-dnh.mv.net comp.os.msdos.djgpp:3653 Path: news-dnh.mv.net!mv!barney.gvi.net!news.sprintlink.net!datalytics!news.ahc.ameritech.com!news.heurikon.com!daffy!uwvax!uwm.edu!newsfeed.internetmci.com!news.sesqui.net!rice!news!sandmann From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: V2 questions Date: Mon, 04 Dec 1995 08:59:49 CST Organization: Rice University, Houston, Texas Lines: 16 References: <49uj8t$hk0 AT news DOT cea DOT fr> Reply-To: sandmann AT clio DOT rice DOT edu Nntp-Posting-Host: clio.rice.edu To: djgpp AT sun DOT soe DOT clarkson DOT edu Dj-Gateway: from newsgroup comp.os.msdos.djgpp > 1. V2 is dpmi-compliant, but it is possible to make and use DLLs like in > well-known dpmi servers (windoze...) ? You can make DXE's with V2, which are a very simple form of dynamic executable code (used by EMU387). I believe a more extensive DLL package will get released eventually, too. But you can't use Windows DLLs. > 3. I found some code in the tests directory about loading a second program > in memory (V2load() function) and jump to it. Is this only a test or this > feature will stay in the final draft ? This feature is used by the debuggers (and the V2 version of "go32") and will be in the final release. You must use -ldbg to link this routine. It's on my (too long) list of things to do to either enhance this routine to be able to load V1 coff images also or to write a v1load subroutine to do this also.