Date: Fri, 20 Sep 1996 08:49:56 +0000
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: wanted : Loadable Module support
To: "Alexander V. Lukyanov" <lav AT video DOT yars DOT free DOT net>
Cc: alaric AT abwillms DOT demon DOT co DOT uk, djgpp AT delorie DOT com
Message-id: <32425AB4.221F@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <199609190800 DOT MAA29992 AT video DOT yars DOT free DOT net>

Alexander V. Lukyanov wrote:
> 
> > You'd need to put some level of debug info in the executables, so as
> > to find them symbols, or change the stub to be a "runtime linker",
> 
> It's better to load runtime linker as a simpler module at runtime.

I agree with this, but I was thinking you would still need a special stub.  The new stub goes 
into protected mode in the usual way, then checks to see if the loader is already present 
(probably via the OEM dpmi extensions, or whatever they're called) and either invokes it with the 
appropriate parameters to load the rest of the program, or loads it from somewhere on the path, 
much the same as the stub does for cwsdpmi.

Of course all the above could be done in a 32 bit stub (written in your favourite language) 
rather than using djasm (though it would only add a few dozen bytes to the stub and save on 
double buffered transfers).

Bill