If someone is willing to experiment....
You could take the DLLS that the java plugin needs from VACPP and
DLLRNAME them in the Java DLL and the DLL to similar names - XPCO1.
And then the Java plugin would use the VACPP DLLs, and the browser would
use EMX.
I have no idea if this will work.
We are looking at changing calling conventions of things so that they
will be compatible between EMX and VACPP.
Our plan is to switch all public interfaces to _System.
Mike Kaply
IBM
Henry Sobotka wrote:
> Kunihiko Aizawa wrote:
> >
> > This is a trap message:
> > ------------------------------------------------------------
> > 04-07-2001 00:16:42 SYS2070 PID 02da TID 0001 Slot 00b8
> > F:\WARPZILLA-EMX\BIN\MOZILLA.EXE
> > NPOJI6->XPCOM.__dt__13nsCOMPtr_baseFv
> > 127
> > ------------------------------------------------------------
>
> Definitely incompatibility between the plug-in DLL and EMX xpcom.dll.
>
> h~
