I'm not sure why this happens - jnext.ocx is the ActiveX control that
communicates with the extension dlls when Internet Explorer is used.
IE uses the the unique id (GUID) of the ActiveX from the Web page and
then Windows uses this id with the help of the registry to lookup the
path from which to load the ActiveX control (standard ActiveX behavior).
When jnext.ocx is loaded by IE, it then uses a relative path to load all
the jnext extension dll files, so if your directory structure is the
same there shouldn't be a problem.
In order to change the path of jnext.ocx it should be registered with
Windows, but this should be done automatically by the build process.
Another method of registering the ocx is using Start->Run... and then
typing: regsvr32 <path of jnext.ocx>
Another possibility is that the relative path to the JNEXT extension dll
files that is used in the source code you have is not the same as the
one used in the Windows setup. In the file
jnext-core\common\nativelogic.cpp locate the following comment:
// Linux NPAPI or Windows ActiveX
and put a breakpoint in the line below it to see what path is actually
being used when IE loads the jnext.ocx control.
hope this helps
Amnon
> ------------------------------------------------------------------------
> [广告] 金秋最关注楼盘-房不胜房
> <
http://popme.163.com/link/003985_1010_7027.html>
> >